Error: Cannot bind argument to parapmeter 'LiteralPath' because it is empty

//Error: Cannot bind argument to parapmeter 'LiteralPath' because it is empty
Error: Cannot bind argument to parapmeter 'LiteralPath' because it is empty 2016-04-07T12:22:53+00:00

The Toolkit Forums General Error: Cannot bind argument to parapmeter 'LiteralPath' because it is empty

  • Author
    Posts
  • Long
    Participant
    Post count: 14
    #1251 |

    Getting this error on a simple script. Downloaded toolkit 3.8.6

    Downloaded http://www.7-zip.org/a/7z1514-x64.msi put it in “Files”

    Added this line to script under ## <Perform Installation tasks here>

    Execute-MSI -Action ‘Install’ -Path “$dirfiles\7z1514-x64.msi”

    running the script i get this error.

    Error Record
    Message: Cannot bind argument to parameter ‘LiteralPath’ because it is an empty string.

    InnerException:’FullyQualifiedErrorId:
    ParameterArgumentValidationErrorEmptyStringNotAllowed,Microsoft.PowerShell.Commands.TestPathCommand

    ScriptStackTrace: at Execute-MSI<Process>, X:\PackageDev\test\DistributionFiles\AppDeployToolkit\AppDeployToolkitMain.ps1: Line 2191
    at <ScriptBlock>,X:\PackageDev\test\DistributionFiles\Deploy.-Application.ps1: lone 131

    line 131 is this:
    Execute-MSI -Action ‘Install’ -Path “$dirfiles\7z1514-x64.msi”

  • Michael
    Participant
    Post count: 1

    I am also having an issue with this -LiteralPath error. Were you able to resolve it, or does anyone have any advice?
    I found my cause, an invalid log path defined in the AppDeployToolkitConfig.xml.

    • This reply was modified 1 year, 6 months ago by  Michael. Reason: Resolved issue
  • Long
    Participant
    Post count: 14

    No have not resolve it. Use execute-process as work around for now. It really strange cause it worked before.

You must be logged in to reply to this topic.