VSTS release level "Windows PowerShell Cannot Run Script Whose Path Contains Spaces"

Question

I worked on DevOps with VSTS. Currently I used the “PowerShell” Task to run the PowerShell script. But unfortunately my VSTS repository name having space (for example “WebApp Demo”), that’s why I am getting the issue while executing the PowerShell script at VSTS release level.

[error] Process completed with exit code 0 and had 1 error(s) written to the error stream.

PowerShell Task configuration in VSTS release definition

For resolving the above error I followed so many blogs but issue will be the same.

This is a long shot but did you try encapsulating the script path in double quotes? — Persistent13
– Persistent13, Commented Feb 9, 2018 at 18:29
It should work, add System.debug variable and set the value to true, then start release and share this log on the OneDrive. — starian chen-MSFT
– starian chen-MSFT, Commented Feb 12, 2018 at 2:38
@Persistent13, I already tried with double quotes, but it won't be work properly. — Pradeep
– Pradeep, Commented Feb 12, 2018 at 5:29

starian chen-MSFT · Accepted Answer · 2018-02-12 06:11:17Z

2

Based on the log, you the value of ConfigFilePath is the path that contains space.

Change argument to:

-webConfigFilePath "$(ConfigFilePath)"

answered Feb 12, 2018 at 6:11

starian chen-MSFT

33.8k2 gold badges32 silver badges55 bronze badges

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

VSTS release level "Windows PowerShell Cannot Run Script Whose Path Contains Spaces"

1 Answer 1

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Your Answer

Sign up or log in

Post as a guest

Related