Re: Application popup: termsrv.exe - Application Error
- From: "Vera Noest [MVP]" <vera.noest@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Sat, 28 Jan 2006 04:17:33 -0800
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@xxxxxxxxxxxxxxxxxxxxxxxxx> 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
.
- References:
- Re: Application popup: termsrv.exe - Application Error
- From: Vera Noest [MVP]
- Re: Application popup: termsrv.exe - Application Error
- From: JMS
- Re: Application popup: termsrv.exe - Application Error
- Prev by Date: Printer Redirects, But No Output
- Next by Date: Re: Printer Redirects, But No Output
- Previous by thread: Re: Application popup: termsrv.exe - Application Error
- Next by thread: Licensing issues and warnings in event log
- Index(es):
Relevant Pages
|
