PowerShell Inline Fails with Parsing Program Files Path

Issue #8 resolved
Justin Schneck created an issue

C:\Program : The term 'C:\Program' 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:3635

  • ... elpnow/Vendor';C:\Program Files\Bamboo\temp\1376257-1507329-2260993-PowerShellTa ...
  • ~~

Comments (11)

  1. Justin Schneck reporter

    error 22-Oct-2013 13:00:08 C:\Program : The term 'C:\Program' is not recognized as the name of a cmdlet, error 22-Oct-2013 13:00:08 function, script file, or operable program. Check the spelling of the name, or error 22-Oct-2013 13:00:08 if a path was included, verify that the path is correct and try again. error 22-Oct-2013 13:00:08 At line:1 char:3727 error 22-Oct-2013 13:00:08 + ... elpnow/Vendor';C:\Program error 22-Oct-2013 13:00:08 Files\Bamboo\temp\1376257-1507329-2260996-PowerShellTa ... error 22-Oct-2013 13:00:08 + ~~ error 22-Oct-2013 13:00:08 + CategoryInfo : ObjectNotFound: (C:\Program:String) [], ParentCo error 22-Oct-2013 13:00:08 ntainsErrorRecordException error 22-Oct-2013 13:00:08 + FullyQualifiedErrorId : CommandNotFoundException error 22-Oct-2013 13:00:08
    simple 22-Oct-2013 13:00:08 Failing task since return code of [C:\Program Files\Bamboo\temp\1376257-1507329-2260996-PowerShellTask-8814897692172926876.cmd] was 1 while expected 0

  2. Justin Schneck reporter

    I ran a basic PowerShell Script directly and it returned normally. I added the same script contents and it fails the same way.

  3. Log in to comment