Jump to content


Photo

Session hung at logoff on Windows Server 2012 R2

Started by Benjamin Österle , 21 July 2015 - 11:44 AM
61 replies to this topic

Benjamin Österle Members

Benjamin Österle
  • 18 posts

Posted 21 July 2015 - 11:44 AM

Hello,

 

im using XenApp 7.6 on Windows Server 2012 R2 (Published Desktops).

 

When the user logs of the session is stuck and it looks like the screenshot in the attachments.

 

The following processes are running:

csrss.exe

dwm.exe

LogonUI.exe

winlogon.exe

 

i am not able to sign of the session.

 

In this moment the user is not able to login on another server.

When i kill winlogon.exe the session closes, but the user is still not able to login.

When i restart the server the problem is temporary solved..

 

On the DDC i got this error in event viewer:

Error ID 12346, No available ressource found for user

 

Any idea on this issue?



Carl Stalhood CTP Member

Carl Stalhood
  • 11,582 posts

Posted 21 July 2015 - 12:31 PM

Are all Windows Updates installed? What VDA patches to you have installed?

 

For attachments, make sure you click "Add to Post"



Anton Klont Members

Anton Klont
  • 1 posts

Posted 31 August 2015 - 02:31 PM

Are you also using Outlook 2013 and Windows search? I am having the same problem and i am expecting that is the source of the problem. But I also don't know how to fix it.



Angus Sutherland Members

Angus Sutherland
  • 25 posts

Posted 01 September 2015 - 01:55 AM

A process might be holding the session and because you end winlogon it closes it down. Id check what else is running. Also check logoffchecksysmodules. I had the same issue with SCNotification.exe was keeping sessions alive even after user logoff.

SYSTEM\CurrentControlSet\Control\Citrix\wfshell\TWI, LogoffCheckSysModules.



Benjamin Österle Members

Benjamin Österle
  • 18 posts

Posted 02 September 2015 - 05:52 AM

Are you also using Outlook 2013 and Windows search? I am having the same problem and i am expecting that is the source of the problem. But I also don't know how to fix it.

 

Yep, running Windows Search and Outlook 2013.. 

I'll keep you up to date if i find any solution



Mike Yuen Members

Mike Yuen
  • 42 posts

Posted 23 November 2015 - 05:58 PM

Am having the same problem. XA 7.6 with PVS 7.6. Both on Win Server 2012 R2. Latest Windows updates installed.

 

Users are unable to connect to Citrix.

 

In Director: Several users show multiple sessions in "Disconnected", "Active", and/or "Connected" states (for the same user). I am unable to Disconnect or Logoff their sessions either.

 

I get the same 4 processes (as Benjamin/Original poster) showing in Disconnected state with a "(4)" as the user.

 

Server reboot is the only way for me to resolve the issue too, but doing so in full production hours (and kicking everyone else offline) is not an ideal solution.

 

This has happened 3x in our environment.

Attached Thumbnails

  • Session.png


Mike Yuen Members

Mike Yuen
  • 42 posts

Posted 23 November 2015 - 06:07 PM

Found this:

http://blogs.serioustek.net/post/2014/08/06/xenapp-7-1-7-5-disconnected-sessions-not-logging-off-aspx

http://support.citrix.com/article/CTX139726

 

Instead of modifying the Registry and running the patches, I may plan to update to XA/PVS 7.6 FP3 instead, installing the latest VDA. However, I'll open up a case with Citrix first.

 

EDIT: case has been opened, and CDFTrace has been collected for the server the user is able to log in to, and for the server she cannot use. For each attempt to connect to the non-working server, a new "Connected" session is left running (after Receiver popped up and quickly disappeared). Waiting on Citrix now to analyze the logs.



Siegfried MARECHAL Members

Siegfried MARECHAL
  • 104 posts

Posted 01 December 2015 - 07:40 AM

Hello,

 

For Office: http://gavindye.com/install-office-2013-on-xenapp/

 

 

 

 



Mike Yuen Members

Mike Yuen
  • 42 posts

Posted 02 December 2015 - 06:07 PM

Case with Citrix is still on-going. They are having me collect more logs without rebooting the servers. Several users are affected by this issue, and it pains me not to be able to reboot the servers (which would clear any logs Citrix could gather).

 

The symptom that is most alarming is that those stuck sessions prevent users from logging on to those servers. They can log on to other servers -- just not the ones where they have a stuck session with.



Mike Yuen Members
  • #10

Mike Yuen
  • 42 posts

Posted 12 December 2015 - 12:49 AM

Case #70622723 was escalated to an engineer. He looked at the logs, dumps, etc., and asked to upgrade to XD 7.6 FP3 before escalating the case even further. This is going to take a while to upgrade the environment.



Loren Saxby Members
  • #11

Loren Saxby
  • 4 posts

Posted 06 January 2016 - 07:16 AM

We seem to be having the exact same problem, but only on one of our VDAs. Citrix told us to install this after reviewing a memory dump: http://support.citrix.com/article/CTX141880 but it didn't help at all.

 

