Unable to Reboot MID Server (Windows Server) via ECC Queue

小沢真
Tera Contributor

3 weeks ago

Hello everyone,

Please excuse my English if it’s not perfect.

 

Our team manages a MID Server running on Windows Server 2016.
As part of a certain process, we have a requirement to reboot this server.

We are using the following method to perform the reboot:
A PowerShell script containing the following command is saved as a MID Server Script File and executed via ECC Queue:

===

Restart-Computer -Force

===

 

This method used to work in the past, but at some point, the reboot stopped working and has remained that way since.
(According to what I’ve been told, this issue has been occurring since last year. However, I recently joined the team, so I’m not familiar with the exact circumstances at that time.)

 

After the reboot attempt, the following output is returned.

It seems like a permissions issue, but we are not sure of the root cause:

===

restart-computer : Failed to restart the computer EC2AMAZ-CNJN0Q0 with the following error message: Privilege held.
At line:1 char:1 + restart-computer -force + ~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : OperationStopped: (EC2AMAZ-CNJN0Q0:String) [Restart-Computer], InvalidOperationException
+ FullyQualifiedErrorId : RestartcomputerFailed,Microsoft.PowerShell.Commands.RestartComputerCommand

===

 

If anyone has experienced a similar issue or has any ideas, we would greatly appreciate your support.

 

Here is what we have checked so far to isolate the issue:

  • We have another MID Server (same configuration) where the reboot via ECC Queue works fine.

  • The MID Server account is a member of the local Administrators group.

  • When we log into the server interactively using the MID Server account and execute Restart-Computer -Force, it successfully reboots.

  • There are no differences in UAC settings between the two MID Servers.

Thank you in advance for any advice or suggestions.

0 Helpfuls
  • 263 Views
1 REPLY 1

Rafael Batistot
Kilo Patron

3 weeks ago

Hi @小沢真 

 

…is usually caused by how PowerShell remoting or service accounts handle privileges, rather than a problem with the Restart-Computer command itself. 

 

Possible Causes

  1. MID Server account lacks “Shut down the system” or “Force shutdown from a remote system” rights.
  2. Service execution context (MID Server) may not have full admin privileges due to UAC or session type.
  3. Differences in local security policy or user rights assignments between servers.

 

 

0 Helpfuls