<div>
Hi, 
I'm affraid I didn't test WSUS with SEP first. I was running an older version of the AV software on the test machines. That'll teach me to assume things will be compatible. 
 
From looking at the info in your first link, that seems to confirm my theory that the problem is something to do with IIS7 and that it should be repairable. 
 
WSUS and SEP are setup to use seperate virtual directories in IIS and neither of them use the default web site on port 80. 
That link suggests re-creating the default web site virtual directories but the instructions are for IIS6. I'm not really sure how re-creating the default website can make a difference as it's not being used. 
When I tried re-installing WSUS I did it in the same way suggested in your first link. 
Do you have any ideas what I can try next? 
Thanks. 
 

</div>

<div>
I forgot to mention; I tried shutting down all of the SEP services and then restarting the IIS and WSUS services. WSUS was still broken and prodiced the same errors in the event log. 
 
I'm going to try shutting down SEP and re-installing WSUS to see if that allows WSUS to istall properly. I'll post my fidings after lunch. 

</div>

<div>
Hi, 
 
Follow this solution step-by-step: 
 
Uninstall WSUS but keep the logs, database, and content. 
Warning: This is VERY important, otherwise you will have to create a new WSUS site from scratch. 
 
Then re-install WSUS and specify a new web site using port 8530. (Recommended) 
On one of the clients, force a group policy update &nbsp;by the following method: 
Click Start&gt; Run 
Type in gpupdate /force, and press Enter. 
 
Stop &quot;Wuauserv&quot; and type wuauclt /resetauthorization /detectnow in the Run tab. 
Confirm that the client is now able to download new updates . 
Confirm that the WSUS console shows that the client has checked into the WSUS server. 
 
 
Important: A new Content Virtual Directory must be created in the default web site, for the Symantec application becasue the uninstallation of WSUS removes it 
 
To create a new Virtual Directory for the Symantec Webserver Website in IIS, follow the steps outlined below - 
&nbsp; 
&nbsp;In IIS Manager, expand the local computer, expand the Web Sites Folder, right-click the Symantec Webserver Site or folder within which you want to create the virtual directory, point to New, and then click Virtual Directory. The Virtual Directory Creation Wizard appears. 
&nbsp;Click Next. 
&nbsp;In the Alias box, type a name for the virtual directory. (For Example - SEPM) 
&nbsp;Click Next. 
&nbsp;In the Path box, type or browse to the physical directory in which the virtual directory resides, and then click Next. 
&nbsp;Under Allow the following permissions, select the check boxes for the access permissions you want to assign to your users, and then click Next. 
&nbsp;Click Finish. 
 
The virtual directory is created below the currently selected folder level. 
 
Fore more information, check the following KB articles: 
 
<a href="http://service1.symantec.com/support/ent-security.nsf/854fa02b4f5013678825731a007d06af/3b007a2cd99191cc88257457005c63db?OpenDocument" rel="ugc nofollow">http://service1.symantec.com/support/ent-security.nsf/854fa02b4f5013678825731a007d06af/3b007a2cd99191cc88257457005c63db?OpenDocument</a> 
 
<a href="http://service1.symantec.com/support/ent-security.nsf/854fa02b4f5013678825731a007d06af/1b477a99f66cb881882573980078ae94?OpenDocument" rel="ugc nofollow">http://service1.symantec.com/support/ent-security.nsf/854fa02b4f5013678825731a007d06af/1b477a99f66cb881882573980078ae94?OpenDocument</a> 
 
<a href="http://service1.symantec.com/support/ent-security.nsf/854fa02b4f5013678825731a007d06af/0c49b572d809ab4f8825738d00764725?OpenDocument" rel="ugc nofollow">http://service1.symantec.com/support/ent-security.nsf/854fa02b4f5013678825731a007d06af/0c49b572d809ab4f8825738d00764725?OpenDocument</a> 
 
<a href="http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2007111212591048?Open&docid=2008052809491248&nsf=ent-security.nsf&view=docid" rel="ugc nofollow">http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2007111212591048?Open&docid=2008052809491248&nsf=ent-security.nsf&view=docid</a> 
 
A Symantec Certified Specialist @ your service 

</div>

<div>
Hi xmachine, 
 
I'm sorry but you obviously didn't read my comments fully. 
None of the things you suggested apply to me as both WSUS and SEP are already installed in separate virtual directories in IIS and always have been. Neither of them were installed in the default site. 
 
In IIS I have the Default site on port 80, &quot;Symantec Web Server&quot; on port 8014 and &quot;WSUS Administrator&quot; on port 8530. 
 
