Failed to load Terminal Server Profile path

[Bill]

I am getting this error on my W2k# terminal servers

Source: Winlogon
Event ID: 1218
Type: Error
Category: None

Failed to load Terminal Server Profile path. Note that the profile
path must be less than 256 characters in length. User Name: xxxxxx
Domain: xxxxxxx

I have checked and the profile path is only 25 characters long.
Everything was working fine in a test enviorment but now that the
system in production nothing works. ie group policies. I have
search the web but the only solution I found is to move the shared
profile directory closer to root. Since the profile directory is one
folder under the root I don't think this is my problem. If someone
has a solution I would love to hear it as it driving me crazy.

Thanks Bill

[Vera Noest [MVP]]

Your best bet is to download FileMon and RegMon from
http://www.sysinternals.com/. Run them as administrator and start
a TS session as a normal user.

FileMon and RegMon will show you what is going on, and which
profile path the system tries to use. I believe that you can get
this problem when there is a space in the path and the value in
the registry doesn't have quotes around the path.

--
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
--- please respond in newsgroup ---

Bill <bill_golem@nospam@bwdsb.on.ca> wrote in
news:pd9hlv40i9gqkgk6f...@4ax.com:

[Mike Silverman]

What are the security rights that you see assigned to the users profile
directory?

SYSTEM should have full control
<username> should have full control

I think you may be getting that error because SYSTEM doesn't have
appropriate rights.

The other thing that comes to mind is, are there spaces in the folder
names that make up the profile path? That should be avoided.

Mike.

[sean]

I fixed this problem by editing the TCP-RDP protocal permissions and
added the users that I wanted to have access to the server( This can
be found admintrative tools> Terminal server confiuration , then rigth
mouse on tcp-rdp> Properties). Also logon locally rigths in the Local
security policy as well.

Mike Silverman <Noah...@nowhere.ca> wrote in message news:<u3P0oZcd...@TK2MSFTNGP11.phx.gbl>...