페푸리의 Office Server 이야기

문제 서명:

  문제 이벤트 이름:        PowerShell

  NameOfExe:        powershell.exe

  FileVersionOfSystemManagementAutomation:        6.1.7601.18606

  InnermostExceptionType:        System.Management.Automation.PSArgument

  OutermostExceptionType:        System.Management.Automation.PSArgument

  DeepestPowerShellFrame:        ell.ConsoleControl.CheckWriteConsoleOutputContents

  DeepestFrame:        ell.ConsoleControl.CheckWriteConsoleOutputContents

  ThreadName:        Consol.. main thread

  OS 버전:        6.3.9600.2.0.0.400.8

  로캘 ID:        1042

온라인 개인 정보 취급 방침 읽기:

  http://go.microsoft.com/fwlink/?linkid=280262

온라인 개인 정보 취급 방침을 사용할 수 없으면 오프라인으로 개인 정보 취급 방침을 읽으십시오.

  C:\Windows\system32\ko-KR\erofflps.txt

In this log file excerpt, Return value 3 appears next to CA_SAVEDATA_STOP_SERVICES.

Microsoft Exchange uses Custom Actions (CAs) when it installs update rollup packages by using the Windows Installer engine. In the CA_SAVEDATA_STOP_SERVICES custom action, Microsoft Exchange tries to run the PowerShell script that is named servicecontrol.ps1 together with the BeforePatch option.

In this case, the script did not run because of an incorrect ExecutionPolicy setting in PowerShell. To determine the current PowerShell execution policy, run the Get-ExecutionPolicy cmdlet. By default, the PowerShell execution policy is set to RemoteSigned.

To resolve this issue, set the ExecutionPolicy to RemoteSigned or to Unrestricted. Then, try to install the update rollup again. After the update rollup has been installed, set the ExecutionPolicy to RemoteSigned.