July 9, 2007 at 4:30 pm
I'm getting ready to upgrade from SS 2000 to SS 2005 and am having problems with the SQL server 2005 upgrade advisor analysis wizard. I'm running the developer's edition of SQL Server. I do most of the SS development on my local machine and then upload changes to my client's site. My client has indicated that they want to upgrade everything next week (short notice!). They're taking care of most of the details, but I need to make sure that all the stored procedures, etc. that I've been working on will run ok in 2005.
I can't seem to get past the Connection Parameters screen. I get the following message whether I try Windows Authentication or SQL Server Authentication.
"Unable to connect to server. Reason: An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: TCP Provider, error: 0 - A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.)"
I don't have SQL Server 2005 installed yet. I checked the SQL Server Network Utility and do have TCP/IP and Named Pipes enabled.
I'm stumped. Any ideas of how I might get the Upgrade Advisor to work?
Thanks!
July 9, 2007 at 11:29 pm
Strange!
Are you sure that you are trying to run SQL upgrade advisor to SQL 2000 instance?
July 10, 2007 at 12:09 am
Nothing strange in it.
If you use SQL Native Client, this message is common. I guess you are confused with "SQL 2005" in error message.
Please check SQL Error Logs and make sure SQL is listening on those protocols
July 10, 2007 at 3:27 am
Could you post us the error part from the error log file when you try to access using advisor. That might give more details than this.
Cheers,
Sugeshkumar Rajendran
SQL Server MVP
http://sugeshkr.blogspot.com
July 10, 2007 at 12:24 pm
You are running Upgrade Advisor as a prudent way to forecast issues on switch to 2005 (good for you!). Your client gave you a week's notice, because you built SPs for them, presumably for an application, no? Did you ask if they ran UA on their end? If so, can they share the report with you? If not, then who is doing the conversion for them?
You could always go into brute force mode, install 2005 on your own system and port the database files over and test on your own system. I believe you can get a trial copy that will support Stored Procedures.
Otherwise, we will need more diagnostic information to better guide you to an effective resolution. Specific error messages, at a minimum.
July 12, 2007 at 1:12 am
Any chance there is a named instance that needs to be referenced? I forget that all the time...
Todd Carrier
MCITP - Database Administrator (SQL 2008)
MCSE: Data Platform (SQL 2012)
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply