Issues with 2000 SP4 Upgrade.

I have two servers now, which I am getting the same issue. The servers are
Windows 2000 O/S. The SQL Servers were at 760 version. The setup gets
through copying files and then says "Initializing Server for Upgrade". I se
e
that the server starts but nothing happens......Hi
What does your log file "sqlsp.log" in your c:\windows or c:\winnt directory
say ?
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Tom" <Tom@.discussions.microsoft.com> wrote in message
news:996FEBDC-FC3B-4FEF-A052-E764A080E419@.microsoft.com...
>I have two servers now, which I am getting the same issue. The servers are
> Windows 2000 O/S. The SQL Servers were at 760 version. The setup gets
> through copying files and then says "Initializing Server for Upgrade". I
> see
> that the server starts but nothing happens......
>
>|||Here is the last portion of the log.
....
....
14:03:17 End Action: CreateRegistrySetSQL
14:03:17 Begin Action: RegWriteSetupEntry
14:03:17 End Action: RegWriteSetupEntry
14:03:17 *** Unable to get RegisteredOwner to apply to Serial number
14:03:17 Begin Action: CreateSer
14:03:17 End Action: CreateSer
14:03:17 SetFileSecuritySQLAndAdmin for C:\WINNT\setup.iss returned: 0, 0
14:03:17 SetFileSecuritySQLAndAdmin for C:\WINNT\sqlsp.log returned: 0, 0
14:03:17 SetFileSecuritySQLAndAdmin for returned: 3, 3
14:03:17 SetFileSecuritySQLAndAdmin for C:\WINNT\sqlsp.log returned: 0, 0
14:03:17 SetFileSecuritySQLAndAdmin for C:\WINNT\sqlstp.log returned: 0, 0
14:03:17 SetFileSecPerfAndLogUsers for C:\Program Files\Microsoft SQL
Server\MSSQL\Binn\SQLCTR80.DLL returned: 1332, 1332
14:03:17 Begin ServPriv (MSSQLSERVER)
14:03:17 End ServPriv()
14:03:18 Upgrading databases
14:03:18 Upgrading databases on instance 'MSSQLSERVER'
14:03:18 C:\DOCUME~1\SQL_SE~1\LOCALS~1\Temp\2\Sql
Setup\Bin\scm.exe -Silent
1 -Action 6 -Service MSSQLSERVER
14:03:18 Process Exit Code: (0)
14:03:18 C:\DOCUME~1\SQL_SE~1\LOCALS~1\Temp\2\Sql
Setup\Bin\scm.exe -Silent
1 -Action 6 -Service MSSQLSERVER
14:03:18 Process Exit Code: (0)
14:03:18 C:\DOCUME~1\SQL_SE~1\LOCALS~1\Temp\2\Sql
Setup\Bin\scm.exe -Silent
1 -Action 1 -Service MSSQLSERVER -StartupOptions \-T4022 \-T4010 \-m
"Mike Epprecht (SQL MVP)" wrote:

> Hi
> What does your log file "sqlsp.log" in your c:\windows or c:\winnt directo
ry
> say ?
> --
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Tom" <Tom@.discussions.microsoft.com> wrote in message
> news:996FEBDC-FC3B-4FEF-A052-E764A080E419@.microsoft.com...
>
>

Issues with 2000 SP4 Upgrade.

