Quantcast
Channel: Group Policy forum
Viewing all articles
Browse latest Browse all 19997

Cannot query DllName registry entry

$
0
0

Hi,

Our XP PC seems having Winlogon application error that related to the following:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\GPExtensions\]{7B849a69-220F-451E-B3FE-2CB811AF94AE} = Internet Explorer User Accelerators
{CF7639F3-ABA2-41DB-97F2-81E2C5DBFC5D} = Internet Explorer Machine Accelerators

http://social.technet.microsoft.com/Forums/en-US/winserverGP/thread/a26a9c59-c692-416c-b13d-411a578342c3/

Event Type: Error
Event Source: Userenv
Event Category: None
Event ID: 1085
Date:  4/6/2013
Time:  8:39:57 AM
User:  NT AUTHORITY\SYSTEM
Computer: 
Description:
The Group Policy client-side extension Internet Explorer Zonemapping failed to execute. Please look for any errors reported earlier by that extension.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

If the XP PC link enabled to the IE policy, it will register cannot query DllName registry entry in event log. This happen after some update to the policy.

On userenv>>

USERENV(3e8.3ec) 10:35:56:437 CUserProfile::CleanupUserProfile: Ref Count is not 0
USERENV(3e8.3ec) 10:35:56:437 CUserProfile::CleanupUserProfile: Ref Count is not 0
USERENV(3e8.eb8) 10:36:41:234 ProcessGPOs: Extension Internet Explorer Zonemapping ProcessGroupPolicy failed, status 0x57.

On rsop>>

Saturday, April 06, 2013 11:57:15 AM

Note:  This component only reports overall status information.  It does not report information about its individual policy settings; consequently, those settings will not appear in this tool.  Please contact the vendor of this component to check if an updated version is available.

Internet Explorer Zonemapping failed due to the error listed below.
The parameter is incorrect.


But it is not issue on Windows 7 PC.



Viewing all articles
Browse latest Browse all 19997

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>