7 Replies Latest reply on Jan 5, 2012 2:32 AM by Steven Wyns

    CreateProcessW failed.

    Mike Reider

      Hi all, we are running an app deploy job (server build job) onto a windows web server,

       

      getting this error on the job in the logs,

       

      CreateProcessW failed. CODE=14001 ERROR_STRING=This application has failed to start because the application configuration is incorrect. Reinstalling the application may fix this problem.

      12/30/10 12:58:28.304 ERROR    bldeploy - Execute of command failed

       

      We restarted the BL server, reran the job but same error, the job works for other server builds.

       

      I havent been able to find any documentation or explanation of the error code #,

       

      the enviornment is BL 8.0.0.433, Windows 2003 Enterprise, SQL 2005

       

      heres the full log

       

      12/30/10 12:58:28.257 DEBUG    bldeploy - BlTargetJobManager started

      12/30/10 12:58:28.257 DEBUG    bldeploy - Commandline: bltargetjobmanager -start -cmd bldeploy d59ffc3bd94b3c52bc8635cfc3d91818 -N=/temp/stage/d59ffc3bd94b3c52bc8635cfc3d91818 -P=POQDEVIDWEB01 -Q=params.txt -DryRun -Xr -V1 -js0 -jr0 -jc0  -me d59ffc3bd94b3c52bc8635cfc3d91818 -mp -sp -ps -h60

      12/30/10 12:58:28.288 DEBUG    bldeploy - Executing "C:\Program Files\Bladelogic\rsc\sbin\bldeploy.exe" d59ffc3bd94b3c52bc8635cfc3d91818 -N=/temp/stage/d59ffc3bd94b3c52bc8635cfc3d91818 -P=POQDEVIDWEB01 -Q=params.txt -DryRun -Xr -V1 -js0 -jr0 -jc0  -StartNew

      12/30/10 12:58:28.288 DEBUG    bldeploy - ProcessExecutor::createProcess batchFile=, cmd="C:\Program Files\Bladelogic\rsc\sbin\bldeploy.exe" d59ffc3bd94b3c52bc8635cfc3d91818 -N=/temp/stage/d59ffc3bd94b3c52bc8635cfc3d91818 -P=POQDEVIDWEB01 -Q=params.txt -DryRun -Xr -V1 -js0 -jr0 -jc0  -StartNew, cmdDir=

      12/30/10 12:58:28.288 ERROR    bldeploy - ProcessExecutor::createProcess: CreateProcessW failed. CODE=14001 ERROR_STRING=This application has failed to start because the application configuration is incorrect. Reinstalling the application may fix this problem.

      12/30/10 12:58:28.304 ERROR    bldeploy - Execute of command failed

      12/30/10 12:58:28.304 ERROR    bldeploy - Could not start application: bldeploy d59ffc3bd94b3c52bc8635cfc3d91818 -N=/temp/stage/d59ffc3bd94b3c52bc8635cfc3d91818 -P=POQDEVIDWEB01 -Q=params.txt -DryRun -Xr -V1 -js0 -jr0 -jc0

      12/30/10 12:58:28.304 DEBUG    bldeploy - Deleted event file: C:\Program Files\Bladelogic\rsc\Transactions\events\d59ffc3bd94b3c52bc8635cfc3d91818.out

      12/30/10 12:58:28.304 DEBUG    bldeploy - Deleted event file: C:\Program Files\Bladelogic\rsc\Transactions\events\d59ffc3bd94b3c52bc8635cfc3d91818.in

      12/30/10 12:58:28.304 DEBUG    bldeploy - TJM generated Exit message: exitCode=-5000: MSG=Failure to start. Unable to execute bldeploy process. ( exitCode = -5000 ):

      12/30/10 12:58:28.304 DEBUG    bldeploy - Operation complete return code -5000

       

       

       

      anyone have ideas as to possible cause? we otherwise have no other issues with BL server, so the 'application configuration is incorrect' message makes no sense.

        • 1. Re: CreateProcessW failed.
          Bill Robinson

          What are you deploying?

           

          If you run the deploy w/o bladelogic, do you get the same error?

          • 2. Re: CreateProcessW failed.
            Mike Reider

            Hi Bill, the deploy job consists of various items within the BL package. There are folders, user accounts, external commands, and depot software.

             

            the problem is that I dont see a point in the logs where it shows where the failure occurs, on which BL package item.  Heres the screenshot of the BLPackage, (the client does not deploy the installables outside of bladelogic deploy jobs)

             

            blpac1.JPG

             

            Im also seeing this error in logs,

             

            Deploy] executing command bltargetjobmanager -start -cmd "bldeploy  d59ffc3bd94b3c52bc8635cfc3d91818  -N="/temp/stage/d59ffc3bd94b3c52bc8635cfc3d91818" -P=SERVERWEB01 -Q=params.txt  -DryRun -Xr -V1 -js0 -jr0 -jc0 " -me "d59ffc3bd94b3c52bc8635cfc3d91818" -mp -sp   -ps  -h60 on server SERVERWEB01

            [30 Dec 2010 12:58:28,605] [WorkItem-Thread-35] [ERROR]  [user:BLAdmins:] [Deploy]

            DRYRUN failed for  server SERVERWEB01. Exit code = -5000

            • 3. Re: CreateProcessW failed.
              Bill Robinson

              Have you opened up a support ticket about this?

              I’m not sure if it’s something in the agent causing the error or the deployed software.

              • 4. Re: CreateProcessW failed.
                Mike Reider

                we are running this deploy job on another target server, and it looks like this error may be caused by the target server not having enough disk space. The target server's D: had 130MB of space, and this may have been the issue. I will confirm once we test this job on few other servers.

                • 5. Re: CreateProcessW failed.
                  Dipak Gaigole

                  This “This application has failed to start because the application configuration is incorrect” error is thrown by the application you are trying to deploy.

                  If you set the bldeploy log level to “debug” (Need Agent restart to make this value effective), just before the above mentioned “This application has …” error message, you will see log message like:

                    ProcessExecutor::createProcess batchFile=

                   

                  This will provide you details of what exact command is failing and throwing above error and you can investigate it further.

                  • 6. CreateProcessW failed.

                    The messages are from the TargetJobManager log, so it means the TargetJobManager cannot start the deploy process because of the 14001 error. Below is the explaination of the error code from Microsoft:

                    ----------------------------------------
                    ERROR_SXS_CANT_GEN_ACTCTX
                    14001 (0x36B1)

                    The application has failed to start because its side-by-side configuration is incorrect. Please see the application event log or use the command-line sxstrace.exe tools for more detail.

                    ----------------------------------------

                     

                    It is likely deploy is loading wrong/incompatible dll on the system due to wrong order in %PATH% (could be old dlls left from previous agent installation, etc). Removing the old agent files (if there are any) and reinstalling the agent could fix the problem.

                     

                    Hope this helps.

                    1 of 1 people found this helpful
                    • 7. Re: CreateProcessW failed.
                      Steven Wyns

                      For future reference:  I've just encoutered a comparable problem. Every external command in the blpackages failed with:

                      Error Jan 5, 2012 7:47:53 AM  Unable to run (null).  CreateProcessW failed. Ret: 5 Access is denied. 

                      2

                       

                      Which was caused by mcafee anti spyware who was blocking execution of files within c:\temp ( c:\temp\stage) to be correct.

                      1 of 1 people found this helpful