RE: URGENT: Please help upgrade SQL 7 STD to SQL 2000 STD

In addition to my previous post:

I noted that in the master database there are some tables called:
- sysfiles
- sysfiles1
- sysdevices

In the sysfiles and sysfiles1 all the paths are correct:
master E:\MSSQL7\DATA\master.mdf
mastlog E:\MSSQL7\log\mastlog.ldf

However...in the sysdevices it states:
master E:\MSSQL7\DATA\master.mdf
mastlog E:\MSSQL7\DATA\mastlog.ldf

And the last line is wrong!

Could this be the cause of our upgrade problem?
How do I solve this? Can I just manually change the path without a reboot or
stop of SQL?

Thanx in advance


"Wim" wrote:

Hope someone can help me a.s.a.p:
We tried to upgrade our SQL 7 server to SQL 2000.
After staring the upgrade the screen "Setup is initializing the server for
the upgrade process" appears. This screen stayed on for about an hour and I
knew that the upgrade failed. So I started to check te error-logs. There were
some strange things which I hope someone can help me solve!
It seems SQL upgrade stops SQL server and then tries to start it again.
That's the part where it fails in my opinion. Here's a part of the log:
***Begin of Log!
2006-02-03 18:11:10.68 server Microsoft SQL Server 2000 - 8.00.194
(Intel X86)
Aug 6 2000 00:57:48
Copyright (c) 1988-2000 Microsoft Corporation
Standard Edition on Windows NT 5.0 (Build 2195: Service Pack 3)

2006-02-03 18:11:10.68 server Copyright (C) 1988-2000 Microsoft
Corporation.
2006-02-03 18:11:10.68 server All rights reserved.
2006-02-03 18:11:10.68 server Server Process ID is 2280.
2006-02-03 18:11:10.68 server Logging SQL Server messages in file
'e:\MSSQL7\log\ERRORLOG'.
2006-02-03 18:11:10.68 server Warning: -f command line flag
used...minimal server configured.
2006-02-03 18:11:10.70 server SQL Server is starting at priority class
'normal'(4 CPUs detected).
2006-02-03 18:11:10.73 server Performance monitor shared memory setup
failed: -1
2006-02-03 18:11:10.82 server SQL Server configured for thread mode
processing.
2006-02-03 18:11:10.82 server Using dynamic lock allocation. [2500] Lock
Blocks, [5000] Lock Owner Blocks.
2006-02-03 21:44:49.95 server MS DTC initialization skipped because of
start up option.
2006-02-03 21:44:49.95 spid2 Warning ******************
2006-02-03 21:44:49.95 spid2 SQL Server started in single user mode.
Updates allowed to system catalogs.
2006-02-03 21:44:49.95 spid2 Starting up database 'master'.
2006-02-03 21:44:49.96 spid2 udopen: Operating system error 2(The system
cannot find the file specified.) during the creation/opening of physical
device e:\MSSQL7\data\mastlog.ldf.
2006-02-03 21:44:49.98 spid2 FCB::Open failed: Could not open device
e:\MSSQL7\data\mastlog.ldf for virtual device number (VDN) 2.
2006-02-03 21:44:49.98 spid2 Error: 5105, Severity: 16, State: 4.
2006-02-03 21:44:50.06 spid2 02/03/06 21:44:50 Stack Overflow Dump not
possible - Exception c00000fd E at 0x00404FFB
2006-02-03 21:44:50.06 spid2 Address=404ffb Exception Code = c00000fd
2006-02-03 21:44:50.06 spid2 eax=42bf4538 ebx=00000000 ecx=01ad3418
edx=00000000
2006-02-03 21:44:50.06 spid2 esi=00000000 edi=00000000 eip=00404ffb
esp=01ad3000
2006-02-03 21:44:50.06 spid2 ebp=01ad37e8 efl=00010246
2006-02-03 21:44:50.06 spid2 cs=1b ss=23 ds=23 es=23 fs=3b gs=0
2006-02-03 21:44:50.06 spid2 1: Return Address 00404FFB
2006-02-03 21:44:50.06 spid2 2: Return Address 00444EE7
2006-02-03 21:44:50.06 spid2 3: Return Address 00444DC7
2006-02-03 21:44:50.06 spid2 4: Return Address 0040467D
2006-02-03 21:44:50.06 spid2 5: Return Address 004B1E51
2006-02-03 21:44:50.06 spid2 6: Return Address 004046DA
2006-02-03 21:44:50.06 spid2 7: Return Address 0042074C
2006-02-03 21:44:50.06 spid2 8: Return Address 0042051F
2006-02-03 21:44:50.06 spid2 9: Return Address 00420982
2006-02-03 21:44:50.06 spid2 10: Return Address 004662BC
2006-02-03 21:44:50.06 spid2 11: Return Address 00825A4A
2006-02-03 21:44:50.06 spid2 12: Return Address 00444EE7
2006-02-03 21:44:50.06 spid2 13: Return Address 00444DC7
2006-02-03 21:44:50.06 spid2 14: Return Address 0040467D
2006-02-03 21:44:50.06 spid2 15: Return Address 004B1E51
2006-02-03 21:44:50.06 spid2 16: Return Address 004046DA
2006-02-03 21:44:50.06 spid2 17: Return Address 0042074C
2006-02-03 21:44:50.06 spid2 18: Return Address 0042051F
2006-02-03 21:44:50.06 spid2 19: Return Address 00420982
2006-02-03 21:44:50.06 spid2 20: Return Address 004662BC
2006-02-03 21:44:50.06 spid2
2006-02-03 21:44:50.06 spid2 TotalPhysicalMemory = 3925356544,
AvailablePhysicalMemory = 3628933120
2006-02-03 21:44:50.06 spid2 AvailableVirtualMemory = 268845056,
AvailablePagingFile = 7907880960
*** End of Log!

The strange thing is that we have our SQL 7 server setup with all the
LOG-files on the D-drive and the databases on the E-drive!
So I'm totally confused with the above error! At startup during the upgrade
it seems that it's looking for the log file of the masterdatabse on the
E-drive! Anyone got any idea's about that?

Also in the WINNT dir there's a log file called "setupapi.log". There are
some lines like this:
START<<
Copying file C:\WINNT\Temp\IXP000.TMP\sqlxmlx.inf to C:\Program Files\Common
Files\Microsoft Shared\dasetup\sqlxmlx.inf.
An unsigned or incorrectly signed file
(C:\WINNT\Temp\IXP000.TMP\sqlxmlx.inf) was installed. Error 0x800b0003: The
form specified for the subject is not one supported or known by the specified
trust provider.
END<<
Is this "killing" the upgrade?

Then...in the "sqlstp.log" the last lines are:
START<<
21:44:49 C:\WINNT\TEMP\SqlSetup\Bin\scm.exe -Silent 1 -Action 6 -Service
MSSQLSERVER
21:44:49 Process Exit Code: (0)
21:44:49 C:\WINNT\TEMP\SqlSetup\Bin\scm.exe -Silent 1 -Action 1 -Service
MSSQLSERVER -StartupOptions \-f \-m \-T4010
END<<
And the upgrade just stops responding...just shows the message "Setup is
initializing the server for the upgrade process"


If someone has any ideas / tips / known issues about these problems I've run
into...please do not hesitate to help me out.
Thanx in advance!!!

Wim
.

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: 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)
  • Re: upgrading from SQL 7.0 to SQL2000
    ... I like the idea of doing a fresh install of SQL> 2000. ... > 2) install SQL 7.0 on a separate machine which is a test server. ... > 3) Restore the databases from my production server on to my test server> running SQL 7.0. ... While the upgrade should work just fine I like to start>> fresh if possible. ...
    (microsoft.public.sqlserver.setup)
Quantcast