I have never seen this issue on 2008 but then again, most folks were smart and skipped 2008! :) In my opinion, XA5/2008 is the ugly red-headed stepchild of the XenApp product family (my apologies if you are red-headed and or a stepchild and or ugly like Joe Shonk). I am really trying hard to think of any customer I know running XA5/2008 in production and I am drawing a blank. Sorry. Webster From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf Of Aljets, Paul Sent: Wednesday, March 20, 2013 1:58 PM To: 'thin@xxxxxxxxxxxxx' Subject: [THIN] Re: Urgent Issue -- "Please Wait for Local Session Manager" Two replies from the most knowledgeable guys I know and you've never seen this issue before? :) Paul Aljets Sr Citrix Architect From: thin-bounce@xxxxxxxxxxxxx<mailto:thin-bounce@xxxxxxxxxxxxx> [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf Of Joe Shonk Sent: Wednesday, March 20, 2013 10:55 AM To: thin@xxxxxxxxxxxxx<mailto:thin@xxxxxxxxxxxxx> Subject: [THIN] Re: Urgent Issue -- "Please Wait for Local Session Manager" Yeah, understandable. Most places don't run Windows 2008. Those organizations that did go Windows 2008 have since migrated to Windows 2008 R2 w/ XenApp 6.5. Hint, Hint, Wink Wink. Joe On Wed, Mar 20, 2013 at 10:41 AM, Webster <webster@xxxxxxxxxxxxxxx<mailto:webster@xxxxxxxxxxxxxxx>> wrote: DOH, completely missed that part where you are running 2008. Sorry about that. Webster From: thin-bounce@xxxxxxxxxxxxx<mailto:thin-bounce@xxxxxxxxxxxxx> [mailto:thin-bounce@xxxxxxxxxxxxx<mailto:thin-bounce@xxxxxxxxxxxxx>] On Behalf Of Aljets, Paul Sent: Wednesday, March 20, 2013 1:26 PM To: 'thin@xxxxxxxxxxxxx<mailto:thin@xxxxxxxxxxxxx>' Subject: [THIN] Re: Urgent Issue -- "Please Wait for Local Session Manager" This issue is occurring on a Xenapp Presentation Server Running.. Running XA 5.0 (Platinum Edition) The latest released Rollup pack for Win2008 For Xenapp 5.0 is Rolloup 01 Unless I'm missing something completely :) I see a Rollup 07 for Xenapp 4.5 but we're not running that.. Paul Aljets Sr Citrix Architect From: thin-bounce@xxxxxxxxxxxxx<mailto:thin-bounce@xxxxxxxxxxxxx> [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf Of Webster Sent: Wednesday, March 20, 2013 10:05 AM To: thin@xxxxxxxxxxxxx<mailto:thin@xxxxxxxxxxxxx> Subject: [THIN] Re: Urgent Issue -- "Please Wait for Local Session Manager" Why are you just on R01 when R07 has been out for a good while? Or did you mean XA 6.5 Platinum on 2008 R2? Webster From: thin-bounce@xxxxxxxxxxxxx<mailto:thin-bounce@xxxxxxxxxxxxx> [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf Of Aljets, Paul Sent: Wednesday, March 20, 2013 11:41 AM To: 'thin@xxxxxxxxxxxxx<mailto:thin@xxxxxxxxxxxxx>' Subject: [THIN] Urgent Issue -- "Please Wait for Local Session Manager" Let me preface this with the following information Environment: XA 5 Platinum Rollup 01 applied (and a couple post R01 Printing related Hotfixes) Citrix Profile Management 4 (Although all users are logging in anonymously on the servers this is impacting) Presentation Servers running: Windows Server 2008 Enterprise Edition x64bit Occurs on both Physical and Virtual machines Only occurring in "One" of our 2 Datacenters MS KB2661001 already applied and issue still occurring. When launching a Published app or attempting to RDP against an affected server the user receives the message "Please Wait for Local Session Manager" and it will just sit there. Sometimes eventually logging the user in ~15 minutes later but more frequently it just sits forever The only "Fix" is to either reboot the server, or forcefully terminate IMA and restart. It should be noted I had a memory dump sent to MS for analysis what they came back with is the following: The analysis from the MS Debugging team shows that LSM (Local session manager) is blocked on a chain of blocked threads that leads up to Citrix's ImaSrv service. In this process there request processing threads are blocked on a lock that is owned by another thread within ImaSrv and this lock owning thread has been waiting from past ~4 minutes to receive acknowledgement of a RPC bind packet that it has sent to mydomaincontroller.domain.com<http://mydomaincontroller.domain.com> over TCP transport at port 49156. The client will wait for a timeout period of ~15 minutes. As such I don't see if this request is blocked in the local network stack, but appears that the DC has not been responding. IMASrv has issued DsCrackNames on "MYDOMAIN\UserID1234" to convert the directory service object names from one format to another. However what we are interested here is to understand why RPC bind didn't complete. Forcefully terminating IMA and restarting it, "Fixes" the error for the time being. But if ANYONE has seen this issue before and has any suggestions I would welcome them. I have a case open with Citrix, and they're analyzing the memory dump as well, but I thought I would ask the brain trust to see if they had any suggestions. :) This is a new one on me. Any assistance is welcome! Paul Aljets Sr Citrix Admin Stanford Hospitals and Clinics