eZDeploy issues
This topic contains information to help you troubleshoot problems in the eZDeploy utility.
You can check the following log file for entries that might help diagnose the problem:
Log file | Location |
|---|---|
eZDeploy.log | eZDeployInstallationDirectory/eZDeploy.log |
The following table contains the explanations and workarounds for problems that you might encounter while working with the eZDeploy utility:
Problem | Solution |
|---|---|
The export or import of a service blueprint does not end. No errors are detected on the console, yet the process hangs. | This problem can arise if you have not accepted the BMC Server Automation Authentication X509 certificate. Close the command prompt to abort the current process, and then accept the certificate. Then you can start using the eZDeploy utility. |
The No Authentication Profile Found error appears in the log file. | This error often appears if you have deleted the BMC Server Automation Server Authentication Profile by mistake from the BMC Server Automation console. Delete the eZDeploy profile and create it again. |
No option is provided for the profile command to change the BMC Server Automation or BMC Atrium Orchestrator servers. | Open the eZDeployInstallationDirectory/profiles directory. You can see .json files with the file name as eZProfileName. Open the file that you want and modify the server details. |
If you provide an incorrect version of a BMC Atrium Orchestrator activated module for a service blueprint export, the module with invalid content is exported in the eZ file. | Ensure that you provide the correct version of the BMC Atrium Orchestrator activated module when you export a blueprint. |
eZDeploy intermittently shows [ERROR] Terminal initialization failed while launching. | You must change the folder structure to avoid recurrence of this error message when eZDeploy launches. For example, if eZDeploy is in C:\eZDeploy, try placing it in C:\New Folder\eZDeploy. |