MSDE sp4 upgrade syntax

Trying to upgrade from sp3. Syntax is:
C:\MSDEsp4\MSDE>setup.exe /upgradesp SQLRUN INSTANCENAME=ACME
SECURITYMODE=SQL UPGRADEUSER=SA UPGRADEPWD=ACMEPWD /L*v c:\msde.log
message log always shows:
An error was encountered during connection to server: 1
Ending custom action UpgDetectBlankSaLogin().
Action ended 14:17:12:
UpgDetectBlankSaLogin.2D02443E_7002_4C0B_ABC9_EAB2 C064397B. Return value 3.
Action ended 14:17:12: INSTALL. Return value 3.
Property(S): UpgradeCode = {421A321C-2214-4713-B3EB-253F2FBCCE49}
Property(S): SqlDataDir = c:\Microsoft SQL Server\Mssql\data\
Property(S): SqlProgramDir = c:\Microsoft SQL Server\Mssql\binn\
Property(S): SqlInstanceName = ACME
Property(S): SqlSecurityMode = SQL
Property(S): SqlUpgradeUser = sa
Property(S): SqlUpgrade...
hi,
kwicker wrote:
> Trying to upgrade from sp3. Syntax is:
> C:\MSDEsp4\MSDE>setup.exe /upgradesp SQLRUN INSTANCENAME=ACME
> SECURITYMODE=SQL UPGRADEUSER=SA UPGRADEPWD=ACMEPWD /L*v c:\msde.log
C:\MSDEsp4\MSDE>setup.exe /upgradesp SQLRUN INSTANCENAME=ACME SAPWD=xxxx
SECURITYMODE=SQL /L*v c:\msde.log
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.12.0 - DbaMgr ver 0.58.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||So you think I don't need to use the UpgradeUser syntax? I've tried what you
wrote (C:\MSDEsp4\MSDE>setup.exe /upgradesp SQLRUN INSTANCENAME=ACME
SAPWD=xxxx SECURITYMODE=SQL /L*v c:\msde.log) and I still receive the same
error. At end of log it is returning a 1603. SP3 was installed with a
strong password. What am I missing here?
"Andrea Montanari" wrote:

> hi,
> kwicker wrote:
> C:\MSDEsp4\MSDE>setup.exe /upgradesp SQLRUN INSTANCENAME=ACME SAPWD=xxxx
> SECURITYMODE=SQL /L*v c:\msde.log
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.12.0 - DbaMgr ver 0.58.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
>
|||hi,
kwicker wrote:
> So you think I don't need to use the UpgradeUser syntax? I've tried
> what you wrote (C:\MSDEsp4\MSDE>setup.exe /upgradesp SQLRUN
> INSTANCENAME=ACME SAPWD=xxxx SECURITYMODE=SQL /L*v c:\msde.log) and
> I still receive the same error. At end of log it is returning a
> 1603. SP3 was installed with a strong password. What am I missing
> here?
you have to provide the strong password you initially provided at MSDE
installation...
or... you can log in via oSql.exe with a trusted connection (as long as you
are logged in Windows as a local admini) and set the sa password to
wathever you want via
EXEC sp_password @.new = 'whatever' . @.loginane = 'sa'
then do upgrade via
C:\MSDEsp4\MSDE>setup.exe /upgradesp SQLRUN INSTANCENAME=ACME SAPWD=whatever
SECURITYMODE=SQL /L*v c:\msde.log
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.12.0 - DbaMgr ver 0.58.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||I still receive the same error of "UpgDetectBlankSaLogin" looking at the
Return Value 3 area of the log file. At end of log it is returning a 1603. I
know I have the correct password because I installed sp3 on this test system
just to test the upgrade to sp4.
This is the syntax I used:
C:\MSDEsp4\MSDE>setup.exe /upgradesp SQLRUN INSTANCENAME=ACME
SAPWD=mypassword SECURITYMODE=SQL /L*v c:\msde.log
I cannot get anything to work that does NOT produce the errors above! I
tried not entering an SAPWD just to see what error I would get and no matter
what syntax I seem to enter, I still get the same error!
|||hi,
kwicker wrote:
> I still receive the same error of "UpgDetectBlankSaLogin" looking at
> the Return Value 3 area of the log file. At end of log it is
> returning a 1603. I know I have the correct password because I
> installed sp3 on this test system just to test the upgrade to sp4.
> This is the syntax I used:
> C:\MSDEsp4\MSDE>setup.exe /upgradesp SQLRUN INSTANCENAME=ACME
> SAPWD=mypassword SECURITYMODE=SQL /L*v c:\msde.log
> I cannot get anything to work that does NOT produce the errors above!
> I tried not entering an SAPWD just to see what error I would get and
> no matter what syntax I seem to enter, I still get the same error!
except fo including /L*v c:\msde.log in quotes, like /L*v "c:\msde.log" , I
really have no further idea...
I always succesfully upgraded MSDE RTM and sp3/sp3a instances...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.14.0 - DbaMgr ver 0.59.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Slowly bullying my way through this. Here's the latest error I receive:
states osql.exe did not return properly. Unable to run the script files.
Error code=1
This is the syntax that produced the error:
C:\MSDEsp4\MSDE>setup.exe /upgradesp SQLRUN blanksapwd=1 INSTANCENAME=ACME
SAPWD=mypassword SECURITYMODE=SQL /L*v c:\msde.log
Can send error log if needed. Please help...this is VERY frustrating.
|||hi,
kwicker wrote:
> Slowly bullying my way through this. Here's the latest error I
> receive:
> states osql.exe did not return properly. Unable to run the script
> files. Error code=1
> This is the syntax that produced the error:
> C:\MSDEsp4\MSDE>setup.exe /upgradesp SQLRUN blanksapwd=1
> INSTANCENAME=ACME SAPWD=mypassword SECURITYMODE=SQL /L*v c:\msde.log
> Can send error log if needed. Please help...this is VERY frustrating.
:-|
just a note... blanksapwd=1 and SAPWD=mypassword shoud be mutual exclusive..
and /L*v c:\msde.log should be /L*v "c:\msde.log" to prevent long name
problems... but should not cause problem in the case...
sorry... out of ideas... never heard this exception on sp4 .. but please
have a look at http://tinyurl.com/bu5r3
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.14.0 - DbaMgr ver 0.59.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply