Hi there,I've been noticing I get the following error after every start-up of SCE. Please advise: Event code: 3001 Event message: The request has been aborted. Event time: 4/7/2009 9:17:08 AM Event time (UTC): 4/7/2009 7:17:08 AM Event ID: 4bc60d1a19e746b7bdc8a3fe81b5e67e Event sequence: 38 Event occurrence: 1 Event detail code: 0 Application information: Application domain: /LM/W3SVC/556861111/ROOT/ClientWebService-4-128835618982049504 Trust level: Full Application Virtual Path: /ClientWebService Application Path: c:\Program Files\Update Services\WebServices\ClientWebService\ Machine name:<Server Name>Process information: Process ID: 5016 Process name: w3wp.exe Account name: NT AUTHORITY\NETWORK SERVICE Exception information:Exception type: HttpException Exception message: Request timed out. Request information: Request URL: http://raven.onesys.local:8530/ClientWebService/client.asmx Request path: /ClientWebService/client.asmx User host address:<Server IP>User: Is authenticated: False Authentication Type: Thread account name: NT AUTHORITY\NETWORK SERVICE Thread information: Thread ID: 8 Thread account name: NT AUTHORITY\NETWORK SERVICE Is impersonating: False On the Server, when I try to browse http://raven.onesys.local:8530/ClientWebService/client.asmx, it gives me the following error on Internet Explorer: Server Error in '/ClientWebService' Application. Request format is unrecognized. Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code. Exception Details: System.InvalidOperationException: Request format is unrecognized.Source Error: An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below. Stack Trace: [InvalidOperationException: Request format is unrecognized.] System.Web.Services.Protocols.WebServiceHandlerFactory.CoreGetHandler(Type type, HttpContext context, HttpRequest request, HttpResponse response) +401258 System.Web.Services.Protocols.WebServiceHandlerFactory.GetHandler(HttpContext context, String verb, String url, String filePath) +281 System.Web.HttpApplication.MapHttpHandler(HttpContext context, String requestType, VirtualPath path, String pathTranslated, Boolean useAppConfig) +564 System.Web.MapHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +142 System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +263 Version Information:Microsoft .NET Framework Version:2.0.50727.3074; ASP.NET Version:2.0.50727.3074

Hi,It could be caused by thatSelfUpdate tree does not work. The SelfUpdate tree MUST be installed into port 80 regardless of whether you are runningWSUS on port 80 / 8530. Or the SelfUpdate treedoes not work if you have the website bound to a specific IP address in your IIS configuration. Procedure to enable SelfUpdate tree: 1. Open IIS Manager from Administrative Tools 2. In the website running on port 80, create a virtual directory called 'Selfupdate'. 3. Point the physical path to 'C:\Program Files\Update Services\Selfupdate'. 4. Make sure you allow anonymous users to connect to it under the 'Directory Security' tab - Enable Anonymous Access.5. Change the security of the 'Selfupdate' virtual directory (right click, properties) and tick the 'Directory Browsing' check box. The workaround is either to set your IIS Configuration to respond to "All unassigned" addresses or add 127.0.0.1 to the list of IP addresses used for Selfupdate.Thanks,Yog Li - MSFT

Hi there,The Selfupdate is already present.It already points to the correct folder.Allow Anonymous Access is already set.The only thing I had to do,based on your instruction, was to Enable Directory Browsing.Still, I get the exact same issue mentioned above.With regards to your last sentence, I'm not sure where this list of IP's are you referring to?

Hi,Did you use SQL Express edition database? Please check if its sizeexceededthelimitationof 4GB. Once the size exceeded the database stopped inserting any data, which corrupted the database and its functionality.To set IIS to respond to "ALL unassigned" addresses: Open IIS management console, right click on the default web site, select properties, in the web site tab, in the "IP Address" field, select "(all unassigned)" and then click OK. To add 127.0.0.1 to the list of IP addresses: Open IIS management console, right click on the default web site, select properties, in the web site tab, click advance button, then click addbutton, input IP address 127.0.0.1 and port 80, click OK to confirm.Please also add IP address 127.0.0.1 and port 443 for SSL in the below frame. Thanks,Yog Li - MSFT

