MSDE and MSDE SQL SP4

Hi,

After installing WSUS I would like to update MSDE to SQL 2000 (MSDE version)
SP4. When I run setup.exe it says that the sa password is weak so setup
cannot continue! It says use SAPWD to fix the problem.

Does anyone know what the default sa password is for a WSUS MSDE install?
Has anyone installed SQL 2000 SP4 (MSDE version)?

ANy help would be appreciated.

What the message means is that you need to supply a strong sa password in
order to execute the setup command to upgrade the existing installation.

The command line should be:

setup INSTANCENAME="WSUS" SAPWD="a_strong_password"


There is no 'default' sa password for a WSUS MSDE install because WSUS does
not install MSDE. If MSDE is installed on Windows 2000, a sysadmin had to do
that before installing WSUS. The sa password would be whatever that sysadmin
assigned it to be. WSUS installs WMSDE on Windows Server 2003, and it
assigns a random password to the sa account, because Integrated
Authentication is used and the sa account is irrelevant.

"Bob" <Bob@discussions.microsoft.com> wrote in message
news:60344297-D973-41D3-9BAE-088B90C93289@microsoft.com...
> Hi,
>
> After installing WSUS I would like to update MSDE to SQL 2000 (MSDE
> version)
> SP4. When I run setup.exe it says that the sa password is weak so setup
> cannot continue! It says use SAPWD to fix the problem.
>
> Does anyone know what the default sa password is for a WSUS MSDE install?
> Has anyone installed SQL 2000 SP4 (MSDE version)?
>
> ANy help would be appreciated.

When I use that command it says the instance name specified is invalid.

I installed WSUS using all defaults.

Also, WSUS is working perfectly, so I can't understand why it doesn't
recognise the instance name "WSUS".

By the way, I executed this command in the folder where the SQL 2000 SP4
[MSDE edition] files were extracted. Is this OK?

Any further help would be appreciated.

Did you install this on Windows 2000 Server or Windows Server 2003.

Please open the services MMC, and look for all entries beginning with MSSQL.

Post back your results, and the current status (started/stopped) for each
entry of MSSQL*

Also, please post the /exact/ syntax you used for the command.

Yes, the correct location to initiate the command is in the SP4 extracted
folder, where setup.exe is located.

btw, there are different SP4 bundles, depending on which version you have
installed.
Please verify that you downloaded and extracted the bundle named:

SQL2000.MSDE-KB884525-SP4-x86-ENU.EXE


"Bob" <Bob@discussions.microsoft.com> wrote in message
news:B7404532-050D-482E-9058-78C5E2333E8C@microsoft.com...
> When I use that command it says the instance name specified is invalid.
>
> I installed WSUS using all defaults.
>
> Also, WSUS is working perfectly, so I can't understand why it doesn't
> recognise the instance name "WSUS".
>
> By the way, I executed this command in the folder where the SQL 2000 SP4
> [MSDE edition] files were extracted. Is this OK?
>
> Any further help would be appreciated.
>
>

I installed WSUS on Windows Server 2003 running SP1.

I can confirm I am using the correct SQL SP4 version as you stated.

MSSQL$WSUS Started Automatic
MSSQLServerADHelper Stopped Manual
SQLAgent$WSUS Stopped Manual

ASP.NET State Service Stopped Manual (I remember WSUS installs
ASP.NET 1.1 during install, so I thought I better let you know!)

The exact syntax I use is: -

setup INSTANCENAME="WSUS" SAPWD="123letmein987"

The error is : The instance name specified is invalid.

Hmmm!!! ....... I duzzint know, Bob.

I would think that would work -- it's certainly what the SP4 documentation
suggests.


