Application does not launch - login, then immediate logoff, in the Citrix XenApp / Presentation Server forum on BrianMadden.com

rated by 0 users
This post has 0 verified answers | 8 Replies | 3 Followers

Suggest an Answer

Points 360

Henning strumpen posted on Wed, May 3 2006 8:20 AM

rated by 0 users

Hello everybody,

we switched to PS4.0 a few weeks ago and since then my users have troubles starting outlook as the first application.

it is always the same:
user double clicks outlook, user credentials are retrieved, connection to the server is established, logON script runs and then the logOFF scripts runs, without outlook beeing started.

other published applications start correctly.

if you have already a connection running then outlook starts correctly too.

I published a batchfile that start outlook.exe, and even that is running.

It seems to be some kind of timeout that logs the user off before outlook.exe is started.

Can somebody help me with this?

System: PS4.0, W2kSP4, Office2000, PNAgent 9.150

Please help!
Henning Strumpen

| Post Points: 20

All Replies

Points 88,205

Jeff Pitsch replied on Wed, May 3 2006 1:52 PM

rated by 0 users

Is it a particular server? Any errors in the event logs of the server?

| Post Points: 20

Guest replied on Wed, May 3 2006 11:44 PM

rated by 0 users

I know this problem well. :)

A new registry key has been available since hotfix rollup pack XE104W2K3R01 for MetaFrame XP FR3 that addresses an issue when launching certain published applications; the session was logged off before the application was started. The issue occurred if both session and application startup took several seconds. This fix adds support for a registry setting to configure the time allotted before checking to determine if the session should be logged out because no more user processes exist.

To do this, one must set the following registry key:

HKEY_LOCAL_MACHINE\SYSTEM CurrentControlSet\Control\Citrix\Wfshell\TWI
Name: IntervalsForLogoffCheck
Type: REG_DWORD
Value: 5000 Decimal
[size=2]
What this means is that when the logout checker notices that there is no user process for the session, it will wait a certain interval of time (5 seconds in this case) then checks again. If there is still no process, the session is shut down. Start off at 5 seonds and increase a second at a time until it becomes reliable.

Having said all that, this will be ignored if outlook.exe is in the following key:

HKEY_LOCAL_MACHINE\SYSTEM CurrentControlSet\Control\Citrix\Wfshell\TWI\LogoffCheckSysModules

This key represents the exception list for the logoff checker (see CTX891671). Therefore, Outlook will be excluded from the Logoffchecker comparison, and the system will find no processes for the session and shuts down.

These keys are still applicable for MPS3 and PS4.

Cheers,
Jeremy.

| Post Points: 20

Points 360

Henning strumpen replied on Thu, May 4 2006 5:26 AM

rated by 0 users

Jeff,
all servers are affected, there are no entries in the event log.

Jeremy,
IntervalsForLogoffCheck did the trick.
However, I had to remove Outlook.exe from LogoffCheckSysModules to get it running.
I put Outlook.exe in there some weeks ago because the Citrix session does not close after you close Outlook. You can see the outlook.exe still running on the server.

So I can either fix the logon OR fix the logoff with these keys.

So the next big question is: How do I find out why Outlook does not close correctly?

Thank you both for your help!

Best regards,
Henning

| Post Points: 20

Guest replied on Thu, May 11 2006 1:23 PM

rated by 0 users

Do you have any addins or plugins to Outlook? The best thing to do is to run process explorer from System Internals to see what handle is keeping Outlook open.

People often misuse the LogoffCheckSysModules key instead of fixing the real problem.

How about using UPHClean from Microsoft?

Cheers,
Jeremy.

| Post Points: 20

Points 360

Henning strumpen replied on Mon, May 15 2006 5:46 AM

rated by 0 users

Here is the solution:
Outlook did not close because the affected users did previously use Outlook 2003 in a testing environment.
There is a Hotfix against this behaviour: KB834005

That means I can also use IntervalsForLogoffCheck and everybody is happy again.

Thank you guys.

Henning

| Post Points: 20

Points 90

scottab replied on Thu, Jan 8 2009 5:41 PM

rated by 0 users

I hate to revive an old thread but I appear to be having this "EXACT' issue in XenApp 5 on my 2008 Servers. I have added the Registry key but it doesnt seem to do anything.... Does anyone know if there is a similar registry key in XenApp 5 somewhere or if this reg key has been removed completely?

Scott