Code Error 80041001 – Call Failed

Troubleshooting Code Error 80041001 – Call Failed

Introduction to Code 80041001

I will be frank with you, I do not know much about this error.  What little that I do know is thanks to Mark P, Shane and Ramesh.  Here is a wild guess, you are using WMI to connect to an object like DNS or Performance Monitor.

The Symptoms You Get

When you run the Windows Management Instrumentation Tester (WBEMTEST), connect to one of the Windows Management Instrumentation (WMI) namespaces (ROOT\CIMV2\xxxxxxxx), where xxxxxxx = perfmon or DNS.

The Cause of Code 80041001

It’s probably no consolation that this is a poorly documented error.  Again, thanks to Mark he said that it was intermittent, and the same script worked fine on another server.  Makes me suspect that one source of this problem is Active Directory synchronisation.  Another cause of a Code 80041001 problem is that the underlying service has stopped, for example the spooler service.  (Thanks to Robin Lee for this info).

The Solutions

Try running your VBScript on another machine?  If this works, then your code is probably fine, it’s more of a logical problem, or something up with the OS / Active Directory.  I hate it when people say ‘reboot the server’, so try simply restarting the services that you are investigating.

One possibility is that your winmgmts service is corrupted if so, you have the following options.  To be honest, I believe that there is only a 20% chance that these procedures will cure your 80041001 problem.  A bonus is that you will learn or have a refresher on restarting services and registering services in the registry.


Start and Stop the winmgmts service

Navigate to the command prompt.

net stop winmgmt WBEM Directory 80041001

Using Windows Explorer, navigate to %systemroot%\system32\wbem directory and delete the Repository directory. By default, the repository folder is located in the C:\Windows\system32\wbem directory.
Switch to Command Prompt window, and type:
net start winmgmt

Re-Register the DLLs

The .DLL and .EXE files which WMI uses are located in %windir%\system32\wbem.  This is how you re-register all the .DLL and .EXE files in the WBEM directory. To re-register the WMI components, run the following commands at the command prompt:

cd /d %windir%\system32\wbem
for %i in (*.dll) do RegSvr32 -s %i
for %i in (*.exe) do %i /RegServer

Recommended: Solarwinds’ Permissions Analyzer – Free Active Directory ToolFree Permissions Analyzer for Active Directory

I like thePermissions Analyzer because it enables me to see WHO has permissions to do WHAT at a glance.  When you launch this tool it analyzes a users effective NTFS permissions for a specific file or folder, and takes into account network share access, then displays the results in a nifty desktop dashboard!

Think of all the frustration that this free SolarWinds utility saves when you are troubleshooting authorization problems for user’s access to a resource.  Give this permissions monitor a try – it’s free!

Download SolarWinds’ Free Permissions Analyser – Active Directory Tool

Re-Install WMI files

If you suspect that the WMI files are damaged, then you could re-install them from the Windows Server 2003 or XP CD.  Here is the nifty command:

rundll32.exe setupapi,InstallHinfSection WBEM 132 %windir%\inf\wbemoc.inf

I thank Shane and Ramesh for supplying this extra information on WMI Errors in general and 80041001 in particular.

Example of Error Code 80041001 Script

To date this is the only example that I have.

80041001 Call Failed error


Real Life DNS Problem

Scenario: Script to create DNS entries. Kindly sent in by Martin Jeppesen

Problem: ‘A’ Host records already exist.

Solution: Delete the existing ‘A’ Host records.

Lesson for all of us, the script may be trying to create something that already exists.  If so, one solution is to add:
On Error Resume Next.


See More Windows Update Error Codes 8004 Series

Error 80004005 Unspecified Error   •Error 80041021   •Error 80041001   •Error 80041002

Error 80048820   •Error 8004100E   •Review of SolarWinds Application Monitor (SAM)

Error 80040E14   • Error 80040E37   • Error 80041006   • Error 80041006

Solarwinds Free WMI MonitorGuy Recommends: WMI Monitor and It’s Free!

Windows Management Instrumentation (WMI) is one of the hidden treasures of Microsoft operating systems.  Fortunately, SolarWinds have created the WMI Monitor so that you can examine these gems of performance information for free.  Take the guess work out of which WMI counters to use for applications like Microsoft Active Directory, SQL or Exchange Server.

Download your free copy of WMI Monitor

Do you need additional help?

Give something back?

Would you like to help others?  If you have a good example of this error, then please email me, I will publish it with a credit to you:

If you like this page then please share it with your friends