I have two servers now, which I am getting the same issue. The servers are
Windows 2000 O/S. The SQL Servers were at 760 version. The setup gets
through copying files and then says "Initializing Server for Upgrade". I see
that the server starts but nothing happens......
Hi
What does your log file "sqlsp.log" in your c:\windows or c:\winnt directory
say ?
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Tom" <Tom@.discussions.microsoft.com> wrote in message
news:996FEBDC-FC3B-4FEF-A052-E764A080E419@.microsoft.com...
>I have two servers now, which I am getting the same issue. The servers are
> Windows 2000 O/S. The SQL Servers were at 760 version. The setup gets
> through copying files and then says "Initializing Server for Upgrade". I
> see
> that the server starts but nothing happens......
>
>
|||Here is the last portion of the log.
.....
.....
14:03:17 End Action: CreateRegistrySetSQL
14:03:17 Begin Action: RegWriteSetupEntry
14:03:17 End Action: RegWriteSetupEntry
14:03:17 *** Unable to get RegisteredOwner to apply to Serial number
14:03:17 Begin Action: CreateSer
14:03:17 End Action: CreateSer
14:03:17 SetFileSecuritySQLAndAdmin for C:\WINNT\setup.iss returned: 0, 0
14:03:17 SetFileSecuritySQLAndAdmin for C:\WINNT\sqlsp.log returned: 0, 0
14:03:17 SetFileSecuritySQLAndAdmin for returned: 3, 3
14:03:17 SetFileSecuritySQLAndAdmin for C:\WINNT\sqlsp.log returned: 0, 0
14:03:17 SetFileSecuritySQLAndAdmin for C:\WINNT\sqlstp.log returned: 0, 0
14:03:17 SetFileSecPerfAndLogUsers for C:\Program Files\Microsoft SQL
Server\MSSQL\Binn\SQLCTR80.DLL returned: 1332, 1332
14:03:17 Begin ServPriv (MSSQLSERVER)
14:03:17 End ServPriv()
14:03:18 Upgrading databases
14:03:18 Upgrading databases on instance 'MSSQLSERVER'
14:03:18 C:\DOCUME~1\SQL_SE~1\LOCALS~1\Temp\2\SqlSetup\Bin\ scm.exe -Silent
1 -Action 6 -Service MSSQLSERVER
14:03:18 Process Exit Code: (0)
14:03:18 C:\DOCUME~1\SQL_SE~1\LOCALS~1\Temp\2\SqlSetup\Bin\ scm.exe -Silent
1 -Action 6 -Service MSSQLSERVER
14:03:18 Process Exit Code: (0)
14:03:18 C:\DOCUME~1\SQL_SE~1\LOCALS~1\Temp\2\SqlSetup\Bin\ scm.exe -Silent
1 -Action 1 -Service MSSQLSERVER -StartupOptions \-T4022 \-T4010 \-m
"Mike Epprecht (SQL MVP)" wrote:

> Hi
> What does your log file "sqlsp.log" in your c:\windows or c:\winnt directory
> say ?
> --
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Tom" <Tom@.discussions.microsoft.com> wrote in message
> news:996FEBDC-FC3B-4FEF-A052-E764A080E419@.microsoft.com...
>
>

Issues with 2000 SP4 Upgrade.

I have two servers now, which I am getting the same issue. The servers are
Windows 2000 O/S. The SQL Servers were at 760 version. The setup gets
through copying files and then says "Initializing Server for Upgrade". I see
that the server starts but nothing happens......Hi
What does your log file "sqlsp.log" in your c:\windows or c:\winnt directory
say ?
--
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Tom" <Tom@.discussions.microsoft.com> wrote in message
news:996FEBDC-FC3B-4FEF-A052-E764A080E419@.microsoft.com...
>I have two servers now, which I am getting the same issue. The servers are
> Windows 2000 O/S. The SQL Servers were at 760 version. The setup gets
> through copying files and then says "Initializing Server for Upgrade". I
> see
> that the server starts but nothing happens......
>
>|||Here is the last portion of the log.
....
....
14:03:17 End Action: CreateRegistrySetSQL
14:03:17 Begin Action: RegWriteSetupEntry
14:03:17 End Action: RegWriteSetupEntry
14:03:17 *** Unable to get RegisteredOwner to apply to Serial number
14:03:17 Begin Action: CreateSer
14:03:17 End Action: CreateSer
14:03:17 SetFileSecuritySQLAndAdmin for C:\WINNT\setup.iss returned: 0, 0
14:03:17 SetFileSecuritySQLAndAdmin for C:\WINNT\sqlsp.log returned: 0, 0
14:03:17 SetFileSecuritySQLAndAdmin for returned: 3, 3
14:03:17 SetFileSecuritySQLAndAdmin for C:\WINNT\sqlsp.log returned: 0, 0
14:03:17 SetFileSecuritySQLAndAdmin for C:\WINNT\sqlstp.log returned: 0, 0
14:03:17 SetFileSecPerfAndLogUsers for C:\Program Files\Microsoft SQL
Server\MSSQL\Binn\SQLCTR80.DLL returned: 1332, 1332
14:03:17 Begin ServPriv (MSSQLSERVER)
14:03:17 End ServPriv()
14:03:18 Upgrading databases
14:03:18 Upgrading databases on instance 'MSSQLSERVER'
14:03:18 C:\DOCUME~1\SQL_SE~1\LOCALS~1\Temp\2\SqlSetup\Bin\scm.exe -Silent
1 -Action 6 -Service MSSQLSERVER
14:03:18 Process Exit Code: (0)
14:03:18 C:\DOCUME~1\SQL_SE~1\LOCALS~1\Temp\2\SqlSetup\Bin\scm.exe -Silent
1 -Action 6 -Service MSSQLSERVER
14:03:18 Process Exit Code: (0)
14:03:18 C:\DOCUME~1\SQL_SE~1\LOCALS~1\Temp\2\SqlSetup\Bin\scm.exe -Silent
1 -Action 1 -Service MSSQLSERVER -StartupOptions \-T4022 \-T4010 \-m
"Mike Epprecht (SQL MVP)" wrote:
> Hi
> What does your log file "sqlsp.log" in your c:\windows or c:\winnt directory
> say ?
> --
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Tom" <Tom@.discussions.microsoft.com> wrote in message
> news:996FEBDC-FC3B-4FEF-A052-E764A080E419@.microsoft.com...
> >I have two servers now, which I am getting the same issue. The servers are
> > Windows 2000 O/S. The SQL Servers were at 760 version. The setup gets
> > through copying files and then says "Initializing Server for Upgrade". I
> > see
> > that the server starts but nothing happens......
> >
> >
> >
>
>

