Re: Wrong MSDE installed

That is the command line to install a new default instance. You need to get the MSDE SP4 download

http://www.microsoft.com/downloads/details.aspx?FamilyId=8E2DFC8D-C20E-4446-99A9-B7F0213F8BC5&displaylang=en

Here is a link to the syntax for updating an existing instance:

http://download.microsoft.com/download/1/B/D/1BDF5B78-584E-4DE0-B36F-C44E06B0D2A3/ReadmeSql2k32desksp4.htm#_3467464_upgrading_existing_instances_of__fzpy

I think you should be using something like:

setup /upgradesp sqlrun SECURITYMODE=SQL UPGRADEUSER=sa UPGRADEPWD=sql
/L*v C:\MSDELog.log

I'm guessing a bit but based on what you've posted so far it should be something very similar unless they used a different password for sa. You will end up with an error log C:\MSDELog.log which should give you more info if it doesn't work.

This will upgrade the existing instance but do nothing to get SBS Monitoring and Sharepoint installed. They use WMSDE not MSDE. To get those working see the following articles

http://support.microsoft.com/kb/829114/

http://support.microsoft.com/kb/555432

It sounds like the server is a real mess. In the long run it may be easier for you and quicker for the client to start over from a clean slate. Even if you get the current problems fixed what else will you find down the road? Possibly a repair install may fix it. Before going any farther I'd make sure I had known good backups then try a repair install. I'd do a couple of SBS backups then a couple of images of all the drives and have at it.

--
Kerry Brown
Microsoft MVP - Shell/User
www.vistahelp.ca/phpBB2


"Gregg Hill" <bogus@xxxxxxxxxxx> wrote in message news:%23Bb%23P3vJHHA.320@xxxxxxxxxxxxxxxxxxxxxxx
Kerry,

Indeed, those folders are as you say on my SBS 2003 server that has been upgraded to SP1. However, my client only has the RTM of SBS 2003, and those folders obviously (no SP4 yet) are not there. The only "MSDE" folder on this server is at C:\Program Files\Microsoft Windows Small Business Server\Monitoring\MSDE.

I do not know if that is normal for an RTM installation, but that is the way this server is right now, and I do not have any non-SP1 servers to check.

The setup wizard will not run because of the older version of MSDE. It dies with a blocking error stating, "SQL Server 2000 needs SP3 for Windows Server 2003 compatibility." Since I have the C:\Program Files\Microsoft Windows Small Business Server\Monitoring\MSDE setup files, shouldn't I be able to re-install the proper MSDE from there so that I can at least get the SBS setup wizard to run?

I have tried to install the MSDE SP4 update using the SQL2000.MSDE-KB884525-SP4-x86-ENU.EXE file, but I keep getting an error stating "The instance name specified in invalid." The vendor said to use this syntax when doing the SP4 update:

c:\sql2ksp4\msde\setup.exe securitymode=sql SAPWD=sql DISABLENETWORKPROTOCOLS=0

but that fails with the "The instance name specified in invalid." error message. Do you know why I would keep getting that error? Am I missing something in the syntax?

Gregg Hill


"Kerry Brown" <kerry@xxxxxxxxxxxxxxxxxxx*a*m> wrote in message news:OivtVotJHHA.4848@xxxxxxxxxxxxxxxxxxxxxxx
On a normal SBS install both the MSDE and the WMSDE installation files are installed. Normally you'll find them here.

C:\Program Files\Microsoft SQL Server SP4\MSDE

and

C:\Program Files\Microsoft SQL Server SP4\WMSDE

As far as I know only Microsoft programs can use the WMSDE instalation files. If I need to install an MSDE instance I always do it from the MSDE folder.

--
Kerry Brown
Microsoft MVP - Shell/User
www.vistahelp.ca/phpBB2


"Gregg Hill" <bogus@xxxxxxxxxxx> wrote in message news:ecW5RZsJHHA.448@xxxxxxxxxxxxxxxxxxxxxxx
KJ,

I have installed Backup Exec several times on SBS and it always works with what I assumed was the MSDE that comes with SBS. It just creates another instance.

Per this info from my SBS 2003 SP1 system, Backup Exec 10 and Sharepoint appear to be using the same version of MSDE, except that the Sharepoint one calls it "Desktop Engine (Windows) on Windows NT 5.2" instead of "Desktop Engine on Windows NT 5.2." If you look at the build numbers and dates, they are the same.

C:\>osql -E -S sbs2003\bkupexec
1> select @@version
2> go

-----------------------------------------------------------------------

Microsoft SQL Server 2000 - 8.00.2039 (Intel X86)
May 3 2005 23:18:38
Copyright (c) 1988-2003 Microsoft Corporati
on
Desktop Engine on Windows NT 5.2 (Build 3790: Service Pack 1)

(1 row affected)
1> exit



C:\>osql -E -S sbs2003\sharepoint
1> select @@version
2> go

---------------------------------------------------------------------
Microsoft SQL Server 2000 - 8.00.2039 (Intel X86)
May 3 2005 23:18:38
Copyright (c) 1988-2003 Microsoft Corporati
on
Desktop Engine (Windows) on Windows NT 5.2 (Build 3790: Service Pack 1)

