Workflow
View Markdown
Error: Container is not recognised#
Problem: When deploying an Application Compatibility Package/Container, the following error is received:
Applies to: Alchemy
Cloudhouse.Container.Deployment.exe -- Cloudhouse.Container.Deployment.exe : The term
'Cloudhouse.Container.Deployment.exe' is not recognized as the name
of a cmdlet, function, script file, or operable program. Check the
spelling of the name, or if a path was included, verify that the path is
correct and try again.
At line:1 char:1
+ Cloudhouse.Container.Deployment.exe --deploydir c:\temp --accepteula
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : ObjectNotFound: (Cloudhouse.Container.Deploym
ent.exe:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException
Suggestion [3,General]: The command Cloudhouse.Container.Deployment.exe was not
found, but does exist in the current location. Windows PowerShell
does not load commands from the current location by default. If you trust this command, instead type:
".\Cloudhouse.Container.Deployment.exe". See "get-help
about_Command_Precedence" for more details.
Cause: The default Windows PowerShell does not load commands from the current location.
Solution: To fix this issue, make sure you:
- Run the command from the location of the EXE (
Cloudhouse.Container.Deployment.exewhich is in the root of your Container in this example). - Add the relative path command "
.\" to the beginning of your command. For example:
.\Cloudhouse.Container.Deployment.exe --deploydir c:\temp --accepteula
Note
If you still encounter problems, please contact your Cloudhouse Partner in the first instance (if relevant), otherwise contact Cloudhouse Support for further assistance.