Archive for the ‘runtime 80010108’ tag
What Can You Do About The Runtime Error 80010108?
Your runtime error 80010108 could be simple to eradicate or it could be difficult. Typical PC users frequently get this error when an ActiveX object they need is inaccessible for use. Believe it or not, that may be the best scenario.
The support for an ActiveX object originates in the actively operating application it is created from. For example, pretend you want to automate the export of some data from an Excel spreadsheet in to Visual Basic. You begin your work inside Excel defining the desired data for the task and when you are done, you shut Excel down. You are working with Visual Basic as you get the runtime error 80010108 “the object invoked has disconnected from its clients” message. If Visual Basic is the “client” and the automation process is the “object invoked,” your challenge is finding out why the object disconnection happened and fixing it.
Puzzled about why your computer is spitting out a runtime error 80010108? You shut Excel (in our example) down and Excel sustains the ActiveX object you need to access. To maintain the connection with the desired object, you need to have the application it originated in running. In our example, that tells you Excel must be running if you want to automate an export from Excel into Visual Basic.
You certainly dodged the bullet if that was the cause of your runtime error 80010108. The complexity of causes for ActiveX object errors increases from there – maybe there is a DLL problem or the ever present threat of a malware infection. A wise way to begin is with basic computer maintenance. Now is the time to download Microsoft Windows updates and to track down patches for the individual programs on your PC. Because a lot of runtime errors arise from incompatibility between applications or within your system, getting updates is generally smart. To get the most recent DLLs and object instructions, you need to update routinely.
If you are still getting the error message even following the updates, then dust off your anti-virus utility and give your computer a complete once over for malware. Once you are certain your PC is malware free, run best registry repair software in order to register DLLs, fix ActiveX problems, and erase irrelevant junk that sticks to the registry. Since lots of computer troubles come from registry corruption, having a registry cleaner in your PC care toolbox is a good preventative step. I recommend running the complimentary diagnostic scan that many registry cleaner programs give before you commit to a purchase so that you can be sure that the program will solve your specific challenge. (Be certain the specific registry cleaner can aid you before you purchase it!)
As you can guess, it can occure that doing all the trouble shooting steps still doesn’t solve the runtime error 80010108. Yet there is always that worst case scenario. If your error is coming from a flawed bit of programming, then someone who can edit code will need to be practically intimate with your particular operating system. Don’t take it to heart! Many programmers run into the runtime error 80010108 as they write code and fixing it is generally agony for them, also. Here’s wishing your error is triggered by the easiest mistake: Is the application that supports your “disconnected” object running?
Mail this postPopularity: 1% [?]