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-08-15T14:39:34+00:00

    That's good to know! All symptoms I've seen lead to that service being stopped. We are working with our SOC to verify if it is indeed S1 causing it.

    0 comments
  2. Anonymous
    2024-08-15T14:48:26+00:00

    Yes, we see local session manager crashing on the systems that have this issue. We have been downgrading the S1 agent to v23.3.3.264 but it is too soon to tell if that will correct the issue.

    0 comments
  3. Anonymous
    2024-08-15T16:50:06+00:00

    Dealing with this same garbage since April 2024 - that's when we first started noticing it. We also have S1 in our environment but like you all said every endpoint we have has S1 installed but its only about 15 or so Windows 2022 servers we have that continue to Local Session Manager crash. We've created alerts to track how often its happened but it's always the same servers. One thing I noticed is that when it would LSM crash we would have a windows update installed the same day that the LSM crash would happen. I've been thinking its patches this whole time. I was convinced it was the April security patches but we uninstalled those on the servers. Had 15 or so days of no crashing, then suddenly a week of constant crashing.

    I haven't checked the S1 avenue at all, but I will investigate it. Please let me know if you guys find something substantial on the S1 end.

    0 comments
  4. Anonymous
    2024-08-15T20:01:16+00:00

    This is our exact symptoms as well. We have removed SentinelOne from the affected machine and replaced with MWB temporarily, going to let this stew for 48 hours and will report back in when this either reoccurs or not.

    0 comments
  5. Anonymous
    2024-08-15T20:16:20+00:00

    What we've found is the LSM service stops during a sign-out process, sometimes it takes several log-out and log-in attempts to get it to get to break, but we can recreate the issue pretty much on command. Once issue occurs the only way to log back in is to restart the server. We have seen this on a mix of Operating Systems. Server 2022, Server 2019, and Windows 10.

    0 comments