I can't upgrade MSDE sp2 to sp3a

I am trying to upgrade an instance of MSDE on my XP computer using
setup /upgradesp sqlrun SECURITYMODE=SQL UPGRADEUSER=AnAdminLogin
UPGRADEPWD=AdminPassword
It runs for a while and then looks like it rolls back the installation. I
check the event viewer and I see an entry that states
"Product: Microsoft SQL Server Desktop Engine -- Configuration failed.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp."
But when I look further at the other entries I can see nothing that would
indicate why it failed.
I only have one instance of MSDE on my computer and this is the results of
my @.@.version before the upgrade
Microsoft SQL Server 2000 - 8.00.194 (Intel X86)
Aug 6 2000 00:57:48
Copyright (c) 1988-2000 Microsoft Corporation
Desktop Engine on Windows NT 5.1
(Build 2600: Service Pack 2)
I had checked the registry as per a MS article and it looks like it was
isntalled via sqlrun01.msi
Does anybody have any thoughts?
Thanks
Richard
hi Richard,
"Richard Speiss" <rspeiss@.mtxinc.com> ha scritto nel messaggio
news:%23WD%23x$TiEHA.1276@.TK2MSFTNGP09.phx.gbl...
> I am trying to upgrade an instance of MSDE on my XP computer using
> setup /upgradesp sqlrun SECURITYMODE=SQL UPGRADEUSER=AnAdminLogin
> UPGRADEPWD=AdminPassword
> It runs for a while and then looks like it rolls back the installation. I
> check the event viewer and I see an entry that states
> "Product: Microsoft SQL Server Desktop Engine -- Configuration failed.
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp."
> But when I look further at the other entries I can see nothing that would
> indicate why it failed.
> I only have one instance of MSDE on my computer and this is the results of
> my @.@.version before the upgrade
> Microsoft SQL Server 2000 - 8.00.194 (Intel X86)
> Aug 6 2000 00:57:48
> Copyright (c) 1988-2000 Microsoft Corporation
> Desktop Engine on Windows NT 5.1
> (Build 2600: Service Pack 2)
> I had checked the registry as per a MS article and it looks like it was
> isntalled via sqlrun01.msi
> Does anybody have any thoughts?
please add the
/L*v "c:\msdesp3.log"
command line parameter, in order to full log the installation to a (about)
2mb log txt file where you can search for
Return Value 3 in order to toubleshoot your upgrade
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.8.0 - DbaMgr ver 0.54.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
sql

I can't restore my master DB

I have 2 servers (Prod & Staging)
Prod is running SQL 2k Enterprise SP2 (obviously with some fix)
Staging is running SQL 2k Enterprise SP2
I can't get the versions to match, thus I can't restore any of my backed up databases to the staging server from the production one.
Server: Msg 3168, Level 16, State 1, Line 1
The backup of the system database on device g:\DBBACKUP\Master.bak cannot be restored because it was created by a different version of the server (134218407) than this server (134218262).
Server: Msg 3013, Level 16, State 1, Line 1
RESTORE DATABASE is terminating abnormally.
I would determine what versions you are running on both, and then upgrade
staging to match production. Is this possible?
----
Need SQL Server Examples check out my website at
http://www.geocities.com/sqlserverexamples
"HELP! Can't Restore DB's" <HELP! Can't Restore
DB's@.discussions.microsoft.com> wrote in message
news:75D5B62B-2A21-4BF4-889C-92CE4A645F36@.microsoft.com...
> I have 2 servers (Prod & Staging)
> Prod is running SQL 2k Enterprise SP2 (obviously with some fix)
> Staging is running SQL 2k Enterprise SP2
> I can't get the versions to match, thus I can't restore any of my backed
up databases to the staging server from the production one.
>
> Server: Msg 3168, Level 16, State 1, Line 1
> The backup of the system database on device g:\DBBACKUP\Master.bak cannot
be restored because it was created by a different version of the server
(134218407) than this server (134218262).
> Server: Msg 3013, Level 16, State 1, Line 1
> RESTORE DATABASE is terminating abnormally.
>
|||I figured out the problem. A network guy implemented a security fix that altered the version on the production box and he didn't implement the same fix on the Staging box.
"Gregory A. Larsen" wrote:

