-
Notifications
You must be signed in to change notification settings - Fork 905
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Start-ChocolateyProcessAsAdmin.ps1 errors when running PowerShell scripts #1220
Comments
Its related to this change: e208ca2#diff-208a9466943493065fc7c68d8479cdccR118 I'm calling Start-ChocolateyProcessAsAdmin like this:
and I'm getting the error:
I'm not sure why the change is causing it to fail, but I do think the push-location should be part of the Start- call's arguments so I'm making that modification. |
@skyguy94 I think your script has a possible bug in it. We always say full paths to files. Always. Before we started up PowerShell from the location of the script, which may have allowed it to work properly.
|
That could be, I'll fix it up to specify the full path, but I'm seeing the issue in a new provisioned server with chef too:
|
I think its more of an issue with the
|
I'm seeing that as well. We are working to turn around 0.10.5 to get this fixed ASAP. |
Use old encoded command method for now. It works well although it puts a lot of CLIXML into stderr and onto the screen when it runs.
* stable: (version) 0.10.5 (doc) update CHANGELOG/nuspec (GH-1224) support longer timeouts (doc) update CHANGELOG/nuspec (GH-1222) choco outdated -r output - no header (maint) update NuGet.Core (GH-1220) Use old method (GH-1220) Fix: PowerShell blocks fail in Start-ChocolateyProcessAsAdmin (doc) update CHANGELOG/nuspec
What You Are Seeing?
On 0.10.4 I am getting back a try/catch error. I have a gist of it working in 0.10.3 and failing in 0.10.4. Currently this is for the tomcat module. I haven't checked or seen issues in other modules yet.
gist
What is Expected?
No errors.
How Did You Get This To Happen? (Steps to Reproduce)
Our Puppet system upgraded servers to 0.10.4, attempted to install the tomcat module and received this failure.
Output Log
See above gist
Notes
This reverts what was implemented with #1126
The text was updated successfully, but these errors were encountered: