event ID 7034 - Local Session Manager service terminated unexpectedly

Question

One of our RDS session host server stopped serving user connection request.  From AWS console, the RDS session host server was still alive.

 lot of users could not get connection. I would like to know why this happened or root cause of it.

The event detail is shown below:

- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

- <System>

  <Provider Name="Service Control Manager" EventSourceName="Service Control Manager" /> 

  <EventID Qualifiers="49152">7034</EventID> 

  <Version>0</Version> 

  <Level>2</Level> 

  <Task>0</Task> 

  <Opcode>0</Opcode> 

  <Keywords>0x8080000000000000</Keywords> 

  <TimeCreated SystemTime="2025-01-30T15:37:13.716799600Z" /> 

  <EventRecordID>1522810</EventRecordID> 

  <Correlation /> 

  <Execution ProcessID="884" ThreadID="12392" /> 

  <Channel>System</Channel> 

   <Security /> 

  </System>

- <EventData>

  <Data Name="param1">Local Session Manager</Data> 

  <Data Name="param2">1</Data> 

  <Binary>4C0053004D000000</Binary> 

  </EventData>

  </Event>

Answer 1

Hello,

Here are some more in-depth steps you can take to troubleshoot the issue on your RDS session host server:

1. Look for additional error messages or warnings in the System and Application logs around the time of the event (2025-01-30T15:37:13.716799600Z). Pay attention to events related to resource usage, service dependencies, or user profile issues.
2. Use tools like Performance Monitor or Task Manager to check CPU, memory, and disk usage around the time of the crash. Look for patterns of high resource consumption.
3. Open the Services console (services.msc) and check the dependencies of the Local Session Manager service. Ensure that all dependent services are running.

I hope this information helps.

Best regards,

Karlie Weng

Answer 2

Thank you for providing troubleshooting steps.

Could you also tell me how to fix this issue?

Answer 3

Hello,

Without knowing the results of the troubleshooting steps, it’s difficult to recommend a precise solution. Could you please share the findings from the steps I provided? This will help us move forward with a targeted and effective fix.

The steps I provided earlier are designed to help us pinpoint the exact cause of the Local Session Manager service termination. For example:

1. If the issue is due to high resource usage (CPU, memory, or disk), we might need to optimize the server’s performance or scale up resources.
2. If it’s caused by a corrupted system file, we would need to repair or replace the affected files.
3. If it’s related to a software conflict or misconfiguration, we would need to address the specific software or settings causing the issue.