Click here to Skip to main content
11,703,505 members (74,840 online)
Click here to Skip to main content

Tagged as

System.Runtime.InteropServices - An approach to debugging for COMException (0x80010108)

, 25 Dec 2011 CPOL 15.3K 1
Rate this:
Please Sign up or sign in to vote.
An approach to debugging for COMException (0x80010108): The object invoked has disconnected from its clients.
I got this error using Office automation:

System.Runtime.InteropServices.COMException (0x80010108): The object invoked has disconnected from its clients. (Exception from HRESULT: 0x80010108 (RPC_E_DISCONNECTED)),


It can be nasty to debug.

One strategy to address this error is to see if an event has occurred to interrupt the Office application running under automation.

I traced my problem to a Word macro I was running from a Visual Basic program. I did not notice that the macro caused Word to exit. Once Word shut down, the automation couldn't continue and I got the error that the "object invoked has disconnected."

The solution was to edit the macro so it ran without shutting down Word.

Perhaps this will help someone.

License

This article, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Share

About the Author

Dhruva Hein
United States United States
No Biography provided

You may also be interested in...

Comments and Discussions

 
-- There are no messages in this forum --
| Advertise | Privacy | Terms of Use | Mobile
Web01 | 2.8.150819.1 | Last Updated 25 Dec 2011
Article Copyright 2011 by Dhruva Hein
Everything else Copyright © CodeProject, 1999-2015
Layout: fixed | fluid