> I would determine what versions you are running on both, and then upgrade
> staging to match production. Is this possible?
>
> --
> ----
> ----
> --
> Need SQL Server Examples check out my website at
> http://www.geocities.com/sqlserverexamples
> "HELP! Can't Restore DB's" <HELP! Can't Restore
> DB's@.discussions.microsoft.com> wrote in message
> news:75D5B62B-2A21-4BF4-889C-92CE4A645F36@.microsoft.com...
> up databases to the staging server from the production one.
> be restored because it was created by a different version of the server
> (134218407) than this server (134218262).
>
>

I can't restore my master DB

I have 2 servers (Prod & Staging)
Prod is running SQL 2k Enterprise SP2 (obviously with some fix)
Staging is running SQL 2k Enterprise SP2
I can't get the versions to match, thus I can't restore any of my backed up databases to the staging server from the production one.
---
Server: Msg 3168, Level 16, State 1, Line 1
The backup of the system database on device g:\DBBACKUP\Master.bak cannot be restored because it was created by a different version of the server (134218407) than this server (134218262).
Server: Msg 3013, Level 16, State 1, Line 1
RESTORE DATABASE is terminating abnormally.I would determine what versions you are running on both, and then upgrade
staging to match production. Is this possible?
----
----
--
Need SQL Server Examples check out my website at
http://www.geocities.com/sqlserverexamples
"HELP! Can't Restore DB's" <HELP! Can't Restore
DB's@.discussions.microsoft.com> wrote in message
news:75D5B62B-2A21-4BF4-889C-92CE4A645F36@.microsoft.com...
> I have 2 servers (Prod & Staging)
> Prod is running SQL 2k Enterprise SP2 (obviously with some fix)
> Staging is running SQL 2k Enterprise SP2
> I can't get the versions to match, thus I can't restore any of my backed
up databases to the staging server from the production one.
> ---
> Server: Msg 3168, Level 16, State 1, Line 1
> The backup of the system database on device g:\DBBACKUP\Master.bak cannot
be restored because it was created by a different version of the server
(134218407) than this server (134218262).
> Server: Msg 3013, Level 16, State 1, Line 1
> RESTORE DATABASE is terminating abnormally.
>|||I figured out the problem. A network guy implemented a security fix that altered the version on the production box and he didn't implement the same fix on the Staging box.
"Gregory A. Larsen" wrote:
> I would determine what versions you are running on both, and then upgrade
> staging to match production. Is this possible?
>
> --
> ----
> ----
> --
> Need SQL Server Examples check out my website at
> http://www.geocities.com/sqlserverexamples
> "HELP! Can't Restore DB's" <HELP! Can't Restore
> DB's@.discussions.microsoft.com> wrote in message
> news:75D5B62B-2A21-4BF4-889C-92CE4A645F36@.microsoft.com...
> > I have 2 servers (Prod & Staging)
> >
> > Prod is running SQL 2k Enterprise SP2 (obviously with some fix)
> > Staging is running SQL 2k Enterprise SP2
> >
> > I can't get the versions to match, thus I can't restore any of my backed
> up databases to the staging server from the production one.
> >
> > ---
> >
> > Server: Msg 3168, Level 16, State 1, Line 1
> > The backup of the system database on device g:\DBBACKUP\Master.bak cannot
> be restored because it was created by a different version of the server
> (134218407) than this server (134218262).
> > Server: Msg 3013, Level 16, State 1, Line 1
> > RESTORE DATABASE is terminating abnormally.
> >
>
>

I can't restore my master DB

