Quantcast
Channel: Configuration Manager 2012 - Security, Updates and Compliance forum
Viewing all articles
Browse latest Browse all 6382

WSUS Post Deployment Configuration Failure - HTTP Error 405

$
0
0

Hi all,

I recently graduated college and attained my first job in the IT realm.  I am lucky enough to get to work with System Center here at work.  When I started I realized updates were not deploying and have not been since around when the system was upgraded to MSSC 2012 SP1.  Currently we Have a 2008 R2 WSUS  server, a configuration manager server that points to the WSUS server as an upstream server ( I have double checked ports fyi, and it is not configured for SSL ), and a Group Policy that brings it all together ( which is definitely applying correctly as far as I can see with RSOP / GPRESULT).  

The 2008 R2 WSUS server was due for an update so I created  2012 R2 server for WSUS  (Plus for some unsightly reason none of the PC'S were checking in and hadn't in around 600 days).  I have wsus installed and configured 'properly'.  It is syncing with microsoft and computers are checking in, yada yada. 

However, in configuration manager, many of my components are failing.  I have done massive amounts of google and taken many steps to mitigate this issue.  The logs are helpful but they don't paint the best picture.

The following components are in critical or warning status.

SMS_DISTRIBUTION_MANAGER  -  CRITICAL

SMS_WSUS_CONFIGURATION_MANAGER  -  WARNING

SMS_WSUS_SYNC_MANAGER  -  WARNING

SMS_PORTALWEB_CONTROL_MANAGER  -  WARNING

SMS_AWEBSVC_CONTROL_MANAGER  -  WARNING

I think the main reason why my WSUS components are failing is because the post deployment configuration will not launch.    I tried to run this command in an elevated powershell session "%programfiles%\update services\tools\wsusutil.exe postinstall CONTENT_DIR=C:\Wsus"

I got a message saying post install is starting.. the log file is here.. It never finished installing so I took a look at the log file where I find this:

2014-08-27 11:48:36  Instantiating UpdateServer
2014-08-27 11:48:38  CreateDefaultSubscription failed. Exception: System.Net.WebException: The request failed with HTTP status 405: Method Not Allowed.
   at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
   at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
   at Microsoft.UpdateServices.Internal.ApiRemoting.GetServerVersion()
   at Microsoft.UpdateServices.Internal.DatabaseAccess.AdminDataAccessProxy.GetServerVersion()
   at Microsoft.UpdateServices.Internal.BaseApi.UpdateServer.CreateUpdateServer(String serverName, Boolean useSecureConnection, Int32 portNumber)
   at Microsoft.UpdateServices.Internal.BaseApi.UpdateServer..ctor(Boolean bypassApiRemoting)
   at Microsoft.UpdateServices.Setup.StartServer.StartServer.CreateDefaultSubscription()
2014-08-27 11:48:38  StartServer encountered errors. Exception=The request failed with HTTP status 405: Method Not Allowed.
2014-08-27 11:48:38  Microsoft.UpdateServices.Administration.CommandException: Failed to start and configure the WSUS service
   at Microsoft.UpdateServices.Administration.PostInstall.Run()
   at Microsoft.UpdateServices.Administration.PostInstall.Execute(String[] arguments)

I have configuration manager pointed to my new server using port 8530.  I am running out of ideas!  I have tried restarting the IIS services and sites, the WSUS services, and a bunch of other stuff.  

Please help!!!!!!!!!!!!!! TIA!


Viewing all articles
Browse latest Browse all 6382

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>