Visualcron is causing wmiprvse.exe to crash. Here are details from event log:

Faulting application name: wmiprvse.exe, version: 6.1.7600.16385, time stamp: 0x4a5bc794
Faulting module name: ole32.dll, version: 6.1.7600.16385, time stamp: 0x4a5be01a
Exception code: 0xc0000005
Fault offset: 0x00000000000204e4
Faulting process id: 0x2acc
Faulting application start time: 0x01cc20cbf110d5c4
Faulting application path: C:\Windows\system32\wbem\wmiprvse.exe
Faulting module path: C:\Windows\system32\ole32.dll
Report Id: 0a06be33-8d23-11e0-9309-0015c5e5eef9

Enviroment: Windows Server 2008 R2 64-BIT

This is a serious problem that can impact other appliations that use the WMI api. I really like this software but I cannot purchase it with these kinds of issues.

Jason

Hi Jason,

how do you know that VisualCron is crashing wmiprvse?

What we do know is that VisualCron make use of WMI for various things. Mostly for some Triggers and performance counters - and yes, as you can use any setting you like for polling WMI there is a possibility, that WMI could get overloaded.

It is however not very likely if the WMI is not corrupt from the beginning as VisualCron uses managed code, so the .NET layer is between and preventing any direct calls and making many things to proceed in a controlled matter.

The big question, if this is really related to VisualCron, is what VisualCron is doing when it happens?

There are also various sources on the Internet describing how to repair an already corrupted WMI (because it contains a database of instrumentation that could get corrupted). If you search on "repair wmi" you will get a lot of answers how to proceed.

---

Thank you for the quick response.

Question 1: How do you know that VisualCron is crashing wmiprvse.exe?

Answer: The process never crashed on that server prior to installing VisualCron

Question 2: What is VisualCron doing when it happens?

Answer: At this point all of our jobs simply call scripts on linux servers using ssh connection. I can't pinpoint one exact job that runs at the same time when wmiprvse.exe crashes. We do have on job that calls a script on the linux box every minute. So obviously this job will line up with the times of the crash, but I'm not sure there is any relationship.

No other users have reported this issue? I will continue to dig into the cause, but I don't think the wmiprvse.exe needs to be fixed as we never saw this issue on the server prior to using VisualCron.


Jason

There is no known connection between running SSH Tasks and WMI. If you feel that VisualCron is associated with those crashes we need your help to determine when it crashes.

It is also interesting how often this happens.

As WMI is central for some operations we have received reports that some functionality is VisualCron is not working. The reason have been that WMI was corrupted. After repair it worked normally.

---

It seems to be a common problem on Windows Server 2008 R2:

http://social.technet.mi...-41fc-ad87-a0380f4c953b/ 

http://www.techadre.com/...tent/fix-wmi-memory-leak 

In the last link there is also a link to a Microsoft Hotfix for the error (or similar):

http://support.microsoft.com/kb/981314 

---

Thank you for the helpful links. I'm going to look into the issue and perhaps install the hotfix. Please leave this issue open and I will follow up later this week. This issue only occurs a couple of times a day so I will need time to ensure any fix we put in place actually solves the problem.


Jason

Thanks for your patience and that you follow up on this case.

---

Update: The error we are having with wmiprvse.exe crashing has been confirmed on other Windows 2008 Servers that are not running VisualCron. The common factor with this error is Windows 2008 and SQL Server. I have not applied the hotfix yet, but I wanted to follow up on this post because this is definitely not an issue caused by VisualCron.


Jason

Update: The error we are having with wmiprvse.exe crashing has been confirmed on other Windows 2008 Servers that are not running VisualCron. The common factor with this error is Windows 2008 and SQL Server. I have not applied the hotfix yet, but I wanted to follow up on this post because this is definitely not an issue caused by VisualCron.


Jason

Thanks for the quick feedback!

---