I have 2 servers (Prod & Staging)
Prod is running SQL 2k Enterprise SP2 (obviously with some fix)
Staging is running SQL 2k Enterprise SP2
I can't get the versions to match, thus I can't restore any of my backed up
databases to the staging server from the production one.
---
Server: Msg 3168, Level 16, State 1, Line 1
The backup of the system database on device g:\DBBACKUP\Master.bak cannot be
restored because it was created by a different version of the server (13421
8407) than this server (134218262).
Server: Msg 3013, Level 16, State 1, Line 1
RESTORE DATABASE is terminating abnormally.I would determine what versions you are running on both, and then upgrade
staging to match production. Is this possible?
----
----
--
Need SQL Server Examples check out my website at
http://www.geocities.com/sqlserverexamples
"HELP! Can't Restore DB's" <HELP! Can't Restore
DB's@.discussions.microsoft.com> wrote in message
news:75D5B62B-2A21-4BF4-889C-92CE4A645F36@.microsoft.com...
> I have 2 servers (Prod & Staging)
> Prod is running SQL 2k Enterprise SP2 (obviously with some fix)
> Staging is running SQL 2k Enterprise SP2
> I can't get the versions to match, thus I can't restore any of my backed
up databases to the staging server from the production one.
> ---
> Server: Msg 3168, Level 16, State 1, Line 1
> The backup of the system database on device g:\DBBACKUP\Master.bak cannot
be restored because it was created by a different version of the server
(134218407) than this server (134218262).
> Server: Msg 3013, Level 16, State 1, Line 1
> RESTORE DATABASE is terminating abnormally.
>|||I figured out the problem. A network guy implemented a security fix that alt
ered the version on the production box and he didn't implement the same fix
on the Staging box.
"Gregory A. Larsen" wrote:

> I would determine what versions you are running on both, and then upgrade
> staging to match production. Is this possible?
>
> --
> ----
--
> ----
--
> --
> Need SQL Server Examples check out my website at
> http://www.geocities.com/sqlserverexamples
> "HELP! Can't Restore DB's" <HELP! Can't Restore
> DB's@.discussions.microsoft.com> wrote in message
> news:75D5B62B-2A21-4BF4-889C-92CE4A645F36@.microsoft.com...
> up databases to the staging server from the production one.
> be restored because it was created by a different version of the server
> (134218407) than this server (134218262).
>
>

I can't connect to my local database.mdf file

I have just upgraded to Microsoft SQL Server 2005 Express Edition with Advanced Services SP2.

Now I can't connect to my local database.mdf file.

When trying to open or doubleclick or expand my .mdf file the following message pops up:

Generating user instances in SQL Server is disabled. Use sp_configure 'user instance enabled' to generate user instances.

What is the solution for this problem?

hi,

by default, User Instances feature is disabled when you install a SQLExpress instance.. the Install Wizard provides an option to enable it at install time, but you can enable it via sp_configure execution as

EXEC sp_configure 'show advanced option', '1'; GO EXEC sp_configure 'user instances enabled','1'; GO RECONFIGURE GO EXEC sp_configure 'show advanced option', '0'; GO

(restart the SQLExpress service)

that can be executed both in SqlCmd.exe (command line tool) or in a SQL Server Management Studio Express query window (or even via an ADO/Ado.Net connection)..

you can have a look at all "configurable" options at http://msdn2.microsoft.com/en-us/library/ms189631.aspx

regards

|||

Hi Andrea.

I have entered your code in the query editor and saved it as SQLQuery5.sql.
SQL server is restarted.

I right clicked in the query editor and hit Execute and get the folloving error:

Msg 233, Level 20, State 0, Line 0
A transport-level error has occurred when sending the request to the server. (provider: Shared Memory Provider, error: 0 - No process is on the other end of the pipe.)

The problem is still there?...

|||

Hi again :)

I right clicked in the query editor and hit Execute again after a while. It works now.

Thanks :)

I can't connect to my local database.mdf file

I have just upgraded to Microsoft SQL Server 2005 Express Edition with Advanced Services SP2.

Now I can't connect to my local database.mdf file.

When trying to open or doubleclick or expand my .mdf file the following message pops up:

Generating user instances in SQL Server is disabled. Use sp_configure 'user instance enabled' to generate user instances.

What is the solution for this problem?

hi,

by default, User Instances feature is disabled when you install a SQLExpress instance.. the Install Wizard provides an option to enable it at install time, but you can enable it via sp_configure execution as

EXEC sp_configure 'show advanced option', '1'; GO EXEC sp_configure 'user instances enabled','1'; GO RECONFIGURE GO EXEC sp_configure 'show advanced option', '0'; GO

(restart the SQLExpress service)

that can be executed both in SqlCmd.exe (command line tool) or in a SQL Server Management Studio Express query window (or even via an ADO/Ado.Net connection)..

you can have a look at all "configurable" options at http://msdn2.microsoft.com/en-us/library/ms189631.aspx

regards

|||

Hi Andrea.

I have entered your code in the query editor and saved it as SQLQuery5.sql.
SQL server is restarted.

I right clicked in the query editor and hit Execute and get the folloving error:

