Follow along:

1. Create a new site template from SharePoint Designer.  Doesn’t really matter what the site template is for or what options you choose (based on my experience).
2. Go into SharePoint and create a new site based on the new custom Site Template.
3. Note that your top navigation bar (the global navigation) should now have a “Home” tab, and an “Error” tab.
4. Click refresh.
5. Your top navigation bar now appears as normal!

I’ll chalk this one up as a “feature”.

One of our SharePoint servers at work was updated with the most recent round of security patches the other day.  Unfortunately, the result of this update was the inability to login to the SharePoint Portal from the server, and the search crawler not being able to access the site.

After some significant research on the matter I came across http://support.microsoft.com/kb/896861 which indicates that an IIS website that is using Integrated Windows Authentication and the URL is different from the computer name, will result in a 401.1 error.  The fix is to add the other names of the computer into a registry key and restart IIS.  After following the instructions in the knowledge base article I was able to login to the site from the server, and the search crawler was once again able to crawl the content.

Just to see if it would work, I decided the other day to pair my Motorola HS3 Bluetooth Headset with my Lenovo Thinkpad T60.

I have to admit that I am really digging using my headset with Google Talk and Messenger. I like having the option to switch into a voice chat from IM but maintain a form of privacy by using the headset. I think I’ll leave my headset paired with my computer and leave my phone out of it!

UPDATE:  Okay, I paved my laptop the other day and installed Vista, now I no longer have a working Bluetooth headset!  Apparently the Bluetooth stack in Vista does not include the drivers to support a Bluetooth headset :-(.

If you are using SPS 2003 or MOSS 2007 with a SQL Server 2005 box that does not have SP2 installed, you may discover that your crawls never complete.  There is a bug in SQL 2005 that if you have a Reindex Maintenance Plan it clears some attributes of the SharePoint indexes when it reindexes which in turn breaks the search functionality of SharePoint.  Long story short, consider SP2 for SQL 2005 to be a system requirement of SharePoint.  More information available here:  http://support.microsoft.com/kb/930887