Faulting module MSVBVM60.DLL v6.0.97.82 causes application to crash
Quote:
> We are testing a 3rd party application that have never encountered
> this issue before now. It's actually that in our automated script we
> execute script to open and close the 3rd party application a few
> times, which isnt unreasonable and shouldnt cause a crash.
> We are getting the error that the application had to close along with
> the the faulting module msvbvm60.dll, version 6.0.97.82.
> I checked in c:\windows\system32 for msvbvm60.dll and it exists. What
> do I need to do to resolve? Any help that someone can suggest would be
> great.
> Terry
Not enough information to venture more than a few hints.
First off, various 3rd products have had problems msvbvm60 and MS has issued
hotfixes in the past for some issues. Most of these hotfixes were
incorporated in later versions. These issues are part of the problems
experienced with VB SP6.
One 'fix' was to recompile applications with SP6.
You really need to put this to the vendor of the 3rd party application.
Second, the reporting of an error in msvbvm60 may only be a red herring.
After-all ALL VB apps use this runtime. Occasionally errors are not caught
until they reach the runtime. eg look at the number of times an error is
reported in the general dll service component ntdll. The error didn't start
there - it was only caught there. So you need to run a post-mortum de{*filter*}
and look at the call stack to determine where the error is coming from.
The fact that it used to work and is only failing now leads me to suspect
that it is another component that has been affected by a recent install, hot
patch, etc. Also consider this might be a flaw that has always been there,
but only is showing up now because of a change in location or data.
hth
-ralph