Benjamin or Mike- Were you able to reach a solution? Your feedback is appreciated.



Mike Yuen Members
  • #12

Mike Yuen
  • 42 posts

Posted 11 January 2016 - 07:54 PM

We seem to be having the exact same problem, but only on one of our VDAs. Citrix told us to install this after reviewing a memory dump: http://support.citrix.com/article/CTX141880 but it didn't help at all.

 

Benjamin or Mike- Were you able to reach a solution? Your feedback is appreciated.

 

We upgraded to 7.6 FP3, but the issue returned. Sending an email to the escalation engineer resulted in no response for the last 2 weeks. I will be sending another follow-up and involve our account manager as necessary.

 

We have plans to upgrade to 7.7 sometime in February.



Raul Gonzalez Members
  • #13

Raul Gonzalez
  • 572 posts

Posted 14 January 2016 - 02:33 AM

Are you running Symantec Endpoint Protection?  It can cause logoffs to stall.  When I made Symantec's recommended adjustment, users could log off properly.

 

https://support.symantec.com/en_US/article.TECH91070.html



Björn Wikzell Members
  • #14

Björn Wikzell
  • 23 posts

Posted 14 January 2016 - 08:38 AM

Hi 
 
We are seeing the same issues in our environment Windows 2012R2, XenDesktop 7.6
Have been doing some test and sometimes got things to start working after killing UPM and Windows profile manager. A co-worker sent me this link
 
Will do some testing with password changes and then try to disable cred manager
 
We are not runing Symantec 
 
//Björn


Kevin Halstead Members
  • #15

Kevin Halstead
  • 84 posts

Posted 28 January 2016 - 10:57 AM

Hi,

 

Any update on this? we are having the same issue on Xenapp 7.6, stuck sessions. Can see the session in Studio/Director but not in Terminal Services manager, renders the users unable to work without a server reboot.

 

Kevin



Martin Lauritzen Members
  • #16

Martin Lauritzen
  • 27 posts

Posted 28 January 2016 - 01:34 PM

We are having the same issue. XenApp 7.6 . The Users can't reconnect and only solution is reboot of server. When it happens Endpoint name and Receiver version goes to n/a. I can't force a logoff or disconnect of user. Hope Citrix find a solution to this. We are having an old RDP server as backup for XenApp because of this.  :(



Mike Yuen Members
  • #17

Mike Yuen
  • 42 posts

Posted 28 January 2016 - 05:34 PM

Here's the latest update from the Citrix escalation engineer... I had to suspend the VM and send him a copy of the suspended VMware .vmss file. He analyzed it and, paraphrasing:

 

"I've been stepping through the latest system dump and ran into a roadblock. Because the sessions were present for 25 days, the data has been paged out and the callstacks were no longer present in memory. This makes it impossible for me to follow the ALPC wait chains."

 

He's proposing that the moment we detect another stuck session, to go ahead and suspend the VM again that evening and send the .vmss file for analysis. This will be hard to detect... I suppose I'll have to check Director every day to see if a stuck session is there.

 

I've upgraded to XD 7.7 yesterday. It's a waiting game now.

 

If I remember right, the issue has something to do with "ALPC wait chains".



Loren Saxby Members
  • #18

Loren Saxby
  • 4 posts

Posted 29 January 2016 - 02:48 AM

We ended up reinstalling the problem VDA and everything is back to normal. We kept being told it was a Microsoft problem after Citrix engineers analyzed our mem dump files, not once, but several times. I'm not sure if I buy it, but maybe, just maybe, there was a corruption during a Windows Update. Anyway, so far so good on the reinstall. Will report here if the issue returns.



Brent Christensen Members
  • #19

Brent Christensen
  • 13 posts

Posted 29 January 2016 - 03:45 AM

We had a similar issue and it turned out to be the App-V client that was installed.  We initially did the TWI reg key fix above which worked, then later removed App-V completely.   It still happens very occasionally for random users, perhaps once a month, but that's the extent of it now.



Guy Mcpherson Members
  • #20

Guy Mcpherson
  • 6 posts

Posted 07 February 2016 - 02:50 AM

Here's the latest update from the Citrix escalation engineer... I had to suspend the VM and send him a copy of the suspended VMware .vmss file. He analyzed it and, paraphrasing:

 

"I've been stepping through the latest system dump and ran into a roadblock. Because the sessions were present for 25 days, the data has been paged out and the callstacks were no longer present in memory. This makes it impossible for me to follow the ALPC wait chains."

 

He's proposing that the moment we detect another stuck session, to go ahead and suspend the VM again that evening and send the .vmss file for analysis. This will be hard to detect... I suppose I'll have to check Director every day to see if a stuck session is there.

 

I've upgraded to XD 7.7 yesterday. It's a waiting game now.

 

If I remember right, the issue has something to do with "ALPC wait chains".

 

 

 

Did you ever get anything back from Citrix.  We have a brand new environment and are starting to see the same thing.

 

Thanks

-guy