Ошибка при проверке authorizationmanager - Ремонт и установка крупной бытовой техники

Hi All,

I’m having a problem with my Powershell. When I load either the ISE or command window I get the following error.

AuthorizationManager check failed.
At line:0 char:0

$Error[0] | select * gives me

Text

ErrorRecord                 : AuthorizationManager check failed.
Message                     : AuthorizationManager check failed.
StackTrace                  :    at System.Management.Automation.AuthorizationManager.ShouldRunInternal(CommandInfo commandInfo, CommandOrigin origin, PSHost host)
                                 at System.Management.Automation.CommandDiscovery.ShouldRun(ExecutionContext context, PSHost host, CommandInfo commandInfo, CommandOrigin commandOrigin)
                                 at System.Management.Automation.CommandDiscovery.LookupCommandProcessor(CommandInfo commandInfo, CommandOrigin commandOrigin, Nullable`1 useLocalScope, SessionStateInternal sessionState)
                                 at System.Management.Automation.CommandDiscovery.LookupCommandProcessor(String commandName, CommandOrigin commandOrigin, Nullable`1 useLocalScope)
                                 at System.Management.Automation.Runspaces.Command.CreateCommandProcessor(ExecutionContext executionContext, CommandFactory commandFactory, Boolean addToHistory, CommandOrigin origin)
                                 at System.Management.Automation.Runspaces.LocalPipeline.CreatePipelineProcessor()
                                 at System.Management.Automation.Runspaces.LocalPipeline.InvokeHelper()
                                 at System.Management.Automation.Runspaces.LocalPipeline.InvokeThreadProc()
WasThrownFromThrowStatement : False
Data                        : {}
InnerException              : System.Management.ManagementException: Invalid namespace 
                                 at System.Management.ManagementScope.Initialize()
                                 at System.Management.ManagementObject.Initialize(Boolean getObject)
                                 at System.Management.ManagementObject.Get()
                                 at System.Management.Automation.PsUtils.GetParentProcess(Process current)
                                 at System.Management.Automation.SecuritySupport.GetExecutionPolicy(String shellId, ExecutionPolicyScope scope)
                                 at System.Management.Automation.SecuritySupport.GetExecutionPolicy(String shellId)
                                 at Microsoft.PowerShell.PSAuthorizationManager.CheckPolicy(ExternalScriptInfo script, PSHost host, Exception& reason)
                                 at Microsoft.PowerShell.PSAuthorizationManager.ShouldRun(CommandInfo commandInfo, CommandOrigin origin, PSHost host, Exception& reason)
                                 at System.Management.Automation.AuthorizationManager.ShouldRunInternal(CommandInfo commandInfo, CommandOrigin origin, PSHost host)
TargetSite                  : System.Collections.ObjectModel.Collection`1[System.Management.Automation.PSObject] Invoke(System.Collections.IEnumerable)
HelpLink                    : 
Source                      : System.Management.Automation
HResult                     : -2146233087

All of the information I’ve got about this so far tells me to check my execution policy however.

Powershell

PS:> Get-ExecutionPolicy
Get-ExecutionPolicy : Invalid namespace 
At line:1 char:1
+ Get-ExecutionPolicy
+ ~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [Get-ExecutionPolicy], ManagementException
    + FullyQualifiedErrorId : System.Management.ManagementException,Microsoft.PowerShell.Commands.GetExecutionPolicyCommand

If I remove my powershell profile I don’t get an error message when starting but I do still get the error for the execution policy and I can’t run any scripts unless I copy and paste them into the ISE script pain.

Any help on this greatly appreciated as it is started to get a little annoying.

Источник

Remove From My Forums

Общие обсуждения
При попытке установить CU3 на Echange2013 CU2 на втором этапе появилось сообщение с ошибкой:
```
Ошибка:
При выполнении "$error.Clear(); 
                    & $RoleBinPathServiceControl.ps1 EnableServices Critical
                " произошла следующая ошибка: "Ошибка при проверке AuthorizationManager.".
