Winlogon.exe, Userenv.dll errors

[Guest]

Hello.

I’m experiencing the following errors on a new Windows 2003 terminal
servers. SP1 is not installed, but all other available hotfixes are:

- Whenever anyone logs on, the following error message appears:
‘winlogon.exe encountered a problem and needed to close.’
The details are : AppName: winlogon.exe AppVer: 0.0.0.0
ModName: userenv.dll ModVer: 5.2.3790.0 Offset: 00028902

The following message appears in the application event log as an
informational event:
Application event 1004 Category 100
Reporting queued error: faulting application winlogon.exe, version 0.0.0.0,
faulting module userenv.dll, version 5.2.3790.0, fault address 0x00028902.

- When certain users log on, they are immediately kicked out during the
Applying Personal Settings portion, and the following events appear in order
in the Application event log:
USERENV 1091
The Group Policy client-side extension Internet Explorer Branding failed to
log RSOP (Resultant Set of Policy) data. Please look for any errors reported
earlier by that extension.
USERENV 1003
Windows cannot process Group Policy Client Side Extension (Internet Explorer
Branding). Exception 0xc0000005.
Application error 1000
Faulting application , version 0.0.0.0, faulting module userenv.dll, version
5.2.3790.0, fault address 0x00028902.


I have disabled any Internet Explorer maintenance policies and the error
persists. For users who are unable to logon, if I delete their roaming
profile and have them connect to a different Terminal Server, they are fine.
I am unable to delete their local profile on a server they have already
logged on to because it says that the ‘USRCLASS.DAT file is in use’.

Any help would be greatly appreciated.

Thanks.

 

[Tatsumi]

Do you have old roamingprofiles from Windows 2000 terminal server enviroment and are now using them in Windows 2003 terminal server enviroment?

I'm Having the same problem, i think it could have something to do with mixed enviroment consisting of windows 2000 and 2003 terminal servers.

I'm in the stage of isolating 2000 server profiles and create new 2003 profiles for my users.

Please give me feedback if you had another solution.

Regards

Tatsumi Morota

 

[Guest]

I came to the same conclusion - I ended up recreating the roaming profiles.
Apparently, the conflict is caused when there is any GP settings for Internet
Explorer.

 

[Guest]

To solve user kickout issue immediately without restarting the server, you
may enable "use only local profile" in group policy..However this is not a
permanent solution but a quickfix.It is better to have an uniform environment.
Regards

 

[MarkAAinsworth]

Hotfix from Microsoft

I've experienced the same problem with XP Pro SP2 clients and a W2K server. It appears that the problem is due to a bug in the way that the Folder Redirection policy interferes with the way that Internet Explorer settings are applied in Group Policy.

You can see the details of the hotfix that is available from Microsoft at:
http://support.microsoft.com/Default.aspx?kbid=888254


I originally found a discussion of the problem on a cached page of another discussion forum. At the time of writing, I could see the page at:
http://66.249.93.104/search?q=cache:AG-cjRh9qP0J:x220.minasi.com/forum/topic.asp?TOPIC_ID=11178
I'm not sure how long the cached version of the page will be there and I couldn't find the original (i.e. non-cached) version.

Hope this helps.

 

[Guest]

I have the same error and I cannot figure out what the problem is, using
local profiles is not an issue because this affecte 300 people.

Our old farm is Win2k and our new farm is win2k3.