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

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

Dear Scott,

I would like to follow up on my previous response.

If the "SQL Server Configuration Manager" and "SQL Server Browser" is
currently not available for us to configure , please do the following
procedures to force using the SQL Server 2000 Resolution protocol during
the upgrade.

1) Install a new instance of SQL 2005.
2) Change the Browser Setting to make it inactive (same steps in my
previous post) so that we are using the SSRP(SQL Server 2000 Resolution
protocol).
3) Upgrade the original SQL Server 2000 instance and then revert back the
Browser changes.

Thank you for your time on above troubleshooting steps.

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.
--------------------
| Newsgroups: microsoft.public.sqlserver.setup
| From: v-adamqu@xxxxxxxxxxxxxxxxxxxx (Adams Qu [MSFT])
| Organization: Microsoft
| Date: Tue, 18 Dec 2007 09:26:28 GMT
| Subject: Re: Upgrade 2000 -> 2005 Timeout period elapsed...
| X-Tomcat-NG: microsoft.public.sqlserver.setup
| MIME-Version: 1.0
| Content-Type: text/plain
| Content-Transfer-Encoding: 7bit
|
| Dear Scott,
|
| Thank you for taking time to send the log files.
|
| After checking the setup log files, I found the following error message:
|
| ########################
| MSI (c) (CC!F8) [11:08:06:796]: PROPERTY CHANGE: Modifying SqlLogMessage
| property. Its current value is ' Error Code: 0x80077370 (29552)
| Windows Error Text: Source File Name: sqlca\sqlguica.cpp
| ########################
|
| According to my experience, above error message normally occurs when the
| SQL Server 2005 Upgrade engine uses information that the SQL Server
Browser
| service returns when the SQL Server 2005 upgrade engine tries to connect
to
| an instance of SQL Server 2000. However, the SQL Server Browser service
| cannot return the correct information about the connection request.
| Therefore, the connection fails.
|
| At this point, we can try to use the following method to further
| troubleshoot the problem:
|
| 1. Open the SQL Server Configuration Manager.
| 2. In the left pane, click SQL Server 2005 Services.
| 3. Right-click SQL Server Browser, and then click Properties. The SQL
| Server Browser Properties dialog box appears.
| 4. Click the Advanced tab, and then set the Active property to No.
|
| After you complete these steps, you can upgrade the instances of SQL
Server
| 2000 and SQL Server 2000 Analysis Server. After the upgrade is complete,
| re-enable SQL Server Browser service. To do this, set the Active property
| to Yes, and then restart the SQL Server Browser service.
|
| 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>
| | References: <C63AA41E-34C3-465A-947F-9828C8CEE75D@xxxxxxxxxxxxx>
| <#r8530iPIHA.7908@xxxxxxxxxxxxxxxxxxxxxx>
| | In-Reply-To: <#r8530iPIHA.7908@xxxxxxxxxxxxxxxxxxxxxx>
| | Subject: Re: Upgrade 2000 -> 2005 Timeout period elapsed...
| | Date: Mon, 17 Dec 2007 11:35:49 -0800
| | Lines: 193
| | Message-ID: <FDE7CB30-EBC4-4C5C-8354-8A2575AAF83C@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-PostID: {FDE7CB30-EBC4-4C5C-8354-8A2575AAF83C}
| | X-MS-CommunityGroup-ThreadID: BC28F5A2-EB6A-4056-805E-F5DB52BF4BA6
| | X-MS-CommunityGroup-ParentID: D8784C34-B7F9-470A-8BE8-6A9959D76DFF
| | Newsgroups: microsoft.public.sqlserver.setup
| | Path: TK2MSFTNGHUB02.phx.gbl
| | Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.sqlserver.setup:3878
| | NNTP-Posting-Host: TK2MSFTNGHUB02.phx.gbl 127.0.0.1
| | X-Tomcat-NG: microsoft.public.sqlserver.setup
| |
| | I've sent you the Log files.
| |
| | Here is the error part:
| | MSI (c) (CC!F8) [11:08:06:578]: PROPERTY CHANGE: Modifying
SqlLogMessage
| | property. Its current value is 'Checking for SQL Connectivity...'. Its
| new
| | value: 'Message type: Exception'.
| | MSI (c) (CC!F8) [11:08:06:578]: PROPERTY CHANGE: Modifying
SqlLogMessage
| | property. Its current value is 'Message type: Exception'. Its new
value:
| | 'Timeout expired. The timeout period elapsed prior to completion of
the
| | operation or the server is not responding. .Net SqlClient Data
Provider
| | at
| |
|
Microsoft.SqlServer.BestPracticesAnalyzer.Upgrade.BPAUAAnalyzer.ValidateSQL(
| )
| | at
| |
|
Microsoft.SqlServer.BestPracticesAnalyzer.Upgrade.BPAUAAnalyzer.ValidatePara
| meters()
| | at
| |
Microsoft.SqlServer.BestPracticesAnalyzer.Upgrade.BPAUAAnalyzer.Execute()
| | at
| Microsoft.SqlServer.UpgradeAdvisor.AnalyzerEngine.RunAnalyzer(Object
| | analyzerInfo)'.
| | MSI (c) (CC!F8) [11:08:06:578]: PROPERTY CHANGE: Modifying
SqlLogMessage
| | property. Its current value is 'Timeout expired. The timeout period
| elapsed
| | prior to completion of the operation or the server is not responding.
| .Net
| | SqlClient Data Provider at
| |
|
Microsoft.SqlServer.BestPracticesAnalyzer.Upgrade.BPAUAAnalyzer.ValidateSQL(
| )
| | at
| |
|
Microsoft.SqlServer.BestPracticesAnalyzer.Upgrade.BPAUAAnalyzer.ValidatePara
| meters()
| | at
| |
Microsoft.SqlServer.BestPracticesAnalyzer.Upgrade.BPAUAAnalyzer.Execute()
| | at
| Microsoft.SqlServer.UpgradeAdvisor.AnalyzerEngine.RunAnalyzer(Object
| | analyzerInfo)'. Its new value: 'Message type: Progress'.
| | MSI (c) (CC!F8) [11:08:06:578]: PROPERTY CHANGE: Modifying
SqlLogMessage
| | property. Its current value is 'Message type: Progress'. Its new value:
| | '100'.
| | MSI (c) (CC!F8) [11:08:06:781]: PROPERTY CHANGE: Modifying
SqlLogMessage
| | property. Its current value is '100'. Its new value:
| | 'UpgradeAdvisor.returned 4294967295'.
| | MSI (c) (CC!F8) [11:08:06:796]: PROPERTY CHANGE: Modifying
SqlLogMessage
| | property. Its current value is 'UpgradeAdvisor.returned 4294967295'.
Its
| new
| | value: ' Error Code: 0x80077370 (29552)
| | Windows Error Text: Source File Name: sqlca\sqlguica.cpp
| | Compiler Timestamp: Mon Aug 29 01:18:41 2005
| | Function Name: IsUpgradeBlocked
| | Source Line Number: 4441
| | '.
| | MSI (c) (CC!F8) [11:08:06:796]: PROPERTY CHANGE: Modifying
SqlLogMessage
| | property. Its current value is ' Error Code: 0x80077370 (29552)
| | Windows Error Text: Source File Name: sqlca\sqlguica.cpp
| | Compiler Timestamp: Mon Aug 29 01:18:41 2005
| | Function Name: IsUpgradeBlocked
| | Source Line Number: 4441
| | '. Its new value: '
| | '.
| | MSI (c) (CC!F8) [11:08:06:796]: PROPERTY CHANGE: Adding ERROR_TEXT
| property.
| | Its value is '1'.
| | MSI (c) (CC!F8) [11:08:46:875]: PROPERTY CHANGE: Modifying
SqlLogMessage
| | property. Its current value is '
| | '. Its new value: '<EndFunc Name='RunUpgradeAdvisorDlg' Return='0'
| | GetLastError='0'>'.
| | MSI (c) (CC!F8) [11:08:46:875]: PROPERTY CHANGE: Modifying
SqlLogMessage
| | property. Its current value is '<EndFunc Name='RunUpgradeAdvisorDlg'
| | Return='0' GetLastError='0'>'. Its new value: 'PerfTime Stop:
| | RunUpgradeAdvisorDlg : Mon Dec 17 11:08:46 2007'.
| | MSI (c) (CC!F8) [11:08:46:875]: PROPERTY CHANGE: Modifying
SqlLogMessage
| | property. Its current value is 'PerfTime Stop: RunUpgradeAdvisorDlg :
Mon
| | Dec 17 11:08:46 2007'. Its new value: '<EndFunc Name='LaunchFunction'
| | Return='0' GetLastError='0'>'.
| | Action ended 11:08:46: RunUpgradeAdvisorDlg. Return value 1.
| |
| |
| | "Adams Qu [MSFT]" <v-adamqu@xxxxxxxxxxxxxxxxxxxx> wrote in message
| | news:%23r8530iPIHA.7908@xxxxxxxxxxxxxxxxxxxxxxxxx
| | > 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

  • Critical Alert Update - W32.Slammer
    ... It's not clear if SQL Server 2000 SP1/SP2 includes the ... Microsoft SQL Desktop ... and all applications that install ... >most recent cumulative SQL Server security patch, ...
    (microsoft.public.security)
  • Re: are ado questions allowed here?
    ... Microsoft re MDAC ... This article describes the past, present, and future of Microsoft data ... * OLE DB (including SQL Server OLE DB Provider, ... will be available on the 64-bit Windows operating system. ...
    (comp.databases.ms-access)
  • Re: Critical Alert Update - W32.Slammer
    ... > It's not clear if SQL Server 2000 SP1/SP2 includes the ... > Microsoft SQL Desktop ... >>most recent cumulative SQL Server security patch, ...
    (microsoft.public.security)
  • RE: MSDE, Access, SharePoint... I am not sure where to ask this qu
    ... 1.>> What is the difference between MSDE and WMSDE? ... MSDE that is targeted for use by Windows components only. ... isn't SQL Server Express replacing MSDE and WMSDE? ... Microsoft CSS Online Newsgroup Support ...
    (microsoft.public.windows.server.sbs)
  • Re: Backup still not working
    ... So you may try to rebuild the RSM database if the ... > rename the existing files in this folder to a .old file extension, ... > this time unchecks "First Storage Group" under Microsoft Exchange Server. ... > 1) Open SQL Server Enterprise Manager. ...
    (microsoft.public.windows.server.sbs)