User can not logon to TS as profile will not load

[Ken Merrigan]

I have a user that had been connecting to a Terminal Server but was
having various problems, such as ini files getting corrupt and very
slow performance. I decided to delete his profile from the TS, and
have him log on again, thus recreating the profile. However, after
removing the profile when he tries to logon to the TS, he gets the
following message:

Windows cannot log you on because the profile can not be loaded.
Contact your network Administrator.

DETAIL – There is not enough space on the disk.


There is a single partition and it has plenty of space (nearly 25
Gigs), so this would seem to be a false message. The event log shows
EVENT ID 1000 with the source being USERENV. The description shows
the same message as above.

This issue is specific to this user. Other users are able to log on.
I am able to create a new profile on the TS by logging on with a user
name who has not previously logged on to this TS. I then removed this
new profile, and logged on again as the same use, successfully
recreating the profile.

I have looked in the Microsoft KB and Google Groups, and found similar
circumstances, but nothing identical to mine. I installed W2K SP4 on
the server. This did not solve the issue.

We have tried logging this user in from a different machine. We have
tried machines with different OS' (W2K Pro & XP), to no avail.

If anyone has experienced this before, or has any ideas, or could
point me to a good source of information, it would be much
appreciated.

Thanks in advance

Ken Merrigan
Network Administrator
Core-Mark International.

 

[Matthew Harris [MVP]]

Try turning on user environment logging to see if this
helps you any...

support.microsoft.com/default.aspx?scid=kb%3Ben-us%3B221833

-M

 

[Robin Caron]

The symptoms would seem to indicate that this user has a disk space limit
(quota) enforced on him. I would check that.

 

[Ken Merrigan]

The symptoms would seem to indicate that this user has a disk space limit
(quota) enforced on him. I would check that.

Robin,

Disk quotas were indeed the cause of the issue. Thank you for the
suggestion.

One additional piece of information. Disk quotas had been enabled,
but not enforced. In other words the "Deny Disk Space to users
exceeding quota limit" was not selected. As a result, this user had
long ago exceeded the default limit that had been set (by more than
200 MBs). Its interesting that although he was free to exceed this
limit through file storage, Windows would not allow the new profile
to be created because the limit had been exceeded.

Thank you again

Ken Merrigan
Core-Mark International, Inc.