Runtime Error 80010108
The runtime error 80010108 is often an easy one to fix as long as you aren’t a programmer trying to write new code.
That’s because the runtime error 80010108 comes up for the average pc user when an ActiveX object is not available for an automation process you are attempting to create. That’s ok – most often the program that generated the object references isn’t running anymore and that’s why you got the error.
Check to see if you have a more complex cause for runtime error 80010108:
Explore the Registry Cleaner that Identifies
Specific Error Causes Inside Your Registry!
Did you close down your Excel spreadsheet and then try to use Visual Basic to create something that used the Excel worksheet data-”the object”? The runtime error 80010108 error message is “the object invoked has disconnected from its clients.” So that would mean the Visual Basic (“client”) has “invoked” the Excel “object” but the object isn’t there anymore for Visual Basic to reference.
The runtime error 80010108 means you can’t access an object because you turned off the program that supports the object!
Of course, this is a best case scenario. All you need to do is start running Excel and then attempt the automation process with Visual Basic again. The “object” (say a set of worksheet data) will be available for your automation process and you shouldn’t get the runtime error 80010108 again. Problem solved. Obviously, you could be using different applications than Excel and Visual Basic – but you get the drift.
However, if your runtime error 80010108 is a recurring problem and you suspect that the ActiveX objects are not just unavailable because the object’s program of origin isn’t running, you could have a more complex cause for the runtime error 80010108. If the objects are being destroyed somehow, or they are unavailable for manipulation even when the program of origin is running, that indicates a more serious issue.
You may need to solve your ActiveX problems by updating programs, re-registering the DLL that controls the object, or you may have a virus that is corrupting your registry files (where the ActiveX controls live) and messing up your ActiveX objects across the board. Begin troubleshooting the runtime error 80010108 by getting the current WindowsTM updates and any patches or hotfixes from the programs in question (in our example, Excel and Visual Basic).
So many runtime errors are caused by incompatibility between applications and/or system that updates are the place to start.
If updates don’t solve your problem, you can try a registry cleaner software. A good registry cleaner re-registers your DLL’s for you and can manage your ActiveX object problems. This type of software is designed to repair corruption in files or pathways inside your PC that cause errors like the runtime error 80010108. You can get a free diagnostic scan and see immediately if the registry cleaner can detect a WindowsTM registry problem that is causing your specific runtime error 80010108. (That way you aren’t wasting money on a program that won’t fix your runtime error 80010108.)
If a registry cleaner can’t spot the cause and fix it, then you’ll have to pay a REALLY good repair tech to comb through your files and/or code for the source of runtime error 80010108. And that’s obviously the worst case, most expensive scenario!
Explore the Only Registry Cleaner that