Server 2003 hangs during logon at "Applying Personal Settings"
From: Damox (anonymous_at_discussions.microsoft.com)
Date: 04/20/04
- Next message: tomppa: "Re: License question"
- Previous message: Kristofer Gafvert: "Re: Subsequent hotfixes"
- Next in thread: DAMOX: "Server 2003 hangs during logon at "Applying Personal Settings""
- Reply: DAMOX: "Server 2003 hangs during logon at "Applying Personal Settings""
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 20 Apr 2004 12:40:33 -0700
We are currently accessing our 2003 Servers via remote
desktop or terminal services. On Friday I first noticed
there was a problem with one of the servers running out of
drive space on C drive. After adjusting the pagefile so
that part was on D drive, I rebooted the Server and found
that I could not log on. The problem is that when we
attempt to log on, either remotely or locally, the
computer hangs at "Applying Personal Settings". The cause
of the hang is that the profile of the individual logging
on becomes huge and takes up all the remaining free space
on the C drive. It doesn't matter if there is 1 GB of free
space, or 3, the profile will continue to grow until there
is no more space left. Actually there is only one file
that grows, and that is a file called brndlog.txt. The
file has to do with Internet Explorer branding. In looking
at the brndlog.txt file in Internet Explorer, the reason
the file grows so big is because of an error in a file
that is being processed, wininet.dll. After logging
numerous bits of information, whichever process is doing
the logging seems to hang on the wininet.dll. It logs the
following error information continually until the drive
runs out of space:
ProcesswwininetCS return error: 8004005. Processing
wininet.dll settings.
To date, this is what we've tried or learned:
1. We found we are able to log on locally in
the safe mode.
2. We can log on locally if we disconnect the server
from the network. When we've done this it seems that the
logging process does not take place.
3. I tried renaming the file wininet.dll to see what
would happen. When I did that, I could log on. It seemed
that the logging process does not take place or ends when
the wininet.dll is not available. However, renaming the
wininet.dll causes other errors, for one thing, Internet
Explorer does not run. When I renamed the wininet.dll, I
was able to log on remotely as well, but again it caused
some errors. I found several processes that wouldn't run
when the wininet.dll was not available.
4. Wininet.dll is apparently a key Internet Explorer
file.
5. I tried another version of wininet.dll that I
found under \Program Files (x86)\Network
Associates\NetShield 2000 directory, but that resolve the
issue.
6. I copied the wininet.dll file from the Server 2003
CD thinking that it might be a different version or that
it might be corrupt, but that did not produce a resolution
either. The wininet.dll file on the CD seems to be the
same as file that was already present on the system.
7. I have also tried disabling certain services, such
as "DHCP Client", "Automatic Updates", and "IIS" none of
this made any difference.
8. I have checked for patches that may have been
installed recently, but the last patches were run late
last year. It seems that this problem has arisen in the
past 2-3 weeks.
9. Someone suggested that "Microsoft Product Support
Reporting Tool" was causing the logging. I checked, and
the MPSRT is not installed on these servers.
10. I changed the DNS server from xxx.x, which is not
a DNS server (at least to my knowledge) to xxx.x a known
dns server, but that did not help.
The question is, what is causing the logging to take place?
I have determined that this logging is taking place on all
Servers and in fact all computers each time they log on to
the network. I could not find anything in the default
domain policy that would cause this to happen. I do not
know what process is generating the logging. On the
Windows 2000 Servers the logging completes normally
without incident. On the 2003 Servers, it hangs on the
wininet.dll. What is different between the Windows 2000
and 2003 Servers?
The Windows 2003 Servers have 2 versions of Internet
Explorer 6, a 64-bit version and a 32-bit version. Is this
normal? It is my belief that this may be causing the
problem.
I was hoping to uninstall the 32-bit version of Internet
Explorer, however I could not find any obvious way to do
that.
Does anyone know how to uninstall Internet Explorer from
Server 2003? Is it even possible? Also is it normal for
Server 2003 (64 Bit version), to have both 64 and 32 bit
versions of IE6?
- Next message: tomppa: "Re: License question"
- Previous message: Kristofer Gafvert: "Re: Subsequent hotfixes"
- Next in thread: DAMOX: "Server 2003 hangs during logon at "Applying Personal Settings""
- Reply: DAMOX: "Server 2003 hangs during logon at "Applying Personal Settings""
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
