Skip to main content

SharePoint 2013 - .master file not generated from masterpage html

Created a master page from seattle.html and uploaded it via a Sandbox solution. But the master page file .master was not generated automatically.

Saved the file manually and the .master file was generated.

Tried updating the file with powershell, still masterpage .master file not generated.

Noticed the following properties and the value was set to true for a successful conversion.

<mso:htmldesignconversionsucceeded msdt:dt="string">False</mso:htmldesignconversionsucceeded>


<mso:htmldesignstatusandpreview msdt:dt="string"></mso:htmldesignstatusandpreview>

used powershell to set the value to false and updated the file. The .master file was generated successfully.

Wrote a small powershell snippet as part of deployment to ensure that .master is generated before setting the masterpage.



Labels:

Comments

Post a Comment

Popular posts from this blog

SharePoint 2013 workflow : The server was unable to process the request

Here, I received another SharePoint 2013 workflow error. This time the workflow was not able to send emails and the following error was being shown Retrying last request. Next attempt scheduled in less than one minute. Details of last request: HTTP Unauthorized to http://sitename/_vti_bin/client.svc/web/lists/getbyid(guid'guid') Correlation Id: id Instance Id: id Fortunately I came across this post which gave me the answer http://sharepoint.stackexchange.com/questions/89101/failed-to-retrieve-the-com-class-factory-for-component-with-clsid-sp-sprequest Solution 1: In InetMgr, go to advanced settings for Security Token Service Application Pool and change "Load User Profile" to true. Recycle application pool. Reason 2 and Solution 2 : There could be another reason for this error. The workflow authentication can fail if the user executing the workflow (this will be the user initiating the workflow) is given permission through active directory group and the co
4 comments
Read more

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
11 comments
Read more