Wednesday, 21 August 2013

WSUS Service will not start Error 193: 0xc1

I had this problem today.

Config Mgr 2012 SP1 CU2
Windows Server 2012
SQL 2012 SP1

Software updating was not working correctly and there were errors in the ConfigMgr console


Component Status


Site Status


wsyncmgr.log file showed WSUS errors


WSUSCtrl.log file showed errors


Event log showed that the WSUS Service could not start with the following error:

The WSUS Service failed to start due to the following error:
WSUS Service is not a valid Win32 application


WSUS Service could not be started:


Could not start the %{Service} service on local computer.
Error 193: 0xc1



It seems that this was the result of a rogue file on the C: drive of the server (C:\Program)

I don't know how the file was created but this blog post pointed me in the right direction

http://ibus.kayako.com/Knowledgebase/Article/View/16/0/cannot-start-the-service-on-local-computer--error-1930xc1-services-cannot-be-started-or-scheduled-backup-missed

Here is an extract:

This issue occurs when one or both of the following conditions is true:

There is a file named 'Program' in your SystemDrive folder.
There is a file named 'Common' in your ProgramFiles folder.

When Windows Service Control Manager (Services.exe) tries to start the Server service, the program verifies the following paths:

SystemDrive\Program
Program Files\Common

If the Program or Common paths exist as files, the Service Control Manager cannot locate the required folders, you will receive the error messages and event ID messages that are listed in the Problem Description section of this article.


I renamed the file


and was able to start the service.



Problem solved

15 comments:

  1. Excellent post this post saved my life thanks buddy

    Regards,
    Vamshi

    ReplyDelete
  2. This typically happens because of an issue with the path to the service binary. If this path contains spaces such as in "Program Files", it may lead to this "ghost" file being created in the corresponding parent folder.

    To be sure that the service looks at the right location, you can edit the "ImagePath" key for the service in the Windows registry. This way the service won't be confused by such a file and should start up as expected.

    The ImagePath key can be found here:
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\

    To fix the problem, add double quotes to the path.

    ReplyDelete
  3. I hace this issue: "2014-04-04 11:16:38 Postinstall started
    2014-04-04 11:16:38 Detected role services: Api, Database, UI, Services
    2014-04-04 11:16:38 Start: LoadSettingsFromParameters
    2014-04-04 11:16:38 Content local is: True
    2014-04-04 11:16:38 Content directory is: E:\Source\Updates
    2014-04-04 11:16:38 SQL instname is: MX-DBSYSCENT-01\SCCM
    2014-04-04 11:16:38 End: LoadSettingsFromParameters
    2014-04-04 11:16:39 Start: Run
    2014-04-04 11:16:39 Configuring content directory...
    2014-04-04 11:16:39 Configuring groups...
    2014-04-04 11:16:39 Starting group configuration for WSUS Administrators...
    2014-04-04 11:16:39 Found group in regsitry, attempting to use it...
    2014-04-04 11:16:41 Writing group to registry...
    2014-04-04 11:16:41 Finished group creation
    2014-04-04 11:16:41 Starting group configuration for WSUS Reporters...
    2014-04-04 11:16:41 Found group in regsitry, attempting to use it...
    2014-04-04 11:16:41 Writing group to registry...
    2014-04-04 11:16:41 Finished group creation
    2014-04-04 11:16:41 Configuring permissions...
    2014-04-04 11:16:41 Fetching content directory...
    2014-04-04 11:16:41 Fetching ContentDir from registry store
    2014-04-04 11:16:41 Value is E:\Source\Updates
    2014-04-04 11:16:41 Fetching group SIDs...
    2014-04-04 11:16:41 Fetching WsusAdministratorsSid from registry store
    2014-04-04 11:16:41 Value is S-1-5-21-1609399286-214871114-315836718-1007
    2014-04-04 11:16:41 Fetching WsusReportersSid from registry store
    2014-04-04 11:16:41 Value is S-1-5-21-1609399286-214871114-315836718-1008
    2014-04-04 11:16:41 Creating group principals...
    2014-04-04 11:16:41 Granting directory permissions...
    2014-04-04 11:16:41 System.UnauthorizedAccessException: Attempted to perform an unauthorized operation.
    at System.Security.AccessControl.Win32.SetSecurityInfo(ResourceType type, String name, SafeHandle handle, SecurityInfos securityInformation, SecurityIdentifier owner, SecurityIdentifier group, GenericAcl sacl, GenericAcl dacl)
    at System.Security.AccessControl.NativeObjectSecurity.Persist(String name, SafeHandle handle, AccessControlSections includeSections, Object exceptionContext)
    at System.Security.AccessControl.FileSystemSecurity.Persist(String fullPath)
    at System.IO.DirectoryInfo.SetAccessControl(DirectorySecurity directorySecurity)
    at Microsoft.UpdateServices.Administration.ConfigurePermissions.GrantDirectoryPermissions()
    at Microsoft.UpdateServices.Administration.ConfigurePermissions.Configure()
    at Microsoft.UpdateServices.Administration.PostInstall.Run()
    at Microsoft.UpdateServices.Administration.PostInstall.Execute(String[] arguments)"

    This occurs then install wsus role on Windows server 2012'

    Any idea?

    Help!!

    ReplyDelete
  4. This post has just saved our mail server, thank you so much!

    David

    ReplyDelete
  5. This is awesome Gerry. This blog helps me and save my lots of time. Really great.
    Thanks Shankar.

    ReplyDelete
  6. I found that each time I uninstalled and reinstalled WSUS, I would get a new "program" file that would ask me to rename the file upon booting back into windows.

    ReplyDelete
  7. You sir... are awesome!!
    THANKS

    ReplyDelete
  8. Thanks, that worked perfect......

    ReplyDelete
  9. Hat's off to you Gerry..... MS's latest WSUS stuff up caused me to reinstall WSUS from scratch on my SCCM server: https://redmondmag.com/articles/2016/08/08/sccm-requires-patch.aspx

    This saved me having to rebuild the server from scratch.... much appreciated

    ReplyDelete