Hi Yog Li,I'm running SQL 2005 SP3 Standard 64bit Edition.I've set all the databases with unrestricted growthwayinitially when I installed the systemand keeping an eye on the growth, however I have 1.2TB available so no worries there. Please note with the IIS how to given above I had to do it differently since it's running on IIS7 (with IIS6 compatibility) on Windows Server 2008 Standard 64bit Edition.I'll clear the logs and reboot the machine and let you know in a few hours if the warning still persists.Thank you.

Hi Yog Li,The Server has been up and running now for about 2 hours and I've received the error once. What is interesting, is one of the lines returned in the error that states: Request URL: http://raven.onesys.local:8530/ClientWebService/client.asmx When I go to the IIS7 Console I can see that the WSUS Administrations Site is set for browsing on: HTTP-8530 and HTTPS-8531. I understand that in your last reply you said I should do the ammendments, which I did, buton the Default Web Site andnot the WSUS Administrator Site.Please advise...

Hi Cyberflake,Thanks for the latest information. That is a careless mistake that I forgot to replace Default Web Site with WSUS Administrator Site. Did you finish the configuration below?Install Internet Information Services (IIS) 7.0 in Server Manager. When configuring IIS 7.0, select the Web Server check box to enable Web Server Role services. Then, under Application Development ensure that Active Server Pages (ASP) and ASP .NET are selected. Thanks,Yog Li - MSFT

I went into the Web Server Role Services as you instructed and I can confirm that the ASP and ASP.NET are both selected. However, regarding these settings, please note that initially when I installed the server, I used the following installation method(which completed sucessfully at that time):In Administrator mode I ran the following from the Command Prompt:call start /w %SYSTEMDRIVE%\windows\system32\pkgmgr /l:log.etw /iu:IIS-WebServerRole;IIS-WebServer;IIS-CommonHttpFeatures;IIS-StaticContent;IIS-DefaultDocument;IIS-DirectoryBrowsing;IIS-HttpErrors;IIS-HttpRedirect;IIS-ApplicationDevelopment;IIS-ASPNET;IIS-NetFxExtensibility;IIS-ASP;IIS-CGI;IIS-ISAPIExtensions;IIS-ISAPIFilter;IIS-ServerSideIncludes;IIS-HealthAndDiagnostics;IIS-HttpLogging;IIS-LoggingLibraries;IIS-RequestMonitor;IIS-HttpTracing;IIS-CustomLogging;IIS-ODBCLogging;IIS-Security;IIS-BasicAuthentication;IIS-WindowsAuthentication;IIS-DigestAuthentication;IIS-ClientCertificateMappingAuthentication;IIS-IISCertificateMappingAuthentication;IIS-URLAuthorization;IIS-RequestFiltering;IIS-IPSecurity;IIS-Performance;IIS-HttpCompressionStatic;IIS-HttpCompressionDynamic;IIS-WebServerManagementTools;IIS-ManagementConsole;IIS-ManagementScriptingTools;IIS-ManagementService;IIS-IIS6ManagementCompatibility;IIS-Metabase;IIS-WMICompatibility;IIS-LegacyScripts;IIS-LegacySnapIn;IIS-FTPPublishingService;IIS-FTPServer;IIS-FTPManagement;WAS-WindowsActivationService;WAS-ProcessModel;WAS-NetFxEnvironment;WAS-ConfigurationAPIPlease advise...

Yog Li,Just one thing to be crystal-clear on your last response: Your saying that I should've added the ammendments to Administration Site and NOT the Default Web site ?

Yog Li,Just one thing to be crystal-clear on your last response: Your saying that I should've added the ammendments to Administration Site and NOT the Default Web site ? Yes, exactly.Besdies, the configuration on IIS 7.0seems no problem.Yog Li - MSFT