Can't connect with Upgrade Advisor

I'm having trouble connecting the Upgrade Advisor to a SQL 2000 box at a client. Here's the setup:

1> I'm running UA on a Virtual PC image

2> I can run UA against other SQL machines on the same domain

3> I can register and administer the SQL server I'm having trouble with in Enterprise Manager

4> I have SA rights on the SQL box I'm having trouble with.

5> The problem is when entering the server name and clicking "detect," it errors out with "The network path not found (mscorlib)."

6> I've tried server name, FQDN and IP address.

This is a fairly convoluted layout, so there could be a firewall issue that I'm not aware of (but I don't think so).

Any help would be appreciated!

Bob

Bob, have you tried running UA directly on the target server? It shouldn't be a problem unless the OS level on the server doesn't support UA.|||

Hey, Allen. Thanks for the feedback...as we discussed Thursday (but I mention here in case anyone else is interested), I don't want to add the .Net Framework to the server at this point.

Bob

Can't connect to SQL Server 2005 remotly

I am running SQL Server 2005 on Virtual PC.
I can connect to in VPC using SMS if I set server =win03 SQL Server
Authentication
Shimon2 and password
If I go to my host machine I can't connect the same way - time out.
I can see server. I have Team Server running on it and VS has no problem
connecting.
I made sure that Allow Remote Connections to this server is checked.
So what else did I miss?
ThanksA lot of people seem to be missing the fact that many of the versions of SQL
Server 2005 have remote connections disabled by default. Have you checked
the surface area configuration tool to make sure that you have a remote
protocol enabled for the SQL Server itself (as opposed to the server)?
If you do, and are still getting errors, run Profiler on the SQL Server and
trace for logins. That way, you will have at least leveled it down to one
layer.
Let us know how it goes.
--
MeanOldDBA
derrickleggett@.hotmail.com
http://weblogs.sqlteam.com/derrickl
When life gives you a lemon, fire the DBA.
"Shimon Sim" wrote:

> I am running SQL Server 2005 on Virtual PC.
> I can connect to in VPC using SMS if I set server =win03 SQL Server
> Authentication
> Shimon2 and password
> If I go to my host machine I can't connect the same way - time out.
> I can see server. I have Team Server running on it and VS has no problem
> connecting.
> I made sure that Allow Remote Connections to this server is checked.
> So what else did I miss?
> Thanks
>
>|||Hi Shimon,
Thank you for your post and thanks Derrick's suggestion.
Please first confirm you have enable the remote connection in the surface
area configuration tool as Derrick's suggestion.
If you still can not access the sqlserver instance, please do the following
to troubleshoot.
1. Ping the VPC machine to see if you could access it.
2. Telnet the machine on port 1433:
Telnet < machine name> < Port Number >
3. Also, please use the following KB article to troubleshoot the connection
issue:
827422 How to troubleshoot connectivity issues in SQL Server 2000
http://support.microsoft.com/defaul...kb;EN-US;827422
Hope this will be helpful.
Sincerely,
Wei Lu
Microsoft Online Community 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.|||I am not sure what is remote protocol.
I have four protocols in the surface area configuration tool and all of them
are enabled.
But still can't connect. Telnet tells me that it can't connect.
Am I enabling right thing?
Thanks
"MeanOldDBA" <MeanOldDBA@.discussions.microsoft.com> wrote in message
news:C26B8FFD-2912-4DA2-8E08-8880F0527352@.microsoft.com...
>A lot of people seem to be missing the fact that many of the versions of
>SQL
> Server 2005 have remote connections disabled by default. Have you checked
> the surface area configuration tool to make sure that you have a remote
> protocol enabled for the SQL Server itself (as opposed to the server)?
> If you do, and are still getting errors, run Profiler on the SQL Server
> and
> trace for logins. That way, you will have at least leveled it down to
> one
> layer.
> Let us know how it goes.
> --
> MeanOldDBA
> derrickleggett@.hotmail.com
> http://weblogs.sqlteam.com/derrickl
> When life gives you a lemon, fire the DBA.
>
> "Shimon Sim" wrote:
>|||Well
I found this here
http://support.microsoft.com/?kbid=914277&SD=tech
And remove access was enabled. So what do I do now?
Thanks
"Shimon Sim" <shimonsim048@.community.nospam> wrote in message
news:%23QDps4deGHA.5040@.TK2MSFTNGP03.phx.gbl...
>I am not sure what is remote protocol.
> I have four protocols in the surface area configuration tool and all of
> them are enabled.
> But still can't connect. Telnet tells me that it can't connect.
> Am I enabling right thing?
> Thanks
> "MeanOldDBA" <MeanOldDBA@.discussions.microsoft.com> wrote in message
> news:C26B8FFD-2912-4DA2-8E08-8880F0527352@.microsoft.com...
>|||Hi Shimon,
Since you can not telnet to the port, I think you need to check your VPC
configuration and to see do you enable and configure a IP address for it.
And you will need to check the Network configuration.
Please confirm you could telnet the 1433 port and then try to connect to
the SQL Server.
Sincerely,
Wei Lu
Microsoft Online Community 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.

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.

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/kitkai
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.
|||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/.../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.

Cant connect remotely to SQL Express on Virtual Private Server

I've just bought a Virtual Private Server Account because I want to host a number of different ASP.NET sites, each backed by their own SQL database. I've downloaded SQLEXPRE.EXE and SQLServer2005_SSMEE-x64.msi to the server and installed the database engine and Management Studio Express on the VPS.

My problem is that I cannot access the SQLEXPRESS on my server from my local machine. The Management Studio Express cannot get logged in. I've used "Surface Area Configuration Manager" to allow "Local and remote connections" using TCP/IP only. I've used SQL Server Configuration Manager" to enable the TCP/IP protocol. After making these changes I've stopped and started the SQL server - and even rebooted the machine. I've created a login "Remote User" for this access. I've added sqlservr.exe as an exception to the firewall.

What else do I need to do? Is there a simpleton's guide to completing this task?

Did you start the sql server browsing service?

http://support.microsoft.com/default.aspx?scid=kb;EN-US;914277