Re: VB6 Run-time errors after microsoft patches and updates
- From: szurlo@xxxxxxxxx
- Date: 26 Apr 2007 07:22:05 -0700
On Apr 25, 7:00 pm, Gary <G...@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
HI,
We are running some VB6 automations that allow folks to take FileNet OCX
control treeview items and register them to a corporate RDBMS database
through ADO ODBC Oracle 9i. On the 14th we placed a series of new Microsoft
patches on the users PC's and all of a sudden we started getting
"FormsOutSearch - Unanticipatederror: Component 'MSDATGRD.OCX' or one of its
dependencies not correctly registered: as file is missing or invalid" - or -
we get "Run-timeerror'339' Component 'MSADODC.OCX' or one of its
dependencies not correctly registered: a file is missing or invalid" - or -
we get "Runtime-error'713': Class not registered. You need the following
file to be installed on your machine. MSSTDFMT.dll"
As remedy we have exhausted all we know and the only thing we know that
works is to take the ghost of the machine from before the update and use it
with that user's profile for updates shut off. That is not a very good
solution so can someone help me troubleshoot what recent patches may be doing
to clobber the ADO component set? Further more what can we do to get our
indexers back to running with all the security patches applied?
I have had some responses from other groups across the internet on this so
let me start off by saying that we have the animated cursor patch isolated as
the direct culprit for this intermittent behavior. If we uninstall that
patch the thing starts working bug free. We have had viruses in the company
(not in this area) so we have opted to keep trying to get this patch on. We
have had patch patches from Microsoft, but they too are causing the same
results.
My call out is to see if anyone has this exact situation and to collaborate
the remedy with you. If you are not experiencing this please don't respond.
Thanks
Gary McFarling
Sr. Software Engineer II
North Dakota, Workforce Safety & Insurance
701-328-6013
We have about 30 tablet PCs running a VB 6 app that uses ADO to access
local SQL Express 2005 tables. Starting maybe 2 or 3 weeks ago we
started randomly getting rte 339 on MSADODC.OCX or rte 50003
(unexpected error) on application start. I'm pretty sure the error is
bogus, because simply reattempting to start the application a few
times usually eventually succeeds. Rebooting also seems to help. The
really confusing thing is that all of these tablets were created using
the same image but only maybe 20% of them are having this issue. I am
currently waiting for one of the users that gets it often enough to
make it possible for me to troubleshoot to bring me his tablet. I
will post more when/if I learn anything.
.
- Prev by Date: Re: Problem with Events (lost focus)
- Next by Date: Re: Can someone suggest a powerful GridView?
- Previous by thread: Re: VB6 Run-time errors after microsoft patches and updates
- Next by thread: FYI: ccrpTmr6 vs VB native control
- Index(es):
Relevant Pages
|
