Problem after upgrade to Windows 2003

[Jens Hyllegaard]

We have just upgradet one of our existing W2K Terminal servers to Windows
2003 Server, standard edition.

After upgrading it, and adding the users to the Remote Desktop Users group.
They can log on, but they don't get their roaming profile with them. The
eventlog contains this:
***
Event Type: Error
Event Source: Userenv
Event Category: None
Event ID: 1506
Date: 21-10-2003
Time: 15:11:09
User: SGSFAXION\MA
Computer: SGSTS02
Description:
Your roaming profile is not available. You are logged on with the locally
stored profile. Changes to the profile will not be copied to the server.
Possible causes of this error include network problems or insufficient
security rights. If this problem persists, contact your network
administrator.

DETAIL - The request is not supported.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
***
There is no other indication of errors. Can anybody help?

Kind regards

Jens Hyllegaard
IT
SGS AS

 

[Matthew Harris [MVP]]

Try going to eventid.net and searching for 1506.

-M

 

[Jens Hyllegaard]

Tried that, no information found. I even tried clicking on then link
provided in the eventlog, No information available at microsoft either.

Kind regards Jens Hyllegaard

 

[Matthew Harris [MVP]]

Ok...try enabling UserEnv logging through the registry to
see if you can track down the problem.

http://support.microsoft.com/default.aspx?scid=kb;en-
us;221833&Product=win2000

-M

 

[Jens Hyllegaard]

Ok I did that, and I discovered that our current Terminal server user
profiles path was truncated?
Instead of \\server\tsdata\profiles\username it became
\\server\tsdata\username, why is that.

Well anyhow, I tried moving the profile, my own in this case, to the
location, where it tries to find it. But it did not help. The following is
what appears in the .log file.
***
USERENV(1ec.228) 09:50:34:747 LoadUserProfile: Entering, hToken = <0x6f4>,
lpProfileInfo = 0xaf9258
USERENV(1ec.228) 09:50:34:747 LoadUserProfile: lpProfileInfo->dwFlags =
<0x0>
USERENV(1ec.228) 09:50:34:747 LoadUserProfile: lpProfileInfo->lpUserName =
<jeh>
USERENV(1ec.228) 09:50:34:747 LoadUserProfile: lpProfileInfo->lpProfilePath
= <\\sgsdc\tsdata\jeh>
USERENV(1ec.228) 09:50:34:747 LoadUserProfile: lpProfileInfo->lpDefaultPath
= <\\SGSDC\netlogon\Default User>
USERENV(1ec.228) 09:50:34:747 LoadUserProfile: NULL server name
USERENV(1ec.228) 09:50:34:747 LoadUserProfile: User sid:
S-1-5-21-2025429265-1343024091-725345543-1107
USERENV(1ec.228) 09:50:34:747 CSyncManager::EnterLock
<S-1-5-21-2025429265-1343024091-725345543-1107>
USERENV(1ec.228) 09:50:34:747 CSyncManager::EnterLock: No existing entry
found
USERENV(1ec.228) 09:50:34:747 CSyncManager::EnterLock: New entry created
USERENV(1ec.228) 09:50:34:747 CHashTable::HashAdd:
S-1-5-21-2025429265-1343024091-725345543-1107 added in bucket 17
USERENV(1ec.228) 09:50:34:747 LoadUserProfile: Wait succeeded. In critical
section.
USERENV(1ec.228) 09:50:34:747 LoadUserProfile: Expanded profile path is
\\sgsdc\tsdata\jeh
USERENV(1ec.228) 09:50:34:747 ParseProfilePath: Entering, lpProfilePath =
<\\sgsdc\tsdata\jeh>
USERENV(1ec.228) 09:50:34:747 CheckXForestLogon: checking x-forest logon,
user handle = 1780
USERENV(1ec.228) 09:50:34:747 CheckXForestLogon: not XForest logon.
USERENV(1ec.228) 09:50:34:763 AbleToBypassCSC: Try to bypass CSC
USERENV(1ec.228) 09:50:34:794 AbleToBypassCSC: tried
NPAddConnection3ForCSCAgent. Error 1208
USERENV(1ec.228) 09:50:34:825 ParseProfilePath: CSC bypassed failed.
Ignoring Roaming profile path
USERENV(1ec.228) 09:50:34:825 ReportError: Impersonating user.
USERENV(1ec.228) 09:50:34:825 ReportError: Logging Error <Windows cannot
locate the server copy of your roaming profile and is attempting to log you
on with your local profile. Changes to the profile will not be copied to the
server when you logoff. Possible causes of this error include network
problems or insufficient security rights. If this problem persists, contact
your network administrator.
***
So somehow it appears to have something to do with CSC, whatever that is?

Kind regards

Jens Hyllegaard

 

[Jens Hyllegaard]

Ok, solved the problem now. It appears that Windows 2003 won't load profile
data, that is located on a non Windows server. We stored the data on an
AS/400 network drive, for backup reasons. After I moved the data to a NTFS
formated drive it worked. Go figure...

Thanks for your help, I would not have come this far without it.

Kind regards

Jens Hyllegaard
IT
SGS AS