Skip to main content


Showing posts from July, 2014

SharePoint 2010 - Adding user to a group throws error in IE 9

SharePoint 2010 - Adding user to a group throws error in IE 9 System.InvalidOperationException: Namespace prefix 'xsd' is not defined. at System.Xml.Serialization.XmlSerializationReader.ToXmlQualifiedName(String value, Boolean decodeName) at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationReaderDictionaryEntryArray.Read1_Object(Boolean isNullable, Boolean checkType) at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationReaderDictionaryEntryArray.Read2_DictionaryEntry(Boolean checkType) at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationReaderDictionaryEntryArray.Read3_ArrayOfDictionaryEntry() Happens when you force your page to render in IE 9 and higher. There is a detailed discussion here :

Delete office 2013 document cache

Using office 2013 with skydrive and skydrive pro I was getting the following error. An error occurred while accessing the Office Document Cache. a quick startup/shutdown script was created to fix this. cd "C:\Users\ \AppData\Local\Microsoft\Office\15.0" rd OfficeFileCache /s y echo "delete successful" Add to startup and shutdown scripts by opening gpedit.msc

OWA not working after security update

Office web apps for SharePoint 2013 not working after security updates / server patching. After installation of the following security patches, OWA stopped working there by causing issues with SharePoint 2013. Details of ULS logs are provided below. FarmStateReplicator.exe (0x0CD8) Office Web Apps Farm State Error when trying to connect to Farm State Manager service: System.ServiceModel.EndpointNotFoundException: There was no endpoint listening at http:// /farmstatemanager/FarmStateManager.svc that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details. ---> System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress) at System.Net.ServicePoint.ConnectSocketInternal