RE: Upgrade 2000 -> 2005 Timeout period elapsed...

Tech-Archive recommends: Fix windows errors by optimizing your registry

Dear Scott,

Thank you for posting here.

The error message "The timeout period has elapsed prior to the completion
of the operation or the server is not responding" indicates that the
upgrade operation has been time out. We can try adjust the timeout
parameters to do the troubleshooting. Please refer to the steps below:

1. Let's first adjust the Time-out settings on the SQL Server
--------------------------------
1). Open the Query Analyzer
2). Run the following commands and then press F5

sp_configure 'querys waits', 3600
sp_configure 'remote query timeout',3600
Reconfigure

2. Use the Windows Installer Cleanup utility
--------------------------------
1). Please download and install the Windows Installer Cleanup utility from
this link:
http://download.microsoft.com/download/E/9/D/E9D80355-7AB4-45B8-80E8-983A48D
5E1BD/msicuu2.exe

Note: although it is released as a Microsoft Office update, it can be used
to fix Windows Installer.

2). Then, please run it from Start-> All Programs-> Windows Install Clean
Up.
3). Please remove all SQL 2005 components (if exist)

After that, please try to upgrade to the SQL Server 2005 again to see if it
can be successful this time.

If the issue persists, please send all the log files in the following
folder to me at v-adamqu@xxxxxxxxxxxxx

%ProgramFiles%\Microsoft SQL Server\90\Setup Bootstrap\LOG

If anything is unclear in my post, please don't hesitate to let me know and
I will be glad to help.

Have a nice day!

Best regards,

Adams Qu
MCSE, MCDBA, MCTS
Microsoft Online Support

Microsoft Global Technical Support Center

Get Secure! - www.microsoft.com/security
=====================================================
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.

--------------------
| Reply-To: "Scott Townsend" <scooter133@xxxxxxxxxxxxxxxx>
| From: "Scott Townsend" <scooter133@xxxxxxxxxxxxxxxx>
| Subject: Upgrade 2000 -> 2005 Timeout period elapsed...
| Date: Thu, 13 Dec 2007 10:26:36 -0800
| Lines: 27
| Message-ID: <C63AA41E-34C3-465A-947F-9828C8CEE75D@xxxxxxxxxxxxx>
| MIME-Version: 1.0
| Content-Type: text/plain;
| format=flowed;
| charset="iso-8859-1";
| reply-type=original
| Content-Transfer-Encoding: 7bit
| X-Priority: 3
| X-MSMail-Priority: Normal
| X-Newsreader: Microsoft Windows Mail 6.0.6000.16480
| X-MimeOLE: Produced By Microsoft MimeOLE V6.0.6000.16545
| X-MS-CommunityGroup-MessageCategory:
{E4FCE0A9-75B4-4168-BFF9-16C22D8747EC}
| X-MS-CommunityGroup-PostID: {C63AA41E-34C3-465A-947F-9828C8CEE75D}
| Newsgroups: microsoft.public.sqlserver.setup
| NNTP-Posting-Host: 204-145-245-49.enm.com 204.145.245.49
| Path: TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP04.phx.gbl
| Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.sqlserver.setup:3828
| X-Tomcat-NG: microsoft.public.sqlserver.setup
|
| So I was given a SQL 2000 server with a SQL 2000 DBMS installed and some
| wackjob installed the SQL2005 Management Studio/tools/components on it.
|
| So lots of things were broken when trying to upgrade. The SKUUPGRADE=1
| didn't help either.
|
| So I removed all of the SQL2005 stuff I could from the server and Tried
to
| Install SQL 2005 again.
|
| So I get the point where it says Hey there is v8.0 already here, you can
| upgrade, select the default instance, Use either Integrated or SQL
| Authentication and hit next.
|
| I always get the error
| UpgradeAdvisor returned -1
| Error Message: Timeout Expired. The timeout period has elapsed prior to
the
| completion of the operation or the server is not responding. .Net
SqlClient
| Data Provider
|
| I can load up Query Analyzer and connect, I can Connect to the SQL 2000
DBMS
| from another SQL2005 Server.
|
|
| What Gives?
|
| Scott<-
|
|

.

Relevant Pages

  • RE: MSDE to SQL Server
    ... I understand that you want to upgrade MSDE instances ... We can upgrade the instance SHAREPOINT to SQL and it is not recommended ... Business Server 2003 ...
    (microsoft.public.windows.server.sbs)
  • Problem upgrading named instance in SQL 2000
    ... I have installed SQL 2000 Server on my machine with Default Instance ... After selecting the Database Engine ... Reason: Your upgrade is blocked. ...
    (microsoft.public.sqlserver.clients)
  • Re: Upgrade 2000 -> 2005 Timeout period elapsed...
    ... Any SQL 2005 tool on the Server would not allow a Connection to the SQL 2000 DBMS. ... Any other machine on the network could connect to the SQL 2000 server Just fine. ... I was able to upgrade the DB and remove the 2nd Named Instance I installed. ... The timeout period elapsed prior to completion of the ...
    (microsoft.public.sqlserver.setup)
  • Re: New Hardware, moving
    ... resources to NodeB and repeat the upgrade. ... Senior Database Administrator ... Microsoft SQL Server MVP ... SQL 2000 and Windows 2003 support up to four node clusters. ...
    (microsoft.public.sqlserver.clustering)
  • Re: MSSQL on XP-Pro
    ... These old versions of SQL Server should run on XP. ... There are two ways to upgrade. ... upgrade when you run the 7.0 install. ...
    (microsoft.public.sqlserver.setup)