Re: Wrong MSDE installed

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: trouble installing companyweb
    ... gone ahead and patched the server before continuing with step 13 of KB884453. ... sbs components that I could, ... install any 3rd-party software before you finish the installation. ... For the failed intranet component ...
    (microsoft.public.windows.server.sbs)
  • RE: Monitoring and Reporting
    ... I understand that you unable to get SBS ... monitoring report after you install Windows server 2003 sp2. ... To successfully install SBS 2003 SP1, ... Downloading and Installing Windows Small Business Server 2003 Service Pack 1 ...
    (microsoft.public.windows.server.sbs)
  • RE: SBS 2003 R2 - Please Help
    ... computers be slow after you install the full SBS 2003 R2 components. ... log on slow is probably refer to incorrect DNS ... as the DNS server on the clients rather than the ISP DNS servers. ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS 2003 Fax Sharepoint Routing
    ... Business Server 2003 and click "Change/Remove", ... If the Fax Services component was original installed by using the SBS ... Install fro the Fax Server component. ... And then we should push the shared fax client application from server to ...
    (microsoft.public.windows.server.sbs)
  • Re: Cannot activate SBS 2003 SP2
    ... slip stream SBS you would have had it ages ago. ... How did they buy this Server? ... My main reason for slipstreaming the install is because I cannot get the ...
    (microsoft.public.windows.server.sbs)