SharePoint 2013
Class not registered exception – SharePoint 2013
Retrieving the COM class factory for component with CLSID {BDEADF26-C265-11D0-BCED-00A0C90AB50F} failed due to the following error: 80040154 Class not registered (Exception from HRESULT: 0x80040154 (REGDB_E_CLASSNOTREG)).
http://saiabhilash.blogspot.co.nz/2013/02/class-not-registered-exception.html
Resolution:
The console application is running under 32 bit processor. Just change it to 64 bit.
To do this:
- Right click on Console Application
- Select Properties
- Under Build Tab, change Platform Target to x64
- Rerun the application and hopefully the error should go away now !
Solution: Accessing SharePoint Site or WebApp via Code Returns Null
SharePoint 2013
net stop “SharePoint Server Search”
net start “SharePoint Server Search”
net stop “SharePoint Administration”
net start “SharePoint Administration”
net stop “SharePoint Timer”
net start “SharePoint Timer”
Security Token Service could not activated SecurityTokenServiceApplication/securitytoken.svc/actas’ could not be activated.
1. Type iisreset on command line. Recycle application pool that still keeping wrong information even if your application pool stop and re-start. So, the best solutions is resetting your IIS.
Install SharePoint 2013 with SQL Server 2014, User profile synchronization in SharePoint Server 2013 not starting. (ILM Configuration: Error ‘ERR_CONFIG_DB’)
Install SharePoint 2013 with SQL Server 2014, User profile synchronization in SharePoint Server 2013 not starting. (ILM Configuration: Error ‘ERR_CONFIG_DB’)
ULS Log:
ILM Configuration: Error ‘ERR_CONFIG_DB’.
UserProfileApplication.SynchronizeMIIS: Failed to configure MIIS post database, will attempt during next rerun. Exception: System.Configuration.ConfigurationErrorsException: ERR_CONFIG_DB at Microsoft.Office.Server.UserProfiles.Synchronization.ILMPostSetupConfiguration.ValidateConfigurationResult(UInt32 result) at Microsoft.Office.Server.UserProfiles.Synchronization.ILMPostSetupConfiguration.ConfigureMiisStage2() at Microsoft.Office.Server.Administration.UserProfileApplication.SetupSynchronizationService(ProfileSynchronizationServiceInstance profileSyncInstance).
UserProfileApplication.SynchronizeMIIS: End setup for ‘User Profile Service’.
Tried below:
- Farm account running as local admin on SP server
• Farm account have local logon rights (also verified by logging into the server as the farm)
• Farm user mapped to DBO for the Sync DB (I’m creating the UPS App as the farm user so this is already done, just for the record if I click on properties for the Sync DB dbo user it shows my farm user under Logon Name)
• Attempted to create the UPS via the CA, same issue
• Cleared SP cache (https://spcachecleaner.codeplex.com/)
• Manually starting FIM Sync service
• My SQL server have a named instance. But I tried to make an SQL alias anyway
• Time is in sync on all servers.
• Completely removed the UPS Application & Proxy countless times (Probably over 10-15+ times)
• Rebooted the server countless times
Solution to FIX
I found out that the April 2014 CU contained a fix (http://support.microsoft.com/kb/2760265 )
I Installed the April CU (which took an extremely long time), restarted the server and on first go the service started.
After installing the fixes you need to run the SharePoint 2013 Products Configuration Wizard on each machine in the farm.
You must install Microsoft SharePoint Server 2013 Service Pack 1 before you apply this hotfix package:
P.S: Jun 2014 CU has the full package : http://support.microsoft.com/hotfix/KBHotfix.aspx?kbnum=2817414
