ProfilePath issue

[Guest]

Does anybody know how to fix this error?
"Windows cannot log you on because the profile cannot be loaded. Contact
your Network Administrator.
DETAIL - There is not enough space on the disk"

So far, the "ProfilePath" is set to e:\users
Thanks.....

 

[Guest]

2 things come to mind on this.

1. Check the E: drive to verify the disk space is enough for the profile
being loaded.
2. Check the permissions on the E: drive to verify the user has the modify
permission to be able to write the profile data to that drive.

HTH

Drum on .. .. . .

 

[Dave Patrick]

What does this mean?

--
Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

:
<snip>
| So far, the "ProfilePath" is set to e:\users
<snip>

 

[Guest]

It means that on the "environment variables", i created a "ProfilePath"
variable called e:\users on the e:\drive instead of the C:\drive.
Originally, we were having issues with users from a different domain logging
in to this Terminal server. e:\users fixed that issue, but now a single user
who was able to log in originally is having issue logging back in.

 

[Dave Patrick]

An environment variable you create would have nothing to do with this. The
Reg_Sz string
'ProfileImagePath'
found at
HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList
would determine this. If the E:\ is a network drive then it probably
wouldn't exist until after logon.

Check Event Viewer for details on the error. Also this article may help.

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

--
Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

:
| It means that on the "environment variables", i created a "ProfilePath"
| variable called e:\users on the e:\drive instead of the C:\drive.
| Originally, we were having issues with users from a different domain
logging
| in to this Terminal server. e:\users fixed that issue, but now a single
user
| who was able to log in originally is having issue logging back in.