Share via

2022 Server randomly requires reboot due to "The RPC server is unavailable." error

Anonymous
2024-07-25T16:46:16+00:00

I have a 2022 Server that randomly (usually once daily, no specific time) stops allowing RDP and local logins. It throws an RPC server is unavailable error. Any one still logged in remains in, though they are unable to reset/shut down the server. When attempting to do so via cmd prompt it returns RPC error as well. Any new login get the error after typing in user/PW. Doesn't matter if it's a domain or local account. Only way to get past this is a hard reboot.

After the reboot things return to normal and logins happen just fine. This is a VM running in Nutanix AHV. Things I've tried so far:

Upgrade VirtIO driver

Checked DNS

Checked Time

RPC service is running
Remote Registry isn't running, but it is set to auto start (triggered). Checked other working servers and it was set to this.

Checked this page from MS

https://learn.microsoft.com/en-us/troubleshoot/windows-server/user-profiles-and-logon/not-log-on-error-rpc-server-unavailable

UPDATE:

To save everyone some reading, there appear a common factor between a lot of the community. Sentinel1. Some users are reporting uninstalling it has fixed there issue. Others are downgrading versions.

Windows Server Remote and virtual desktops Session connectivity

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question. To protect privacy, user profiles for migrated questions are anonymized.

0 comments

38 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2024-09-20T16:44:33+00:00

    We finally heard from our S1 partner. We are being told the latest Service Pack (23.4 SP2 (23.4.5.337) resolves this issue.

    2 people found this answer helpful.
    0 comments
  2. Anonymous
    2024-09-20T17:12:03+00:00

    Lets go! Glad they were able to prove it was S1.

    0 comments
  3. Anonymous
    2024-10-29T00:41:05+00:00

    How are you guys holding up on this? We've updated to the version posted above for S1 and still deal with this crash ever so often. Besides trying every version only thing i got at this point is remove S1. MS support is entirely useless. Have sent the same email over and over to them for a few months and they just come back and ask the same questions. These guys can't get off the script to save their life. Anyone have a way or logging this kind of issue? Thank you

    0 comments