AuthorizationManager check failed

[derekgreer]

When installing NuGetPowerTools, I receive the following error:

PM> Install-Package NuGetPowerTools
Successfully installed 'NuGetPowerTools 0.29'.
Import-Module : AuthorizationManager check failed.
At C:\Temp\ConsoleApplication1\packages\NuGetPowerTools.0.29\tools\init.ps1:2 char:14

• Import-Module <<<< (Join-Path $toolsPath NuGetPowerTools.psd1)
  • CategoryInfo : NotSpecified: (:) [Import-Module], PSSecurityException
  • FullyQualifiedErrorId : RuntimeException,Microsoft.PowerShell.Commands.ImportModuleCommand

This was also reported by someone else on David's article: http://blog.davidebbo.com/2011/08/easy-way-to-set-up-nuget-to-restore.html

[ddyson]

I am also getting this error with version 0.29

[Henrik-R]

Version 0.29

I also get this on VS 2010

Version 10.0.31118.1 SP1Rel

[davidfowl]

Are you guys in a corporate environment where script execution is disabled?

[ddyson]

I am in a corporate environment. What type of scripts? I have full admin rights on my machine

[davidfowl]

Powershell

[Henrik-R]

I'm also in a corporate environment. I work as a consultant, but one of the regulars does not think that PowerShell execution is disabled.

He used the following workaround:

Set-executionpolicy bypass –scope process

However another workaround also did the trick for me:

http://blog.davidebbo.com/2011/08/easy-way-to-set-up-nuget-to-restore.html?showComment=1316201271755#c7109629103299493214

[Henrik-R]

I'm also in a corporate environment. I work as a consultant, but one of the
regulars does not think that PowerShell execution is disabled.

He used the following workaround:

Set-executionpolicy bypass scope process

However another workaround also did the trick for me

http://blog.davidebbo.com/2011/08/easy-way-to-set-up-nuget-to-restore.html?showComment=1316201271755#c7109629103299493214

/Henrik

On Tue, Sep 27, 2011 at 12:07, David Fowler <
reply@reply.github.com>wrote:

Are you guys in a corporate environment where script execution is disabled?

Reply to this email directly or view it on GitHub:
#8 (comment)

[derekgreer]

I have execution policy set to unrestricted, but I'm still receiving the same error.

PM> install-package nugetpowertools
Successfully installed 'NuGetPowerTools 0.29'.
Import-Module : AuthorizationManager check failed.
At C:\Temp\ClassLibrary1\packages\NuGetPowerTools.0.29\tools\init.ps1:2 char:14

• Import-Module <<<< (Join-Path $toolsPath NuGetPowerTools.psd1)
  • CategoryInfo : NotSpecified: (:) [Import-Module], PSSecurityException
  • FullyQualifiedErrorId : RuntimeException,Microsoft.PowerShell.Commands.ImportModuleCommand

---

INSTRUCTIONS

---

• To enable building a package from a project use the Enable-PackageBuild command
• To enable restoring packages on build use the Enable-PackageRestore command.
• When using one of the above commands, a .nuget folder will been added to your
  solution root. Make sure you check it in!
• For for information, see https://github.com/davidfowl/NuGetPowerTools

  ---

PM> get-executionpolicy -list

                                                                          Scope                                                                    ExecutionPolicy
                                                                          -----                                                                    ---------------
                                                                  MachinePolicy                                                                          Undefined
                                                                     UserPolicy                                                                          Undefined
                                                                        Process                                                                       Unrestricted
                                                                    CurrentUser                                                                          Undefined
                                                                   LocalMachine                                                                       Unrestricted

[Henrik-R]

PM> get-executionpolicy -list

Scope                                                                           ExecutionPolicy
-----                                                                           ---------------
MachinePolicy                                                                   Undefined
UserPolicy                                                                      Undefined
Process                                                                         RemoteSigned
CurrentUser                                                                     Undefined
LocalMachine                                                                    Undefined

[davidfowl]

What's the encoding of the NuGetPowerTools script files on disk.

[Henrik-R]

As previously mentioned I changed the encoding of the tools/NuGetPowerTools.psm1 file as suggested here

http://blog.davidebbo.com/2011/08/easy-way-to-set-up-nuget-to-restore.html?showComment=1316201271755#c7109629103299493214

File                                                         Encoding as seen in Notepad++
-----                                                        ----------
tools/MSBuild.psm1                                           Ansi (Dos/Windows)
tools/NuGetMSBuild.psm1                                      Ansi (Dos/Windows)
tools/NuGetPowerTools.psd1                                   Ansi (Dos/Windows)
tools/NuGetPowerTools.psm1                                   UTF-8 (Unix)
tools/VS.psm1                                                Ansi (Dos/Windows)
tools/init.ps1                                               Ansi (Dos/Windows)

[derekgreer]

How do I determine this?

On Wed, Sep 28, 2011 at 7:21 AM, David Fowler <
reply@reply.github.com>wrote:

What's the encoding of the NuGetPowerTools script files on disk.

Reply to this email directly or view it on GitHub:
#8 (comment)

Derek Greer
dbgreer@gmail.com s @derekgreer http://twitter.com/derekgreer
aspiringcraftsman.com s lostechies.com http://derekgreer.lostechies.com/

[jeffgoo]

I too am seeing the ANSI encoded powershell scripts in version 0.29 causing the failed AuthorizationManager check. When I fixed up my NuGetPowerTools.nupkg locally, that is changing the scripts to utf-8, the problem was resolved.