none
Windows Deployment Services Server service will not start.

    Question

  • I am experiencing an issue with installing WDS onto my 2008 R2 x64 server.  When I install the role it completes successfully but when I attempt to configure the settings I get an error indicating the service failed to start:

    “The Windows Deployment Services Server service terminated with service-specific error Access is denied”

     

    I am using the domain admin account to complete the install, so I don’t think the issue is related to my account.  Further, the WDS service runs as local system anyway.

    SCCM 2007 R2 SP2 is installed on this box and I need WDS to use the PXE features.  I’m not sure if this is related either.

    The windows Event log sadly doesn’t report much more than the message above:

    Log Name:      System

    Source:        Service Control Manager

    Date:          12/9/2009 3:58:01 PM

    Event ID:      7024

    Task Category: None

    Level:         Error

    Keywords:      Classic

    User:          N/A

    Computer:      pgcsms.domain.com

    Description:

    The Windows Deployment Services Server service terminated with service-specific error Access is denied..

    Event Xml:

    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

      <System>

        <Provider Name="Service Control Manager" Guid="{555908d1-a6d7-4695-8e1e-26931d2012f4}" EventSourceName="Service Control Manager" />

        <EventID Qualifiers="49152">7024</EventID>

        <Version>0</Version>

        <Level>2</Level>

        <Task>0</Task>

        <Opcode>0</Opcode>

        <Keywords>0x8080000000000000</Keywords>

        <TimeCreated SystemTime="2009-12-09T20:58:01.144624000Z" />

        <EventRecordID>12418</EventRecordID>

        <Correlation />

        <Execution ProcessID="584" ThreadID="4048" />

        <Channel>System</Channel>

        <Computer>pgcsms.domain.com</Computer>

        <Security />

      </System>

      <EventData>

        <Data Name="param1">Windows Deployment Services Server</Data>

        <Data Name="param2">%%5</Data>

      </EventData>

    </Event>

     

    Any help would be appreciated!

    Wednesday, December 09, 2009 9:03 PM

