Sign in
Microsoft.com
 
System Center Configuration Manager TechCenter
 
 
 
System Center Configuration Manager TechCenter > System Center Configuration Manager Forums > Configuration Manager Operating System Deployment > WDS service fails to start
Ask a questionAsk a question
Search Forums:
 

AnswerWDS service fails to start

  • Tuesday, July 15, 2008 3:32 PMIan Burnell Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote

    Have installed WDS and PXE but the WDS services fails to start on reboot. I have done all the usual things namely

     

    Remove PXE service point

    Remove WDS

    reboot

    Remove remote install directory

    Add WDS (reboot)

    add PXE point

     

    Done this a few time but still get this error. In event log I get two errors

     

    The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID
    {05D1D5D8-18D1-4B83-85ED-A0F99D53C885}
     to the user NT AUTHORITY\SYSTEM SID (S-1-5-18).  This security permission can be modified using the Component Services administrative tool.

    and then

     

    The Windows Deployment Services (WDS) Server service terminated with service-specific error 16389 (0x4005).

     

    Strangely when I log on I can manually start the WDS service no problem and PXE boot works ok - but I'd like to get rid of this problem

     

    I thought I'd cracked it when I saw this article http://support.microsoft.com/kb/927770 because I DID move the server's entry in AD to a different OU. However, I have moved it back and removed/readded the WDS/PXE to no avail. I don't think you can use WDSUTIL with SCCM since its doing all the configuration

     

    any thoughts ?

     

Answers

  • Monday, October 27, 2008 10:44 AMAnonymous8424 Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer
    Sign In to Vote
    0
    Sign In to Vote
    Hello!
    I solve a similar problem by setting a depence from MSSQLSERVER service. After this all work just fine!
     
  • Tuesday, November 04, 2008 12:09 PMAlter-Ego Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer
    Sign In to Vote
    0
    Sign In to Vote

     

    Fredrik

     

    Well, it's certainly an access denied issue.  Within the SMS database you will find a role for the PSP to have the correct permissions within the database.  You'll need to configure this account at the PSP end too and then in my experience these issues go away,

     

