naveenkohli,
I can't find this "depends" tool....it's not in the IDE or my start menu for vs.net and I'm pretty sure I did a full install when I installed vs.net....how do I get to this tool?
Main Topics
Browse All TopicsHi all,
I have a COM object I'm trying to use in an asp.net application.
Not sure what the COM is written in, buy it belongs to an asp based CRM app, Sage CRM.
According to tutorials that I have found all I need to do to be able to make this work in .Net is:
1. register the dll on the system using regsvr32
2. add a reference to the dll using vs.net which would then create interop assembly needed to use the objects in the COM
or
use tlbimp.exe from command line to create the interop
...neither seems to work...I get the error message I posted in the Q both ways...which, from what I could find, says that the dll is not registered or cannot be found (which I know it is)...
Any ideas?
Thanks!
Sam
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
naveenkohli,
all dependencies accounted for...
eyal_mt,
thanks for that tip...I hadn't come across that requirement before in my research....
just as a test to make sure...I gave aspnet account full control of my entire c:\ drive...still no luck
...tried moving it into the \bin folder of the app...no luck
This dll belongs to a ASP 3.0 application...is it possible that it is just simply incompatible with .Net ?
I wouldn't think so...
Incompatibility is unlikely to generate this particualr error - but just in case try adding AspCompat="true" to your Page directive - this should make you ASP.NET almost identical to the way ASP is working:
http://msdn.microsoft.com/
Hi there,
I found another solution and it did work for me. Maybe you can try it as well.
Checkout the registry key with this class ID in your registry under HKEY_CLASSES_ROOT\CLSID.
If you have a PC, where your application works, then check there first and compare with the other PC where it doesn't work. In my case the registry key was missing on the PC where it threw the error. Then just copy over from one registry to the other with export and import.
Usually in this key there should be a folder called InprocServer32 and this key has a Default value, that points to a dll somewhere on your PC. Set this value to the dll on the imported machine correctly and then try to run your application again. Worked for me and I was looking quite long for any solution.
Best, M.
That's an interesting solution, MartinLangrock. I was going to try that then found that the registry keys existed in both places. What ended up being my solution was allowing the "Users" group read-access to the folder where the .dll's the web site was trying to access were located. I didn't even know that could have been an option (as in why didn't that group have read access in the first place?), but at a customer site, anything goes!!
Business Accounts
Answer for Membership
by: naveenkohliPosted on 2005-12-06 at 10:07:51ID: 15429784
Does the COM object depend on other third party DLLs?
I am assuming your regsvr32 failed..
Here is what I will do....
In VS tools there is a utilility called "depends". Open the COM dll in that utility and it will tell you want all dependecies it has. Anything that shows up with RED will indicate that the referenced binary could not be found or does not exists.