All replies

  • Hi,

    See solution in this KB article:

    954410    The WDS server may not start, and an error is logged in the System log when you start the WDS server
    http://support.microsoft.com/default.aspx?scid=kb;EN-US;954410
    Thursday, December 10, 2009 6:22 AM
  • Hi,


    Are there firewall rules in place? 
    Enable WDS tracing and check the logs (%windir%\tracing\wdsserver.log and %windir%\tracing\wdsmgmt.log)

    Hope this helps. 
    Thursday, December 10, 2009 11:51 AM
  • Eric, thanks for your reply.  That KB states:

    This issue occurs if the following conditions are true:
    • The DHCP server and the WDS server are installed on the same computer.
    • The Do not listen on port 67 option is enabled in the DHCP tab.

    I've toggled the "listen on port 67" box and it didn't seem to make a difference in my inability to start the service.  Also the DHCP server is on another machine.


    McLeod, Thank you as well.  This WDS/SCCM box does not have the Windows firewall enabled.  I'll check those logs and report back.

    Thursday, December 10, 2009 2:51 PM
  • McLeod,

    Below is the log.  Any help analyzing it would be appreciated.  Seems there is a problem with the PXE service, which is what I was thinking when I asked about SCCM conflicts.  I do not currently have the PXE role on the SCCM box, but it was at one time.  Are there other areas I should check within SCCM to ensure no conflict?

     

    [3588] 10:10:45: ===>Starting logging of module [WDSServer]

    [3588] 10:10:45: [UDPPorts] Policy: 1, Dynamic Port Range: 64001-65000.

    [3588] 10:10:45: [RPC] Using Tcp Port 5040 for Rpc Calls.

    [3588] 10:10:45: [RPC] Client Impersonation Logging=Disabled

    [3588] 10:10:45: [RPC] Host Name: pgcsms.domain.com

    [3588] 10:10:45: [RPC] NTLM/Kerberos Spn: ldap/pgcsms.domain.com

    [3588] 10:10:45: [RPC] Initialized

    [3360] 10:10:45: [RPC] Server Started.

    [3588] 10:10:45: [BINLSVC][RPC][Ep={5F4FB9F0-C0E3-41C1-AA00-9A7C690AC3A3}] Registered

    [3588] 10:10:45: [BINLSVC] Provider Initialized.

    [3588] 10:10:45: [WDSDDPS][RPC][Ep={FA0A27E1-C2BA-4B3B-94B2-025E82FFAA6D}] Registered

    [3588] 10:10:45: [WDSDDPS][RPC][Ep={011D24AC-CB3A-4739-A339-5D2E1B5306CE}] Registered

    [3588] 10:10:47: [WDSDDPS] Provider Initialized.

    [3588] 10:10:47: [1470][WdsImgSrv] -> WdsProviderInitialize

    [3588] 10:10:47: [1470][WdsImgSrv] GetDSSServer: Domain=

    [3588] 10:10:47: [1471][WdsImgSrv] GetDSServer: Ldap Server=pgcdc1.domain.com

    [3588] 10:10:47: [1471][WdsImgSrv] CLdap::Open: Server=pgcdc1.domain.com, Port=389, DN=

     

    [3588] 10:10:47: [1476][WdsImgSrv] GetDSSServer: Domain=domain.com

    [3588] 10:10:47: [1477][WdsImgSrv] GetDSServer: Ldap Server=pgcdc1.domain.com

    [3588] 10:10:47: [1477][WdsImgSrv] CLdap::Open: Server=pgcdc1.domain.com, Port=389, DN=

     

    [3588] 10:10:47: [1479][WdsImgSrv] -> pInitializeManagement

    [3588] 10:10:47: [1547][WdsImgSrv] <- pInitializeManagement=0

    [3588] 10:10:47: [1547][WdsImgSrv] -> pWdsImgSrvRefreshSettings

    [3588] 10:10:47: [1592][WdsImgSrv] <- pWdsImgSrvRefreshSettings=0

    [3588] 10:10:47: [1597][WdsImgSrv] Image Cache: Refreshing...

    [3588] 10:10:47: [1599][WdsImgSrv] Image Cache: Total 0 Images Found.

    [3588] 10:10:47: [WdsImgSrv][RPC][Ep={D8DEEB5A-EFFD-43B2-99FC-1A8A5921C227}] Registered

    [3588] 10:10:47: [1600][WdsImgSrv] <- WdsProviderInitialize=0

    [3588] 10:10:47: [WdsImgSrv] Provider Initialized.

    [3588] 10:10:48: [WDSMC][RPC][Ep={865BCE30-ACF1-410C-B5ED-142096663914}] Registered

    [3588] 10:10:48: [WDSMC][RPC][Ep={6F13A317-3687-4B54-81A5-504DAA9062FA}] Registered

    [3588] 10:10:48: [WDSMC][UDP][Ep=5041] Registered

    [3588] 10:10:48: UpdEndpoint::UdpEndpoint = 00000000005F79E0

     

    [3588] 10:10:48: [WDSMC][UDP][Ep=10.1.4.124:5041][0x00000000005F79E0] Created

    [3588] 10:10:48: UpdEndpoint::UdpEndpoint = 0000000001527D20

     

    [3588] 10:10:48: [WDSMC][UDP][Ep=::1:5041][0x0000000001527D20] Created

    [3588] 10:10:48: [WDSMC] Provider Initialized.

    [3588] 10:10:48: [d:\w7rtm\base\ntsetup\opktools\wds\wdssrv\server\src\wdsprovider.cpp:144] Expression: , Win32 Error=0x5

    [3588] 10:10:48: [WDSPXE] Initialization Failed (rc=5)

    [3588] 10:10:48: [d:\w7rtm\base\ntsetup\opktools\wds\wdssrv\server\src\wdsprovhdl.cpp:172] Expression: , Win32 Error=0x5

    [3588] 10:10:48: [WDSPXE] Deleted.

    [3588] 10:10:48: [d:\w7rtm\base\ntsetup\opktools\wds\wdssrv\server\src\wdsservice.cpp:178] Expression: , Win32 Error=0x5

    [3588] 10:10:48: [WDSMC][UDP][Ep=10.1.4.124:5041] Deleted.

    [3588] 10:10:48: UpdEndpoint::~UdpEndpoint = 00000000005F79E0

     

    [3588] 10:10:48: [WDSMC][UDP][Ep=::1:5041] Deleted.

    [3588] 10:10:48: UpdEndpoint::~UdpEndpoint = 0000000001527D20

     

    [3588] 10:10:48: [Udp] Listen Shutdown.

    [3360] 10:10:48: [RPC] Server terminated (rc=0)

    [3588] 10:10:48: [RPC] Listen Stopped.

    [3588] 10:10:48: [BINLSVC] Shutting down

    [3588] 10:10:48: [BINLSVC][RPC][Ep={5F4FB9F0-C0E3-41C1-AA00-9A7C690AC3A3}] Closed

    [3588] 10:10:48: -> CBannedGuids::Shutdown

    [3588] 10:10:48: <- CBannedGuids::Shutdown=0

    [3588] 10:10:48: -> CBannedGuids::Shutdown

    [3588] 10:10:48: <- CBannedGuids::Shutdown=0

    [3588] 10:10:48: [BINLSVC] Deleted.

    [3588] 10:10:48: [WDSDDPS] Shutting down

    [3588] 10:10:48: [WDSDDPS][RPC][Ep={FA0A27E1-C2BA-4B3B-94B2-025E82FFAA6D}] Closed

    [3588] 10:10:48: [WDSDDPS][RPC][Ep={011D24AC-CB3A-4739-A339-5D2E1B5306CE}] Closed

    [3588] 10:10:48: [WDSDDPS] Deleted.

    [3588] 10:10:48: [WdsImgSrv] Shutting down

    [3588] 10:10:48: [2547][WdsImgSrv] -> WdsProviderShutdown

    [3588] 10:10:48: [WdsImgSrv][RPC][Ep={D8DEEB5A-EFFD-43B2-99FC-1A8A5921C227}] Closed

    [3588] 10:10:48: [2548][WdsImgSrv] <- WdsProviderShutdown=0

    [3588] 10:10:48: [WdsImgSrv] Deleted.

    [3588] 10:10:48: [WDSMC] Shutting down

    [3588] 10:10:48: [WDSMC][RPC][Ep={865BCE30-ACF1-410C-B5ED-142096663914}] Closed

    [3588] 10:10:48: [WDSMC][RPC][Ep={6F13A317-3687-4B54-81A5-504DAA9062FA}] Closed

    [3588] 10:10:48: [WDSMC][UDP][Ep=5041] Closed

    [3588] 10:10:48: [WDSMC] Deleted.

    [3588] 10:10:48: <===Ending logging of module [WDSServer]

     

    Thursday, December 10, 2009 3:15 PM
  • I just found this post

    http://social.technet.microsoft.com/Forums/en/winserversetup/thread/43e72e0c-45a5-443b-b998-e1f8f100c0df

    seems permissions might have changed with 2008 SP2 which means they might also be different for my R2 install.  I'm going to try the AD permission adjustment they suggest and report back.


    Thursday, December 10, 2009 3:48 PM
  • excellent info thanks for sharing
    my SCCM step by step Guides > http://www.windows-noob.com/forums/index.php?showtopic=1064
    Thursday, December 10, 2009 5:10 PM
    Moderator
  • ok, so it looked like that above link worked. I changed the permissions and was then able to start the service!

    I then re-installed the PXE role.

    Now I rebooted and the service wont start again - same error text in the trace! This is so frusturating. Why did it work after the permissions and now does not?
    Thursday, December 10, 2009 5:46 PM
  • sounds like the permissions are getting changed, have you checked the permissions again on that object in AD ?
    my SCCM step by step Guides > http://www.windows-noob.com/forums/index.php?showtopic=1064
    Thursday, December 10, 2009 6:40 PM
    Moderator
  • That is my next move.  People aren't changing them (too obscure) - what else might it be?  I'll check and post back.
    Thursday, December 10, 2009 7:22 PM
  • Sure enough the permissions were reset.  What could cause this?
    Thursday, December 10, 2009 7:46 PM
  • if you change the permissions again as it is now, then reboot does the problem re-occur ?
    my SCCM step by step Guides > http://www.windows-noob.com/forums/index.php?showtopic=1064
    Thursday, December 10, 2009 8:22 PM
    Moderator
  • it does indeed.  :(  I now am going to change them for a 3rd time.

    UPDATE: I unmarked my previous answer, since it seems the permission resetting is the bigger issue here.
    Mike Crowley: MCT, MCSE, MCTS, MCITP: Enterprise Administrator / Messaging Administrator
    Thursday, December 17, 2009 4:22 PM
  • sorry for bringing this old topic alive...

    is the permissions reset problem fixed?

    i still have to do it after every reboot.

    Friday, June 17, 2011 8:37 AM