Can't connect to Sql 2005 after sysprep
I don't know how many of you out there actually uses differentiating disks to create your libraries of virtual machines to do testing and development, so I can't gauge how useful this post would be.
I have a library of virtual machines all properly sealed up using sysprep. From windows 2003 base, to sharepoint 2003 base. Any technology I get to work on, I always try to keep a base machine so that I can create new environment to test new stuff with just a few clicks. I'm sure you know by now Sql 2005 just launched recently, so I went to build a base system with Sql 2005 and some other server product. As usual, I sysprep it and make the virtual harddisk read only. Then I create a differentiating disk, and start up the machine.
I thought it would work, like sql 2000, but instead, I got this error message.
"A connection was successfully established with 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: 233)"
I couldn't find help in Microsoft managed newgroup, and I keep asking around, since sysprep helped me save lots of time especially when starting new projects. Finally Sukhdev, SQL MVP and Singapore Sql Usergroup lead helpped me solve the problem. When you install SQL 2005, make sure that the server is not started before you sysprep the machine. Once you start up the differentiated versions of the base machine, do whatever machine renaming before starting SQL 2005.