none
WDSServer (Windows Deployment Server) Fails to Start RRS feed

  • Question

  • WDS will not start on the Head node.  The guy who set it up, I think manually installed the WDS Service, and included the Deployment role?  I've uninstalled that, and now only have the transport role installed.  That's all that was installed in my lab enviornment when I did a fresh install.  Every time I try to start the service I see the following errors:

     

    Application Log:

    An error occurred while trying to start the Windows Deployment Services server.  Error Information: 0x8009000F

     

    System Log:

    The Windows Deployment Services Server service terminated with service-specific error %%-2146893809.

     

    Applications and Services Logs/Microsoft/HPC/Management/Admin:

    Error 6005: Failed to start service Windows Deployment Services Server. Time out has expired and the operation has not been completed. Check the event log for further information.

     

    I enabled tracing on the WDSServer and collected this entry from the WDSServer.LOG (c:\windows\tracing) [9536] 10:14:38: <===Ending logging of module [WDSServer] [10080] 10:16:08: ===>Starting logging of module [WDSServer] [10080] 10:16:08: [UDPPorts] Policy: 0, Dynamic Port Range: 64001-65000.

    [10080] 10:16:08: [RPC] Using Tcp Port 5040 for Rpc Calls.

    [10080] 10:16:08: [RPC] Client Impersonation Logging=Disabled [10080] 10:16:08: [RPC] Host Name: etp-h1.portal.arl.hpc.mil [10080] 10:16:08: [RPC] NTLM/Kerberos Spn: ldap/etp-h1.portal.arl.hpc.mil [10080] 10:16:08: [RPC] Initialized [1880] 10:16:08: [RPC] Server Started.

    [10080] 10:16:08: [d:\w7rtm\base\ntsetup\opktools\wds\wdssrv\server\src\wdsvsswriter.cpp:508] Expression: , Win32 Error=0x800401f3 [10080] 10:16:08: The WDS Management API isn't registered on the server which indicates that the Deployment Server role isn't installed.

    [10080] 10:16:08: We are not running under Deployment Server. Not Pre-initialzing VSS Writer [10080] 10:16:09: [d:\w7rtm\base\ntsetup\opktools\wds\wdssrv\server\src\wdsprovider.cpp:144] Expression: , Win32 Error=0x8009000f [10080] 10:16:09: [WDSMC] Initialization Failed (rc=2148073487) [10080] 10:16:09: [d:\w7rtm\base\ntsetup\opktools\wds\wdssrv\server\src\wdsprovhdl.cpp:172] Expression: , Win32 Error=0x8009000f [10080] 10:16:09: [WDSMC] Deleted.

    [10080] 10:16:09: [d:\w7rtm\base\ntsetup\opktools\wds\wdssrv\server\src\wdsservice.cpp:178] Expression: , Win32 Error=0x8009000f [10080] 10:16:09: [Udp] Listen Shutdown.

    [1880] 10:16:09: [RPC] Server terminated (rc=0) [10080] 10:16:09: [RPC] Listen Stopped.

    [10080] 10:16:09: <===Ending logging of module [WDSServer]

    ([d:\w7rtm\base\ntsetup\opktools\wds\wdssrv\server\src\wdsservice.cpp:178] source code paths, not really related to the issue directly, other than a line of code with the issue) 

    Hopefully someone might have some ideas...  Thanks!

    Rob

    Tuesday, November 1, 2011 2:40 PM

Answers

  • We ran into a similar problem it turns out a while back, and were getting access denied on files in the C:\ProgramData\Microsoft\Crypto\RSA\S-1-5-18 folder.  For whatever reason, the System account didn't have full control of this folder and the files inside, 58aaa1dc6dc8f3c60d7f532fad0b97a4_21ea7910-74e6-48e6-9b9a-fa1f8444c207 is part of WDSServer.  Once I granted permissions to this file, the WDS Server started itself right up.

    Process Monitor saved the day on this one.


    • Marked as answer by Rob-HPC Tuesday, November 1, 2011 4:00 PM
    • Edited by Rob-HPC Tuesday, November 1, 2011 4:42 PM
    Tuesday, November 1, 2011 4:00 PM

