Re: Cannot complete WSUS 3.0 reinstall

"BobHickok" <> wrote in message
news:...

From SQL Server 2005 documentation (Books Online):

sp_attach_db
http://msdn.microsoft.com/en-us/libr...7(SQL.90).aspx

CREATE DATABASE
http://msdn.microsoft.com/en-us/libr...1(SQL.90).aspx


> That SQL Server Management Studio attach fails, and that's what started
> this whole problem for me.

If you could share the *exact* sequence of steps you are performing from the
time you start up SSMS until the "attach fails" including the exact messages
you get in response to the "attach fails", I can possibly give you a more
detailed answer than just pointing you at how-to documentation.


> Since I cannot find any syntax to correctly attach the SUSDB,

Really... I'm sorry you had such troubles. I entered the word sp_attach_db
into Bing and got back a half dozen pointers to three different versions of
SQL Server documentation at MSDN.

> How can I get a WSUS re-install to act like a new, clean,
> available-to-use installation of WSUS 3.0? Where All the default
> adminstration tools are visible and available for use?

Uninstall WSUS using Add/Remove Programs.
Uninstall the Windows Internal Database
Delete the 'wsus' (msc) file in the local user profile.
Delete the %programfiles%\Update Services folder.
Delete the ~\WSUS folder.
Reboot

Rerun the installer.



--
Lawrence Garvin, M.S., MCITP:EA, MCDBA
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2009)

MS WSUS Website: http://www.microsoft.com/wsus
My Websites: http://www.onsitechsolutions.com;
http://wsusinfo.onsitechsolutions.com
My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin

"BobHickok" <> wrote in message
news:...

> I have now run the steps you gave me for a removal and clean install.
> Step by step I did this and saw this:

> 3. Uninstall the Windows Internal Database from Add/Remove Programs.

> (WSUS still starts with the same Connection
> Error at this point as it did before shutting down services and
> uninstalling.)

This is not particularly surprising. You stopped the service in Step #1.
Even if you didn't uninstall (partially or successfully) in Step #2, this
would be a normal indication with the w3svc and wsus services stopped.


> 6. Delete the %programfiles%\Update Services folder.
> - I could not delete "EventCategories.dll" from the Common folder,

This is not a good sign. When a DLL file is not deletable, it means one of
two things. Either the permissions on the file are mucked up -- or something
is still using it.


> therefore I deleted everthing in \program files\Update Services, then
> renamed the folder.

Interesting. Not sure what the implications are of renaming a folder tree of
a in-use DLL -- I'd be surprised if it could be done -- which then would
suggest the deletion issue was a permissions error.

So, I assume by "renamed the folder" you mean you renamed the Common folder?
Why not rename/delete the "Update Services" folder?


> 8. Reboot
> - Still cannot delete or rename file EventCategories.dll

Now this indicates either some other malware process has taken over the DLL
and is still running (which would likely be smart enough to overcome the
renamed folder tree), or the permissions on the file are incorrect --
preventing its deletion. Either way, I would continue troubleshooting this
specific issue before I tried to reinstall the software - something is not
right with this -- and it's important when 'fixing' things to never continue
with a procedure when something else "is not right".


> When I clicked Finish I got:
> an error box headed "W.S.U.S. Configuration Wizard"
> with this message: "An error occurred when communicating with the
> server, and this wizard must be closed. You may restart the WSUS Server
> Configuration Wizard from the Options page on WSUS 3. Console."


> 11. Start up WSUS, the server (\\doc-it) is not listed on the Servers
> Administered list

> When I try to Connect To... servers, it defaults to port 80, I type in
> servername (doc-it) and it fails. Tried using \\doc-it and that fails
> too.

Just to clarify -- the value that goes in that blank is the simple machine
name 'doc-it', not a UNC pathname. Likewise, in the console, the node of the
navigation tree will be the simple machine name, not containing leading
backslashes.


What do you get from the command 'nslookup doc-it' when run on the WSUS
Server?

