WSUS Server not responding

i don't want hijack original poster's thread, experiencing same issue on windows 2003 standard edition sp2 server began supporting. perhaps has same cause, here's bit more detailed info 1 setup @ least. maybe all.

context:
- wsus3 sp1.
- same 7032 error.
- wsus on same server mmc trying invoke  (though happen connecting 1 server via vpn+rdp)
- pre-existing wsus install (not new)
- iit appears woirking until approximately 10 days before took on supporting server (1 may 2009)
- long while workstations  appeared continue updating thought temperamental snap-in - have been backlog of updates being rolled out via gpo

have tried , noted:
- have deleted wsus xml file user's application data directory
- have restarted iis , wsus.
- there not appear unique database wsus, assume <!-- @page { margin: 2cm } p { margin-bottom: 0.21cm } --> was setup during installation use minimal (windows internal database) instance  @ <!-- @page { margin: 2cm } p { margin-bottom: 0.21cm } -->server \microsoft##ssee (as mentioned - did not install don't know how should look)
- however, when viewl sql instances via mmc config manager sqlserver 2005,  windows internal database ( ##ssee)  not listed (hmmm.... seems bit strange checked 1 of our other wsus setups , can see there)
- 2 files mdf , ldf data , transactions exist have not been written since end of april

mmc wsus continues hang.

so, 2 things suppose:
1. possible sql config somehow "lost" reference builtl-in db (even though files exist) - in case how? , how/can resolved?
2. other potential causes might there 7032?

many pointers.

hello again
thanks response - appreciated.

curiously when did regedit landed @ entry hkey_local_machine\software\microsoft\windows\currentversion\uninstall\windows internal database. suggests else has been in here doing "stuff" (according client previous incumbents made mess of installing sharepoint before leaving - sharepoint listed in sql config manager having own instance).

should know installing windows sharepoint services on existing wsus server break wsus every single time. root cause of issues wsus server. issue has nothing database; because sharepoint takes on default web site of iis, wsus installed (by default). when wss takes on v-root, wsus becomes "invisible" outside world.

as start, suggest uninstalling sharepoint if it's not yet being used. if is, simplest remediation uninstall/reinstall wsus (which install wsus alternate virtual server), , you'll need modify sharepoint wsus resources required in default web site "not managed by" sharepoint. of particular note, selfupdate virtual directory, , files iuident.cab , wutrack.bin.

---

lawrence garvin, m.s., mcitp:ea, mcdba
principal/cto, onsite technology solutions, houston, texas
microsoft mvp - software distribution (2005-2009)

Windows Server  >  WSUS