Had an issue today where a developer was testing a web part that required a user profile, and an exception was being thrown that the user profile did not exist.  We verified in the SSP that the user profile indeed existed, and also used the "stsadm -o sync" command to force a profile synchronization.  However, we discovered that SharePoint was not seeing the actual user name that the user was logged in as, instead SharePoint saw it as "SHAREPOINT\System".  This led us to the following forum thread:

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1195418&SiteID=1

What ended up being the issue is that the developer had configured the SharePoint application pool to run as the same identity that he was logging into SharePoint as.  We changed the configured identity in Central Admin -> Operations -> Service Accounts to use Network Service instead and the issue was resolved.

The other day Tomas Restrepo released a new Visual Studio Color Theme called Distant Shores.  It is a low-contrast theme with a dark background, and I must admit I am a BIG FAN!  Have a look at the following screen shot.  BTW - The font I am using is Damien Guard’s Envy CodeR font that Tomas Restrepo recommends in his blog posting.

Give it a shot!  Your eyes will thank you!

Came in the office today to an issue with a MOSS box that was recently stood up in our lab environment.  The server was configured to do automatic updates, and installed SharePoint updates overnight.  Turns out the upgrade portion of the update failed, and perusing the diagnostic logs revealed the following error:

Cannot start service SPAdmin on computer ‘.’

I came across the following blog posting that ultimately supplied the remedy:

Bill Baer : KB934525 Troubleshooting "Cannot start service SPAdmin on computer ‘.’."

Option #4 took care of things:

• On the machine where psconfig failed to start the SPAdmin service run:

%commonprogramfiles%\Microsoft Shared\Web Server Extensions\12\BIN\psconfig -cmd upgrade -inplace b2b -wait -force

A movement of sorts is afoot in the blogosphere.  Apparently everyone who has a popular blog has seen fit to alter their employment status in the past 6 months:

Joel Oleson:  http://blogs.msdn.com/joelo/archive/2008/03/12/moving-on.aspx

Jeff Atwood: http://www.codinghorror.com/blog/archives/001074.html

Scott Hanselman: http://www.hanselman.com/blog/BlueBadge.aspx

Craig Shoemaker: http://www.dotnetjunkies.com/WebLog/craigshoemaker/archive/2007/11/14/366194.aspx

Simply an observation.  Bizarre.

Found a great new trick today for mounting Virtual PC VHD files as drives within the host operating system.  In the Virtual Server 2005 R2 SP1 installer is a utility called "VHDMount".  If you install Virtual Server you can elect to only install this utility (if you do a custom install).  This will create a directory "[drive]:\Program Files\Microsoft Virtual Server\VHDMount" within it is a file called VHDMount.exe.  This is a command-line utility that you can use to mount your VHD files.  I regularly use a VHD drive that I share with multiple VPC’s that has common development utilities, and being able to populate that drive without having to boot up one of the VPC’s as a big plus.