Msg 233, Level 20, State 0, Line 0
A transport-level error has occurred when sending the request to the server. (provider: Shared Memory Provider, error: 0 - No process is on the other end of the pipe.)

The problem is still there?...

|||

Hi again :)

I right clicked in the query editor and hit Execute again after a while. It works now.

Thanks :)

I can not connect to SQL Server 2000 on WinXP SP2

Hi,
I am using 'SQLServer 2000 Driver for JDBC' in my java application. My SQL
Server is running in Windows XP pc. I dont had any problem before install
WindowsXP Service Pack 2. But when i have installed WinXP SP2 my application
can not connected to SQL Server. I have disabled firewall option in windows
but problem already continue. Is there any way for fixing this problem.
Thanks.
Sql Server SP3 is required
"Sercan AYYILDIZ" <sercan@.politeknik.us> wrote in message
news:O4umfOqEFHA.2756@.TK2MSFTNGP15.phx.gbl...
> Hi,
> I am using 'SQLServer 2000 Driver for JDBC' in my java application. My
> SQL
> Server is running in Windows XP pc. I dont had any problem before install
> WindowsXP Service Pack 2. But when i have installed WinXP SP2 my
> application
> can not connected to SQL Server. I have disabled firewall option in
> windows
> but problem already continue. Is there any way for fixing this problem.
> Thanks.
>

I am unable to install SQL Server 2005 on Win XP SP2 box

I get to the point of starting the services and receive the following message after about 4 minutes of trying to start. I tried in Mixed Mode and Windows Authentication Mode. Message:

TITLE: Microsoft SQL Server 2005 Setup

The SQL Server service failed to start. For more information, see the SQL Server Books Online topics, "How to: View SQL Server 2005 Setup Log Files" and "Starting SQL Server Manually."

For help, click: http://go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft+SQL+Server&ProdVer=9.00.2047.00&EvtSrc=setup.rll&EvtID=29503&EvtType=sqlsetuplib%5cservice.cpp%40Do_sqlScript%40sqls%3a%3aService%3a%3aWaitForServiceState%40x41d

BUTTONS:

&Retry
Cancel

YOu need do have a look in the WIndows event log or in the log files of SQL Server mentioned. There is a problem starting the service, the message that you provided is just a generic one which doesn′t tell the specific error.

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de
|||I can find nothing useful in the Windows event log and I guess I do not understand where the sql server log files are.|||For me its located in here:

C:\Program Files\Microsoft SQL Server\MSSQL.4\MSSQL\LOG

Could be something different for you depending on your installation.

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de
|||

here is the log contents of the last attempted installation and of course it timed out while trying to start the service:

2006-05-28 07:37:06.92 Server Microsoft SQL Server 2005 - 9.00.2047.00 (Intel X86)

Apr 14 2006 01:12:25

Copyright (c) 1988-2005 Microsoft Corporation

Express Edition with Advanced Services on Windows NT 5.1 (Build 2600: Service Pack 2)

2006-05-28 07:37:06.92 Server (c) 2005 Microsoft Corporation.

2006-05-28 07:37:06.92 Server All rights reserved.

2006-05-28 07:37:06.92 Server Server process ID is 4776.

2006-05-28 07:37:06.92 Server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG'.

2006-05-28 07:37:06.94 Server Registry startup parameters:

2006-05-28 07:37:06.94 Server -d C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf

2006-05-28 07:37:06.94 Server -e C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG

2006-05-28 07:37:06.94 Server -l C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf

2006-05-28 07:37:06.94 Server Command Line Startup Parameters:

2006-05-28 07:37:06.95 Server -m SqlSetup

2006-05-28 07:37:06.95 Server SqlSetup

2006-05-28 07:37:06.95 Server -Q

2006-05-28 07:37:06.95 Server -q SQL_Latin1_General_CP1_CI_AS

2006-05-28 07:37:06.95 Server -T 4022

2006-05-28 07:37:06.95 Server -T 3659

2006-05-28 07:37:06.95 Server -T 3610

2006-05-28 07:37:06.95 Server -T 4010

2006-05-28 07:37:06.98 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.

2006-05-28 07:37:06.98 Server Detected 1 CPUs. This is an informational message; no user action is required.

2006-05-28 07:40:49.72 Server Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required.

2006-05-28 07:40:50.88 Server Database Mirroring Transport is disabled in the endpoint configuration.