```
как обновиться до CU3 — или вернуться к предыдущему рабочему состоянию!

Все ответы

PS C:Windowssystem32> Set-ExecutionPolicy AllSigned

Изменение политики выполнения
Политика выполнения защищает компьютер от ненадежных сценариев. Изменение политики выполнения может поставить под
угрозу безопасность системы, как описано в разделе справки, вызываемом командой about_Execution_Policies. Вы хотите
изменить политику выполнения?
[Y] Да - Y  [N] Нет - N  [S] Приостановить - S  [?] Справка (значением по умолчанию является "Y"): y
Set-ExecutionPolicy : Указанная служба не может быть запущена, так как отключена либо она сама, либо все связанные с
й устройства. (Исключение из HRESULT: 0x80070422)
строка:1 знак:1
+ Set-ExecutionPolicy AllSigned
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [Set-ExecutionPolicy], COMException
    + FullyQualifiedErrorId : System.Runtime.InteropServices.COMException,Microsoft.PowerShell.Commands.SetExecutionP
   licyCommand

Источник

I have the problem when I try to excecute file 3 (auth_test2.ps1), then I get the error-message (and the output):

AuthorizationManager check failed.
At C:UserssystemCESCHDocumentsWorkspace.auth_test1.ps1:2 char:2
+ . <<<<  ($thisScript + '.auth_test0.ps1')
    + CategoryInfo          : NotSpecified: (:) [], PSSecurityException
    + FullyQualifiedErrorId : RuntimeException

auth_test1
auth_test2

File 1 (auth_test0.ps1):

Write-Host "auth_test0"

File 2 (auth_test1.ps1):

$thisScript = Split-Path -Path $MyInvocation.MyCommand.Definition -Parent
. ($thisScript + '.auth_test0.ps1')

Write-Host "auth_test1"

File 3 (auth_test2.ps1):

$thisScript = Split-Path -Path $MyInvocation.MyCommand.Definition -Parent
. ($thisScript + '.auth_test1.ps1')

Write-Host "auth_test2"

The «ExecutionPolicy» is «RemoteSigned», «Unrestricted» makes no difference…
I hope someone can help me solve the problem.

Источник

Remove From My Forums

Общие обсуждения
При попытке установить CU3 на Echange2013 CU2 на втором этапе появилось сообщение с ошибкой:
```
Ошибка:
При выполнении "$error.Clear(); 
                    & $RoleBinPathServiceControl.ps1 EnableServices Critical
                " произошла следующая ошибка: "Ошибка при проверке AuthorizationManager.".
