SBS2003R2, Error 0x80070643 when installing WSUS from R2 disk

Hi Guys,

I had SBS2003R2 with WSUSv3 running on one of my servers. The customer filled the D: drive where the WSUS folder resided. I was aware of a large (errant) WSUS download  due to an MS fopar and decided to cleanup and gain temporary space by uninstalling WSUSv3. I did this and the customer was happy. I should also note that this server has WIN2K3 SP2 applied . . . I'd be interested in if this can be rolled back safely since all discussion on my error condition seams to relate to SP1.

After adding some more disk space (second Raid array as drive F:) I set about reinstalling WSUS with a view to reestablishing WSUSv3 support through the SBS server management console (I had this prior to the space problem).

I attempted to install WSUSv2 from the SBSR2 disk (prerequisite SPs/KBs were already applied) The install persitently failes with WMSDE Installation failed (ERROR 0x80070643: Fatal error during installation). All of the related error logs are attached.

I have scoured the web for info on this and found various recommendations including MS KBs to manually uninstall all elements of WMSDE using REGEDT32 and MSIZAP which I have followed maticulously to no avail, the same error persists. Can anyone shine any more light on this problem. I need to get the customer back to a position of having managed updates through the SBS server console.

I will be onsite later today and will try any forth coming diagnostics/proposals and post back at that time.

Regards
Trevor
WSUSSetup-080204-1924.log
WSUSMSDESetup-080204-1925.log
WSUSCa-080204-1924.log
TrevorWhiteIT ConsultantAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

lnkevinCommented:
Did you run Terminal Service on this box? If yes, check this out:
http://www.devnewsgroups.net/group/microsoft.public.sqlserver.xml/topic27761.aspx

If there is no TS running, check the MS forum, The green color post was the answer for most of guys who has the same error:
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=442741&SiteID=1


K
0
TrevorWhiteIT ConsultantAuthor Commented:
Hi lnKevin,
I saw the problem with TS but had not installed in knowingly. I checked out the Windows options and could only find an option for Terminal Services Licensing which was not installed. None the less I looked through the Services for this server and found an entry for TerminalServices which I disabled and rebooted . . .all to no avail. Was this OK to prevent TS issues here.

I'll check the MS forum out. . . hmmm do you know I say that lodctr /R suggestion but I can't remember try it. I'll give it a go and post back, thanks for your help so far.

