In short, I have a situation where a user logs off a 2000 TS session they
would get a blue screen until the specified timeout would occur. Upon further
investigation, I looked at the hung session and determined that the process
that was hung was Adobe Acrobat reader. If I ended the process, the TS
session disconnected immediately. Basically, we have an application that
calls adobe acrobat reader within IE6. Once the user sees the data, they
close Acrobat. Shortly after, they close the application and the TS session
starts its log off process but hangs. If they do not invoke Acrobat within
the app, log offs work flawlessly.

This server has more than enough RAM and processing power, all the latest
service packs and windows updates. The latest build of Acrobat (7 something.
It also had this problem with 5.x and 6.x).

I have even applied the following registry entries to kill the process at
logoff.

User Key: [HKEY_CURRENT_USER\Control Panel\Desktop]
System Key: [HKEY_USERS\.DEFAULT\Control Panel\Desktop]
Value Name: AutoEndTasks
Data Type: REG_SZ (String Value)
Value Data: (0 = disabled, 1 = enabled)

and

User Key: [HKEY_CURRENT_USER\Control Panel\Desktop]
System Key: [HKEY_USERS\.DEFAULT\Control Panel\Desktop]
Value Name: HungAppTimeout
Data Type: REG_SZ (String Value)
Value Data: Time in milliseconds (1000 = 1 second) I set it to 5000

This has not worked either. I'm totally stumped and have exhausted all
options. If anyone has a way to force/kill a process at logoff or even a
third party utility to help me with this, it would be appreciated.

Regards,

Sean

The real problem could lie in the way that Acrobat is started by
your application.
One way to work around this issue is to start your application
from a command file:

start / wait my_app.exe
logoff

--
Vera Noest
MCSE,CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
*----------- Please reply in newsgroup -------------*

"=?Utf-8?B?ZGNzZGl2ZXI=?=" <(E-Mail Removed)>
wrote on 24 dec 2004:

> In short, I have a situation where a user logs off a 2000 TS
> session they would get a blue screen until the specified timeout
> would occur. Upon further investigation, I looked at the hung
> session and determined that the process that was hung was Adobe
> Acrobat reader. If I ended the process, the TS session
> disconnected immediately. Basically, we have an application that
> calls adobe acrobat reader within IE6. Once the user sees the
> data, they close Acrobat. Shortly after, they close the
> application and the TS session starts its log off process but
> hangs. If they do not invoke Acrobat within the app, log offs
> work flawlessly.
>
> This server has more than enough RAM and processing power, all
> the latest service packs and windows updates. The latest build
> of Acrobat (7 something. It also had this problem with 5.x and
> 6.x).
>
> I have even applied the following registry entries to kill the
> process at logoff.
>
> User Key: [HKEY_CURRENT_USER\Control Panel\Desktop]
> System Key: [HKEY_USERS\.DEFAULT\Control Panel\Desktop]
> Value Name: AutoEndTasks
> Data Type: REG_SZ (String Value)
> Value Data: (0 = disabled, 1 = enabled)
>
> and
>
> User Key: [HKEY_CURRENT_USER\Control Panel\Desktop]
> System Key: [HKEY_USERS\.DEFAULT\Control Panel\Desktop]
> Value Name: HungAppTimeout
> Data Type: REG_SZ (String Value)
> Value Data: Time in milliseconds (1000 = 1 second) I set it to
> 5000
>
> This has not worked either. I'm totally stumped and have
> exhausted all options. If anyone has a way to force/kill a
> process at logoff or even a third party utility to help me with
> this, it would be appreciated.
>
> Regards,
>
> Sean