User cannot logon to terminal server - profile cannot be loaded.

Event ID: 1500
Source: Userenv
Type: Error
Windows cannot log you on because your profile cannot be loaded. Check that you are connected to the network, or that your network is functioning correctly. If this problem persists, contact your network administrator.

 DETAIL - Insufficient system resources exist to complete the requested service.
*******************************************************************************************************************

From time-to-time users are prevented from connecting to this Windows 03 Terminal Server and the above event is being logged.  It may only affect a particular user while others are currently connected.  I can also connect (remote deskop) to investigate.  It is not always the same user.

This is a Windows 2003 server WITHOUT any service pack installed.  Total RAM is 1GB.

Any ideas?
 
wwITmanAsked:
Who is Participating?
 
bank_on_itConnect With a Mentor Commented:
Try deleting all users profiles and check to make sure there is enough storage space to handle all the users that login.
0
 
Cláudio RodriguesFounder and CEOCommented:
Well 1GB RAM could be an issue depending on how many users you have. Besides that, a couple questions:
1. How often do you reboot this server? TSs should be rebooted, ideally, on a daily basis. This alone may get rid of the issue.
2. Do you have UPHClean installed on this box? That will help with profile handling and help avoiding profile errors.

Cláudio Rodrigues
Citrix CTP
0
 
wwITmanAuthor Commented:
*** I too think 1GB is very low for a terminal server even though the user count is only 2 to 4 users at a time.  May be addressing that in the future.
*** There is plenty of storage space for the profiles.
*** Server is not booted regularly - last time was a couple months ago - when this same issue arose.
*** UPHClean - I did think of this mayself as I noticed related events but noticed an "Informational" event right after the "Warning" event - thought is was being handled without UPHClean.
0
Free Tool: Port Scanner

Check which ports are open to the outside world. Helps make sure that your firewall rules are working as intended.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

 
Cláudio RodriguesFounder and CEOCommented:
Ok, for 2 or 4 users 1GB should be fine.
The reboot as I said will probably fix the problem and again, it is a best practice. UPHClean will help but it is not a silver bullet for all profile issues. :-)

Cláudio Rodrigues
Citrix CTP
0
 
beesterCommented:
As bank_on_it says - try deleting the profile(s) in question here. Everyone who is running MS Terminal Services have to delete some user profiles now and then. :)
0
 
wwITmanAuthor Commented:
Yes, I could delete profiles if needed but a server restart cleared the issue for this user.  Wondering why a suspect profile would be the cause if a server restart fixed the issue - at least temporarily.
0
 
Cláudio RodriguesFounder and CEOCommented:
It is not a single user profile that is the issue. The fact the TS is rebooted rarely simply gives you time until it cannot handle it anymore and then this happens. It is like the last drop in the bucket. :-)
Regular reboots will almost certainly eliminate the issue completely.

Cláudio Rodrigues
Citrix CTP
0
 
beesterCommented:
I personally set up automated reboots on my terminal servers at LEAST once a week, preferrably more often. This eliminates alot of problems like the one described here.

Just a tip I got when attending a Metaframe course ten years ago :)
0
 
wwITmanAuthor Commented:
I "assume" that cleaning up some profiles "may" have corrected the problem but don't know for sure as the problem was so intermittent.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.