WSUS MSDE Install on a SBS2003 server with SQL Already installed fails. (Rolls Back)

You have to love new products.   Many sleepless hours.

Another issue that I have found with WSUS is that if you install it on a SBS2003 Box, that already has SQL installed (Premium Tech).   Then the installer will get to the stage of setting up the MSDE instance, then start to roll back and fail.

The workaround for this is to download MSDE from the Microsoft site and install an instance manually.   Then setup WSUS again and use that instance.

This may sound messy, and you are probably wondering why you would use MSDE when you have SQL already installed?   Well the answer is simple for me.   I am more than 400 miles away from the client in some situations, and setting up MSDE by downloading it is far far easier than trying to explain to my clients to put the correct SQL disk in the drive 😉

If I get a fix from MS, I will post it here.

Cheers,

 

Nick.

  17 Replies to “WSUS MSDE Install on a SBS2003 server with SQL Already installed fails. (Rolls Back)”

  1. Christian Cipolat
    June 9, 2005 at 11:25 pm

    Hi Nick,

    I have a call in with Microsoft on exactly the same issue, but with standard. MSDE gets in the way, even if I stop the SBSmonitoring and SharePoint services. I’ll post their findings. It’s been three days now

    Cheers



    Christian

  2. Nick Whittome
    June 10, 2005 at 10:02 am

    Yes, I have also just reproduced this on a box without SQL. Something is not quite right 🙂

    Please do let us know the findings. I also have an open case with them.

  3. PS
    June 12, 2005 at 10:08 am

    Hi All,

    I have exactly the same problem. Tried installing on several clients. Only SBS Premium installs with no problem. All standards fail with errors relating to MSDE.

  4. Charlesb
    June 15, 2005 at 2:03 am

    I have been working with Don Cottman at Microsoft. In my case I have two Dell oem pre loads that won’t install wsus. I have another that was a preload but I wiped clean as the client wanted different domain name, that one works fine but the other two don’t work. Is any of your guys oem preloads either hp or dell? Hoping to get resolution from MS but they find it odd and think it could be with the dell oem version.

  5. Jud
    June 15, 2005 at 11:27 pm

    I’ve got this same issue — Dell pre-loaded Win2003 Server, no previous SQL or MSDE installs.

  6. mark
    June 16, 2005 at 10:52 am

    how about using the wmsde from the installer package.. anyone who can tell me the commandline for the msi? my default msde instance is set up for mcafee protection pilot; I don’t want to mix them..

  7. mark
    June 16, 2005 at 1:10 pm

    this works:

    start install and make a copy of the extracted package; specifically the wmsde folder.

    after rolling back and leaving you with the logfiles go to the copied files and run the sqlserv installer:

    U:Copy of 53fdca17868c30092b78016cWMSDE>SqlRun03.msi INSTANCENAME="WSUS" BLANKSAPWD=1 TARGETDIR=U:WSUS DATADIR=U:WS

    US

    then retry the install and implicitly choose to install wmsde again..

    I ended up with (what appears to be) a working system.

  8. Jud
    June 16, 2005 at 11:48 pm

    Has anyone else had this method work? I tried it today and no dice.

  9. June 22, 2005 at 7:04 pm

    Note that there are differences (explained in the WSUS deployment guide) between the WMSDE that comes with WSUS (for example, it’s only for Windows Server 2003) and the MSDE that you can download from Microsoft’s website. I generally recommend staying away from (W)MSDE since it’s a dumbed down version, like XPHome, that prevents resonable troubleshooting.

  10. Mike
    July 13, 2005 at 8:30 pm

    I struggled with this issue for two days before finally resolving it. I was installing wsus on an sbs2003 premium box with sql already installed and when the installer would get to the point where it was setting up the sql data base it would fail and roll back the install. After reviewing the logs time and time again I determined that it was a permissions issue in the sql server. This is what you must do.

    1. Make sure NT AUTHORITY/ NETWORK SERVICE EXISTS IN SQL AND IT HAS DATABASE CREATION CHECKED

    2. Make sure NT AUTHORITY IS NOT! in any other data base that exists within sql with the exception of SHAREPOINT

    3. run wsussetup.exe /o from a command line this will overwrite any wsus data base the exists in the sql server or that the installer thinks exists in the sql server.

    I think that is it I will check back if anyone has and questions.

    You gotta love Microsoft

  11. Nick
    August 25, 2005 at 8:08 am

    Hi All,

    I am going to post official workaround steps today in a new blogpost. Thanks for all the feedback here.

  12. Nick
    August 25, 2005 at 8:19 am
  13. Don
    September 13, 2005 at 11:50 pm

    Start the WSUS installation, after the splash screen comes up make a copy of the extracted package; specifically the wmsde folder.

    Then cancel the installation and go to the copied files and run the sqlserv installer:

    SqlRun03.msi INSTANCENAME="WSUS" BLANKSAPWD=1 TARGETDIR=C:WSUS DATADIR=C:WSUS

    Next, Follow method 2 in Microsoft TechNet Article# 889289.

    • Method 2

    This method requires that you un-register and then re-register the Atl.dll file after you install SQL Server 2000 Desktop Engine.

    To do this, follow these steps:

    1. Click Start, click Run, type cmd, and then click OK.

    2. Type the following line at the command prompt: regsvr32 /u Atl.dll

    3. Press ENTER to un-register the file.

    4. Type the following line at the command prompt: regsvr32 Atl.dll

    5. Press ENTER to register the file.

    6. Type exit, and then press ENTER.

    Then Start the newly created service "MSSQL$WSUS"

    Now retry the install and implicitly choose to install wmsde again.

    Note: There is a TechNet Article related to WSUS setup issues at the included URL.

  14. Troy Helms
    June 9, 2006 at 9:39 am

    For people still having an issue even after following all the directions posted all over, start looking at other applications installed. Look and see if you have an application that also uses MSDE but may use a hacked version that doesn’t show up as MSDE. A good example of this is Cisco ACS! Uninstall Cisco ACS and bingo, it installs. ArcServe also does this, but it shows up as MSDE. Both will keep WSUS from installing correctly. Good luck!

  15. June 9, 2006 at 12:02 pm

    Troy… thanks for this information. It is all welcome!

    Nick

  16. mamma-jamma (Jeff)
    September 4, 2009 at 3:02 pm

    Ok – i may have similar problem. MSDE sql srvr mgr does not show anything if I am rdp to ‘0’ (console).
    Now, if I am rdp to just a separate session, it shows green and I can see the SharePoint instances.

    What Microsoft fails to make clear about Bus Contact Mgr 2007 Database Tool is that you MUST upgrade your MSDE 2000 that comes with Windows SBS 2003 to MSDE 2005! And they don’t tell you HOW to do that! I found one lady on the Internet so far who ‘figured it out’ and has HUGE disclaimer – what I want are the OFFICIAL MICROSOFT STEPS to upgrade the ‘built-in’ MSDE 2000 that comes w/ SBS 2003 R2 to MSDE 2005!
    Help – please. Thanks.
    email – noSPAM->computerz4u(-at~)yahoo(^dot$)com

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.