Have you made *any* changes to the configuration of IIS?
Is anything else running on this server that uses IIS?
In any of these repair attempts have you ever uninstalled/reinstalled IIS?

Can you access this resource from IE on the WSUS Server:
http://doc-it/iuident.cab
http://doc-it/selfupdate/iuident.cab
http://doc-it/simpleauthwebservice/simpleauth.asmx

The first two should give you File Open/Save dialog boxes; the last will
give you a webservices description page.

I don't know that we've ever talked about the specifics of your
installation, since this is a long running thread and most of the early
posts have rolled off my reader. Please provide a synopsis of the server
(hardware/os/software) and environment in which it is installed. At this
point I'm concerned about =assumptions= interfering with continued
diagnostic efforts.





--
Lawrence Garvin, M.S., MCITP:EA, MCDBA
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2009)

MS WSUS Website: http://www.microsoft.com/wsus
My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin

"BobHickok" <> wrote in message
news:...


> You wrote: Just to clarify -- the value that goes in that blank is the
> simple machine name 'doc-it', not a UNC pathname. Likewise, in the
> console, the node of the navigation tree will be the simple machine
> name, not containing leading backslashes.
>
> --I had tried the simple name in the past, and have again tried using
> the simple name "doc-it", as well as "doc-it.rothcpa.com" since your
> last post - my comment below will explain why I also try with the domain
> name appended too...
> _________________________________________
> You wrote: What do you get from the command 'nslookup doc-it' when run
> on the WSUS Server?
>
> -- When I lookup "doc-it" I get "Can't find... non-existent domain".
> If I lookup "doc-it.rothcpa.com" then it resolves the correct IP
> address.

This is caused because the domain suffix(es) for this machine are not
properly configured.

Either the default domain suffix is not being supplied by DHCP (if a DHCP
client),

or the Computer | Properties | Computer Name | Change | More dialog has not
had a machine domain suffix specified (for static addressed systems),

or the TCP/IP Properties | DNS tab has not been properly specified to
provide a connection-specific domain suffix for the network interface.

As a result, the machine is not properly appending the domain suffix to the
simple machine name 'doc-it', and as a result, the DNS lookup fails.


--
Lawrence Garvin, M.S., MCITP:EA, MCDBA
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2009)

MS WSUS Website: http://www.microsoft.com/wsus
My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin

"BobHickok" <> wrote in message
news:...


_________________________________________
You wrote: Is anything else running on this server that uses IIS?

-- Not positive. When I go into look at it I see Default App Pool and
WSUS Pool, and I see Default Website and Administration Website.

Okay.. this is a strong suggestion that nothing else is running on the
machine -- but you've provided a *BIG* clue here as to another point. Since
there is a "WSUS Administration" website, WSUS would appear to actually be
installed to port 8530, not port 80.


> You wrote: Can you access this resource from IE on the WSUS Server:
> http://doc-it/iuident.cab
> http://doc-it/selfupdate/iuident.cab
> http://doc-it/simpleauthwebservice/simpleauth.asmx
>
> -- in that order, the responses to the 3 commands are:
> -opens a window with Open/Save/Cancel options (this one's OK?)
> -opens a window with Open/Save/Cancel options (this one's OK?)

These are good. Those are the expected results, and confirms for us that the
selfupdate feature is accessible.

> - "Service unavailable." - I double/triple checked my spelling.
> So the first two are fine, the third is not OK.

Based on what I *now* know... this is an expected indication.

Test, also, these three URLs:
http://doc-it:8530/iuident.cab
http://doc-it:8530/selfupdate/iuident.cab
http://doc-it:8530/simpleauthwebservice/simpleauth.asmx

So, to the point of the Admin Console connection -- you'll need to be sure
to specify the port number =8530= in the "Connect to ... " dialog.

Also, confirm that your policy configurations are including this port number
on the Intranet services URLs:
http://doc-it:8530
should be the actual URL configured for WSUS clients to use.


--
Lawrence Garvin, M.S., MCITP:EA, MCDBA
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2009)

MS WSUS Website: http://www.microsoft.com/wsus
My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin