Application popup: termsrv.exe - Application Error

Hi.

I have a Windows 2000 Advanced server (SP4) with Terminal Server Services
running and Citrix Metaframe XP installed (SP4), the other day the users were
unable to connect to the server and when I was connected I found the next
error in the event log:

Application popup: termsrv.exe - Application Error : The exception Possible
deadlock condition.
(0xc0000194) occurred in the application at location 0x77f8f33d.

Click on OK to terminate the program

After this message I found the next one:

Application popup: ImaSrv.exe - Application Error : The exception Possible
deadlock condition.
(0xc0000194) occurred in the application at location 0x77f8f33d.

Click on OK to terminate the program

I rebooted the server and now its running fine but I'm worry because this is
a mission critical server and this issue suddenly happened and I want to work
proactively before it happens again.

At first I thought it was a Citrix issue but when I contacted them they told
me that its a Microsoft issue, but I've been trying to find any lead which
helps me to resolve it but so far now I have found nothing

I hope you can help me.

Thanks and best regards.

Searching for "deadlock condition" in the KB gives a number of
hits, but all fixes seem to be included in W2K SP4.
Is there anything more in the EventLog on the server (apart from
the Application Popup events)?

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
SQL troubleshooting: http://sql.veranoest.net
___ please respond in newsgroup, NOT by private email ___

=?Utf-8?B?Sk1T?= <JMS@discussions.microsoft.com> wrote on 25 jan
2006 in microsoft.public.win2000.termserv.apps:

> Hi.
>
> I have a Windows 2000 Advanced server (SP4) with Terminal Server
> Services running and Citrix Metaframe XP installed (SP4), the
> other day the users were unable to connect to the server and
> when I was connected I found the next error in the event log:
>
> Application popup: termsrv.exe - Application Error : The
> exception Possible deadlock condition.
> (0xc0000194) occurred in the application at location
> 0x77f8f33d.
>
> Click on OK to terminate the program
>
> After this message I found the next one:
>
> Application popup: ImaSrv.exe - Application Error : The
> exception Possible deadlock condition.
> (0xc0000194) occurred in the application at location
> 0x77f8f33d.
>
> Click on OK to terminate the program
>
> I rebooted the server and now its running fine but I'm worry
> because this is a mission critical server and this issue
> suddenly happened and I want to work proactively before it
> happens again.
>
> At first I thought it was a Citrix issue but when I contacted
> them they told me that its a Microsoft issue, but I've been
> trying to find any lead which helps me to resolve it but so far
> now I have found nothing
>
> I hope you can help me.
>
> Thanks and best regards.

Thanks Vera.

This issue happened around 14:42 but the server was restarted around 19:11,
just before the reboot I found

System Log
At 16:52

No Windows NT or Windows 2000 Domain Controller is available for domain
WORLDSERVER. The following error occurred:
There are currently no logon servers available to service the logon request.

At 17:05

The session setup to the Windows NT or Windows 2000 Domain Controller
\\XXX392 for the domain WORLDSERVER is not responsive. The current RPC call
from Netlogon on \\YYYYYYYY007 to \\XXX392 has been cancelled.

At 17:18

The session setup to the Windows NT or Windows 2000 Domain Controller
\\XXX407 for the domain WORLDSERVER is not responsive. The current RPC call
from Netlogon on \\YYYYYYYY007 to \\XXX407 has been cancelled.

In the Application Log
At 13:34

Windows cannot do loopback processing when the computer is joined to a
downlevel domain or is a member of a workgroup. Loopback processing will be
disabled.

At 14:07

The timeout waiting for the performance data collection function "PerfOS" in
the "C:\WINNT\system32\perfos.dll" Library to finish has expired. There may
be a problem with this extensible counter or the service it is collecting
data from or the system may have been very busy when this call was
attempted.

At 14:35

The timeout waiting for the performance data collection function "PerfProc"
in the "C:\WINNT\system32\perfproc.dll" Library to finish has expired. There
may be a problem with this extensible counter or the service it is
collecting data from or the system may have been very busy when this call
was attempted.

At 14:37

The timeout waiting for the performance data collection function
"TermService" in the "C:\WINNT\system32\perfts.dll" Library to finish has
expired. There may be a problem with this extensible counter or the service
it is collecting data from or the system may have been very busy when this
call was attempted.

Also there are some policy errors but apparently are not a big deal.

Do you have any comment?.

Regards

Seems that your Terminal Server lost contact with your Domain
Controller. Any events on the DC?

Could you please post the EventID and Source of these events, in
stead of the description? That makes it possible to search for them
at www.eventid.net

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
SQL troubleshooting: http://sql.veranoest.net
___ please respond in newsgroup, NOT by private email ___

=?Utf-8?B?Sk1T?= <JMS@discussions.microsoft.com> wrote on 27 jan
2006 in microsoft.public.win2000.termserv.apps:

> Thanks Vera.
>
> This issue happened around 14:42 but the server was restarted
> around 19:11, just before the reboot I found
>
> System Log
> At 16:52
>
> No Windows NT or Windows 2000 Domain Controller is available for
> domain WORLDSERVER. The following error occurred:
> There are currently no logon servers available to service the
> logon request.
>
> At 17:05
>
> The session setup to the Windows NT or Windows 2000 Domain
> Controller \\XXX392 for the domain WORLDSERVER is not
> responsive. The current RPC call from Netlogon on \\YYYYYYYY007
> to \\XXX392 has been cancelled.
>
> At 17:18
>
> The session setup to the Windows NT or Windows 2000 Domain
> Controller \\XXX407 for the domain WORLDSERVER is not
> responsive. The current RPC call from Netlogon on \\YYYYYYYY007
> to \\XXX407 has been cancelled.
>
> In the Application Log
> At 13:34
>
> Windows cannot do loopback processing when the computer is
> joined to a downlevel domain or is a member of a workgroup.
> Loopback processing will be disabled.
>
> At 14:07
>
> The timeout waiting for the performance data collection function
> "PerfOS" in the "C:\WINNT\system32\perfos.dll" Library to finish
> has expired. There may be a problem with this extensible
> counter or the service it is collecting data from or the system
> may have been very busy when this call was attempted.
>
> At 14:35
>
> The timeout waiting for the performance data collection function
> "PerfProc" in the "C:\WINNT\system32\perfproc.dll" Library to
> finish has expired. There may be a problem with this extensible
> counter or the service it is collecting data from or the system
> may have been very busy when this call was attempted.
>
> At 14:37
>
> The timeout waiting for the performance data collection function
> "TermService" in the "C:\WINNT\system32\perfts.dll" Library to
> finish has expired. There may be a problem with this extensible
> counter or the service it is collecting data from or the system
> may have been very busy when this call was attempted.
>
> Also there are some policy errors but apparently are not a big
> deal.
>
> Do you have any comment?.
>
> Regards