I recently came across an issue with Internet Explorer 10 that causes problems with a number of web sites. It took a little over a week back and forth with Microsoft support before we were able to finally target it to the browser. I thought it was an issue with a particular clients Office 365 tenant so that left us chasing our tails for a bit.
The problem stems from the way that Internet Explorer 10 handles websites in compatibility mode. Internet Explorer 8 and 9 respected a meta property embedded in the head of the website. Microsoft products like CRM and SharePoint utilized this property to automatically force the page into compatibility mode without any involvement from the user.
<meta http-equiv="X-UA-Compatible" content="IE=8" />
Internet Explorer 10, however, seems to disable compatibility mode by default… a big step forward in terms of Microsoft’s commitment to web standards but a a step backwards when it comes to… well… compatibility. Continue reading →
Just a quick tip here.
You cannot use the Publishing Portal to create root site collections in Office 365. According to Microsoft support this option may be removed in the future as the site collection provisioning process hangs. Continue reading →
We recently had a VERY strange issue with a client. This specifically was a disaster restore where the previous environment was poorly documented. Due to a total hardware failure new hardware was provisioned… and that’s where the fun begins.
We were able to get SharePoint installed and get Reporting Services fully configured in integrated mode but when we went to configure the SSP… nothing. Always stuck in provisioning.
As we drilled down into the issue we realized that NO timer jobs were working. Another symptom that we noticed is that the Timer Job status page was completely blank… no status could be reported on any timer jobs. Continue reading →
Todd Carter over at todd-carter.com has posted his very in-depth findings regarding a pretty significant memory leak in SharePoint 2007. The problem lies around the HttpApplication object and ultimately around the SPHttpApplication object.
For each HttpApplication which is leaked a potential huge number of child references are too rooted and therefore leaked.
The memory leak has proven to be pretty significant for certain clients as you can see below…
After having the customer install the fix I have described here the process which would normally grow to 10 GB an hour and recycle never went above 2.5 GB! And even after taking all servers out of the load balancer and running the entire farm off one WFE the memory never went above 3.3 GB!!
To learn more read the whole post at Todd’s blog.
Microsoft has released an important news announcement regarding a bug with Service Pack 2 that causes the software to go into trial mode that will expire in 180 days after the service pack was installed. There is currently no hotfix for the problem and the best way to solve this issue is to go into SharePoint Central Administration and re-enter your product key.
At this point we are still recommending that customers upgrade to SP2 but to ensure that after their upgrade they re-enter the product key and ensure that the product is no longer in trial mode.
Read more at the SharePoint team blog and follow the detailed steps to re-enter your product key.