Important Notice: On February 29th, this community was put into read-only mode. All existing posts will remain but customers are unable to add new posts or comment on existing. Please feel to join our Community Discord for any questions and discussions.

Command prompt works, but not in PDQ Deploy

I've had this come up a couple of times. I'll have a job that will run fine in the Command Prompt but fails with PDQ Deploy, usually with an error code 1.

The latest one is this one to remove a homegrown app:

“c:\Program Files (x86)\Common Files\Microsoft Shared\VSTO\10.0\VSTOInstaller.exe” /Uninstall file://parametrix.com/it/Replicated/PDQ%20Deploy/Repository/PMXTemplates/Current/PMXtemplates2013.vsto /Quiet

I have tried running it as the logged on user but that doesn't help either.

Any ideas why this is occurring?

0

Comments

6 comments
Date Votes
  • Is there anything in the Output Log?

    0
  • This:

    At C:\WINDOWS\AdminArsenal\PDQDeployRunner\service-1\exec\user.ps1:1 char:85
    + ... \Common Files\Microsoft Shared\VSTO\10.0\VSTOInstaller.exe" /Uninstal ...
    + ~
    You must provide a value expression following the '/' operator.
    At C:\WINDOWS\AdminArsenal\PDQDeployRunner\service-1\exec\user.ps1:1 char:85
    + ... iles\Microsoft Shared\VSTO\10.0\VSTOInstaller.exe" /Uninstall file:// ...
    + ~~~~~~~~~
    Unexpected token 'Uninstall' in expression or statement.
    + CategoryInfo : ParserError: (:) [], ParentContainsErrorRecordException
    + FullyQualifiedErrorId : ExpectedValueExpression

     

    It does work in the command prompt.

    0
  • It looks like you're running that in a PowerShell step, but it doesn't look like PowerShell code. Have you tried the Command step?

    0
  • Sorry, that was an older attempt when I tried it in PS. Here is the one from Command:

    The filename, directory name, or volume label syntax is incorrect.

    0
  • My assumption is that it's referring to the file:// part, probably the PDQ%20Deploy section. Would you be comfortable exporting your package to XML and sharing it here? If not, contact support@pdq.com. They can dig a lot deeper than I can from here.

    0
  • I'll reach out to support. Thanks for the help.

    0