As was announced yesterday, Service Pack 1 has been released for Commerce Server 2007. This service pack includes support for Windows Vista, the ability to create web application projects in Visual Studio 2005, performance and security enhancements, and a slew of bug fixes.

I have detailed the process for installing SP1 and upgrading your CS sites in the following posts: Commerce Server 2007 Service Pack 1 (SP1) Walkthrough and Commerce Server 2007 Upgrade Wizard (post SP1 install) Walkthrough.

While installing SP1 I encountered a rather strange problem. Let me try to explain how the problem occurred, and what I did to resolve it.

To begin, I decided to upgrade my Commerce Server 2007 virtual machine to SP1. To begin, I did the following:

  1. Followed the steps I detail in my post Commerce Server 2007 Service Pack 1 (SP1) Walkthrough. In fact, these screen shots were taken during this initial installation of SP1.

  2. After I installed SP1, I immediately launched the Upgrade Wizard.

  3. For the most part, I followed the steps outlined in my post Commerce Server 2007 Upgrade Wizard (post SP1 install) Walkthrough. However, instead of upgrading both my StarterSite and CSharpSite, I only upgraded my CSharpSite and then rebooted my machine.

Why did I reboot the machine after only upgrading one site? Well, I’m not exactly sure. Part of me wanted to see what would happen with only one site upgraded, and another part wanted to upgrade one site at a time while rebooting in-between. Regardless, I rebooted after installing only the CSharpSite.

After rebooting, here was my first indication that something was wrong.

At least one service or driver failed during system startup.

So, I immediately went to the Event Viewer. I saw a number of errors involving the SQLSERVERAGENT, Commerce Server, and ENTSSO. Here’s a look at the various errors in the log (the reboot occurred around 10:52 am … some of these other errors were thrown from my playing around before I resolved the problem):

Event Viewer errors

I should note that the system was previously very healthy, as I use this VM all the time while writing the book Professional Commerce Server 2007 for WROX. In fact, I had been using the computer with no problems immediately before installing the service pack.

So, at this point it was clear that:

  1. The SQL Server Agent was no longer able to start-up.

    SQLServerAgent could not be started (reason: Unable to connect to server ‘(local)'; SQLServerAgent cannot start).

  2. Enterprise Single-Sign On (ENTSSO) was also having issues starting because it couldn’t communicate to SQL Server 2005.

    The SSO service failed to start.

    Error Code: 0x800710D9, Unable to read from or write to the database.

  3. Commerce Server was complaining that I hadn’t updated the StarterSite yet (this one is to be expected, as I hadn’t updated it yet):

     Error in Commerce Administration Object : Description - 'The following resources are old. They will not function correctly until they are upgraded:  
     Product Catalog (7.1.0)  
     Marketing (7.0.0)

Obviously, something here is wrong, and SQL Server seemed to be at the heart of it.

The next thing I did was try to connect to SQL Server 2005. Using the SQL Server Management Studio, I tried to login with my Windows credentials. I wasn’t surprised to see that I couldn’t:

A connection was successfully established to the server, but then an error occured during the pre-login handshake. (provider: Shared Memory Provider, error: 0 - No process is on the other end of the pipe.) (Microsoft SQL Server, Error: 223)

A connection was successfully established to the server, but then an error occurred during the pre-login handshake. (provider: Shared Memory Provider, error: 0 - No process is on the other end of the pipe.) (Microsoft SQL Server, Error: 223)" (copied directly from dialog window)

I have never seen this error before, but wasn’t surprised to see that I couldn’t find anything anything on Google or Live (although, hopefully this post will come up in the future). Sure, various iterations of the first part can be found, but nothing seems applicable to this situation.

So, I decide to poke around. What bothered me was that SQL Server (MSSQLSERVER) was running yet I couldn’t connect to it, and the SQL Server Agent (MSSQLSERVER) itself couldn’t start. Even my attempts to manually start the service failed. Here’s a look at SQL Server Configuration Manager:

SQL Server Configuration Manager

Also, I attempted to connect to Commerce Server by running the Upgrade Wizard … it didn’t start, nor did I receive an error. It simply didn’t start.

For some reason, one thing jumped out at me – I was running as LocalSystem rather than NT AUTHORITYNetworkService. Could this have something to do with it?

Not having any other ideas, I changed both SQL Server and SQL Server Agent to “Log on as” the “Network Service” (NT AUTHORITYNetworkService) instead of the LocalSystem account. I then restarted SQL Server 2005 and the SQL Server Agent. Lo and behold, the SQL Server Agent started-up!


A little baffled, but encouraged that I was on track to resolving the problem (even if I don’t understand the root cause), I tried to connect to SQL Server 2005. Sure enough, I was able to login to the database server and interact with the various databases. I also attempted to connect to the Commerce Server 2007 Upgrade Wizard, which immediat ely started with no problems.

Since I wasn’t too confident with the state of the computer (given that some services still weren’t started), I decided to restart the computer. It restarted without a single error, and I was able to run the Upgrade Wizard successfully to upgrade the StarterSite.

At this point I don’t quite know why there was a problem with the LocalSystem account after I installed SP1 for Commerce Server 2007. I intend to do a little more research to look into it.

Have any of you encountered this problem? Can you shed some light on the situation?

Thanks, and I hope this helps!

comments powered by Disqus