```
как обновиться до CU3 — или вернуться к предыдущему рабочему состоянию!

Все ответы

PS C:Windowssystem32> Set-ExecutionPolicy AllSigned

Изменение политики выполнения
Политика выполнения защищает компьютер от ненадежных сценариев. Изменение политики выполнения может поставить под
угрозу безопасность системы, как описано в разделе справки, вызываемом командой about_Execution_Policies. Вы хотите
изменить политику выполнения?
[Y] Да - Y  [N] Нет - N  [S] Приостановить - S  [?] Справка (значением по умолчанию является "Y"): y
Set-ExecutionPolicy : Указанная служба не может быть запущена, так как отключена либо она сама, либо все связанные с
й устройства. (Исключение из HRESULT: 0x80070422)
строка:1 знак:1
+ Set-ExecutionPolicy AllSigned
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [Set-ExecutionPolicy], COMException
    + FullyQualifiedErrorId : System.Runtime.InteropServices.COMException,Microsoft.PowerShell.Commands.SetExecutionP
   licyCommand

Remove From My Forums

Question
Hello,

consider this scenario:

you are a standard user and the execution Policy is set to Unrestricted for the machine (localmachine or for all scopes).

you want to run a powershell script c:testsub1sub2script1.ps1

standard users group have ntfs read permission to c:test and c:testsub1sub2, but NOT c:testsub1

standard users can browse and read files inside c:testsub1sub2

The problem is that when running the command powershell.exe -file c:testsub1sub2script1.ps1

I get the following error:

AuthorizationManager check failed.

CategoryInfo: Not Specified: (:) [], ParentContainsErrorRecordException

FullyQualifiedErrorId: RuntimeException

Is it normal ?

The workaround I’ve found to make it work is to call the powershell with bypass argument:

powershell.exe -executionpolicy bypass -file c:testsub1sub2script1.ps1

or to add at least the ntfs permission «List folder / read data» to users for the folder c:testsub1

I do ask in the forum because I have this problem with SCCM clients, the folder is c:windowsccmcache is not accessible to interactive users, only subfolders which contains packages and scripts. And suddently powershell fails for package
running as current logged on users, and with execution Policy set to remotesigned.

Is there a recent windows update which changed the behavior of powershell ?

Thank you.
- Edited by
  Tuesday, October 13, 2015 9:16 AM

Answers

We got a response from MS:

Cause

Unfortunately the issue is caused by a design limitation. For AppLocker to work the mechanisms (AiGetFullImagePath function) are querying the full path of the folder structure up to where the allowed for the user application or script
is stored, thus breaking up with access denied inside an internal kernel function (GetFinalPathNameByHandleW) when the user does not have at least the desired read access at some point on the folder structure chain and because it is not directly denied by
the AppLocker policy no error is presented directly on the screen and only in the event logs is logged.

Resolution

To resolve the issue the administrator must give the users at least the desired read permissions to user, who have to run these applications or scripts, for all the folder on the chain from the root of the partition up to the folder
where the script or application resides.

Unfortunately this is not possible in the SCCM portion of our scenario because the CCM Executive is resetting the permissions for the users on the ccmcache folder, under which the scripts, which are being run in the user context, are
stored and executed, thus presenting an issue for such scenarios.

Our SCCM product group has been informed of this behavior. This information is being discussed and reviewed for future updates. Unfortunately, I will not be able to give you any timeline for a patch
resolving this scenario.
- Marked as answer by
  Larry.B.IT
  Tuesday, March 8, 2016 12:39 PM

Remove From My Forums

Question
Hello,

consider this scenario:

you are a standard user and the execution Policy is set to Unrestricted for the machine (localmachine or for all scopes).

you want to run a powershell script c:testsub1sub2script1.ps1

standard users group have ntfs read permission to c:test and c:testsub1sub2, but NOT c:testsub1

standard users can browse and read files inside c:testsub1sub2

The problem is that when running the command powershell.exe -file c:testsub1sub2script1.ps1

I get the following error:

AuthorizationManager check failed.

CategoryInfo: Not Specified: (:) [], ParentContainsErrorRecordException

FullyQualifiedErrorId: RuntimeException

Is it normal ?

The workaround I’ve found to make it work is to call the powershell with bypass argument:

powershell.exe -executionpolicy bypass -file c:testsub1sub2script1.ps1

or to add at least the ntfs permission «List folder / read data» to users for the folder c:testsub1

I do ask in the forum because I have this problem with SCCM clients, the folder is c:windowsccmcache is not accessible to interactive users, only subfolders which contains packages and scripts. And suddently powershell fails for package
running as current logged on users, and with execution Policy set to remotesigned.

Is there a recent windows update which changed the behavior of powershell ?

Thank you.
- Edited by
  Tuesday, October 13, 2015 9:16 AM

Answers

We got a response from MS:

Cause

Unfortunately the issue is caused by a design limitation. For AppLocker to work the mechanisms (AiGetFullImagePath function) are querying the full path of the folder structure up to where the allowed for the user application or script
is stored, thus breaking up with access denied inside an internal kernel function (GetFinalPathNameByHandleW) when the user does not have at least the desired read access at some point on the folder structure chain and because it is not directly denied by
the AppLocker policy no error is presented directly on the screen and only in the event logs is logged.

Resolution

To resolve the issue the administrator must give the users at least the desired read permissions to user, who have to run these applications or scripts, for all the folder on the chain from the root of the partition up to the folder
where the script or application resides.

Unfortunately this is not possible in the SCCM portion of our scenario because the CCM Executive is resetting the permissions for the users on the ccmcache folder, under which the scripts, which are being run in the user context, are
stored and executed, thus presenting an issue for such scenarios.

Our SCCM product group has been informed of this behavior. This information is being discussed and reviewed for future updates. Unfortunately, I will not be able to give you any timeline for a patch
resolving this scenario.
- Marked as answer by
  Larry.B.IT
  Tuesday, March 8, 2016 12:39 PM

Remove From My Forums

Question

I’m trying to run a powershell script that access the VSTS API and it works ok if I run it in PowerShell ISE.

But I need to add the script as a task in the release process in VSTS and I’m getting

a security error. The error I got is:

AuthorizationManager check failed. CategoryInfo :

SecurityError: (:) [], PSSecurityException FullyQualifiedErrorId : UnauthorizedAccess

The script just get the work items from an specific build and then saves those

work items to a file like follows

function Invoke-ServiceGetBuilds($headers)
{
    Invoke-RestMethod -Uri https://myaccount.visualstudio.com/DefaultCollection/My-Software/_apis/build/builds?api-version=2.0"&"minFinishTime=2016-12-01"&"buildNumber=master_*"&"resultFilter=succeeded -headers $headers -Method Get
    return $result
}

$username = "usr"
$password = "pass*"
$filePath = "file.html"
$releaseName = ""

$basicAuth = ("{0}:{1}" -f $username, $password)
$basicAuth = [System.Text.Encoding]::UTF8.GetBytes($basicAuth);
$basicAuth = [System.Convert]::ToBase64String($basicAuth)
$headers = @{Authorization=("Basic {0}" -f $basicAuth)}

$returnedBuilds = Invoke-ServiceGetBuilds $headers

#...create the object and the array of workitems HTML
ConvertTo-Html -body "<h2>Build Information and WI</h2> $workItemsHtml" -Title "Release Report" | Out-File $filePath

The script works well if I run it from PowerShell ISE but fails in VSTS Any idea on how to fix this issue

Luis Diego Rojas. http://icomparable.blogspot.com

MCP, MCTS Biztalk Server, MCTS WCF

Edited by
Thursday, December 8, 2016 6:18 PM

Hi All,

I’m having a problem with my Powershell. When I load either the ISE or command window I get the following error.

AuthorizationManager check failed.
At line:0 char:0

$Error[0] | select * gives me

Text

ErrorRecord                 : AuthorizationManager check failed.
Message                     : AuthorizationManager check failed.
StackTrace                  :    at System.Management.Automation.AuthorizationManager.ShouldRunInternal(CommandInfo commandInfo, CommandOrigin origin, PSHost host)
                                 at System.Management.Automation.CommandDiscovery.ShouldRun(ExecutionContext context, PSHost host, CommandInfo commandInfo, CommandOrigin commandOrigin)
                                 at System.Management.Automation.CommandDiscovery.LookupCommandProcessor(CommandInfo commandInfo, CommandOrigin commandOrigin, Nullable`1 useLocalScope, SessionStateInternal sessionState)
                                 at System.Management.Automation.CommandDiscovery.LookupCommandProcessor(String commandName, CommandOrigin commandOrigin, Nullable`1 useLocalScope)
                                 at System.Management.Automation.Runspaces.Command.CreateCommandProcessor(ExecutionContext executionContext, CommandFactory commandFactory, Boolean addToHistory, CommandOrigin origin)
                                 at System.Management.Automation.Runspaces.LocalPipeline.CreatePipelineProcessor()
                                 at System.Management.Automation.Runspaces.LocalPipeline.InvokeHelper()
                                 at System.Management.Automation.Runspaces.LocalPipeline.InvokeThreadProc()
WasThrownFromThrowStatement : False
Data                        : {}
InnerException              : System.Management.ManagementException: Invalid namespace 
                                 at System.Management.ManagementScope.Initialize()
                                 at System.Management.ManagementObject.Initialize(Boolean getObject)
                                 at System.Management.ManagementObject.Get()
                                 at System.Management.Automation.PsUtils.GetParentProcess(Process current)
                                 at System.Management.Automation.SecuritySupport.GetExecutionPolicy(String shellId, ExecutionPolicyScope scope)
                                 at System.Management.Automation.SecuritySupport.GetExecutionPolicy(String shellId)
                                 at Microsoft.PowerShell.PSAuthorizationManager.CheckPolicy(ExternalScriptInfo script, PSHost host, Exception& reason)
                                 at Microsoft.PowerShell.PSAuthorizationManager.ShouldRun(CommandInfo commandInfo, CommandOrigin origin, PSHost host, Exception& reason)
                                 at System.Management.Automation.AuthorizationManager.ShouldRunInternal(CommandInfo commandInfo, CommandOrigin origin, PSHost host)
TargetSite                  : System.Collections.ObjectModel.Collection`1[System.Management.Automation.PSObject] Invoke(System.Collections.IEnumerable)
HelpLink                    : 
Source                      : System.Management.Automation
HResult                     : -2146233087

All of the information I’ve got about this so far tells me to check my execution policy however.

Powershell

PS:> Get-ExecutionPolicy
Get-ExecutionPolicy : Invalid namespace 
At line:1 char:1
+ Get-ExecutionPolicy
+ ~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [Get-ExecutionPolicy], ManagementException
    + FullyQualifiedErrorId : System.Management.ManagementException,Microsoft.PowerShell.Commands.GetExecutionPolicyCommand

Any help on this greatly appreciated as it is started to get a little annoying.

I was recently working in a client environment and running a PowerShell script that calls a bunch of other scripts on the file system using the dot sourcing technique. The scripts run fine in a number of other customer environments as well as our test environment but I kept seeing an “AuthorizationManager check failed” when several scripts were called from the main script.

I messed around with permissions for while and then drank a few beers to see if things with PowerShell were now better. The PowerShell wasn’t better but I felt okay with the addition of the beers. I still needed to find a solution, though, and decided to approach this fresh after a few days (and possibly more beers!).

With a fresh approach, I found a simple post that sprung the entire solution for me. I had used Internet Explorer (I know, I know…I was on a Windows Server 2008 R2 box in a customer environment…not much choice there) to pull down a few PowerShell files over HTTP from our website. Guess which files I pulled down using IE. Yep! You betcha…the very script files that all failed when the AuthorizationManager calls ran! Needless to say, you should unblock PowerShell script files downloaded using IE, even if they’re from your own web site!

The key is to unblock files that you’ve downloaded so PowerShell will run them

Check out the screen shot below to make the simple unblock from the PowerShell script file properties. Just right-click the file and choose Properties from the context menu.

Login

#powershell #module #exchange-server #connect #runspace

#powershell #модуль #exchange-сервер #Контакты #пространство выполнения

Вопрос:

Я пытаюсь запустить свой код из Visual Studio. Код предназначен для создания runspace и подключения exchange online для запуска скрипта poweshell. Начальная строка скрипта

   if (Get-Module -ListAvailable | Where-Object {$_.Name -eq 'ExchangeOnlineManagement'}) {
                                            Write-Host ""Module ExchangeOnlineManagement is not imported, but available on disk. Importing it. ""
                                    Import-Module ExchangeOnlineManagement
                        }

При выполнении он выдает ошибку

 AuthorizationManager check failed.The 'Connect-ExchangeOnline' command was found in the module 'ExchangeOnlineManagement', but the module could not be loaded. For more information, run 'Import-Module ExchangeOnlineManagement'

Кто-нибудь может помочь найти проблему?

Ответ №1:

Решение: создайте веб-задание вместо консольного приложения.

Теперь это разрешено. Проблема была с консольным приложением. Когда я создал новое веб-приложение для работы, тот же код работает хорошо.

Ошибка с ошибкой проверки AuthorizationManager возникает при попытке запустить этот сценарий PowerShell в консольном приложении. Эта ошибка не появляется в веб-задании и успешно подключена к Exchange online.

The workaround is, have additional step before that to copy it locally to a temp folder, and run PS script local.

Sent from my Windows Phone

From: tanyabrmailto:notifications@github.com
Sent: ‎7/‎19/‎2016 11:44 PM
To: Microsoft/vsts-tasksmailto:vsts-tasks@noreply.github.com
Cc: asvyatmailto:asvyat@hotmail.com; Mentionmailto:mention@noreply.github.com
Subject: Re: [Microsoft/vsts-tasks] PS script failure ‘AuthorizationManager check failed (#974)

I have the same error, tried everything listed above, but was unsuccessful… Could you try helping me resolve this?..
I use powerhsell on target machine task to run a deployment script from a shared location (release management). This is the error I receive:
2016-07-19T12:03:48.6324750Z Deployment started on target machine…
2016-07-19T12:03:48.6324750Z System.AggregateException: Failed to execute the configuration data script. Consult the logs below for details of the error.
2016-07-19T12:03:48.6324750Z AuthorizationManager check failed. —> System.Management.Automation.PSSecurityException: AuthorizationManager check failed. —> System.Management.Automation.Host.HostException: A command that prompts the user failed because the host program or the command type does not support user interaction. The host was attempting to request confirmation with the following message: Run only scripts that you trust. While scripts from the internet can be useful, this script can potentially harm your computer. If you trust this script, use the Unblock-File cmdlet to allow the script to run without this warning message. Do you want to run versionserverrepoRMInitScriptsIISInitializationScript.ps1?
2016-07-19T12:03:48.6324750Z at System.Management.Automation.Internal.Host.InternalHostUserInterface.PromptForChoice(String caption, String message, Collection1 choices, Int32 defaultChoice) 2016-07-19T12:03:48.6324750Z at Microsoft.PowerShell.PSAuthorizationManager.RemoteFilePrompt(String path, PSHost host) 2016-07-19T12:03:48.6324750Z at Microsoft.PowerShell.PSAuthorizationManager.CheckPolicy(ExternalScriptInfo script, PSHost host, Exception& reason) 2016-07-19T12:03:48.6324750Z at Microsoft.PowerShell.PSAuthorizationManager.ShouldRun(CommandInfo commandInfo, CommandOrigin origin, PSHost host, Exception& reason) 2016-07-19T12:03:48.6324750Z at System.Management.Automation.AuthorizationManager.ShouldRunInternal(CommandInfo commandInfo, CommandOrigin origin, PSHost host) 2016-07-19T12:03:48.6324750Z --- End of inner exception stack trace --- 2016-07-19T12:03:48.6324750Z at System.Management.Automation.Runspaces.PipelineBase.Invoke(IEnumerable input) 2016-07-19T12:03:48.6324750Z at System.Management.Automation.PowerShell.Worker.ConstructPipelineAndDoWork(Runspace rs, Boolean performSyncInvoke) 2016-07-19T12:03:48.6324750Z at System.Management.Automation.PowerShell.Worker.CreateRunspaceIfNeededAndDoWork(Runspace rsToUse, Boolean isSync) 2016-07-19T12:03:48.6324750Z at System.Management.Automation.PowerShell.CoreInvokeHelper[TInput,TOutput](PSDataCollection1 input, PSDataCollection1 output, PSInvocationSettings settings) 2016-07-19T12:03:48.6324750Z at System.Management.Automation.PowerShell.CoreInvoke[TInput,TOutput](PSDataCollection1 input, PSDataCollection1 output, PSInvocationSettings settings) 2016-07-19T12:03:48.6324750Z at System.Management.Automation.PowerShell.CoreInvoke[TOutput](IEnumerable input, PSDataCollection1 output, PSInvocationSettings settings)
2016-07-19T12:03:48.6324750Z at Microsoft.VisualStudio.Services.DevTestLabs.RemoteDeployer.Deployment.PowershellExecutor.<>c__DisplayClass28_0.b__0()
2016-07-19T12:03:48.6324750Z at Microsoft.VisualStudio.Services.DevTestLabs.RemoteDeployer.Utilities.RetryExecutor.<>c__DisplayClass19_01.<Execute>b__0() 2016-07-19T12:03:48.6324750Z at Microsoft.VisualStudio.Services.DevTestLabs.RemoteDeployer.Utilities.RetryExecutor.Execute(Action action) 2016-07-19T12:03:48.6324750Z at Microsoft.VisualStudio.Services.DevTestLabs.RemoteDeployer.Utilities.RetryExecutor.Execute[T](Func1 action)
2016-07-19T12:03:48.6324750Z at Microsoft.VisualStudio.Services.DevTestLabs.RemoteDeployer.Deployment.PowershellExecutor.Invoke(String errorContextMessage, Boolean writeResultToLog, Boolean isCancellable, ActionPreference errorActionPreference)
2016-07-19T12:03:48.6324750Z — End of inner exception stack trace —
2016-07-19T12:03:48.6324750Z at Microsoft.VisualStudio.Services.DevTestLabs.RemoteDeployer.Deployment.PowershellExecutor.Invoke(String errorContextMessage, Boolean writeResultToLog, Boolean isCancellable, ActionPreference errorActionPreference)
2016-07-19T12:03:48.6324750Z at Microsoft.VisualStudio.Services.DevTestLabs.RemoteDeployer.Deployment.DeploymentService.ExecuteConfigurationData(IPowerShell powerShellSession, String dscConfiguration)
2016-07-19T12:03:48.6324750Z at Microsoft.VisualStudio.Services.DevTestLabs.RemoteDeployer.Deployment.DeploymentService.RunPowerShellScripts(DeploymentMachineSpecification deploymentMachine, ScriptSpecification scriptSpecification, ScriptSpecification initializationScriptSpecification, String applicationPath, IPowerShell powerShellSession)
2016-07-19T12:03:48.6324750Z —> (Inner Exception #0) System.Management.Automation.PSSecurityException: AuthorizationManager check failed. —> System.Management.Automation.Host.HostException: A command that prompts the user failed because the host program or the command type does not support user interaction. The host was attempting to request confirmation with the following message: Run only scripts that you trust. While scripts from the internet can be useful, this script can potentially harm your computer. If you trust this script, use the Unblock-File cmdlet to allow the script to run without this warning message. Do you want to run versionserverrepoRMInitScriptsIISInitializationScript.ps1?
2016-07-19T12:03:48.6324750Z at System.Management.Automation.Internal.Host.InternalHostUserInterface.PromptForChoice(String caption, String message, Collection1 choices, Int32 defaultChoice) 2016-07-19T12:03:48.6324750Z at Microsoft.PowerShell.PSAuthorizationManager.RemoteFilePrompt(String path, PSHost host) 2016-07-19T12:03:48.6324750Z at Microsoft.PowerShell.PSAuthorizationManager.CheckPolicy(ExternalScriptInfo script, PSHost host, Exception& reason) 2016-07-19T12:03:48.6324750Z at Microsoft.PowerShell.PSAuthorizationManager.ShouldRun(CommandInfo commandInfo, CommandOrigin origin, PSHost host, Exception& reason) 2016-07-19T12:03:48.6324750Z at System.Management.Automation.AuthorizationManager.ShouldRunInternal(CommandInfo commandInfo, CommandOrigin origin, PSHost host) 2016-07-19T12:03:48.6324750Z --- End of inner exception stack trace --- 2016-07-19T12:03:48.6324750Z at System.Management.Automation.Runspaces.PipelineBase.Invoke(IEnumerable input) 2016-07-19T12:03:48.6324750Z at System.Management.Automation.PowerShell.Worker.ConstructPipelineAndDoWork(Runspace rs, Boolean performSyncInvoke) 2016-07-19T12:03:48.6324750Z at System.Management.Automation.PowerShell.Worker.CreateRunspaceIfNeededAndDoWork(Runspace rsToUse, Boolean isSync) 2016-07-19T12:03:48.6481064Z at System.Management.Automation.PowerShell.CoreInvokeHelper[TInput,TOutput](PSDataCollection1 input, PSDataCollection1 output, PSInvocationSettings settings) 2016-07-19T12:03:48.6481064Z at System.Management.Automation.PowerShell.CoreInvoke[TInput,TOutput](PSDataCollection1 input, PSDataCollection1 output, PSInvocationSettings settings) 2016-07-19T12:03:48.6481064Z at System.Management.Automation.PowerShell.CoreInvoke[TOutput](IEnumerable input, PSDataCollection1 output, PSInvocationSettings settings)
2016-07-19T12:03:48.6481064Z at Microsoft.VisualStudio.Services.DevTestLabs.RemoteDeployer.Deployment.PowershellExecutor.<>c__DisplayClass28_0.b__0()
2016-07-19T12:03:48.6481064Z at Microsoft.VisualStudio.Services.DevTestLabs.RemoteDeployer.Utilities.RetryExecutor.<>c__DisplayClass19_01.<Execute>b__0() 2016-07-19T12:03:48.6481064Z at Microsoft.VisualStudio.Services.DevTestLabs.RemoteDeployer.Utilities.RetryExecutor.Execute(Action action) 2016-07-19T12:03:48.6481064Z at Microsoft.VisualStudio.Services.DevTestLabs.RemoteDeployer.Utilities.RetryExecutor.Execute[T](Func1 action)
2016-07-19T12:03:48.6481064Z at Microsoft.VisualStudio.Services.DevTestLabs.RemoteDeployer.Deployment.PowershellExecutor.Invoke(String errorContextMessage, Boolean writeResultToLog, Boolean isCancellable, ActionPreference errorActionPreference)<—

You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
#974 (comment)

Источник

Remove From My Forums

Question

I’m trying to run a powershell script that access the VSTS API and it works ok if I run it in PowerShell ISE.

But I need to add the script as a task in the release process in VSTS and I’m getting

a security error. The error I got is:

AuthorizationManager check failed. CategoryInfo :

SecurityError: (:) [], PSSecurityException FullyQualifiedErrorId : UnauthorizedAccess

The script just get the work items from an specific build and then saves those

work items to a file like follows

function Invoke-ServiceGetBuilds($headers)
{
    Invoke-RestMethod -Uri https://myaccount.visualstudio.com/DefaultCollection/My-Software/_apis/build/builds?api-version=2.0"&"minFinishTime=2016-12-01"&"buildNumber=master_*"&"resultFilter=succeeded -headers $headers -Method Get
    return $result
}

$username = "usr"
$password = "pass*"
$filePath = "file.html"
$releaseName = ""

$basicAuth = ("{0}:{1}" -f $username, $password)
$basicAuth = [System.Text.Encoding]::UTF8.GetBytes($basicAuth);
$basicAuth = [System.Convert]::ToBase64String($basicAuth)
$headers = @{Authorization=("Basic {0}" -f $basicAuth)}

$returnedBuilds = Invoke-ServiceGetBuilds $headers

#...create the object and the array of workitems HTML
ConvertTo-Html -body "<h2>Build Information and WI</h2> $workItemsHtml" -Title "Release Report" | Out-File $filePath

The script works well if I run it from PowerShell ISE but fails in VSTS Any idea on how to fix this issue

Luis Diego Rojas. http://icomparable.blogspot.com

MCP, MCTS Biztalk Server, MCTS WCF

Edited by

Thursday, December 8, 2016 6:18 PM

Источник

Общие обсуждения

Все ответы

Общие обсуждения

Все ответы

Question

Answers

Question

Answers

Question

The key is to unblock files that you’ve downloaded so PowerShell will run them

Login

Вопрос:

Ответ №1:

Question