How to check what program libraries are trying to opened a .exe program ???
Hi EXPERTS!
I have made my VB6 application – standard EXE which is referenced to the other program libraries – some are public, some are made from me. In my computer the application is working fine. Now I have problem that when I start the application on deployment computers I get error:
Run-time error 403
Class does not support automation or does not support expected interface.
Error is getting in start of application and I do not see any of my programming screen at all.
It is clear that problem is in a library which is missed in deploy computer, but can I have some options to get some details info for error like CLSID 28762836823 couldn’t be find or even better to get name of library which make problems ? May be with some hacking tool I can open application and review what recourse try to access and to find where is fail ???
I’m VERY experienced with this area as from 10 years I works with VB6 and ActiveX components included to make the installation programs. But now situation is far more complex and application is not done by me, I have all it code but couldn’t deal with it. Please help!
I have made my VB6 application – standard EXE which is referenced to the other program libraries – some are public, some are made from me. In my computer the application is working fine. Now I have problem that when I start the application on deployment computers I get error:
Run-time error 403
Class does not support automation or does not support expected interface.
Error is getting in start of application and I do not see any of my programming screen at all.
It is clear that problem is in a library which is missed in deploy computer, but can I have some options to get some details info for error like CLSID 28762836823 couldn’t be find or even better to get name of library which make problems ? May be with some hacking tool I can open application and review what recourse try to access and to find where is fail ???
I’m VERY experienced with this area as from 10 years I works with VB6 and ActiveX components included to make the installation programs. But now situation is far more complex and application is not done by me, I have all it code but couldn’t deal with it. Please help!
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
10x for help ! Due to your offer I made some tests test and I find DLL which actually do the problems !
Thanks again!!!
Thanks again!!!
Glad it helped!
ASKER
Dear kbirecki
First – THANKS AGAIN for your help !!! As I say I have created on my own about 20 ActiveX and OCX controls, separated from this in every my project I have usually about 10-15 additional libraries which I use, so I’m very deep in practice of using ActiveX . But this time I lose almost 24 hours before I get solution, due to you offer.
I want to share what was problem here.
Problems was with one of created by me with Vb6 ActiveX component. While I detect which one is due to you offer I understand that problem is not in my code, but somewhere in binary CLSID. So I do this – copy this DLL project in the new VB project, change his name and compile this new. While do compile I get this error message:
Programmatic ID string too long 'item'. The Programmatic ID must be 39 characters or less.
Then I reduce the name of project ID , compile again, reference this new ActiveX in my project and was able to start application! What is very strange is that the problem ActiveX was created and compiled in Win XP without problem, but now it is compiled in Win7.
In fact, problem was in errors in CLSID for one of the class, but in binary level and without any warring ..very hard to detect what is going on!
First – THANKS AGAIN for your help !!! As I say I have created on my own about 20 ActiveX and OCX controls, separated from this in every my project I have usually about 10-15 additional libraries which I use, so I’m very deep in practice of using ActiveX . But this time I lose almost 24 hours before I get solution, due to you offer.
I want to share what was problem here.
Problems was with one of created by me with Vb6 ActiveX component. While I detect which one is due to you offer I understand that problem is not in my code, but somewhere in binary CLSID. So I do this – copy this DLL project in the new VB project, change his name and compile this new. While do compile I get this error message:
Programmatic ID string too long 'item'. The Programmatic ID must be 39 characters or less.
Then I reduce the name of project ID , compile again, reference this new ActiveX in my project and was able to start application! What is very strange is that the problem ActiveX was created and compiled in Win XP without problem, but now it is compiled in Win7.
In fact, problem was in errors in CLSID for one of the class, but in binary level and without any warring ..very hard to detect what is going on!
Great program:
http://technet.microsoft.com/en-us/sysinternals/bb896653