For the second time in the recent past, I’ve run into unexpected date results from SharePoint. The first time it happened with the FAST search engine and yesterday I encountered it on a second project while dealing with a simple list.
Basically, when a user submits a date in a SharePoint Date and Time field (think list field), SharePoint stores it in UTC. If SharePoint handles the rendering of that date then users never notice what happens behind the scene. However, if we have to do something with that SharePoint DateTime field (like synchronize to a database) and we ask for...
One of our clients requested our assistance after MOSS a infrastructure update failed. As a result, our client’s intranet site collection had now completely lost both its search box and the Search Center site was now hidden. Although it was possible to navigate to the Search Center site through the “View All Site Content” link, an error occurred when displaying search results. Of course, the error was a standard SharePoint error message that didn’t explain what was really happening. In addition, the Farm’s Search Settings page in the Central Administration SSP also threw an “Unexpected Error”.
After changing the appropriate web.config...