SEP works fine, only WSUS is broken and I installed WSUS after SEP. 
 
I tried re-installing WSUS with SEP switched off as I mentioned above and that didn't help. 

</div>

<div>
Hi xmachine, 
 
I've allready tried the first three and they didn't help. 
On the first one the reg key didn't exist at all, so I created it but it did nothing. 
On the second one the setting was already enabled. 
On the third one the setting was already disabled. 
 
I hadn't tried the 4th but I have now and it didn't help. I turned off the firewall to make sure. 
 
Any more Ideas? 
 
I decided to look into checking all the IIS settings in the WSUS virtual directory. I found <a href="http://technet.microsoft.com/en-us/library/cc720489%28printer%29.aspx" rel="ugc">THIS</a> site and procedded to follow the instructions. 
 
I found 3 settings (using Adsutil) in the APIRemoting30 virtual directory that were different to what it suggested they should be. These are as follows: 
 
AppIsolated: This should be 2, it's set to 0. 
AuthFlags: This should be 21, it's set to 20 
AuthAnonymous: This should be True, it's set to False. 
 
The folder that the APIRemoting30 virtual directory pointed to was also different but I think that's because the guide is for IIS6. So that makes me wonder if the above 3 settings should be changed or not. 
 
I tried changing them using Adsutil but the settings didn't stay set. I don't know if I was doing this correctly. 
 
Does anyone have any ideas about this? 
 

</div>

<div>
I've just accidentally managed to re-create this problem on my Server 2008 test machine without SEP being installed. 
 
I wanted to compare the 3 settings I listed earlier against those on the test machine but I noticed that Adsutil wasn't installed on the test machine. So I ticked all the management tools options in the roles wizzard and clicked install. After they were installed, WSUS was broken and producing the same errors as my production server. 
 
So I'm now trying to roll back the changes to see if I can track down the cause. 

</div>

<div>
I didn't manage to figure out what happened to the test machine to make WSUS break but I did finally manage to get WSUS installed properly on my production server. 
 
I need to do more testing and turn some other things back on before I'll be sure that everything is working but just getting WSUS working is a massive step for me after the hell it's given me. 
 
This is roughly what I did to get WSUS working. 
 
