Ошибка при проверке authorizationmanager - Oshibku.top - решение и исправление самых разных ошибок

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

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(); 
                    & $RoleBinPath\ServiceControl.ps1 EnableServices Critical
                " произошла следующая ошибка: "Ошибка при проверке AuthorizationManager.".
```
как обновиться до CU3 — или вернуться к предыдущему рабочему состоянию!

Все ответы

PS C:\Windows\system32> 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

Источник

Loading…

Skip to page content

Источник

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:\Users\systemCESCH\Documents\Workspace.\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.

Источник

Question

<img decoding="async" onError="javascript: wp_broken_images = window.wp_broken_images || function(){}; wp_broken_images(this);" alt="RRS feed" src="https://i1.social.s-msft.com/globalresources/Images/trans.gif?cver=0001" />

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

Все ответы

Интересное по теме: