Re: NLASVC
- From: Meinolf Weber [MVP-DS] <meiweb(nospam)@gmx.de>
- Date: Fri, 12 Jun 2009 19:13:09 +0000 (UTC)
Hello mark,
Please post an unedited ipconfig /all from the TS and the DNS/DC.
Best regards
Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
When the RDP session starts, the user is prompted for credentials.
Once the credentials are entered and user presses enter (or the
arrow), the RDP session displays "Welcome" with the rotating circle
(to the left), but the log on never gets any further. We've waited
over 20 minutes and nothing.
Normally, a series of messages are displayed like load profile, etc.
The event log is void of errors. The console is also hung. It has
happened to all users and appears to the connection independent - RDP
client version, OS version, do not matter. This happens at least once
a day, sometimes more. A hard reboot is required to reactivate the
server.
"Meinolf Weber [MVP-DS]" <meiweb(nospam)@gmx.de> wrote in message
news:ff16fb66278168cbb9b7db8fee9c@xxxxxxxxxxxxxxxxxxxxxxx
Hello mark,
"Welcome screen hang"? What do you mean with that, slow logons?
Best regards
Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and
confers no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
Thanks. For testing purposes, we ended up disabling the NLASVC and
NIS services. The server runs well without them. The NLASVC errors
went away, but the "Welcome Screen" hang is still present and the
server becomes unresponsive and must be rebooted daily. It has
become such a problem, that we may have have to buildout a
replacement 2003 environment.
"Meinolf Weber [MVP-DS]" <meiweb(nospam)@gmx.de> wrote in message
news:ff16fb66274e38cbb8bf4b74e5e3@xxxxxxxxxxxxxxxxxxxxxxx
Hello mark,
The Network Location Awareness service which collects and stores
network configuration information such as IP addresses, Workgroup
and/or Domain name changes (if your PC is connected to a Windows
network), as well as Location change information, and which
notifies applications when this information changes so that they in
turn adapt to the computer's connectivity changes. So you should
not disable that service.
Is that service started and set to automatic? Do you run TrendMicro
AntiVirus, read about a problem with that AntiVirus software?
Best regards
Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties,
and
confers no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
Our Windows 2008 Terminal Server suffers from an NLASVC timeout
error. The event ID is 7011. What's important is once the error
occurs, the server must be restarted to resume operation. The
timeout occurs once every 8 to 12 hours. The actual error is
below. The server is running all of the latest patches, including
SP2. Can NLASVC be disabled?
Log Name: System
Source: Service Control Manager
Date: 6/10/2009 3:24:11 PM
Event ID: 7011
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: KAVSAPP01.knopf.local
Description:
A timeout (30000 milliseconds) was reached while waiting for a
transaction
response from the NlaSvc service.
Event Xml:
<Event
xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Service Control Manager"
Guid="{555908D1-A6D7-4695-8E1E-26931D2012F4}"
EventSourceName="Service
Control Manager" />
<EventID Qualifiers="49152">7011</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2009-06-10T19:24:11.000Z" />
<EventRecordID>108237</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>System</Channel>
<Computer>KAVSAPP01.knopf.local</Computer>
<Security />
</System>
<EventData>
<Data Name="param1">30000</Data>
<Data Name="param2">NlaSvc</Data>
</EventData>
</Event>
.
- Follow-Ups:
- Re: NLASVC
- From: Mark
- Re: NLASVC
- References:
- Re: NLASVC
- From: Mark
- Re: NLASVC
- Prev by Date: Re: NLASVC
- Next by Date: Re: NLASVC
- Previous by thread: Re: NLASVC
- Next by thread: Re: NLASVC
- Index(es):
Relevant Pages
|