Powershell Start-Process cmdlet not working from within a TFS Powershell scriptHow to run a PowerShell scriptPowerShell says “execution of scripts is disabled on this system.”Unable to run a powershell script using Windows task schedulerPowerShell script won't execute as a Windows scheduled taskStarting VB Script from Powershell script - works from PS environment, but not scheduled taskPowerShell: Another instance of Start-Process is already runningRunning a Powershell script from c#How to Run Long Powershell script from Windows Command Prompt (CMD)Powershell Start-Process works but not from .ps1 scriptPowershell get-websitestate cmdlet not working at Task Scheduler
Can you cast the Shape Water spell without an existing obvious pool of water?
Adjust the Table
Is it possible to complete a PhD in CS in 3 years?
Why is a mixture of two normally distributed variables only bimodal if their means differ by at least two times the common standard deviation?
What kind of Chinook helicopter/airplane hybrid is this?
Is it better in terms of durability to remove card+battery or to connect to charger/computer via USB-C?
What does the multimeter dial do internally?
Why the Cauchy Distribution is so useful?
Sum of even numbers N?
"Distance" between summands in Taylor Series of Cosine
Passwordless authentication - how and when to invalidate a login code
Non-Chromatic Orchestral Instruments?
Intern not wearing safety equipment; how could I have handled this differently?
Is it possible for a character at any level to cast all 44 Cantrips in one week without Magic Items?
Appropriate conduit for several data cables underground over 300' run
What was the profession 芸者 (female entertainer) called in Russia?
split one column into two columns based on it's value using t/sql
Is there a formal/better word than "skyrocket" for the given context?
How does one acquire an undead eyeball encased in a gem?
This LM317 diagram doesn't make any sense to me
Computer name naming convention for security
How to evaluate the performance of open source solver?
What was the profession 芸者 (female entertainer) called in Germany?
Shrinking padding of node with label options
Powershell Start-Process cmdlet not working from within a TFS Powershell script
How to run a PowerShell scriptPowerShell says “execution of scripts is disabled on this system.”Unable to run a powershell script using Windows task schedulerPowerShell script won't execute as a Windows scheduled taskStarting VB Script from Powershell script - works from PS environment, but not scheduled taskPowerShell: Another instance of Start-Process is already runningRunning a Powershell script from c#How to Run Long Powershell script from Windows Command Prompt (CMD)Powershell Start-Process works but not from .ps1 scriptPowershell get-websitestate cmdlet not working at Task Scheduler
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;
VS / TFS 2017 This post was updated to reflect new information
There are 2 PowerShell scripts:
p1.ps1
p2.ps1
p1 is executed as a PowerShell task in a TFS build process. p2 is used twice within p1.
Use 1: p2 is called from p1, meaning p2 is executed inline
Use 2: p2 is launched from p1, meaning p1 does a fire and forget execution of p2, i.e. as a background task.
Within the TFS build process, use 1 works exactly as expected, use 2 does not.
Near the end of p1 are the following 2 different sets of code that have been attempted for the fire and forget execution of p2:
$powershellArguments = "-file C:confp2.ps1" , "refresh" , "C:agent_work4afor-deploywebsite"
Start-Process powershell.exe -Argument $powershellArguments
And the 2nd methodology:
Start-Job -FilePath $baseFolder"p2.ps1" -ArgumentList "refresh", $sourceRoot
If I manually execute p1 in a Command Prompt PowerShell Window, the fire and forget p2 execution happens as expected with either sets of code above.
But when I run the build and p1 is executed as a task within the build, p2 does not fire and forget. Again, to be clear, within the TFS build, the use 1 inline process does execute properly.
At the head of the script I embedded some code to write a small text file to confirm the script is at least being started and the code also writes out the arguments received to ensure the argument syntax has been used correctly. The arguments are passed to p2 properly when p1 is executed outside of the build environment. But when p1 is executed as a PowerShell Script within the build, the small text file does not reflect that p2 even started in the fire and forget mode.
It turns out that p1 and p2 are the same script, they just use switches to execute slightly differently. But I copied p1 and named it p2 just to separate the 2 scripts and the result is the same. I can't get p2 to start using the Start-Process cmdlet or the Start-Job cmdlet when p1 is executing within the build.
I think I've been pretty diligent to narrow this down and it seems there is something about launching a separate script from within a script inside the build process.
Why might this be and is there a way around this?
I did wonder if it relates to the basic script policies such as in a batch file that attempts to run a PowerShell script for which we include -executionpolicy remotesigned. Is that possible?
powershell tfs tfsbuild tfs2017 start-process
asked Mar 25 at 22:45
AlanAlan
7411 gold badge14 silver badges29 bronze badges
|
show 1 more comment
VS / TFS 2017 This post was updated to reflect new information
There are 2 PowerShell scripts:
p1.ps1
p2.ps1
p1 is executed as a PowerShell task in a TFS build process. p2 is used twice within p1.
Use 1: p2 is called from p1, meaning p2 is executed inline
Use 2: p2 is launched from p1, meaning p1 does a fire and forget execution of p2, i.e. as a background task.
Within the TFS build process, use 1 works exactly as expected, use 2 does not.
Near the end of p1 are the following 2 different sets of code that have been attempted for the fire and forget execution of p2:
$powershellArguments = "-file C:confp2.ps1" , "refresh" , "C:agent_work4afor-deploywebsite"
Start-Process powershell.exe -Argument $powershellArguments
And the 2nd methodology:
Start-Job -FilePath $baseFolder"p2.ps1" -ArgumentList "refresh", $sourceRoot
If I manually execute p1 in a Command Prompt PowerShell Window, the fire and forget p2 execution happens as expected with either sets of code above.
But when I run the build and p1 is executed as a task within the build, p2 does not fire and forget. Again, to be clear, within the TFS build, the use 1 inline process does execute properly.
At the head of the script I embedded some code to write a small text file to confirm the script is at least being started and the code also writes out the arguments received to ensure the argument syntax has been used correctly. The arguments are passed to p2 properly when p1 is executed outside of the build environment. But when p1 is executed as a PowerShell Script within the build, the small text file does not reflect that p2 even started in the fire and forget mode.
It turns out that p1 and p2 are the same script, they just use switches to execute slightly differently. But I copied p1 and named it p2 just to separate the 2 scripts and the result is the same. I can't get p2 to start using the Start-Process cmdlet or the Start-Job cmdlet when p1 is executing within the build.
I think I've been pretty diligent to narrow this down and it seems there is something about launching a separate script from within a script inside the build process.
Why might this be and is there a way around this?
I did wonder if it relates to the basic script policies such as in a batch file that attempts to run a PowerShell script for which we include -executionpolicy remotesigned. Is that possible?
powershell tfs tfsbuild tfs2017 start-process
asked Mar 25 at 22:45
AlanAlan
7411 gold badge14 silver badges29 bronze badges
Does using the full path to the script help? often PowerShell.exe starts in the System32 folder, and it would be trying to execute the script from there.
– HAL9256
Mar 25 at 23:07
I think we had async posts here. I now have the full path and still have problems, but as I just commented above, my problems seem to be with the argument passing. Still working on it but will leave the post up until I solve it...
– Alan
Mar 25 at 23:29
Argument passing and full path addressing confirmed good, as discussed in the revised post above.
– Alan
Mar 26 at 0:57
I guess when the p1 build task finished the p2 also terminated, try to putStart-Sleepin the end of p1 (with how much time take p2 run) and check the p2 results.
– Shayki Abramczyk
Mar 26 at 10:35
I will try the sleep as an exercise because that will help diagnose what's going on, but sadly long term it won't solve my issue. I'm trying to drive the build time as low as possible. The p2 execution is a refresh of destination data using time-consuming FTP commands. I was trying to kick-off the refresh as a separate task so the build can exit early. There's no need to delay build completion just for the data update. But that's a great insight into what may be happening. It's hard to tell because build execution is mostly hidden from view. The logs don't really help with that.
– Alan
Mar 26 at 14:37
|
show 1 more comment
VS / TFS 2017 This post was updated to reflect new information
There are 2 PowerShell scripts:
p1.ps1
p2.ps1
p1 is executed as a PowerShell task in a TFS build process. p2 is used twice within p1.
Use 1: p2 is called from p1, meaning p2 is executed inline
Use 2: p2 is launched from p1, meaning p1 does a fire and forget execution of p2, i.e. as a background task.
Within the TFS build process, use 1 works exactly as expected, use 2 does not.
Near the end of p1 are the following 2 different sets of code that have been attempted for the fire and forget execution of p2:
$powershellArguments = "-file C:confp2.ps1" , "refresh" , "C:agent_work4afor-deploywebsite"
Start-Process powershell.exe -Argument $powershellArguments
And the 2nd methodology:
Start-Job -FilePath $baseFolder"p2.ps1" -ArgumentList "refresh", $sourceRoot
If I manually execute p1 in a Command Prompt PowerShell Window, the fire and forget p2 execution happens as expected with either sets of code above.
But when I run the build and p1 is executed as a task within the build, p2 does not fire and forget. Again, to be clear, within the TFS build, the use 1 inline process does execute properly.
At the head of the script I embedded some code to write a small text file to confirm the script is at least being started and the code also writes out the arguments received to ensure the argument syntax has been used correctly. The arguments are passed to p2 properly when p1 is executed outside of the build environment. But when p1 is executed as a PowerShell Script within the build, the small text file does not reflect that p2 even started in the fire and forget mode.
It turns out that p1 and p2 are the same script, they just use switches to execute slightly differently. But I copied p1 and named it p2 just to separate the 2 scripts and the result is the same. I can't get p2 to start using the Start-Process cmdlet or the Start-Job cmdlet when p1 is executing within the build.
I think I've been pretty diligent to narrow this down and it seems there is something about launching a separate script from within a script inside the build process.
Why might this be and is there a way around this?
I did wonder if it relates to the basic script policies such as in a batch file that attempts to run a PowerShell script for which we include -executionpolicy remotesigned. Is that possible?
powershell tfs tfsbuild tfs2017 start-process
asked Mar 25 at 22:45
AlanAlan
7411 gold badge14 silver badges29 bronze badges
VS / TFS 2017 This post was updated to reflect new information
There are 2 PowerShell scripts:
p1.ps1
p2.ps1
p1 is executed as a PowerShell task in a TFS build process. p2 is used twice within p1.
Use 1: p2 is called from p1, meaning p2 is executed inline
Use 2: p2 is launched from p1, meaning p1 does a fire and forget execution of p2, i.e. as a background task.
Within the TFS build process, use 1 works exactly as expected, use 2 does not.
Near the end of p1 are the following 2 different sets of code that have been attempted for the fire and forget execution of p2:
$powershellArguments = "-file C:confp2.ps1" , "refresh" , "C:agent_work4afor-deploywebsite"
Start-Process powershell.exe -Argument $powershellArguments
And the 2nd methodology:
Start-Job -FilePath $baseFolder"p2.ps1" -ArgumentList "refresh", $sourceRoot
If I manually execute p1 in a Command Prompt PowerShell Window, the fire and forget p2 execution happens as expected with either sets of code above.
But when I run the build and p1 is executed as a task within the build, p2 does not fire and forget. Again, to be clear, within the TFS build, the use 1 inline process does execute properly.
At the head of the script I embedded some code to write a small text file to confirm the script is at least being started and the code also writes out the arguments received to ensure the argument syntax has been used correctly. The arguments are passed to p2 properly when p1 is executed outside of the build environment. But when p1 is executed as a PowerShell Script within the build, the small text file does not reflect that p2 even started in the fire and forget mode.
It turns out that p1 and p2 are the same script, they just use switches to execute slightly differently. But I copied p1 and named it p2 just to separate the 2 scripts and the result is the same. I can't get p2 to start using the Start-Process cmdlet or the Start-Job cmdlet when p1 is executing within the build.
I think I've been pretty diligent to narrow this down and it seems there is something about launching a separate script from within a script inside the build process.
Why might this be and is there a way around this?
I did wonder if it relates to the basic script policies such as in a batch file that attempts to run a PowerShell script for which we include -executionpolicy remotesigned. Is that possible?
powershell tfs tfsbuild tfs2017 start-process
powershell tfs tfsbuild tfs2017 start-process
asked Mar 25 at 22:45
AlanAlan
7411 gold badge14 silver badges29 bronze badges
asked Mar 25 at 22:45
AlanAlan
7411 gold badge14 silver badges29 bronze badges
edited Mar 26 at 0:43
Alan
asked Mar 25 at 22:45
AlanAlan
7411 gold badge14 silver badges29 bronze badges
asked Mar 25 at 22:45
AlanAlan
7411 gold badge14 silver badges29 bronze badges
asked Mar 25 at 22:45
AlanAlan
7411 gold badge14 silver badges29 bronze badges
7411 gold badge14 silver badges29 bronze badges
Does using the full path to the script help? often PowerShell.exe starts in the System32 folder, and it would be trying to execute the script from there.
– HAL9256
Mar 25 at 23:07
I think we had async posts here. I now have the full path and still have problems, but as I just commented above, my problems seem to be with the argument passing. Still working on it but will leave the post up until I solve it...
– Alan
Mar 25 at 23:29
Argument passing and full path addressing confirmed good, as discussed in the revised post above.
– Alan
Mar 26 at 0:57
I guess when the p1 build task finished the p2 also terminated, try to putStart-Sleepin the end of p1 (with how much time take p2 run) and check the p2 results.
– Shayki Abramczyk
Mar 26 at 10:35
I will try the sleep as an exercise because that will help diagnose what's going on, but sadly long term it won't solve my issue. I'm trying to drive the build time as low as possible. The p2 execution is a refresh of destination data using time-consuming FTP commands. I was trying to kick-off the refresh as a separate task so the build can exit early. There's no need to delay build completion just for the data update. But that's a great insight into what may be happening. It's hard to tell because build execution is mostly hidden from view. The logs don't really help with that.
– Alan
Mar 26 at 14:37
|
show 1 more comment
Does using the full path to the script help? often PowerShell.exe starts in the System32 folder, and it would be trying to execute the script from there.
– HAL9256
Mar 25 at 23:07
I think we had async posts here. I now have the full path and still have problems, but as I just commented above, my problems seem to be with the argument passing. Still working on it but will leave the post up until I solve it...
– Alan
Mar 25 at 23:29
Argument passing and full path addressing confirmed good, as discussed in the revised post above.
– Alan
Mar 26 at 0:57
I guess when the p1 build task finished the p2 also terminated, try to putStart-Sleepin the end of p1 (with how much time take p2 run) and check the p2 results.
– Shayki Abramczyk
Mar 26 at 10:35
I will try the sleep as an exercise because that will help diagnose what's going on, but sadly long term it won't solve my issue. I'm trying to drive the build time as low as possible. The p2 execution is a refresh of destination data using time-consuming FTP commands. I was trying to kick-off the refresh as a separate task so the build can exit early. There's no need to delay build completion just for the data update. But that's a great insight into what may be happening. It's hard to tell because build execution is mostly hidden from view. The logs don't really help with that.
– Alan
Mar 26 at 14:37
Does using the full path to the script help? often PowerShell.exe starts in the System32 folder, and it would be trying to execute the script from there.
– HAL9256
Mar 25 at 23:07
Does using the full path to the script help? often PowerShell.exe starts in the System32 folder, and it would be trying to execute the script from there.
– HAL9256
Mar 25 at 23:07
I think we had async posts here. I now have the full path and still have problems, but as I just commented above, my problems seem to be with the argument passing. Still working on it but will leave the post up until I solve it...
– Alan
Mar 25 at 23:29
I think we had async posts here. I now have the full path and still have problems, but as I just commented above, my problems seem to be with the argument passing. Still working on it but will leave the post up until I solve it...
– Alan
Mar 25 at 23:29
Argument passing and full path addressing confirmed good, as discussed in the revised post above.
– Alan
Mar 26 at 0:57
Argument passing and full path addressing confirmed good, as discussed in the revised post above.
– Alan
Mar 26 at 0:57
I guess when the p1 build task finished the p2 also terminated, try to put
Start-Sleep in the end of p1 (with how much time take p2 run) and check the p2 results.– Shayki Abramczyk
Mar 26 at 10:35
I guess when the p1 build task finished the p2 also terminated, try to put
Start-Sleep in the end of p1 (with how much time take p2 run) and check the p2 results.– Shayki Abramczyk
Mar 26 at 10:35
I will try the sleep as an exercise because that will help diagnose what's going on, but sadly long term it won't solve my issue. I'm trying to drive the build time as low as possible. The p2 execution is a refresh of destination data using time-consuming FTP commands. I was trying to kick-off the refresh as a separate task so the build can exit early. There's no need to delay build completion just for the data update. But that's a great insight into what may be happening. It's hard to tell because build execution is mostly hidden from view. The logs don't really help with that.
– Alan
Mar 26 at 14:37
I will try the sleep as an exercise because that will help diagnose what's going on, but sadly long term it won't solve my issue. I'm trying to drive the build time as low as possible. The p2 execution is a refresh of destination data using time-consuming FTP commands. I was trying to kick-off the refresh as a separate task so the build can exit early. There's no need to delay build completion just for the data update. But that's a great insight into what may be happening. It's hard to tell because build execution is mostly hidden from view. The logs don't really help with that.
– Alan
Mar 26 at 14:37
|
show 1 more comment
1 Answer
1
active
oldest
votes
@Shayik-Abramczyk in the comments was correct. When you use Start-Job, if the PowerShell session terminates, any executing jobs started via Start-Job also terminate.
There are a few ways you could accomplish what you want. It depends on your particular scenario. You could use Register-ScheduledJob or use Start-Process. I'm thinking you probably want Start-Process:
Start-Process PowerShell.exe -ArgumentList "-NonInteractive", "-NoLogo", "-File", ".$(Join-Path $baseFolder p2.ps1)",
"refresh", "$sourceRoot" -NoNewWindow
HTH.
answered May 13 at 20:25
fourpastmidnightfourpastmidnight
3,1681 gold badge25 silver badges38 bronze badges
Will try this when I revisit it and post back with results. Thx!
– Alan
May 14 at 11:51
1
I updated my answer to add some options to the PowerShell process--otherwise, it may have resulted in a window being opened, which may be undesirable.
– fourpastmidnight
May 14 at 16:13
add a comment |
Your Answer
StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f55347458%2fpowershell-start-process-cmdlet-not-working-from-within-a-tfs-powershell-script%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
@Shayik-Abramczyk in the comments was correct. When you use Start-Job, if the PowerShell session terminates, any executing jobs started via Start-Job also terminate.
There are a few ways you could accomplish what you want. It depends on your particular scenario. You could use Register-ScheduledJob or use Start-Process. I'm thinking you probably want Start-Process:
Start-Process PowerShell.exe -ArgumentList "-NonInteractive", "-NoLogo", "-File", ".$(Join-Path $baseFolder p2.ps1)",
"refresh", "$sourceRoot" -NoNewWindow
HTH.
answered May 13 at 20:25
fourpastmidnightfourpastmidnight
3,1681 gold badge25 silver badges38 bronze badges
Will try this when I revisit it and post back with results. Thx!
– Alan
May 14 at 11:51
1
I updated my answer to add some options to the PowerShell process--otherwise, it may have resulted in a window being opened, which may be undesirable.
– fourpastmidnight
May 14 at 16:13
add a comment |
@Shayik-Abramczyk in the comments was correct. When you use Start-Job, if the PowerShell session terminates, any executing jobs started via Start-Job also terminate.
There are a few ways you could accomplish what you want. It depends on your particular scenario. You could use Register-ScheduledJob or use Start-Process. I'm thinking you probably want Start-Process:
Start-Process PowerShell.exe -ArgumentList "-NonInteractive", "-NoLogo", "-File", ".$(Join-Path $baseFolder p2.ps1)",
"refresh", "$sourceRoot" -NoNewWindow
HTH.
answered May 13 at 20:25
fourpastmidnightfourpastmidnight
3,1681 gold badge25 silver badges38 bronze badges
Will try this when I revisit it and post back with results. Thx!
– Alan
May 14 at 11:51
1
I updated my answer to add some options to the PowerShell process--otherwise, it may have resulted in a window being opened, which may be undesirable.
– fourpastmidnight
May 14 at 16:13
add a comment |
@Shayik-Abramczyk in the comments was correct. When you use Start-Job, if the PowerShell session terminates, any executing jobs started via Start-Job also terminate.
There are a few ways you could accomplish what you want. It depends on your particular scenario. You could use Register-ScheduledJob or use Start-Process. I'm thinking you probably want Start-Process:
Start-Process PowerShell.exe -ArgumentList "-NonInteractive", "-NoLogo", "-File", ".$(Join-Path $baseFolder p2.ps1)",
"refresh", "$sourceRoot" -NoNewWindow
HTH.
answered May 13 at 20:25
fourpastmidnightfourpastmidnight
3,1681 gold badge25 silver badges38 bronze badges
@Shayik-Abramczyk in the comments was correct. When you use Start-Job, if the PowerShell session terminates, any executing jobs started via Start-Job also terminate.
There are a few ways you could accomplish what you want. It depends on your particular scenario. You could use Register-ScheduledJob or use Start-Process. I'm thinking you probably want Start-Process:
Start-Process PowerShell.exe -ArgumentList "-NonInteractive", "-NoLogo", "-File", ".$(Join-Path $baseFolder p2.ps1)",
"refresh", "$sourceRoot" -NoNewWindow
HTH.
answered May 13 at 20:25
fourpastmidnightfourpastmidnight
3,1681 gold badge25 silver badges38 bronze badges
edited May 14 at 16:12
answered May 13 at 20:25
fourpastmidnightfourpastmidnight
3,1681 gold badge25 silver badges38 bronze badges
answered May 13 at 20:25
fourpastmidnightfourpastmidnight
3,1681 gold badge25 silver badges38 bronze badges
answered May 13 at 20:25
fourpastmidnightfourpastmidnight
3,1681 gold badge25 silver badges38 bronze badges
3,1681 gold badge25 silver badges38 bronze badges
Will try this when I revisit it and post back with results. Thx!
– Alan
May 14 at 11:51
1
I updated my answer to add some options to the PowerShell process--otherwise, it may have resulted in a window being opened, which may be undesirable.
– fourpastmidnight
May 14 at 16:13
add a comment |
Will try this when I revisit it and post back with results. Thx!
– Alan
May 14 at 11:51
1
I updated my answer to add some options to the PowerShell process--otherwise, it may have resulted in a window being opened, which may be undesirable.
– fourpastmidnight
May 14 at 16:13
Will try this when I revisit it and post back with results. Thx!
– Alan
May 14 at 11:51
Will try this when I revisit it and post back with results. Thx!
– Alan
May 14 at 11:51
1
1
I updated my answer to add some options to the PowerShell process--otherwise, it may have resulted in a window being opened, which may be undesirable.
– fourpastmidnight
May 14 at 16:13
I updated my answer to add some options to the PowerShell process--otherwise, it may have resulted in a window being opened, which may be undesirable.
– fourpastmidnight
May 14 at 16:13
add a comment |
Got a question that you can’t ask on public Stack Overflow? Learn more about sharing private information with Stack Overflow for Teams.
Got a question that you can’t ask on public Stack Overflow? Learn more about sharing private information with Stack Overflow for Teams.
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f55347458%2fpowershell-start-process-cmdlet-not-working-from-within-a-tfs-powershell-script%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Does using the full path to the script help? often PowerShell.exe starts in the System32 folder, and it would be trying to execute the script from there.
– HAL9256
Mar 25 at 23:07
I think we had async posts here. I now have the full path and still have problems, but as I just commented above, my problems seem to be with the argument passing. Still working on it but will leave the post up until I solve it...
– Alan
Mar 25 at 23:29
Argument passing and full path addressing confirmed good, as discussed in the revised post above.
– Alan
Mar 26 at 0:57
I guess when the p1 build task finished the p2 also terminated, try to put
Start-Sleepin the end of p1 (with how much time take p2 run) and check the p2 results.– Shayki Abramczyk
Mar 26 at 10:35
I will try the sleep as an exercise because that will help diagnose what's going on, but sadly long term it won't solve my issue. I'm trying to drive the build time as low as possible. The p2 execution is a refresh of destination data using time-consuming FTP commands. I was trying to kick-off the refresh as a separate task so the build can exit early. There's no need to delay build completion just for the data update. But that's a great insight into what may be happening. It's hard to tell because build execution is mostly hidden from view. The logs don't really help with that.
– Alan
Mar 26 at 14:37