2 Replies Latest reply on Oct 14, 2014 1:43 PM by emcphail

    Install Provisioning Agent fails in 9.5 SP2

    emcphail Rookie

      We are seeing all of our images fail like clockwork at the "Install Provisioning Agent" action with a return error code of 1603 (MSG_ERROR_INSTALL_FAILURE).   I've turned on logging, and sure enough it's all going pear shaped during that action.

       

      From the ldprovision log I can cull the following information:

       

      2014-10-13 19:53:09(2788-2792) ldProvision.exe:*********  Begin an action - Configure_agent

      2014-10-13 19:53:09(2788-2792) ldProvision.exe:Do EnvironmentCheck

      2014-10-13 19:53:09(2788-2792) ldProvision.exe:Is WinPE Action=0, Is WinPe Environment=0

      2014-10-13 19:53:09(2788-2792) ldProvision.exe:Report might reboot status to core.

      2014-10-13 19:53:09(2788-2792) ldProvision.exe:Call web service SetActionStatus()

      2014-10-13 19:53:09(2788-2792) ldProvision.exe:Start TryallWebService Attempt:0.

      2014-10-13 19:53:10(2788-2792) ldProvision.exe:End TryallWebService Attempt:0. ExitCode:0

      2014-10-13 19:53:10(2788-2792) ldProvision.exe:Session Data: <variables/>

      2014-10-13 19:53:10(2788-2792) ldProvision.exe:Create process (C:\Program Files (x86)\LANDesk\Shared Files\httpclient.exe) with args (  -f "C:\ldprovisioning\ConfigHandler.exe" http://<CORE>/LdLogon/Provisioning/windows/ConfigHandler.exe)

      2014-10-13 19:53:12(2788-2792) ldProvision.exe:Process exit code:0

      2014-10-13 19:53:12(2788-2792) ldProvision.exe:The file (C:\ldprovisioning\ConfigHandler.exe) was successfully downloaded

      2014-10-13 19:53:12(2788-2792) ldProvision.exe:Download handler ok.

      2014-10-13 19:53:12(2788-2792) ldProvision.exe:Launching action handler [ConfigHandler.exe] with parameters ["]

      2014-10-13 19:53:12(2788-2792) ldProvision.exe:handler launched.

      2014-10-13 20:00:05(2788-2792) ldProvision.exe:Reporting action status: 5 to core

      2014-10-13 20:00:05(2788-2792) ldProvision.exe:Call web service GetStatusString()

      2014-10-13 20:00:05(2788-2792) ldProvision.exe:Start TryallWebService Attempt:0.

      2014-10-13 20:00:05(2788-2792) ldProvision.exe:End TryallWebService Attempt:0. ExitCode:0

      2014-10-13 20:00:05(2788-2792) ldProvision.exe:StatusString = The action failed.

      2014-10-13 20:00:05(2788-2792) ldProvision.exe:Call web service SetActionStatus()

      2014-10-13 20:00:05(2788-2792) ldProvision.exe:Start TryallWebService Attempt:0.

      2014-10-13 20:00:06(2788-2792) ldProvision.exe:End TryallWebService Attempt:0. ExitCode:0

      2014-10-13 20:00:06(2788-2792) ldProvision.exe:End of action - Configure_agent

      2014-10-13 20:00:06(2788-2792) ldProvision.exe:Last action failed

      2014-10-13 20:00:06(2788-2792) ldProvision.exe:**********************************  End processing actions  **********************************

      2014-10-13 20:00:06(2788-2792) ldProvision.exe:ldProvision ended

       

      I followed the thread to the ConfigHandler log, which tells me pretty much the same thing.

       

       

      2014-10-13 19:53:12(1756-3056) ConfigHandler.exe:Got core name: <CORE>

      2014-10-13 19:53:12(1756-3056) ConfigHandler.exe:Got config tool: wscfg32.exe

      2014-10-13 19:53:12(1756-3056) ConfigHandler.exe:Got configuration file: Windows Provisioning Agent

      2014-10-13 19:53:12(1756-3056) ConfigHandler.exe:Got user: <CORE>\ldadmin

      2014-10-13 19:53:12(1756-3056) ConfigHandler.exe:password is not variable, encrypted

      2014-10-13 19:53:12(1756-3056) ConfigHandler.exe:Mapping Drive

      2014-10-13 19:53:12(1756-3056) ConfigHandler.exe:Going to connect

      2014-10-13 19:53:12(1756-3056) ConfigHandler.exe:Going to decrypt password

      2014-10-13 19:53:12(1756-3056) ConfigHandler.exe:going to try and connect to [] \\<CORE>\ldlogon with <DOMAIN>\ldadmin

      2014-10-13 19:53:12(1756-3056) ConfigHandler.exe:going to execute \\<CORE>\ldlogon\wscfg32.exe /f /L /NOUI /NOREBOOT /C="Windows Provisioning Agent.ini"

      2014-10-13 20:00:05(1756-3056) ConfigHandler.exe:system() return 1603

       

       

      I can ping the CORE from this machine after it fails, but I understand that using the FQDN is best practice.   Based on the logs, it's not using the FQDN.   Could this be the source of the problem, and if so where should I make the change?  I've been through the Provisioning template and can't see any point where I only have the CORE listed.  The same goes for the Windows Provisioning Agent.   I've also rebuilt the agents, to no effect.

       

      Any ideas?

       

        • 1. Re: Install Provisioning Agent fails in 9.5 SP2
          Apprentice

          Any WSCONFIG32.xlg logs in C:\Windows\Temp?

          • 2. Re: Install Provisioning Agent fails in 9.5 SP2
            emcphail Rookie

            As a matter of fact, YES!   I keep forgetting that the logs are all over the place in 9.5 SP2, something I understand they've worked to correct in 9.6.

             

            Scrolling through it, the only CRITICALERROR that jumps out immediately is regarding the BrokerConfig.

             

            10/13/2014 14:54:52.614 2888 2856 ntstacfgDlg.cpp 1480 INI:  FILE1004=BrokerConfig.lng, %PROGRAMFILES(x86)%\LANDesk\Shared Files\cbaroot\broker\BrokerConfig.lng, NOCOPYERROR

            10/13/2014 14:54:52.630 2888 2856 file.cpp 91 INFO:  Reboot needed for (C:\Program Files (x86)\LANDesk\LDClient\%PROGRAMFILES(x86)%\LANDesk\Shared Files\cbaroot\broker\BrokerConfig.lng)

            10/13/2014 14:54:52.630 2888 2856 tokens.cpp 427 SUCCEEDED:  Copying file 'C:\Program Files (x86)\LANDesk\LDClient\%PROGRAMFILES(x86)%\LANDesk\Shared Files\cbaroot\broker\BrokerConfig.lng'

            10/13/2014 14:54:52.630 2888 2856 ntstacfgDlg.cpp 1480 INI:  EXEC1006=BrokerConfig.exe, /r, INSTALLONLY

            10/13/2014 14:54:52.630 2888 2856 tokens.cpp 664 Starting process: BrokerConfig.exe /r

            10/13/2014 14:59:54.169 2888 2856 tokens.cpp 688 Processes returned : -2146435027

            10/13/2014 14:59:54.169 2888 2856 tokens.cpp 586 CheckProcessExitCode processed app name: BrokerConfig.exe

            10/13/2014 14:59:54.169 2888 2856 tokens.cpp 713 FAILED:  Running application: BrokerConfig.exe /r

            10/13/2014 14:59:54.169 2888 2856 ntstacfgDlg.cpp 1610 FAILED:  bCriticalError set to TRUE. Processing BrokerConfig.exe

             

            It's not set to reboot after this task, so maybe that's the problem?