Re: Update

Had this issue yesterday and today with two specific users. If I renamed
their ntuser.dat, they could login, but got a default profile.
Followed the article for KB935649 and made the registry changes.
Rebooted the server, and it's been fine since (only about 1/2 day so far).

We were getting several Userenv messages in Event Viewer.

Also found that there was a maintenance patch to Symantec for the version I
installed last week to take it to 10.1.6.6010.
It still happened today though after installing the patch last night and
rebooting.

Hopefully the registy changes will help.

Thanks again.



"TP" wrote:

Hi,

Glad to see things are getting better than before.

I suspect you may be running out of paged pool memory.

Please post the sequence of errors in the log with the Source,
Event ID, Type, and Description text. Usually these types
of errors will be from source Userenv. This will help confirm
that my suspicion is correct--I am not certain based on you
saying that other users are able to logon fine.

I prefer to examine the paged pool usage and then increase
the maximum incrementally until the errors stop. If you would
like to just increase to the maximum paged pool setting and
see if that works then follow the instructions in this article:

Error message when you try to log on to a Windows Server
2003-based terminal server: "Windows cannot load the user's
profile but has logged you on with the default profile for the system"

http://support.microsoft.com/kb/935649

If you run into other issues with the maximum settings let me
know and I will help you pick a lower setting.

Please post back either way so that we know if your issue
has been resolved.

Thank you.

-TP

Ray234 wrote:
I have installed the 2GB of RAM, which takes us up to 4GB total. Task
Manager shows right around 2GB used. I checked the UPHClean logs,
and found several per day for the Symantec Anti-Virus as not being
able to close the process. I have installed version 10.1.6.6000 of
Symantec, which was recommended. The UPHClean log entries stopped.
The server ran through the weekend without any issues with Symantec
updates and backups.

On Monday, I had a user that tried to login, but couldn't. It gave
her an error "Cannot load profile..." and "Insufficient system
resources...". She clicks OK, and is logged off. I login, and get
the same errors, but it gives me a default profile (Logged in as an
admin). I researched, and didn't find a fix. I rebooted this
morning, and could get in fine with no errors. So, obviously there
is still something that is taking resources. When I checked the
server yesterday, it had plenty of free memory and CPU. Other users
could login fine.

Any other ideas?

.