Note: Forums will be making significant UX changes to address key usability improvements surrounding search, discoverability and navigation. To learn more about these changes please visit the announcement which can be found HERE.
WDSServer (Windows Deployment Server) Fails to Start

Answered WDSServer (Windows Deployment Server) Fails to Start

  • martedì 1 novembre 2011 14:40
     
     

    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

Tutte le risposte

  • martedì 1 novembre 2011 16:00
     
     Con risposta

    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.


    • Contrassegnato come risposta Rob-HPC martedì 1 novembre 2011 16:00
    • Modificato Rob-HPC martedì 1 novembre 2011 16:42
    •  
  • martedì 30 ottobre 2012 09:18
     
     

    support.microsoft.com/kb/2121690

    download this hotfix, you can solve it.