2006-05-28 07:59:24.50 Server Service control: stop before startup

|||

Thanks.....

Property(S): DatabaseReplRes.D9BC9C10_2DCD_44D3_AACC_9C58CAF76128 = C:\Program Files\Common Files\Microsoft Shared\Database Replication\Resources\
Property(S): DatabaseReplRes1033.D9BC9C10_2DCD_44D3_AACC_9C58CAF76128 = C:\Program Files\Common Files\Microsoft Shared\Database Replication\Resources\1033\
Property(S): SqlVerComBin.8B75390F_DF2F_4C2C_92F5_9B83F3B36340 = C:\Program Files\Microsoft SQL Server\90\COM\
Property(S): Ver.8B75390F_DF2F_4C2C_92F5_9B83F3B36340 = C:\Program Files\Microsoft SQL Server\90\
Property(S): SqlVerComBin.889BED4C_E3F4_4943_956C_6FFD882F721F = C:\Program Files\Microsoft SQL Server\90\COM\
Property(S): Ver.889BED4C_E3F4_4943_956C_6FFD882F721F = C:\Program Files\Microsoft SQL Server\90\
Property(S): SqlVerComBin.CC4DBEA7_CD8B_4AAE_A10F_657CBA390BD6 = C:\Program Files\Microsoft SQL Server\90\COM\
Property(S): Ver.CC4DBEA7_CD8B_4AAE_A10F_657CBA390BD6 = C:\Program Files\Microsoft SQL Server\90\
Property(S): SqlVerComBinRes.CC4DBEA7_CD8B_4AAE_A10F_657CBA390BD6 = C:\Program Files\Microsoft SQL Server\90\COM\Resources\
Property(S): SqlVerComBinRes1033.CC4DBEA7_CD8B_4AAE_A10F_657CBA390BD6 = C:\Program Files\Microsoft SQL Server\90\COM\Resources\1033\
Property(S): CostingComplete = 1
Property(S): OutOfDiskSpace = 0
Property(S): OutOfNoRbDiskSpace = 0
Property(S): PrimaryVolumeSpaceAvailable = 0
Property(S): PrimaryVolumeSpaceRequired = 0
Property(S): PrimaryVolumeSpaceRemaining = 0
Property(S): RSVirtualDirectoryServer = ReportServer$SQLEXPRESS
Property(S): SqlActionManaged = 3
Property(S): SqlNamedInstance = 1
Property(S): SqlStateManaged = 2
Property(S): RSVirtualDirectoryManager = Reports$SQLEXPRESS
Property(S): SOURCEDIR = d:\69a81902561ca8c7a8df\Setup\
Property(S): SourcedirProduct = {2AFFFDD7-ED85-4A90-8C52-5DA9EBDC9B8F}
Property(S): InstallNgenTicks = 110000
Property(S): SQLBROWSERSCMACCOUNT = NT AUTHORITY\NetworkService
Property(S): SQLSCMACCOUNT = NT AUTHORITY\NetworkService
Property(S): DebugClsid.CC1A8C58_27D1_4D38_BF1B_C0A5CBB90616 = {84AFA01D-0112-4F29-990C-7A3EECC00498}
Property(S): ProductToBeRegistered = 1
MSI (s) (EC:1C) [08:37:27:207]: Note: 1: 1708
MSI (s) (EC:1C) [08:37:27:207]: Product: Microsoft SQL Server 2005 Express Edition -- Installation failed.

MSI (s) (EC:1C) [08:37:27:227]: Cleaning up uninstalled install packages, if any exist
MSI (s) (EC:1C) [08:37:27:227]: MainEngineThread is returning 1603
MSI (s) (EC:5C) [08:37:27:337]: Destroying RemoteAPI object.
MSI (s) (EC:D8) [08:37:27:337]: Custom Action Manager thread ending.
=== Logging stopped: 5/28/2006 8:37:27 ===
MSI (c) (78:AC) [08:37:27:377]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (78:AC) [08:37:27:377]: MainEngineThread is returning 1603
=== Verbose logging stopped: 5/28/2006 8:37:27 ===

|||What service account are you using for the service. It could be that the service account used doesn′t have the appropiate permissions to start up SQL Server. Change that (e.g. to Local System) and see if a manual startup comes up successfull.

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de