Thanks for the quick response! I meant to mention that I had found that and thought it might be the issue, but the source for our error is Microsoft-Windows-TerminalServices-Licensing and I have to drill down to Applications and Services Logs\Microsoft\Windows\TerminalServices-LocalSessionManager to see it. But it doesn't show as occurring in the localsessionmanager log.
Or maybe I've stumbled upon a secret code list known only to key individuals at Microsoft, the CIA, and the NSA. My guess is that I'm missing something that's right under my nose. I also have not found a single reference to Event ID 40 in this specific log. But I have searched just about everywhere I could think of and I haven't found any reference to these codes. 5 and 11 are pretty rare.ĭoes anybody know what these reason codes mean? I assume that interpreting this code would give me some insight into the problem(s) we need to correct. 12 shows up a significant number of times. The text is something like " Session 8 has been disconnected, reason code #." I see four reason codes: 0, 5, 11, and 12.
In the Microsoft-Windows-TerminalServices-LocalSessionManager/Operational event log, there are a lot of instances of Event ID 40. Of course, we have a huge number of variables and we're trying to track down each possibility. We have a Server 2012 R2 terminal server farm and we're experiencing random disconnections.
0 kommentar(er)
