[SOLVED] RDS logs randomly off

Hi,

Step 1. Download
6530fbb0f4101-56f31e53c97da-SFCFix.PNG
SFCFix and save it to your desktop.

Warning: This fix was written specifically for this system. Do not run this fix on another system.
  • Save any work you have open, and close all programs.
  • Download the attachment SFCFix.zip and save it to your desktop.
  • Drag the SFCFix.zip file over the SFCFix.exe executable and release it.
650c22f99662d-6190d993a26f3-SFCFix-Zip-Eng.gif

  • SFCFix will launch, let it complete.
  • Once done, a file will appear on your desktop, called SFCFix.txt.
  • Post the logfile (SFCFix.txt) as attachment in your next reply.


Step 2. Run the following DISM command and post the result. If it fails attach a new copy of the CBS log.
Code: 
DISM /online /cleanup-image /RestoreHealth
 

Attachments

here it is

result of dism:

C:\Users\patrick>DISM /online /cleanup-image /RestoreHealth

Tool zur Imageverwaltung für die Bereitstellung
Version: 10.0.20348.1

Abbildversion: 10.0.20348.587

[==========================100.0%==========================] Der Wiederherstellungsvorgang wurde erfolgreich abgeschlossen.
Der Vorgang wurde erfolgreich beendet.

C:\Users\patrick>
 

Attachments

This looks good, please run the System File Checker as well.

Run the following command and post the result. If it fails attach a new copy of the CBS log.
Code: 
SFC /Scannow
 
Hi,

no errors after this sfc scan.

The thing is, if the problem of the logout is now solved, what shall we do? Do we have to send you every time the logs of the server and have to run this sfc fix? We have hundreds of servers...

Do you have any idea what we have to do to solve this error?

Thanks
 
If the problem affects multiple servers with exactly the same issue you can apply the same fix on all of them. But if you are not sure please post the logs of the other server(s) to look at.

Pat_itg said:
Do you have any idea what we have to do to solve this error?
Click to expand...

This is a common problem with Server 2022 and unstable RDP sessions, however, and unfortunately, there's no standard solution to resolve such issues due to the difference in corruptions.
 
Hi,

Please run the System File Checker and post the result, attach also a new copy of the CBS logs.
Code: 
SFC /Scannow
 
C:\Users\patrick>sfc /scannow

Systemsuche wird gestartet. Dieser Vorgang kann einige Zeit dauern.

Überprüfungsphase der Systemsuche wird gestartet.
Überprüfung 100 % abgeschlossen.

Der Windows-Ressourcenschutz hat keine Integritätsverletzungen gefunden.

C:\Users\patrick>
 

Attachments

Are these logs from the server with the RDP issues? If so please provide the event logs as well.

Upload the Event Viewer logs.
  • Click the Start button and in the search box, type Command Prompt
  • When you see Command Prompt on the list, right-click on it and select Run as administrator.
    Copy and paste the following commands one at a time into the command prompt and press enter after each.
    Code: 
    wevtutil epl SYSTEM "%userprofile%\Desktop\System.evt"
wevtutil epl APPLICATION "%userprofile%\Desktop\Application.evt"
PowerShell Compress-Archive -Path "%userprofile%\Desktop\*.evt" -DestinationPath "%UserProfile%\Desktop\EventLogs.zip"
  • These commands will collect the System and Application logs and create EventsLogs.zip on your Desktop.
  • Attach this file in your next reply.
 
here the files you´ve requested
note that i have done this logs with the administrator account and not with the User accounts in question, hope this is not a problem
 

Attachments

We have Servers running Windows Server 2019 without activation, the random logoff problem does not occur on those. We are working on solving the activation issue, but it is most likely not what causes our logoff problem. What else could it be? What do you think?
 
Last edited:
We have a KMS licensing system running per core, so not with an actual license key but rather tied to the machine. With the last few machines, we always encountered an activation error, even though everything was functioning correctly. I should mention that the aforementioned logoff error also occurred with activated machines.

In this specific case, I've now addressed this problem and just found a solution... I was able to activate the machine using a generic AVMA key. Now, we'll wait until tomorrow and see what happens. I'll let you know as soon as I have any updates
 
So far, the problem seems to be resolved as of today. I also don't believe anything else will happen; it appears that in this case, both issues applied. Now, with the license activated and the patch applied, I no longer see any logoffs.

I've noticed that this fix resets a few permissions. Is there a list of things this fix performs? Since we have many servers, it would be interesting for us to check if the same actions are being applied everywhere.
 
In this case we have replaced the following (corrupt) file.
Code: 
C:\Windows\WinSxS\amd64_tsportalwebpart_31bf3856ad364e35_10.0.20348.1_none_be04efa9b8a1c1d2\allusers_tswa.log
 
You must log in or register to reply here.
Back
Top