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 No comments
{count} votes

38 answers

Sort by: Most helpful
  1. Anonymous
    2024-08-15T20:23:01+00:00

    Let me throw this out there. Are any of ya'll running a database on your server? I was running postgres. Looking back the issue seemed to have been fixed after we asked our SOC to exclude the postgres from S1.

    D:\Program Files\PostgreSQL\15\bin\Postgres.exe 

    and 

    D:\Program Files\PostgreSQL\15\data and everything under here

    0 comments No comments
  2. Anonymous
    2024-08-15T20:30:46+00:00

    No Databases \ SQL here.

    0 comments No comments
  3. Anonymous
    2024-08-15T20:57:10+00:00

    Its happened to RDS servers, MSSQL servers, print servers and even on a single Win10 device.

    More often on RDS servers so maybe the more logout events the more likely as someone mentioned here.

    0 comments No comments
  4. Anonymous
    2024-08-15T23:41:19+00:00

    This is very interesting- I wasn’t sure how to recreate but now I’m curious if I can do the same. These servers are RDS ones so I’m going to give this a try. As for Postgres this is possible going to look through the processes on these servers. They all run the same app suite.

    We’ve seen it too on 2019 and 2022 but not on any workstations as of writing

    0 comments No comments
  5. Anonymous
    2024-08-16T02:32:32+00:00

    Been unable to replicate this with multiple logins - did about approx 15 to 20 on an admin and normal end user account but LSM never crashed. Also my server endpoints do not have Postgre SQL or any kind of SQL. We've made no S1 adjustments yet mainly because we don't know what to exclude but S1 itself but we don't have an alternative right now. So far I am just placing a daily restart on these endpoints and waiting for it to happen again. The trend is a few times a week right now and almost ALWAYS after some patch (doesn't matter what KB) has been installed. I've also opened a ticket with MS on this.

    Will update if this gets anywhere

    0 comments No comments