(1 row affected)
1> exit

C:\>



Now back to my client.

The application they have is called Total Service from http://www.expertservicesolutions.com/TS.html. The vendor says it is not compatible with WMSDE and needs MSDE itself. I am not aware of the differences between the two. I am going to download the demo, back up my own SBS, and install the demo to see if it works with SBS' install of WMSDE.

This information:

2006-11-07 17:42:35.84 server 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.2 (Build 3790: )

indicates that they have MSDE 2000 build 8.00.194, which is the RTM build. Since the vendor says it is needed for their app, can I just grab the SBS disks and install the MSDE that is in SBS? Why would two different versions be needed, if indeed the versions are actually different? I will post this message, then Google for the differences between the two, if any.

Thank you again for your time.

Gregg Hill








"kj" <kj@xxxxxxxxxxx> wrote in message news:u0w1AOrJHHA.4112@xxxxxxxxxxxxxxxxxxxxxxx
Anytime Greg. Hope it helps.

Any idea what it was being used for? I know a couple of common third party products use the redistributable MSDE for their DB. (Backup Exec is one)

--
/kj
"Gregg Hill" <bogus@xxxxxxxxxxx> wrote in message news:OkZagenJHHA.1240@xxxxxxxxxxxxxxxxxxxxxxx
Thank you!

And good night!

Gregg Hill


"kj" <kj@xxxxxxxxxxx> wrote in message news:O$8rdVlJHHA.4244@xxxxxxxxxxxxxxxxxxxxxxx
Might want to have a look at;

http://support.microsoft.com/kb/320873/en-us

as you have determined to have MSDE not WMSDE.

--
/kj
"Gregg Hill" <bogus@xxxxxxxxxxx> wrote in message news:%23ujGXpfJHHA.3552@xxxxxxxxxxxxxxxxxxxxxxx
My pleasure. I thought it was funny, too, and it just came to me as I was typing. And my wife keeps telling me that I'm not funny...HA!

See my reply to David Copeland, coming in a few minutes

Gregg




"kj" <kj@xxxxxxxxxxx> wrote in message news:eiTB4NfJHHA.4960@xxxxxxxxxxxxxxxxxxxxxxx
I picked up a new client whose previous IT guy was missing a few letters in between the "I" and the "T" (namely DIO).

Oh that one made my day!! Thanks Gregg.

If he used the distributable version of MSDE you'll need to hack it out of there. I'm pretty sure that all SBS needs are supplied by Wmsde which are only included in the various products. (Montioring, Sharepoint, WSUS).

--
/kj
"Gregg Hill" <bogus@xxxxxxxxxxx> wrote in message news:ewlonBaJHHA.3264@xxxxxxxxxxxxxxxxxxxxxxx
Hello!

I picked up a new client whose previous IT guy was missing a few letters in between the "I" and the "T" (namely DIO).

They have an SBS 2003 server, no service pack, and several things do not work, such as SharePoint companyweb, Monitoring, and the setup wizard. The wizard dies with a blocking error stating, "SQL Server 2000 needs SP3 for Windows Server 2003 compatibility."

I Googled myself into a hole, but did find where to look in the registry to find what media was used to install MSDE. It has a version of MSDE that did NOT come with SBS 2003. The idiot who installed the SBS 2003 server installed an application called Total Service, and he installed the MSDE from the Total Service installation CD instead of using what was in SBS.

Now the setup wizard will not run for me to re-install monitoring.

How can I figure out what version of MSDE is running? I found a suggestion to run "select @@version" but it does not tell me **where** to run it. I am a SQL dunce.

How can I install the proper version of MSDE, and if I do, will it kill the current version? Or should I recommend a complete rebuild of the server, since I do not know what else this bright-eyed genius has done?

Thank you for the help!

Gregg Hill

















.

Relevant Pages

  • Re: Wrong MSDE installed
    ... They have an SBS 2003 server, no service pack, and several things do not ... to find what media was used to install MSDE. ... How can I install the proper version of MSDE, and if I do, will it kill ...
    (microsoft.public.windows.server.sbs)
  • Re: Wrong MSDE installed
    ... those folders are as you say on my SBS 2003 server that has been ... The setup wizard will not run because of the older version of MSDE. ... If I need to install an MSDE instance I always do it from the MSDE ...
    (microsoft.public.windows.server.sbs)
  • Re: Wrong MSDE installed
    ... what I assumed was the MSDE that comes with SBS. ... and install the demo to see if it works with SBS' install of WMSDE. ... The wizard dies with a blocking error stating, "SQL Server ...
    (microsoft.public.windows.server.sbs)
  • Re: Wrong MSDE installed
    ... I was testing the install using SP3a to figure it out after SP4 had failed ... left off the server. ... cancelled to change something enough to think it has SP3 so the SBS Setup ... The setup wizard will not run because of the older version of MSDE. ...
    (microsoft.public.windows.server.sbs)
  • Re: Do I install SQL or MSDE
    ... Thanks for using the SBS newsgroup! ... difference of MSDE and SQL. ... In SBS 2003 environment, after you setup SBS 2003 server box successfully, ...
    (microsoft.public.windows.server.sbs)