Issue with Installation SQL 2005

We are running some tests here to evaluate whether to upgrade and switch som
e
of the databases from Oracle to SQL 2005, but running into a major issue.
We have a W2003 server where we used to have SQL 2000 running. We upgraded
that to SQL 2005 server. So far, so good, but the client tool (Management
Studio) doesn't show up in the menu list. Running sqlwb.exe also doesn't
return anything.
However trying to install the client tools gives a friendly that it is
already there, but it isn't. I tried a client install on a laptop which
works, but on the server it gives a problem.
Are you not able to install the client tools on the server?
We tried to remove SQL 2005 from Remove Programs which removes it from the
list, but SQL server remains installed and we have no way to access the
databases.
Hopefully someone can help here, because it isn't anything good on the
perception of the product, while from a functionality perspective the produc
t
looks promising. We tried to install SQL 2005 Standard Edition.
Thanks in advance.
MattTry uninstalling and reinstalling the client tools.
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Matt" <Matt@.discussions.microsoft.com> wrote in message
news:DD66D067-60E6-4B2B-8574-1C3DE32A4FFA@.microsoft.com...
> We are running some tests here to evaluate whether to upgrade and switch
> some
> of the databases from Oracle to SQL 2005, but running into a major issue.
> We have a W2003 server where we used to have SQL 2000 running. We upgraded
> that to SQL 2005 server. So far, so good, but the client tool (Management
> Studio) doesn't show up in the menu list. Running sqlwb.exe also doesn't
> return anything.
> However trying to install the client tools gives a friendly that it is
> already there, but it isn't. I tried a client install on a laptop which
> works, but on the server it gives a problem.
> Are you not able to install the client tools on the server?
> We tried to remove SQL 2005 from Remove Programs which removes it from the
> list, but SQL server remains installed and we have no way to access the
> databases.
> Hopefully someone can help here, because it isn't anything good on the
> perception of the product, while from a functionality perspective the
> product
> looks promising. We tried to install SQL 2005 Standard Edition.
> Thanks in advance.
> Matt|||YES, it worked. Thank you!
"Roger Wolter[MSFT]" wrote:

> Try uninstalling and reinstalling the client tools.
> --
> This posting is provided "AS IS" with no warranties, and confers no rights
.
> Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm
> "Matt" <Matt@.discussions.microsoft.com> wrote in message
> news:DD66D067-60E6-4B2B-8574-1C3DE32A4FFA@.microsoft.com...
>
>

Issue with Installation SQL 2005

We are running some tests here to evaluate whether to upgrade and switch some
of the databases from Oracle to SQL 2005, but running into a major issue.
We have a W2003 server where we used to have SQL 2000 running. We upgraded
that to SQL 2005 server. So far, so good, but the client tool (Management
Studio) doesn't show up in the menu list. Running sqlwb.exe also doesn't
return anything.
However trying to install the client tools gives a friendly that it is
already there, but it isn't. I tried a client install on a laptop which
works, but on the server it gives a problem.
Are you not able to install the client tools on the server?
We tried to remove SQL 2005 from Remove Programs which removes it from the
list, but SQL server remains installed and we have no way to access the
databases.
Hopefully someone can help here, because it isn't anything good on the
perception of the product, while from a functionality perspective the product
looks promising. We tried to install SQL 2005 Standard Edition.
Thanks in advance.
Matt
Try uninstalling and reinstalling the client tools.
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Matt" <Matt@.discussions.microsoft.com> wrote in message
news:DD66D067-60E6-4B2B-8574-1C3DE32A4FFA@.microsoft.com...
> We are running some tests here to evaluate whether to upgrade and switch
> some
> of the databases from Oracle to SQL 2005, but running into a major issue.
> We have a W2003 server where we used to have SQL 2000 running. We upgraded
> that to SQL 2005 server. So far, so good, but the client tool (Management
> Studio) doesn't show up in the menu list. Running sqlwb.exe also doesn't
> return anything.
> However trying to install the client tools gives a friendly that it is
> already there, but it isn't. I tried a client install on a laptop which
> works, but on the server it gives a problem.
> Are you not able to install the client tools on the server?
> We tried to remove SQL 2005 from Remove Programs which removes it from the
> list, but SQL server remains installed and we have no way to access the
> databases.
> Hopefully someone can help here, because it isn't anything good on the
> perception of the product, while from a functionality perspective the
> product
> looks promising. We tried to install SQL 2005 Standard Edition.
> Thanks in advance.
> Matt
|||YES, it worked. Thank you!
"Roger Wolter[MSFT]" wrote:

> Try uninstalling and reinstalling the client tools.
> --
> This posting is provided "AS IS" with no warranties, and confers no rights.
> Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm
> "Matt" <Matt@.discussions.microsoft.com> wrote in message
> news:DD66D067-60E6-4B2B-8574-1C3DE32A4FFA@.microsoft.com...
>
>

Issue with Installation SQL 2005

We are running some tests here to evaluate whether to upgrade and switch some
of the databases from Oracle to SQL 2005, but running into a major issue.
We have a W2003 server where we used to have SQL 2000 running. We upgraded
that to SQL 2005 server. So far, so good, but the client tool (Management
Studio) doesn't show up in the menu list. Running sqlwb.exe also doesn't
return anything.
However trying to install the client tools gives a friendly that it is
already there, but it isn't. I tried a client install on a laptop which
works, but on the server it gives a problem.
Are you not able to install the client tools on the server?
We tried to remove SQL 2005 from Remove Programs which removes it from the
list, but SQL server remains installed and we have no way to access the
databases.
Hopefully someone can help here, because it isn't anything good on the
perception of the product, while from a functionality perspective the product
looks promising. We tried to install SQL 2005 Standard Edition.
Thanks in advance.
MattTry uninstalling and reinstalling the client tools.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Matt" <Matt@.discussions.microsoft.com> wrote in message
news:DD66D067-60E6-4B2B-8574-1C3DE32A4FFA@.microsoft.com...
> We are running some tests here to evaluate whether to upgrade and switch
> some
> of the databases from Oracle to SQL 2005, but running into a major issue.
> We have a W2003 server where we used to have SQL 2000 running. We upgraded
> that to SQL 2005 server. So far, so good, but the client tool (Management
> Studio) doesn't show up in the menu list. Running sqlwb.exe also doesn't
> return anything.
> However trying to install the client tools gives a friendly that it is
> already there, but it isn't. I tried a client install on a laptop which
> works, but on the server it gives a problem.
> Are you not able to install the client tools on the server?
> We tried to remove SQL 2005 from Remove Programs which removes it from the
> list, but SQL server remains installed and we have no way to access the
> databases.
> Hopefully someone can help here, because it isn't anything good on the
> perception of the product, while from a functionality perspective the
> product
> looks promising. We tried to install SQL 2005 Standard Edition.
> Thanks in advance.
> Matt|||YES, it worked. Thank you!
"Roger Wolter[MSFT]" wrote:
> Try uninstalling and reinstalling the client tools.
> --
> This posting is provided "AS IS" with no warranties, and confers no rights.
> Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm
> "Matt" <Matt@.discussions.microsoft.com> wrote in message
> news:DD66D067-60E6-4B2B-8574-1C3DE32A4FFA@.microsoft.com...
> > We are running some tests here to evaluate whether to upgrade and switch
> > some
> > of the databases from Oracle to SQL 2005, but running into a major issue.
> >
> > We have a W2003 server where we used to have SQL 2000 running. We upgraded
> > that to SQL 2005 server. So far, so good, but the client tool (Management
> > Studio) doesn't show up in the menu list. Running sqlwb.exe also doesn't
> > return anything.
> >
> > However trying to install the client tools gives a friendly that it is
> > already there, but it isn't. I tried a client install on a laptop which
> > works, but on the server it gives a problem.
> >
> > Are you not able to install the client tools on the server?
> >
> > We tried to remove SQL 2005 from Remove Programs which removes it from the
> > list, but SQL server remains installed and we have no way to access the
> > databases.
> >
> > Hopefully someone can help here, because it isn't anything good on the
> > perception of the product, while from a functionality perspective the
> > product
> > looks promising. We tried to install SQL 2005 Standard Edition.
> >
> > Thanks in advance.
> >
> > Matt
>
>