• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 3960
  • Last Modified:

Error Windows can not query DLLname

Since yesterday I'm getting the error every 5-7 minutes "Description: Windows cannot query DllName registry entry for {696FED8A-263C-44C8-8195-A016BA48373D} and it will not be loaded. This is most likely caused by a faulty registration."
I looked it up in the registry (attached).  How do I fix this?


regedit.png
0
J.R. Sitman
Asked:
J.R. Sitman
  • 8
  • 6
  • 2
  • +3
1 Solution
 
Mike KlineCommented:
Did  you install or uninstall anything on the box since yesterday?   Are these 1041 errors in your logs?

http://support.microsoft.com/kb/216358/EN-US/ 

That is an older article about CSEs
0
 
J.R. SitmanAuthor Commented:
Didn't install anything.  There may have been a Microsoft update, but not sure.  Yes there are 1041 errors.  See attached
1041.png
0
 
Mike KlineCommented:
I'd first try to uninstall th update and see if the 1041s stop.  Since that is the only thing that changed on the system.

Is this a member server?

Thanks

Mike
0
Free tool for managing users' photos in Office 365

Easily upload multiple users’ photos to Office 365. Manage them with an intuitive GUI and use handy built-in cropping and resizing options. Link photos with users based on Azure AD attributes. Free tool!

 
J.R. SitmanAuthor Commented:
I just checked add/remove and no updates have been installed since 3/20.  I also checked the logs and it first appeared at 6:27 am today.
It's is a DC
0
 
Mike KlineCommented:
Can you check another DC to see if you have that CSE in the registry.   Since it is saying "value not set" it is probably another program or Microsoft service.

0
 
J.R. SitmanAuthor Commented:
it is not on the other DC
0
 
Mike KlineCommented:
I see a lot of threads about IE but those are talking about a different GUID,  I don't want to tell you to delete it and cause issues.  I'll let you know if I find any specific info on that GUID.

Thanks

Mike
0
 
J.R. SitmanAuthor Commented:
Think I can delete it?  Doesn't seem important.  "forcerefresh"
0
 
J.R. SitmanAuthor Commented:
thanks.  I'll wait for your post.
0
 
J.R. SitmanAuthor Commented:
Any luck finding more info?
0
 
Mike KlineCommented:
I haven't been able to find anything on that GUID, not on my DCs either.
0
 
J.R. SitmanAuthor Commented:
I'm going to backup the registry and delete it.  I'll post results.
0
 
J.R. SitmanAuthor Commented:
Because of your suggestion to check the other DC, I knew it could be deleted.
0
 
Mike KlineCommented:
Great work!!  I wanted to say delete it the entire time...but didn't want to say it without knownin100% ....now I know too :)
0
 
caltrolitCommented:
This is the Desktop Authority 32bit policy that is setup to install the client on machines within your domain.

I tracked this down while building a windows server 2003 box that was put in the wrong OU and our desktop authority policy hit it out of left field.
0
 
kane77573Commented:
Awesome info caltrolit: we also have DA and it appears on the server.
This worked for me as well.
Thanks
0
 
caltrolitCommented:
Glad i could help out!
0
 
svenable1Commented:
I found the same error on several servers in our Domain. We also use Desktop Authority and had recently upgraded to the version with the client management agent deployed by OU. Very helpful, good pickup. thanks!   -SV
0
 
t001zCommented:
Thanks caltrolit!! We had a DC that got demoted then installed the DA client and when it got re-promoted to a DC again, it started screaming these errors at me!!  Your tip really saved me the a great deal of troubleshooting!!
0

Featured Post

The new generation of project management tools

With monday.com’s project management tool, you can see what everyone on your team is working in a single glance. Its intuitive dashboards are customizable, so you can create systems that work for you.

  • 8
  • 6
  • 2
  • +3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now