Prev: Fax Server Name
Next: Change language keyboard
From: LisaConsult on 19 Jan 2006 21:44
I have a VB6 application which installed in several environments and it has
been working fine for years. Suddenly I have 1 Win2K user that is receiving
the error "Automation Error: The object invoked has disconnected from its
client"
-2147417848. The process happens when a 3rd party OCX is invoked by this
statement: If (TypeOf activeChild.ActiveControl Is TextBox) Or _
(TypeOf activeChild.ActiveControl Is TXTextControl) Then
strText = activeChild.ActiveControl.Text
If Len(Trim(strText)) > 0 Then
CheckMate1.CheckTextStream True, strText
End If
End If

There is error handling in the procedure, the control is present on the
form. We believe it is Checkmate because TxText is used in other places
throughout the app and the only time they get a problem is in this routine.
The OCX company is no longer around so I have no support. Is there anyway I
can further debug this problem? What other factors would be causing it? The
OCX is installed in the Program files folder by default, we moved it to
System32 (and reregistered) to see if that might help, but cannot find the
source of the problem. Any help is greatly appreciated.
From: "Peter Huang" [MSFT] on 20 Jan 2006 01:39
Hi,

I think you may try to reregister the ocx to see if that works.
This is very general Automation error. It is hard to say what is the cause.

If possble, I think you may try to copy/paste the code to a new project one
by one to see what is the cause.


Best regards,

Peter Huang
Microsoft Online Partner Support

Get Secure! - www.microsoft.com/security
This posting is provided "AS IS" with no warranties, and confers no rights.

From: LisaConsult on 20 Jan 2006 09:23
Thanks for your message. We have tried registering the OCX again. I can try
to create a project which just uses the spell checking, but I still don't
know what options I have to further detect the problem with the error. Any
ideas of possible areas to look would be appreciated.


""Peter Huang" [MSFT]" wrote:

> Hi,
>
> I think you may try to reregister the ocx to see if that works.
> This is very general Automation error. It is hard to say what is the cause.
>
> If possble, I think you may try to copy/paste the code to a new project one
> by one to see what is the cause.
>
>
> Best regards,
>
> Peter Huang
> Microsoft Online Partner Support
>
> Get Secure! - www.microsoft.com/security
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>
From: "Peter Huang" [MSFT] on 23 Jan 2006 01:43
Hi

Have you tried to isolate the problem by adding the controls into a new
project to see what is the cause?
e.g. once you have added certian control, the problem will occur.
or once you have executed certain codeline or access certian control's
method/property, the problem will occur?

If that still did not help you. I think we have to contact the ocx
developper.
Or you need to contact MSPSS directly which will do dump analysis.
http://support.microsoft. com

BTW: if the problem is raised by the third party control, you have to
contact the control's vendor for support. Because we have no source code or
other resource to debug the issue.

Thanks for your understanding!

Best regards,

Peter Huang
Microsoft Online Partner Support

Get Secure! - www.microsoft.com/security
This posting is provided "AS IS" with no warranties, and confers no rights.

From: David J Mark on 23 Jan 2006 09:23

"LisaConsult" <lisasconsult(a)online.nospam> wrote in message
news:90A39B1B-4705-480B-9B09-8E0B908741D5(a)microsoft.com...
>I have a VB6 application which installed in several environments and it has
> been working fine for years. Suddenly I have 1 Win2K user that is
> receiving
> the error "Automation Error: The object invoked has disconnected from its
> client"
> -2147417848. The process happens when a 3rd party OCX is invoked by this
> statement: If (TypeOf activeChild.ActiveControl Is TextBox) Or _
> (TypeOf activeChild.ActiveControl Is TXTextControl) Then
> strText = activeChild.ActiveControl.Text
> If Len(Trim(strText)) > 0 Then
> CheckMate1.CheckTextStream True, strText
> End If
> End If
>
> There is error handling in the procedure, the control is present on the

Always good.

> form. We believe it is Checkmate because TxText is used in other places

Why guess? Which line is throwing the error?!

> throughout the app and the only time they get a problem is in this
> routine.
> The OCX company is no longer around so I have no support. Is there anyway
> I

Not a shock.

> can further debug this problem? What other factors would be causing it?
> The

Yes. Send this user a debug version. Modify your error handling to log
everything that happens. If the OCX turns out to the be the culprit, start
comparing registration information between a known good installation and the
problem box. What is this a spell checker or something? You may want to
get a new one if you can't get support for this CheckMate thing...

> OCX is installed in the Program files folder by default, we moved it to
> System32 (and reregistered) to see if that might help, but cannot find the

Do not install OCX's in the Program files folder. Fix your setup script,
remove all registry entries for the Checkmate OCX and re-install your app...


> source of the problem. Any help is greatly appreciated.


 | 
Pages: 1
Prev: Fax Server Name
Next: Change language keyboard