Regards
Trevor
0
TrevorWhiteIT ConsultantAuthor Commented:
Hi lnKevin,
I tried the lodctr /R (working remotely and then ran setup.exe from the R2 CD of SBS2003R2, still got the same error. Can you confirm that what I did for Terminal services was OK ???

Regards
Trevor
0
Powerful Yet Easy-to-Use Network Monitoring

Identify excessive bandwidth utilization or unexpected application traffic with SolarWinds Bandwidth Analyzer Pack.

lnkevinCommented:
I saw the problem with TS but had not installed in knowingly. I checked out the Windows options and could only find an option for Terminal Services Licensing which was not installed...
TS is not installed in your system. If TS installed in the system, you should see Terminal Service option checked. Otherwise, you only have remote desktop enable with 2 active connection; it's not your case.

K
0
lnkevinCommented:
Did you have windows script host installed? If not, download it from MS and install it:
http://www.microsoft.com/downloads/details.aspx?FamilyID=887fce82-e3f5-4289-a5e3-6cbb818623aa&displaylang=en

K
0
TrevorWhiteIT ConsultantAuthor Commented:
I haven't got Script Host installed, I'm working remotely by PC-ANYWHERE so will install and post back in 10.

Cheers
Trev
0
lnkevinCommented:
Install and reboot your server before trying WSUS.

K
0
TrevorWhiteIT ConsultantAuthor Commented:
Not sure what Windows Script Host is . . . are we using this is some sort of diagnostics/capture tool.
Just seen the requirement to boot after WSH install, will have to call the handfull of users to warn them.

Regards
Trevor
0
TrevorWhiteIT ConsultantAuthor Commented:
Just started a reboot . . . will be about 10/15 mins.
Regards
Trevor
0
TrevorWhiteIT ConsultantAuthor Commented:
While this is rebooting, you say that Remote desktop is enabled with 2 active connections. I read somewhere that Remote Desktop acn also contribute to my problem.

How do I disable Remote Desktop for the server, I presume this does not affect my PCanywhere acces to the server and other PCs ???

Regards
Trevor
0
TrevorWhiteIT ConsultantAuthor Commented:
Hi K,
Unfortunately the Windows Script Host Install followed by a server reboot and then WSUS install from SBS R2 disk did not work . . . same problem as before. Does this tool give us some insight into the problem ??

Regards
Trev
0
TrevorWhiteIT ConsultantAuthor Commented:
Hi K,
Could you give me an indication as to why you suggested installing this software . . . I may be able to develope the idea. Still stuck at present but going to read up on Windows Script Host.

Thanks
Trev.
0
TrevorWhiteIT ConsultantAuthor Commented:
Hi K,
I see what it is now (Duh!) I take it you believed this install may repair some brokem part of the Windows Server Infrustructure ??? Well unfortunately its still broke !!
I'm still scouring the web so any pointers from anyone would help considerably.

Regards
Trev
0
lnkevinCommented:
I am sorry for the late response. WSH and IIS are initially the prerequisited to install WSUS. WSH enhances your windows to be able accessing vbscript and others windows script. Most of the time, WSH has been installed with Windows 2003 unless it has been remove./disable manually or running in the older version. Therefore, I suggest you to install WSH.
For now, if you have another server (other than SBS because it has domain controller) installing WSUS. Putting WSUS on SBS with domain controller will create huge traffic when it comes in the patching cycle.

K
0
TrevorWhiteIT ConsultantAuthor Commented:
Hi K,
This is a typical SBS installation, IE around 15 local/remote users and small budget. The product is designed to work like this. I have other servers configured this way with no probs. The issue here is not weather it will work after installation . . .it's getting it installed (or rather reinstalled) after an issue as stated above.
Its getting a bit frustrating, have found some other posts indicating that enabling Direct Meta data updates through IIS properties and disabling the AV may help but no go on any of those.
Thanks for your help so far.

Regards
Trevor
0
lnkevinCommented:
I forgot to ask you an important question, did you disable any Antivirus software services during the installation? if not, try to stop the services and disable them during the installation, enable them after installation succeeded.
WSUS will not be installed if antivirus are active running.

K
0
TrevorWhiteIT ConsultantAuthor Commented:
Hi K,
Yeah, have done this but to no avail.
Thanks
Trev
0
lnkevinCommented:
I post my last one as the same time with yours. So you did all those. At this point, I with you on the research because you have tried all the common solutions. Here is what I have found that you may be interested in:
http://sbs.seandaniel.com/2005/08/work-around-steps-for-installing-wsus.html

K
0
TrevorWhiteIT ConsultantAuthor Commented:
Oh hooo Looks interesting. This was an OEM Win2k Update purchase.
I'll take a closer look in about 30 mins. Got something on the go right now.
Will post back
Trev
0
TrevorWhiteIT ConsultantAuthor Commented:
Hi K,
Sorry with the delay getting back to this.
OK I'm onsite now and have read this all a bit closer and decided to try the seperate MSDE install as documented. I created a batchfile for the command line and ran it using the default dir of c:\wsusfiles\wmsde. Didn't get too far the command completed but there was no MSDE instance in the service snap in. I tried several times but no go, also tried typing in long hand at the prompt too (getting desperate now) but no go.

Is it possib;e this has something to do with the fact we have SQLServer2005 on this server (SQL 9.0.3054) There are other SQL based applications installed on the server (SOPHOS, SHAREPOINT, etc) So don't really want to uninstall SQL at this juncture. If this is the issue can WSUS be installed under SQL2005 and will it operate through the SBS console.

Regards
Trev

0
TrevorWhiteIT ConsultantAuthor Commented:
Hi K and all,
Getting really hacked off with this now. Have spent all day up here and still no breakthrough.
An Update - I can install WSUS 3 (which uses MS Internal database ) but it doesn't appear in the SBS console despite my Cancelling from the configuration procedure after installation as instructed. I sort of expected this but an MS doc seemed to imply this was possible. I think my original thought was correct that WSUS2 need to be installed and working through SBS console before upgrading to WSUS3.

I tried a reboot and a restartr of the Internal database service but no go. Does somebody know what the problem is here, even if there is no known solution. See original post and attached error logs.

Situation now is that I have uninstalled WSUS3 using CP and also uninstalled W Internal DB using MSIZAP and its product string (found in MS docs) Tried to install WSUS2 again but exactly the same error as before. Something has been left behind after the installs because this all used to work like a dream before. I have performed WSUS2 uninstall then reinstall then WSUS3 upgrade on many other servers with no problems.

Aaaagh . . . . .Someone put me out of my misery Pleeeeeease !!
Resigned
Trev.
0
lnkevinCommented:
Trevor,

I  am out of resource for a moment. We should post the link of this same question to the network server and Active Directory or SBS server to see if someone else has better idea. I am still doing more research on this while asking for more help. Is it fair?

K
0
TrevorWhiteIT ConsultantAuthor Commented:
Hi K,
Sure its fair.
Thanks so much for yout help so far I really appreciate it as with any time given on this board by experts. I did originally post in the SBS section (Was hoping for some pearls from Jeff 'TechSoEasy)

I did place in a third area too but can't remember where. . . will look and see.
How can I post in more than three sections . . .may be thats not posible.

Have good Sunday.
Regards
Trev
0
TrevorWhiteIT ConsultantAuthor Commented:
Hi K and Others
Is anyone else watching this thread? I'm still stuck and having to allow all users to download updates as a free for all. There must be a fix for this somewhere. Even if it means a huge re-install !!!

Any more thoughts from the experts ???

Regards
Trevor
0
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
I just breezed through this thread and don't see that you have done anything to adjust the SQL permissions per http://support.microsoft.com/kb/920660.

Jeff
TechSoEasy
0
TrevorWhiteIT ConsultantAuthor Commented:
Ok Will try on Monday, thanks for that.
Trev
0
TrevorWhiteIT ConsultantAuthor Commented:
Hi Jeff and all,
I have temporarily changed the <servername>\administors login privilages to include Sysadmin as per the MS article and then reran the setup program. Unfortumately there was not change in outcome. The error log does not match exactly the conditions described in the MS article but it was worth a try.

Any more ideas or pointers

Regards
Trev
0
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
I'm assuming you are logging in with the built-in Administrator account.  Did you delete all the files in the Temp folders of the Administrator's profile directory?

Jeff
TechSoEasy
0
TrevorWhiteIT ConsultantAuthor Commented:
Yeah I did that a few times. . . but seeing as I'm at a loss did it again and reran the install from the R2CD. Still got same problem. . . Getting fed up with saying 'no same prob now . . . booo!

Trev.
0
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
Actually, I missed a comment of yours above... you say you manually UNINSTALLED MSDE, but then did you manually INSTALL it again?  The link that lnkevin provided you above for Sean Daniel's workaround is what needs to be done.  Here's another point of view on that:  http://msmvps.com/blogs/thenakedmvp/archive/2005/08/25/64007.aspx

Jeff
TechSoEasy
0
TrevorWhiteIT ConsultantAuthor Commented:
Good Morning Jeff,
Unfortunately its a case of 'no tried that too' again (http:#20840448) documents this. I found no MSDE service in service.msc after the install. Your link is clearer than the one I followed but none the less the same method.

I have to go to this site today since I Iost remote access last night. Is there anything you'd like me to check while I'm there ???

Regards
Trev.
0
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
Let me clarify a couple of things for you...

" So don't really want to uninstall SQL at this juncture."

SQL isn't something that you would completely uninstall.  There can be multiple instances of SQL 2000, MSDE 2000, SQL 2005 or SQL 2005 Express.  They are not dependant on eachother, and basically don't even interact with eachother unless you configure them to (which you haven't).  

" I found no MSDE service in service.msc after the install."

You wouldn't.  Instead, you should find a MSSQL$WSUS service, which is the instance you installed.  So perhaps you never fully removed this?

Jeff
TechSoEasy
0
TrevorWhiteIT ConsultantAuthor Commented:
Sorry Jeff I really did mean the MSDE instance which (as  you clarify) would have been signified by MSSQL$WSUS. I wasn't entirely sure if all SQL instances were independent of type so thanks for clarifying. I am pretty happy that I did uninstall the WSUS instance of SQL and also the WSUS3 instance which is the WMSDE (yet another variant)

Thanks for your input.
Regards
Trevor
0
TrevorWhiteIT ConsultantAuthor Commented:
Can cloase this now, turned out that there was still some obscure registry entry still refering to the original WSUS install. Had to call in an MVP from Small Bus to help.

Thanks to Kevin and Jeff for their comments and thoughts.
Regards
Trev
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
jbodysCommented:
Do you possibly remember this registry entry? I seem to have a similar (if not the same) problem with my WSUS installation...
0
TrevorWhiteIT ConsultantAuthor Commented:
Hi jbodys
Sorry I (foolishly) didn't record the actual registry entry.
Marina Roos was the consultant from SmallBizServer.com that I used, she didn't actually give me a break down of all that she did. I did have to focus her on the WSUS removal and install issue. I would take a look through the registry for all WSUS or MSDE entries and posibly WMSDE enries.

Sorry I can't be more helpfull
Regards
Trevor
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Installation

From novice to tech pro — start learning today.