All Replies

  • Thursday, July 17, 2008 12:02 AMMoff25 Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote

    Once you manually start the WDS service does it work OK?

     

    If so, then you might have more chance of an answer on another forum that deals with Server OS or the like.

     

    If not, check that the registry is being cleared out when you uninstall WDS. I have seen this before and the only solution (Or the fastest one) was to flatten and rebuild the server.

     

    Good luck

     
  • Thursday, July 17, 2008 2:41 PMIan Burnell Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote

    Yes appears to work ok - done OSD builds etc. no problem

     

    I actually built another server to test and got the same problem

     

    The way I'm building it is to create a named instance called SCCM and also another named instance called WSUS

     

    I'm wondering if its something to do with TCP ports. Has anybody else used the named instances like this?

     

    I didn't realise that TCP ports are dynamically allocatedt so I'm thinking it could SPN issue - I had setup port 1400 on my named SQL account.

     

     
  • Sunday, July 20, 2008 11:37 AMIan Burnell Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote

    Its a strange one. This is from the Application Event Log

     

    An error occurred while trying to initialize provider SMSPXE loaded from D:\Program Files\SMS_CCM\smspxe.dll. If the provider is marked as critical the Windows Deployment Services server will be  shutdown.
     
     Error Information: 0x4005

     

    The account does not seem to be able to load the provider and so the WDSServer process stops.

     

    Yet, if I logon and start it no problem

     

    I've actually rebuilt the server in lab and SQL running under localsystem account to make it nice and simple yet I still get this at restart. As I said if I start the service all appears to work fine - the PXE point repsonds ok

     

    Any thoughts appreciated  - thanks

     

     
  • Monday, July 21, 2008 4:16 AMMoff25 Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote

    This sounds like a permissions issue.

    When the system account is trying to access the DLL it fails but when you log on and try and do it the process works.

     

    Not my area of expertise but that is where I would start looking.

     

     
  • Monday, July 21, 2008 1:05 PMWilliam Bracken Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote

    I have the same exact issue.  After restarting the service manually everything works fine.  Sad

     
  • Wednesday, July 23, 2008 1:45 AMSteve1967 Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote

    Same for me, not sure what is going on.

     

    It was working before and for some reason I am now seeing the same issue.

     

    Manually start the WDS service and all is well.


    Windows Server 2008

    SQL 2005 SP2

    SCCM 2007 SP1

     
  • Wednesday, August 06, 2008 2:59 PMIan Burnell Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote

    Bump - don't know if anybody has an answer for this ?

     

    I completely rebuilt server in lab, Server 2003 R2, SQL2005 SP2 and SCCM 2007 SP1. All perfectly fine until add WDS for the first time and then go into console and setup PXE service point. All sets up perfectly and runs no problem - but reboot and WDS service doen't start.

     

    This is the message I'm getting from smspxe.log

     

    MPDB ERROR - CONNECTION PARAMETERS
    SQL Server Name     : LONSCM01
    SQL Database Name   : SMS_LOS
    Integrated Auth     : True

    MPDB ERROR - EXTENDED INFORMATION
    MPDB Method         : Init()
    MPDB Method HRESULT : 0x80004005
    Error Description   : Cannot open database "SMS_LOS" requested by the login. The login failed.
    OLEDB IID           : {0C733A8B-2A1C-11CE-ADE5-00AA0044773D}
    ProgID              : Microsoft OLE DB Provider for SQL Server

    MPDB ERROR - INFORMATION FROM DRIVER
    SQL Server Name   : LONSCM01
    Native Error no.  : 4060
    Error State       : 1
    Class (Severity)  : 11
    Line number in SP : 1

    Have setup SQL using Local System and also named account with SPN set but still get above message

     

     
  • Wednesday, August 06, 2008 7:37 PMSteve1967 Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote

     

    I have a workaround, as I am runnning Windows Server 2008, I have just set the service to a delayed start and it now starts without a problem
     
  • Friday, August 29, 2008 1:32 PMWilliam Bracken Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote

    BUMP:

     

    I have had this issue in my lab from the get go.  I now have my production server installed and am having the same issue here.  Can anyone from MS explain what causes this and how to fix it?

     

    Server is Windows 2003 SP2 with SCCM SP1, SQL2005 SP2, IIS and WDS.

     

    Thanks!

     

     
  • Monday, October 27, 2008 10:44 AMAnonymous8424 Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer
    Sign In to Vote
    0
    Sign In to Vote
    Hello!
    I solve a similar problem by setting a depence from MSSQLSERVER service. After this all work just fine!
     
  • Monday, October 27, 2008 5:04 PMFredrikSE Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote

    I have a smilar problem. Today I installed the SCCM 2007/SQL 2005 on one machine (SRV001) and the WDS on the other (SRV002). Both are running Server 2008. The PXE service point is installed fine on the WDS machine. But then I get the same problem as many other people in this thread. The WDS service won't start and I think that has something to do why the PXE service point is marked red in SCCM and not operating as it should. By looking at in the smspxe.log I can tell that the default PXE database service account is not working. I went ahead and created a new account in AD which I linked to an account in the SQL database with the db_owner role for the SMS_S02 database. That didn't work out either. I still get the same error. Any ideas what I should try beside installing everything from the beginning?

     

    pxesetup.log from SRV002

     

    <10-27-2008 11:32:24> ====================================================================
    <10-27-2008 11:32:24> SMSPXE Setup Started....
    <10-27-2008 11:32:24> Parameters: \\SRV003\D$\SMS\bin\i386\ROLESE~1.EXE /install /siteserverTongue TiedRV002 SMSPXE
    <10-27-2008 11:32:24> Installing Pre Reqs for SMSPXE
    <10-27-2008 11:32:24>         ======== Installing Pre Reqs for Role SMSPXE ========
    <10-27-2008 11:32:24> Found 2 Pre Reqs for Role SMSPXE
    <10-27-2008 11:32:24> Pre Req MSXML60 found.
    <10-27-2008 11:32:24> No versions of MSXML60 are installed.  Would install new MSXML60.
    <10-27-2008 11:32:24> Enabling MSI logging.  msxml6.msi will log to D:\SMS\logs\msxml6MSI.log
    <10-27-2008 11:32:24> Installing D:\SMS\bin\i386\00000409\msxml6.msi
    <10-27-2008 11:32:25> msxml6.msi exited with return code: 0
    <10-27-2008 11:32:25> msxml6.msi Installation was successful.
    <10-27-2008 11:32:25> Pre Req Wimgapi found.
    <10-27-2008 11:32:25> Wimgapi already installed (Product Code: {721ABC3B-5F12-4332-9C0C-C11424EF666C}). Would not install again.
    <10-27-2008 11:32:25> Pre Req Wimgapi is already installed. Skipping it.
    <10-27-2008 11:32:25>         ======== Completed Installion of Pre Reqs for Role SMSPXE ========
    <10-27-2008 11:32:25> Installing the SMSPXE
    <10-27-2008 11:32:25> Machine is running Windows 2003 SP1 or later. (NTVersion=0X600, ServicePack=1)
    <10-27-2008 11:32:25> WDS Service is installed.
    <10-27-2008 11:32:25> No versions of SMSPXE are installed.  Installing new SMSPXE.
    <10-27-2008 11:32:25> Enabling MSI logging.  pxe.msi will log to D:\SMS\logs\pxeMSI.log
    <10-27-2008 11:32:25> Installing D:\SMS\bin\i386\pxe.msi CCMINSTALLDIR="D:\SMS_CCM" PXEENABLELOGGING=TRUE PXELOGLEVEL=1 PXELOGMAXSIZE=1000000 PXELOGMAXHISTORY=1
    <10-27-2008 11:33:33> pxe.msi exited with return code: 0
    <10-27-2008 11:33:33> Installation was successful.

    pxeperf.log

     

    Failed to open configuration for SmsMP\SMSMP_DAL ccmperf 2008-10-27 11:32:29 4052 (0x0FD4)
    Failed to open configuration for SmsMP\SMSMP_DAL ccmperf 2008-10-27 12:37:37 284 (0x011C)
    Failed to open configuration for SmsMP\SMSMP_DAL ccmperf 2008-10-27 13:45:56 416 (0x01A0)
    Failed to open configuration for SmsMP\SMSMP_DAL ccmperf 2008-10-27 13:47:39 2540 (0x09EC)
    Failed to open configuration for SmsMP\SMSMP_DAL ccmperf 2008-10-27 13:51:05 288 (0x0120)
    Failed to open configuration for SmsMP\SMSMP_DAL ccmperf 2008-10-27 13:52:41 3720 (0x0E88)
    Failed to open configuration for SmsMP\SMSMP_DAL ccmperf 2008-10-27 14:05:54 2612 (0x0A34)
    Failed to open configuration for SmsMP\SMSMP_DAL ccmperf 2008-10-27 14:13:00 220 (0x00DC)
    Failed to open configuration for SmsMP\SMSMP_DAL ccmperf 2008-10-27 14:19:07 3868 (0x0F1C)
    Failed to open configuration for SmsMP\SMSMP_DAL ccmperf 2008-10-27 14:21:56 3028 (0x0BD4)
    Failed to open configuration for SmsMP\SMSMP_DAL ccmperf 2008-10-27 15:07:02 908 (0x038C)
    Failed to open configuration for SmsMP\SMSMP_DAL ccmperf 2008-10-27 15:42:19 1200 (0x04B0)
    Failed to open configuration for SmsMP\SMSMP_DAL ccmperf 2008-10-27 16:01:10 3384 (0x0D38)
    Failed to open configuration for SmsMP\SMSMP_DAL ccmperf 2008-10-27 16:21:38 268 (0x010C)


     

    smspxe.log

    SMSPXE Provider starting
     smspxe 2008-10-27 16:21:38 268 (0x010C)
    ================= PXE Provider loaded. ===================== smspxe 2008-10-27 16:21:38 268 (0x010C)
    Init Policy Provider settings smspxe 2008-10-27 16:21:38 268 (0x010C)
    Machine is running Windows Longhorn. (NTVersion=0X600, ServicePack=1) smspxe 2008-10-27 16:21:38 268 (0x010C)
    Reloading PXE Provider Settings. cached=0 smspxe 2008-10-27 16:21:38 268 (0x010C)
    Loaded PXE settings from reg key HKLM\Software\Microsoft\SMS\Identification:
    SMS Site Settings:
     Server: SRV003
     SiteCode: S02
     Parent SiteCode: <empty>
     smspxe 2008-10-27 16:21:38 268 (0x010C)
    Cannot read the registry value of MACIgnoreListFile (80070002) smspxe 2008-10-27 16:21:38 268 (0x010C)
    Loaded PXE settings from reg key HKLM\Software\Microsoft\SMS\PXE:
    PXE Settings:
        IsActive: Yes
        SupportUnknownMachines: No
        MACIgnoreListFile: <empty>
        ResponseDelay: 0
        CacheExpire: 3600
        HTTP Port: 80
        HTTPS Port: 443
        IISSSLState: 0x0
        BindPolicy: Exclude <empty>
        TRK: <non empty>
        SiteSignCert: <empty>
        Root CA Certs: <empty>
        PXE GUID: 03666e00-d6bc-4825-8abf-904079475824
        PXEPassword: <empty>
     smspxe 2008-10-27 16:21:38 268 (0x010C)
    Loaded TFTP settings from reg key HKLM\System\CurrentControlSet\Services\WDSSERVER\Providers\WDSTFTP:
    TFTP Settings:
     Directory: D:\RemoteInstall
     smspxe 2008-10-27 16:21:38 268 (0x010C)
    MAC Ignore List Filename in registry is empty smspxe 2008-10-27 16:21:38 268 (0x010C)
    Loaded Database settings from reg key HKLM\Software\Microsoft\SMS\PXE:
    Database Settings:
     Server: SRV002
     Database: SMS_S02
     User: testlabb\SCCMDB
     Password: <hidden>
     Use Integrated Security: Yes
     Impersonation Required: Yes
     smspxe 2008-10-27 16:21:38 268 (0x010C)
    PXE Provider Settings Changed smspxe 2008-10-27 16:21:38 268 (0x010C)
    Querying Database for Cert with GUID: 03666e00-d6bc-4825-8abf-904079475824 smspxe 2008-10-27 16:21:38 268 (0x010C)
    inside GetPxeCert SmsPXE 2008-10-27 16:21:38 268 (0x010C)
    Policy Provider settings flushed due to registry change
     smspxe 2008-10-27 16:21:47 704 (0x02C0)
    Reloading PXE Provider Settings. cached=0 smspxe 2008-10-27 16:21:47 704 (0x02C0)
    Loaded PXE settings from reg key HKLM\Software\Microsoft\SMS\Identification:
    SMS Site Settings:
     Server: SRV003
     SiteCode: S02
     Parent SiteCode: <empty>
     smspxe 2008-10-27 16:21:47 704 (0x02C0)
    Cannot read the registry value of MACIgnoreListFile (80070002) smspxe 2008-10-27 16:21:47 704 (0x02C0)
    Loaded PXE settings from reg key HKLM\Software\Microsoft\SMS\PXE:
    PXE Settings:
        IsActive: Yes
        SupportUnknownMachines: No
        MACIgnoreListFile: <empty>
        ResponseDelay: 0
        CacheExpire: 3600
        HTTP Port: 80
        HTTPS Port: 443
        IISSSLState: 0x0
        BindPolicy: Exclude <empty>
        TRK: <non empty>
        SiteSignCert: <empty>
        Root CA Certs: <empty>
        PXE GUID: 03666e00-d6bc-4825-8abf-904079475824
        PXEPassword: <empty>
     smspxe 2008-10-27 16:21:47 704 (0x02C0)
    Loaded TFTP settings from reg key HKLM\System\CurrentControlSet\Services\WDSSERVER\Providers\WDSTFTP:
    TFTP Settings:
     Directory: D:\RemoteInstall
     smspxe 2008-10-27 16:21:47 704 (0x02C0)
    MAC Ignore List Filename in registry is empty smspxe 2008-10-27 16:21:47 704 (0x02C0)
    Loaded Database settings from reg key HKLM\Software\Microsoft\SMS\PXE:
    Database Settings:
     Server: SRV002
     Database: SMS_S02
     User: testlabb\SCCMDB
     Password: <hidden>
     Use Integrated Security: Yes
     Impersonation Required: Yes
     smspxe 2008-10-27 16:21:47 704 (0x02C0)
    PXE Provider Settings Changed smspxe 2008-10-27 16:21:47 704 (0x02C0)
    Querying Database for Cert with GUID: 03666e00-d6bc-4825-8abf-904079475824 smspxe 2008-10-27 16:21:47 704 (0x02C0)
    inside GetPxeCert SmsPXE 2008-10-27 16:21:47 704 (0x02C0)
    CMPDBConnection::Init(): IDBInitialize::Initialize() failed with 0x80004005 SmsPXE 2008-10-27 16:22:42 268 (0x010C)
    ======================================= SmsPXE 2008-10-27 16:22:42 268 (0x010C)

    MPDB ERROR - CONNECTION PARAMETERS
    SQL Server Name     : SRV002
    SQL Database Name   : SMS_S02
    Integrated Auth     : True

    MPDB ERROR - EXTENDED INFORMATION
    MPDB Method         : Init()
    MPDB Method HRESULT : 0x80004005
    Error Description   : [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied.
    OLEDB IID           : {0C733A8B-2A1C-11CE-ADE5-00AA0044773D}
    ProgID              : Microsoft OLE DB Provider for SQL Server

    MPDB ERROR - INFORMATION FROM DRIVER
    Native Error no.  : 17
    Error State       : 1
    Class (Severity)  : 16
     SmsPXE 2008-10-27 16:22:42 268 (0x010C)
    =======================================
     SmsPXE 2008-10-27 16:22:42 268 (0x010C)
    MP: RaiseDBFailureStatusMessage failed to open registry 2 SmsPXE 2008-10-27 16:22:42 268 (0x010C)
    Failed to read PXE DB settings.
    Unspecified error (Error: 80004005; Source: Windows) smspxe 2008-10-27 16:22:42 268 (0x010C)
    PXE Provider failed to read configuration parameters.
    Unspecified error (Error: 80004005; Source: Windows) smspxe 2008-10-27 16:22:42 268 (0x010C)
    Initializing PXEPerfObject. smspxe 2008-10-27 16:22:42 268 (0x010C)
    Reloading PXE Provider Settings. cached=0 smspxe 2008-10-27 16:22:42 268 (0x010C)
    Loaded PXE settings from reg key HKLM\Software\Microsoft\SMS\Identification:
    SMS Site Settings:
     Server: SRV003
     SiteCode: S02
     Parent SiteCode: <empty>
     smspxe 2008-10-27 16:22:42 268 (0x010C)
    Cannot read the registry value of MACIgnoreListFile (80070002) smspxe 2008-10-27 16:22:42 268 (0x010C)
    Loaded PXE settings from reg key HKLM\Software\Microsoft\SMS\PXE:
    PXE Settings:
        IsActive: Yes
        SupportUnknownMachines: No
        MACIgnoreListFile: <empty>
        ResponseDelay: 0
        CacheExpire: 3600
        HTTP Port: 80
        HTTPS Port: 443
        IISSSLState: 0x0
        BindPolicy: Exclude <empty>
        TRK: <non empty>
        SiteSignCert: <empty>
        Root CA Certs: <empty>
        PXE GUID: 03666e00-d6bc-4825-8abf-904079475824
        PXEPassword: <empty>
     smspxe 2008-10-27 16:22:42 268 (0x010C)
    Loaded TFTP settings from reg key HKLM\System\CurrentControlSet\Services\WDSSERVER\Providers\WDSTFTP:
    TFTP Settings:
     Directory: D:\RemoteInstall
     smspxe 2008-10-27 16:22:42 268 (0x010C)
    MAC Ignore List Filename in registry is empty smspxe 2008-10-27 16:22:42 268 (0x010C)
    Loaded Database settings from reg key HKLM\Software\Microsoft\SMS\PXE:
    Database Settings:
     Server: SRV002
     Database: SMS_S02
     User: testlabb\SCCMDB
     Password: <hidden>
     Use Integrated Security: Yes
     Impersonation Required: Yes
     smspxe 2008-10-27 16:22:42 268 (0x010C)
    PXE Provider Settings Changed smspxe 2008-10-27 16:22:42 268 (0x010C)
    Querying Database for Cert with GUID: 03666e00-d6bc-4825-8abf-904079475824 smspxe 2008-10-27 16:22:42 268 (0x010C)
    inside GetPxeCert SmsPXE 2008-10-27 16:22:42 268 (0x010C)
    CMPDBConnection::Init(): IDBInitialize::Initialize() failed with 0x80004005 SmsPXE 2008-10-27 16:22:42 268 (0x010C)
    ======================================= SmsPXE 2008-10-27 16:22:42 268 (0x010C)

    MPDB ERROR - CONNECTION PARAMETERS
    SQL Server Name     : SRV002
    SQL Database Name   : SMS_S02
    Integrated Auth     : True

    MPDB ERROR - EXTENDED INFORMATION
    MPDB Method         : Init()
    MPDB Method HRESULT : 0x80004005
    Error Description   : [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied.
    OLEDB IID           : {0C733A8B-2A1C-11CE-ADE5-00AA0044773D}
    ProgID              : Microsoft OLE DB Provider for SQL Server

    MPDB ERROR - INFORMATION FROM DRIVER
    Native Error no.  : 17
    Error State       : 1
    Class (Severity)  : 16
     SmsPXE 2008-10-27 16:22:42 268 (0x010C)
    =======================================
     SmsPXE 2008-10-27 16:22:42 268 (0x010C)
    MP: RaiseDBFailureStatusMessage failed to open registry 2 SmsPXE 2008-10-27 16:22:42 268 (0x010C)
    Failed to read PXE DB settings.
    Unspecified error (Error: 80004005; Source: Windows) smspxe 2008-10-27 16:22:42 268 (0x010C)
    Failed to retrieve database settings.
    Unspecified error (Error: 80004005; Source: Windows) smspxe 2008-10-27 16:22:42 268 (0x010C)
    PXE Provider failed to initialize database connection.
    Unspecified error (Error: 80004005; Source: Windows) smspxe 2008-10-27 16:22:42 268 (0x010C)
    Reloading PXE Provider Settings. cached=0 smspxe 2008-10-27 16:22:42 268 (0x010C)
    Loaded PXE settings from reg key HKLM\Software\Microsoft\SMS\Identification:
    SMS Site Settings:
     Server: SRV003
     SiteCode: S02
     Parent SiteCode: <empty>
     smspxe 2008-10-27 16:22:42 268 (0x010C)
    Cannot read the registry value of MACIgnoreListFile (80070002) smspxe 2008-10-27 16:22:42 268 (0x010C)
    Loaded PXE settings from reg key HKLM\Software\Microsoft\SMS\PXE:
    PXE Settings:
        IsActive: Yes
        SupportUnknownMachines: No
        MACIgnoreListFile: <empty>
        ResponseDelay: 0
        CacheExpire: 3600
        HTTP Port: 80
        HTTPS Port: 443
        IISSSLState: 0x0
        BindPolicy: Exclude <empty>
        TRK: <non empty>
        SiteSignCert: <empty>
        Root CA Certs: <empty>
        PXE GUID: 03666e00-d6bc-4825-8abf-904079475824
        PXEPassword: <empty>
     smspxe 2008-10-27 16:22:42 268 (0x010C)
    Loaded TFTP settings from reg key HKLM\System\CurrentControlSet\Services\WDSSERVER\Providers\WDSTFTP:
    TFTP Settings:
     Directory: D:\RemoteInstall
     smspxe 2008-10-27 16:22:42 268 (0x010C)
    MAC Ignore List Filename in registry is empty smspxe 2008-10-27 16:22:42 268 (0x010C)
    Loaded Database settings from reg key HKLM\Software\Microsoft\SMS\PXE:
    Database Settings:
     Server: SRV002
     Database: SMS_S02
     User: testlabb\SCCMDB
     Password: <hidden>
     Use Integrated Security: Yes
     Impersonation Required: Yes
     smspxe 2008-10-27 16:22:42 268 (0x010C)
    PXE Provider Settings Changed smspxe 2008-10-27 16:22:42 268 (0x010C)
    Querying Database for Cert with GUID: 03666e00-d6bc-4825-8abf-904079475824 smspxe 2008-10-27 16:22:42 268 (0x010C)
    inside GetPxeCert SmsPXE 2008-10-27 16:22:42 268 (0x010C)
    CMPDBConnection::Init(): IDBInitialize::Initialize() failed with 0x80004005 SmsPXE 2008-10-27 16:22:42 268 (0x010C)
    ======================================= SmsPXE 2008-10-27 16:22:42 268 (0x010C)

    MPDB ERROR - CONNECTION PARAMETERS
    SQL Server Name     : SRV002
    SQL Database Name   : SMS_S02
    Integrated Auth     : True

    MPDB ERROR - EXTENDED INFORMATION
    MPDB Method         : Init()
    MPDB Method HRESULT : 0x80004005
    Error Description   : [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied.
    OLEDB IID           : {0C733A8B-2A1C-11CE-ADE5-00AA0044773D}
    ProgID              : Microsoft OLE DB Provider for SQL Server

    MPDB ERROR - INFORMATION FROM DRIVER
    Native Error no.  : 17
    Error State       : 1
    Class (Severity)  : 16
     SmsPXE 2008-10-27 16:22:42 268 (0x010C)
    =======================================
     SmsPXE 2008-10-27 16:22:42 268 (0x010C)
    MP: RaiseDBFailureStatusMessage failed to open registry 2 SmsPXE 2008-10-27 16:22:42 268 (0x010C)
    Failed to read PXE DB settings.
    Unspecified error (Error: 80004005; Source: Windows) smspxe 2008-10-27 16:22:42 268 (0x010C)
    Failed to initialize PXE Provider.
    Unspecified error (Error: 80004005; Source: Windows) smspxe 2008-10-27 16:22:42 268 (0x010C)
    Failed to initialize PXE provider.
    Unspecified error (Error: 80004005; Source: Windows) smspxe 2008-10-27 16:22:42 268 (0x010C)

    /Fredrik

     
  • Tuesday, November 04, 2008 12:09 PMAlter-Ego Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer
    Sign In to Vote
    0
    Sign In to Vote

     

    Fredrik

     

    Well, it's certainly an access denied issue.  Within the SMS database you will find a role for the PSP to have the correct permissions within the database.  You'll need to configure this account at the PSP end too and then in my experience these issues go away,

     
  • Monday, December 08, 2008 1:55 PMMichael140 Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    I had to reinstall WDS and PXE role but it didn't went on. And if I manually start the service it wouldn't start. Everytime the same error. It's always this stupid "binlsvc.dll" that won't start
    The solution for me was to configure WDS with "wdsutil /initialize-server /reminst:{RemoteInstallFolder}" which started WDS but that's a solution that I don't want. It's not a solution, it's a workaround and it's not clean.
    I can say it's a temporary solution.

    If anybody has the REAL solution, please tell me
     
  • Monday, December 08, 2008 2:20 PMFredrikSE Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote

    Are you installing SCCM/WDS on one or two machines?

     

    When I set up my system I used two separate machines for the SCCM and the WDS. With this configuration I just let the SCCM configure the PXE role on the WDS with the right credentials, and that worked fine.

     

    But when I was to install a single-box-machine with all the roles on the same machine I discovered that I needed to manually configure the WDS (configure the pxe delay for instance) first and then via SCCM install the PXE role, for it to work. A little bit strange I think.

     
  • Monday, December 08, 2008 4:42 PMMichael140 Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    What is as follows

    A parent site A with a working MP, PXE role and WDS install on it. Also connected to an SQL 2005 and also a separated WSUS server. Working fine

    A secondary site B with a working MP, PXE and WDS install that is working fine.

    A secondary site C with not anymore working MP, PXE role and WDS install and was working fine. Everything started when we changed site C to a different ip address. The roles weren't anymore good. I then deleted the whole server and reinstalled from 0. When I was finally there to install WDS it all started over again. The PXE role was shitty because the WDS wouldn't start normally + MP

    I always followed the same install procedure -> install SCCM -> install SP1 -> install WDS -> install MP and PXE roles.

    But it ain't working anymore and I don't know why. Looked over and over in the logs. I can post some logs if you want