Small Talk - Blog by Houratious Albert

Some of you might have noticed during troubleshoot that the SharePoint web services root is in a stopped state. This is quite normal. The error is usually somewhere else.

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.

During troubleshooting a css where the text wrap was just not working even though the style had word-wrap:break-word included. Later figured that there was another css property which was preventing it from working. Added this to style and it started working. white-space: normal;

From an elevated powershell, run the following. Import-Module ServerManager Get-WindowsFeature Add-WindowsFeature RSAT-AD-PowerShell Restart is not required. To import the module, use : Import-Module ActiveDirectory  

I had an issue with a javascript function being called twice on document ready. Finally figured that I had included the script at two locations. Best way to figure this out is to simply search in page view source to see if the file is included twice.