All replies

  • We ran into a similar problem it turns out a while back, and were getting access denied on files in the C:\ProgramData\Microsoft\Crypto\RSA\S-1-5-18 folder.  For whatever reason, the System account didn't have full control of this folder and the files inside, 58aaa1dc6dc8f3c60d7f532fad0b97a4_21ea7910-74e6-48e6-9b9a-fa1f8444c207 is part of WDSServer.  Once I granted permissions to this file, the WDS Server started itself right up.

    Process Monitor saved the day on this one.


    • Marked as answer by Rob-HPC Tuesday, November 1, 2011 4:00 PM
    • Edited by Rob-HPC Tuesday, November 1, 2011 4:42 PM
    Tuesday, November 1, 2011 4:00 PM
  • support.microsoft.com/kb/2121690

    download this hotfix, you can solve it.

    Tuesday, October 30, 2012 9:18 AM
  • Fixed my issue. Great work.
    Tuesday, July 23, 2013 4:27 AM
  • Thank You Rob-HPC

    I now realized after seeing that path to C:\ProgramData\Microsoft\Crypto\RSA\S-1-5-18 folder in this article, that I'd wasted 3-4 hours today, and likely broke imaging from our SCCM 2012 RTM server for about a week unknowingly, because I'd browsed this C:\ProgramData\Microsoft\Crypto\RSA\S-1-5-18 folder after researching updating our soon to expire DP self-signed certificate to find this Microsoft kb from http://support.microsoft.com/kb/2713467/en-us When I browsed to the folder path C:\ProgramData\Microsoft\Crypto\RSA\S-1-5-18 on our SCCM 2012 RTM server running Microsoft Windows Server 2008 R2 Enterprise it modified the security so that I had exclusive rights.  That's when I'd set in motion this issue that would rare it's ugly head when a fellow coworker said she could no longer PXE boot and image a system using unknown computer OSD task sequence close to a week later.  We no longer could image any systems and we're getting the PXE-E53: No boot filename received

    I'd checked over the event logs, and initially could not see any obvious issues.  WDS was running on the server, and had no errors either.  I checked the C:\Program Files\SMS_CCM\Logs\SMSPXE.log file and found a ton of some VERY weird messages.  What the heck was this:

    Out of 1 certs, there is none that has valid keys. SMSPXE 9/4/2013 4:44:17 PM 3732 (0x0E94)
    PXE::DB_InitializeTransport failed; 0x80092004 SMSPXE 9/4/2013 4:44:17 PM 3732 (0x0E94)
    PXE::DB_LookupDevice failed; 0x80092004 SMSPXE 9/4/2013 4:44:17 PM 3732 (0x0E94)
    Out of 1 certs, there is none that has valid keys. SMSPXE 9/4/2013 4:44:17 PM 3732 (0x0E94)
    PXE::DB_InitializeTransport failed; 0x80092004 SMSPXE 9/4/2013 4:44:17 PM 3732 (0x0E94)
    PXE::DB_ReportStatus failed; 0x80092004 SMSPXE 9/4/2013 4:44:17 PM 3732 (0x0E94)
    PXE Provider failed to process message.
    Cannot find object or property. (Error: 80092004; Source: Windows) SMSPXE 9/4/2013 4:44:17 PM 3732 (0x0E94)

    This was the first sign of an issue on our SCCM 2012 RTM server.  This looked like a certificate issue.

    I tried restarting WDS, then it would not start up again.  Tried restarting the server, still Windows Deployment Services would not start up.  Last ditch effort, though I doubted this would help.  Shut down the server altogether, brought it back up, still Windows Deployment Services would not start up.  Just seeing some new errors with WDS events now:

    Log Name:      System
    Source:        Service Control Manager
    Date:          9/4/2013 6:23:01 PM
    Event ID:      7024
    Task Category: None
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:     
    Description:
    The Windows Deployment Services Server service terminated with service-specific error %%-2146893809.

    Log Name:      Application
    Source:        WDSServer
    Date:          9/4/2013 6:23:01 PM
    Event ID:      257
    Task Category: WDSServer
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:     
    Description:
    An error occurred while trying to start the Windows Deployment Services server.
     
     Error Information: 0x8009000F
    Log Name:      Application
    Source:        WDSServer
    Date:          9/4/2013 6:23:01 PM
    Event ID:      513
    Task Category: WDSServer
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:     
    Description:
    An error occurred while trying to initialize provider WDSMC from C:\Windows\system32\wdsmc.dll. Windows Deployment Services server will be shutdown.
     
     Error Information: 0x8009000F

    Luckily I found this article before I went down too many more paths and more wasted time.  It's too bad that there's not one resource where all the specific details are documented about this product can be found.

    All I had to do to resolve the PXE-E53: No boot filename received issue was to modify the permission on the folder C:\ProgramData\Microsoft\Crypto\RSA\S-1-5-18 so that SYSTEM account had FULL, and set replace all child objects, then restarted the Windows Deployment Services. No more errors in C:\Program Files\SMS_CCM\Logs\SMSPXE.log or event logs related to Windows Deployment Services.  Verified that PXE point was now working.

    Yeah!!!  Long story short, be mindful of Microsoft Windows Server 2008 R2 Enterprise enhanced security in the GUI when browsing some system folders.  Don't forget to change security back. 

    Now, time to rest.


    • Edited by swimmer74 Thursday, September 5, 2013 7:47 AM mispelling
    Thursday, September 5, 2013 7:45 AM
  • saved my day! thanks
    Wednesday, June 14, 2017 6:34 PM