Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden using our free interactive tool and use it to determine the right price for your IT services. Start calculating Now!
Citrix sessions launch then immediately log out.
I have a set of 8 server 2008 servers running Xenapp 5.0 and some users are having issues launching apps. This started happening only recently and I can't tie it to any changes on the servers or the user's PCs. A user will launch a published app, the app loads, the app UI pops up on the screen for maybe 1 second, then the session logs out. This is the case for a large number of users on a wide number of system. Some users are not experiencing this issue though they are connecting to the same apps on the same servers. For example, sessions launching from my PC (regardless of which ID is used) work every time. Other apps on other 2008 servers in the same farm work as well on the machines that have issues with the set of 8 servers mentioned above. I don't see any unusual messages in the event log. I have tried to implement the LogoffCheckerStartupDelayI
Any help would be appreciated.
Any help would be appreciated.
Do more with
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Tried to reinstall the citrix receiver? Maybe the problem is on the PC could be window updates...they love to screw things
Yes , first thing I tried. Also, i would expect connections to 2008 servers not in that group would fail as well. Something I forgot to mention- these server have no special policies, Citrix or GPO, applied to them.
Now I am not sure if this would be the same for you but I had to add the url to java console security tab as an exception so I can get to the citrix apps up and running.
I would go to Control Panel, Java, Security Tab, edit site list, add the URL there. It all depends what customer I am connecting to. One of my other customers does not require the use of Java to get into the citrix apps.
We don't use java for Citrix. Also, I would expect that this would cause a failure for any connection to servers in the farm, but it seems to be a limited number of servers I see this symptom on. Thanks for bending some thought to this.
I was reading a blog on this and this is one of the comments an expert posted...
"You have to either disable session pre-launch for the receiver via the registry on the XenApp servers , or uninstall the Citrix receiver on the XenApp servers.
Session Pre-Launch causes this behavior in a published desktop."
"You have to either disable session pre-launch for the receiver via the registry on the XenApp servers , or uninstall the Citrix receiver on the XenApp servers.
Session Pre-Launch causes this behavior in a published desktop."
Try this reg fix and see if this works for you.
Create the following registry key,
HKEY_LOCAL_MACHINE\SYSTEM\
DWord (32bit) – LogoffCheckerStartupDelayI
Set the value of the key as 10.
Create the following registry key,
HKEY_LOCAL_MACHINE\SYSTEM\
DWord (32bit) – LogoffCheckerStartupDelayI
Set the value of the key as 10.
Here is something new I found and I can recreate. When i run and capture with Sysinternals Process Monitor on the problem server the citrix apps all launch normally. When i stop the capture the launch and immediate logoff returns.
try to publish calc.exe (or another system-app) and ask your users to first start this app and afterwards the problam-app.
the problem app should share the session with calculator and possible keeps running.
What is the result?
the problem app should share the session with calculator and possible keeps running.
What is the result?
This is something we tried and with no luck. System apps suffer the same issue- or should I say, suffered. The problem has disappeared as mysteriously as it appeared. Suddenly all of the problematic servers are now behaving properly. From a citrix and windows server angle we made no broad changes (all troubleshooting was done with changes only to a single server). My only thought is some change was made to a GPO (though our AD team denies this) or some strange VMWare issue was resolved. I can't explain why this issue started nor why it resolved itself.
Premium Content
You need an Expert Office subscription to comment.Start Free Trial