"Bob" <Bob@discussions.microsoft.com> wrote in message
news:F5CE9488-458C-42FB-8C67-D744C1C01EB5@microsoft.com...
>I installed WSUS on Windows Server 2003 running SP1.
>
> I can confirm I am using the correct SQL SP4 version as you stated.
>
> MSSQL$WSUS Started Automatic
> MSSQLServerADHelper Stopped Manual
> SQLAgent$WSUS Stopped Manual
>
> ASP.NET State Service Stopped Manual (I remember WSUS
> installs
> ASP.NET 1.1 during install, so I thought I better let you know!)
>
> The exact syntax I use is: -
>
> setup INSTANCENAME="WSUS" SAPWD="123letmein987"
>
> The error is : The instance name specified is invalid.

I got the same behavior when I was trying to upgrade the instance of
SHAREPOINT on SBS2003 - would not recognize the instance name (tried lower
caps as well etc.). When I ran SP4 without specifying an instance name,
thought it would prompt me for one (remember SP3a doing that for SQL Server),
but instead it upgraded all the instances to SP4. Interestingly, I only
succeeded with a named instance of MSSQL$SHAREPOINT which should not have
worked - and it added a new instance called MSSQL$SHAREPOINT!

Bob, I would upgrade w/o using an instance name and then check the version
(the readme has instructions).

Alexis

"Lawrence Garvin" wrote:

> Hmmm!!! ....... I duzzint know, Bob.
>
> I would think that would work -- it's certainly what the SP4 documentation
> suggests.
>
>
> "Bob" <Bob@discussions.microsoft.com> wrote in message
> news:F5CE9488-458C-42FB-8C67-D744C1C01EB5@microsoft.com...
> >I installed WSUS on Windows Server 2003 running SP1.
> >
> > I can confirm I am using the correct SQL SP4 version as you stated.
> >
> > MSSQL$WSUS Started Automatic
> > MSSQLServerADHelper Stopped Manual
> > SQLAgent$WSUS Stopped Manual
> >
> > ASP.NET State Service Stopped Manual (I remember WSUS
> > installs
> > ASP.NET 1.1 during install, so I thought I better let you know!)
> >
> > The exact syntax I use is: -
> >
> > setup INSTANCENAME="WSUS" SAPWD="123letmein987"
> >
> > The error is : The instance name specified is invalid.
>
>
>

I had the exact same issue. I had a 2003 r2 box with wsus installed
with all defaults. it appeared to have msde but did not. i tried to
install msde and got the SAPWD error. I followed Lawrence Garvin's fix
and it worked like a champ!!

c:\MSDERelA\setup INSTANCENAME="WSUS" SAPWD="a_strong_password"

after that i installed the recent service pack no problems.

thanks!!!!!!!!!!!!!!!!




Lawrence Garvin wrote:
> *What the message means is that you need to supply a strong sa
> password in
> order to execute the setup command to upgrade the existing
> installation.
>
> The command line should be:
>
> setup INSTANCENAME="WSUS" SAPWD="a_strong_password"
>
>
> There is no 'default' sa password for a WSUS MSDE install because
> WSUS does
> not install MSDE. If MSDE is installed on Windows 2000, a sysadmin
> had to do
> that before installing WSUS. The sa password would be whatever that
> sysadmin
> assigned it to be. WSUS installs WMSDE on Windows Server 2003, and
> it
> assigns a random password to the sa account, because Integrated
> Authentication is used and the sa account is irrelevant.
>
> "Bob" <Bob@discussions.microsoft.com> wrote in message
> news:60344297-D973-41D3-9BAE-088B90C93289@microsoft.com...
> > Hi,
> >
> > After installing WSUS I would like to update MSDE to SQL 2000
> (MSDE
> > version)
> > SP4. When I run setup.exe it says that the sa password is weak so
> setup
> > cannot continue! It says use SAPWD to fix the problem.
> >
> > Does anyone know what the default sa password is for a WSUS MSDE
> install?
> > Has anyone installed SQL 2000 SP4 (MSDE version)?
> >
> > ANy help would be appreciated. *



--
kDub2006
------------------------------------------------------------------------
http://www.mcse.ms
------------------------------------------------------------------------
View this thread: http://www.mcse.ms/message1692920.html