Pages

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.