Pages

Monday, March 2, 2015

Requested registry access is not allowed in SharePoint 2013

When I try to register SharePoint Service account in SharePoint central admin, got the following error message “Requested registry access is not allowed”.

After Goggled, found that need to provide access to following registry key “HKLM\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\15.0\Secure\FarmAdmin” for the central admin application pool account from one of the

Friday, February 27, 2015

User Agent not available, file operations may not be optimized

I got “Sorry Something Went wrong” error message when adding custom web part in SharePoint 2013 site and also found “User Agent not available, file operations may not be optimized” error message in SharePoint log files.

Resolution:

I have restarted IIS and the issue got fixed.

Wednesday, February 25, 2015

Sharepoint Apps configuration and Yammer Integration with on-premise Sharepoint 2013

The SharePoint 2013 Apps configuration and Yammer integration with on-premise SharePoint 2013 coming Soon in my blog.

Stay Tuned! :)
 

Monday, February 23, 2015

One or more types failed to load. Please refer to the upgrade log for more details

When try to create a site collection, got the below error message in the SharePoint 2013 farm.

“Sorry, something went wrong .One or more types failed to load. Please refer to the upgrade log for more details”

And then found the below exact reason for the above error message in the SharePoint log files

ERROR Exception: Could not load file or assembly 'Microsoft.Data.Edm

Exception: Could not load file or assembly 'Microsoft.Data.OData

To fix this issue, download and install WCF Data Services 5.0 for OData V3 in the SharePoint Server

Download Link: http://www.microsoft.com/en-us/download/details.aspx?id=29306

Monday, February 2, 2015

Some Farm Products and Patches were not Detected in SharePoint 2013

After I installed December 2014 Cumulative update on all the server in the SharePoint 2013 Farm and Ran the SharePoint configuration Wizard in one of the APP server where central admin hosted but I got the following error message “ Error: Some farm products and patches were not detected on this or other servers. If products or patches are missing locally, you must quit this program and install the required products and patches on this server before restarting this wizard

I executed the below SharePoint PowerShell commands to resolve the above error message.

a. Get-spproduct –local

b. (Get-SpServer $env:ComputerName).NeedsUpgrade

c. Then confirm True is returned once you ran the above commands.

Tuesday, January 27, 2015

Failed to configure MIIS post database while provision User profile Synchronization Service

When I was provisioning the User profile Synchronization service in SharePoint 2013, the UPS service got stuck on starting status for more than 4 hours and identified the Failed to configure MIIS post databasein the SharePoint log file.

“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”

For the above issue, found that SQL Native client 2008 R2 didn’t installed on the SharePoint server which is the prerequisite of SharePoint 2013.

After I installed SQL 2008 R2 Native Client on the SharePoint Server 2013 and then able to re-provision the user profile synchronization service successfully.

ILM Certificate could not be created while provisioning UPS in SharePoint 2013

When I was provisioning the User profile Synchronization service in SharePoint 2013, the UPS service started and stopped and identified the “ILM Certificate could not be created: Cert Step 2 could not create” in the Event Log.

clip_image001

Then tried the below fix and worked fine for me.

1. Log in to the SharePoint 2013 server

2. Start-> Run->MMC-> Add/Remove snap-in

3. In the left panel, Select certificate->select computer Account->Next and Finish

clip_image003

4. Expand the certificate tree in the left panel and remove “ForeFrontIdentityManager Certificates from the below three folder locations

a. Personal

b. Trusted Root Certification Authorities

c. Trusted People

clip_image004

5. Once you removed ForeFrontIdentityManager Certificates, then try re-provision the User profile synchronization service.