Can't connect to sql server 2005 after sysprep

I've installed sql2005 on win2k3, running on virtual pc... I can connect to
the sql server using sql server management studio... Because I'm building
base environment for testing, I seal the machine using sysprep. When I start
a new machine, I get this error...
"A connection was successfully established with the server, but then an
error occurred during the pre-login handshake. (provider: Shraed Memory
Provider, error: 0 - No process is on the other end of the pipe.) (Microsoft
SQL Server, Error: 233)
Any idea how to solve this?
Best Regards,
Kit Kai
MVP (asp.net)
SgDotNet Council Member
Visit us @. http://www.sgdotnet.org
My Blog: http://community.sgdotnet.org/blogs/kitkaiHi Loke,
Welcome to use MSDN Managed Newsgroup!
From your descriptions, I understood you setup a machine with SQL Server
2005 and after using sysprep (something like GHOST, am I right?), the SQL
Server report the error message 233. If I have misunderstood your concern,
please feel free to point it out.
Since you are using sysprep, does the machine name remains the same? Please
perform the steps below and let me knwo whether it resolved your issue.
1. Open SQL Server Surface Area Configuration
Click 'Surface Area Configuration for Services and Connections'
Extend Database Engine and make sure Remote Connections is enabled for
both TCP/IP and named pipes.
2. Restart the SQL Server
3. Make sure the Firewall is configured correctly.
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.|||Yup... You understood my problem perfectly.
In this case, the machine name remains the same, but this would be the only
case where the machine name remains the same... Basically, this setup will
be used as a base for other differentiating disk to build upon.
I've followed your steps, but the problem still remains. Firewall shouldn't
be the cause, since I'm still access sql using the same machine...
Best Regards,
Kit Kai
MVP (asp.net)
SgDotNet Council Member
Visit us @. http://www.sgdotnet.org
My Blog: http://community.sgdotnet.org/blogs/kitkai
"Michael Cheng [MSFT]" <v-mingqc@.online.microsoft.com> wrote in message
news:7nDahdh%23FHA.1236@.TK2MSFTNGXA02.phx.gbl...
> Hi Loke,
> Welcome to use MSDN Managed Newsgroup!
> From your descriptions, I understood you setup a machine with SQL Server
> 2005 and after using sysprep (something like GHOST, am I right?), the SQL
> Server report the error message 233. If I have misunderstood your concern,
> please feel free to point it out.
> Since you are using sysprep, does the machine name remains the same?
> Please
> perform the steps below and let me knwo whether it resolved your issue.
> 1. Open SQL Server Surface Area Configuration
> Click 'Surface Area Configuration for Services and Connections'
> Extend Database Engine and make sure Remote Connections is enabled for
> both TCP/IP and named pipes.
> 2. Restart the SQL Server
> 3. Make sure the Firewall is configured correctly.
>
> Sincerely yours,
> Michael Cheng
> Microsoft Online Partner Support
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ========================================
=============
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>|||Hi Kit,
This is a very strange issue. Unfortunately, I am afraid it is not
supported to install SQL Server 2005 like this due to license issues. Would
you please completely uninstall SQL Server 2005 and then reinstall it to
see whether you could login SQL Server 2005 this time?
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are always here to be of
assistance!
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.|||Found the solution with Sukhdev's help.
Posted it @.
http://community.sgdotnet.org/blogs...2/13/23344.aspx
Best Regards,
Kit Kai
MVP (asp.net)
SgDotNet Council Member
Visit us @. http://www.sgdotnet.org
My Blog: http://community.sgdotnet.org/blogs/kitkai
"Michael Cheng [MSFT]" <v-mingqc@.online.microsoft.com> wrote in message
news:Tx%23OqCx%23FHA.3764@.TK2MSFTNGXA02.phx.gbl...
> Hi Kit,
> This is a very strange issue. Unfortunately, I am afraid it is not
> supported to install SQL Server 2005 like this due to license issues.
> Would
> you please completely uninstall SQL Server 2005 and then reinstall it to
> see whether you could login SQL Server 2005 this time?
> Thank you for your patience and cooperation. If you have any questions or
> concerns, don't hesitate to let me know. We are always here to be of
> assistance!
>
> Sincerely yours,
> Michael Cheng
> Microsoft Online Partner Support
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ========================================
=============
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>|||Hi Kit,
Thanks so much for the update and share this invaluable experience here. I
believe other communities will also benefit much from this.
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.