Powershell script fails when run from Bamboo

Naveen Jones

I've a Script task (Windows PowerShell) in a Build plan that automates MS Office Word to convert .docx files to PDF. The script runs fine and creates the PDF files when run directly from Powershell console on the machine (Windows Server 2016). Running the same script file from Bamboo task generates the error below.

New-Object : Retrieving the COM class factory for component with CLSID 
error	19-Dec-2018 12:36:13	{000209FF-0000-0000-C000-000000000046} failed due to the following error: 
error	19-Dec-2018 12:36:13	80080005 Server execution failed (Exception from HRESULT: 0x80080005 
error	19-Dec-2018 12:36:13	(CO_E_SERVER_EXEC_FAILURE)).
error	19-Dec-2018 12:36:13	At [PATH TO Powershell Script file]:75 char:22
error	19-Dec-2018 12:36:13	+ ...             $wdApplication = New-Object -ComObject "Word.Application"
error	19-Dec-2018 12:36:13	+                                  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
error	19-Dec-2018 12:36:13	    + CategoryInfo          : ResourceUnavailable: (:) [New-Object], COMExcept 
error	19-Dec-2018 12:36:13	   ion
error	19-Dec-2018 12:36:13	    + FullyQualifiedErrorId : NoCOMClassIdentified,Microsoft.PowerShell.Comman 
error	19-Dec-2018 12:36:13	   ds.NewObjectCommand 

 

The Bamboo task calls a PS file that has an Import-Module statement to import the function defined in second PS file that actually does the PDF conversion. Bamboo is running as a Windows Service and the task is setup to call the PS file with some arguments.

Does anyone have any suggestions on what I might be missing in the task or Bamboo setup?

Daniel Santos_157bm4

Hi @Naveen Jones,

Is your service configured to use a local user account to start Bamboo?
This is the configuration we recommend, and you can use this page to configure it: Running Bamboo as a Windows service as the local user.

If you have Bamboo running as a local user, can you confirm you are using the same user that was able to run the script from terminal?

The error you have is also described in this article: You may receive an "Error code 80080005 -- server execution failed." error message when you start many COM+ applications. You may want to read it and check if it applies to your case.