February 2010 Entries
If you’ve worked with SQL Server prior to the 2005 release you’ve seen the Service Manager. It was a taskbar tool that let you quickly stop and start SQL Server Instances and Services without having to load the SQL Server Enterprise Manager or the Services MMC. Honestly, I hadn’t used it in ages but this morning I wanted to find and stop all SQL Server instances on a development server in order to save on memory usage and host a Virtual Machine. At that point I remembered that it didn’t exist in the SQL Server 2005 or 2008 versions. ...
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...
Today, while working on some unit tests I encountered an issue I had not encountered before. After setting up a testing fixture and a base test(s) on a project, the test(s) failed to load in the NUnit GUI Test Runner.
An NUnit dialog stated:
Not a Test Assembly
The assembly was not built with any known testing framework
At first the thought was that the issue might be with the version of NUnit framework. Perhaps it was a mismatch with the GUI Runner version? This was not the case. This was a new install on a server that had never...
Recently while working on a client SharePoint project I encountered the following error code and message while executing a CAML update statement against a list: <Results xmlns=\"http://schemas.microsoft.com/sharepoint/soap/\"><Result ID=\"1,Update\"> <ErrorCode>0x81020014</ErrorCode> <ErrorText>One or more field types are not installed properly. Go to the list settings page to delete these fields.</ErrorText><z:row ... xmlns:z=\"#RowsetSchema\" /></Result></Results>
Frankly, the error message wasn't very helpful and I didn't see the issue right away but then I saw it -- I had used the wrong internal column name. The actual internal name in this case had a trailing 1 at...