Uninstalled SEP client. (I don't think this helped) 
Stopped the 2 SEP server services. 
Set them both to disabled. 
Restart server. 
Uninstalled WSUS. Ticked all boxes to remove all files. 
Deleted content folder etc specified at beginning of WSUS install. 
Deleted WSUS folder in Program Files. (I forget it's proper name) 
Restart server. 
Uninstall IIS. 
Restart server. 
Install IIS with correct features for WSUS, including dynamic content compression. 
Server restarts as part of install. 
Restart server again. 
Install WSUS with custom IIS site. 
Follow through the WSUS config wizard. 
Restart Server. 
 
That's where I'm up to now. 
I need to try starting up SEP again etc. 
I'll post more info tomorrow. 
I'm going home for a well desereved beer now. 

</div>

<div>
Apart from me not being able to spell deserved, everything is still going well. 
WSUS is still working despite me turning SEP back on but I am still experiencing some problems. 
 
Here's what I've done so far today: 
 
Installed update for WSUS, KB954960 
Restarted server 
Turned windows firewall back on 
Installed SEP client. 
Restarted server. 
Edit bindings on Symantec Webserver in IIS: Add HTTP on port 8014 (this setting was lost after IIS re-install) 
Website started automatically 
Restarted Server 
Started Symantec embedded database service then Symantec endpoint protection service. 
Restarted server 
 
So everything I had turned on at the beginning of all this is now turned back on again. 
After each stage I verified that I could still access the WSUS management interface. 
 
The problem I have now is that when I try to open the Symantec Endpoint Management interface I get an error message saying &quot;Unable to communicate with the reporting component&quot;. 
I think this has been caused by me re-installing IIS as the Symantec site hosted in IIS has a virtual directory called Reporting. I've tried several fixes listed on the Symantec website but so far I've not fixed the problem. I'll post more info when I have it. 

</div>

<div>
<div class="content wysiwyg-content">
Hi, 
 
I've been testing WSUS over the last few months on Server 2003 and Server 2008. WSUS installed and worked fine on both these systems. However, after installing WSUS on our production Server 2008 machine it refuses to work. 
 
On the production server I have Server 2008 Enterprise 64bit, Symantec Endpoint Protection server and client V11 and Backup Exec media server V12.5. IIS7 is already setup and being used by Endpoint. All of this seems to work fine. 
 
Once I install WSUS from the &quot;Add Roles&quot; wizard I immediately get an error saying something about &quot;can't connect to the API&quot;. 
Upon checking the application event log I'm getting the following events logged: 
 
Log Name: &nbsp; &nbsp; &nbsp;Application 
Source: &nbsp; &nbsp; &nbsp; &nbsp;Windows Server Update Services 
Date: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;27/02/2009 10:23:21 
Event ID: &nbsp; &nbsp; &nbsp;7032 
Task Category: None 
Level: &nbsp; &nbsp; &nbsp; &nbsp; Warning 
Keywords: &nbsp; &nbsp; &nbsp;Classic 
User: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;N/A 
Computer: &nbsp; &nbsp; &nbsp;server 
Description: 
The WSUS administration console was unable to connect to the WSUS Server via the remote API. 
 
Verify that the Update Services service, IIS and SQL are running on the server. If the problem persists, try restarting IIS, SQL, and the Update Services Service. 
 
--------------- 
 
Log Name: &nbsp; &nbsp; &nbsp;Application 
Source: &nbsp; &nbsp; &nbsp; &nbsp;Windows Server Update Services 
Date: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;27/02/2009 05:04:37 
Event ID: &nbsp; &nbsp; &nbsp;12012 
Task Category: 9 
Level: &nbsp; &nbsp; &nbsp; &nbsp; Error 
Keywords: &nbsp; &nbsp; &nbsp;Classic 
User: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;N/A 
Computer: &nbsp; &nbsp; &nbsp;server 
Description: 
The API Remoting Web Service is not working. 
 
---------------- 
 
The WSUS management node doesn't open and I can;t get access to anything WSUS related, I just get error messages about being unable to connect to the API. 
I have all the latest service packs, patches and updates installed for all the software as far as I know. I've tried uninstalling and re-installing WSUS but that didn't help. 
I also found a similar question on here but the solution didn't help me. 
Several hours of Googling also didn't turn up any useful info. 
 
Does anyone know how I can get WSUS working? 
 
Thanks, 
 
David.
</div>
</div>

Hi,

I've been testing WSUS over the last few months on Server 2003 and Server 2008. WSUS installed and worked fine on both these systems. However, after installing WSUS on our production Server 2008 machine it refuses to work.

On the production server I have Server 2008 Enterprise 64bit, Symantec Endpoint Protection server and client V11 and Backup Exec media server V12.5. IIS7 is already setup and being used by Endpoint. All of this seems to work fine.

Once I install WSUS from the "Add Roles" wizard I immediately get an error saying something about "can't connect to the API".
Upon checking the application event log I'm getting the following events logged:

Log Name:      Application
Source:        Windows Server Update Services
Date:          27/02/2009 10:23:21
Event ID:      7032
Task Category: None
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      server
Description:
The WSUS administration console was unable to connect to the WSUS Server via the remote API. 

Verify that the Update Services service, IIS and SQL are running on the server. If the problem persists, try restarting IIS, SQL, and the Update Services Service.

---------------

Log Name:      Application
Source:        Windows Server Update Services
Date:          27/02/2009 05:04:37
Event ID:      12012
Task Category: 9
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      server
Description:
The API Remoting Web Service is not working.

----------------

The WSUS management node doesn't open and I can;t get access to anything WSUS related, I just get error messages about being unable to connect to the API.
I have all the latest service packs, patches and updates installed for all the software as far as I know. I've tried uninstalling and re-installing WSUS but that didn't help.
I also found a similar question on here but the solution didn't help me.
Several hours of Googling also didn't turn up any useful info.

Does anyone know how I can get WSUS working?

Thanks,

David.

WSUS broken

Operating system security (OS security) is the process of ensuring OS integrity, confidentiality and availability. OS security refers to specified steps or measures used to protect the OS from threats, viruses, worms, malware or remote hacker intrusions. OS security encompasses all preventive-control techniques, which safeguard any computer assets capable of being stolen, edited or deleted if OS security is compromised, including authentication, passwords and threats to systems and programs.

OS Security

IIS is Internet Information Services, the web server included with Windows Server operating systems. All current versions are built on a modular architecture; modules can be added or removed individually so that those required for specific functionality are installed. The full installation of IIS includes HTTP, security, content, compression, caching, logging and diagnostics.

Microsoft IIS Web Server

Windows Server 2008 and Windows Server 2008 R2, based on the Microsoft Vista codebase, is the last 32-bit server operating system released by Microsoft. It has a number of versions, including including Foundation, Standard, Enterprise, Datacenter, Web, HPC Server, Itanium and Storage; new features included server core installation and Hyper-V.