Legacy VB6 DCOM Connectivity

Question

0.00/5 (No votes)

See more:

I am debugging connectivity with a legacy vb6 activex dcom application using windows 7 pro 32 bit as the client.

The client has been running under 2000 and xp with no issues for years, and am now attempting to use windows 7 pro before replacing our remaining xp pro machines. Client and server run locally on windows 7 pro, but when pointed to a windows 2003 server the activex exe launches on the server, hangs for around 30 secs and then appears to time out(callbacks are attempted but I believe are being denied).. Nothing in the windows logs.. This appears to be some sort of permissions/security issue I suspect.

Is there a way to set logging levels for dcom under windows 7 ? Or, if you if you have other suggestions I would greatly appreciate, I need to get this solved quickly..

Thanks in advance..

Posted 29-Sep-11 5:08am

adagio62

Updated 29-Sep-11 5:11am

RaisKazi

v2

Add a Solution

Comments

Mehdi Gholam 29-Sep-11 11:40am

Are you on the same domain?
Have you checked the firewall settings on your Win7?

adagio62 29-Sep-11 13:42pm

Yes same domain.. The firewall is turned off on the client, and same dcom permission are assigned from a working xp client.

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

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

E.F. Nijboer · Answer 1 · 2011-09-29T09:58:00

Solution 2

You might need to add a manifest to make it compatible with windows 7. Check out this link:

http://msdn.microsoft.com/en-us/library/bb756929.aspx[^]

Be aware that windows 8 will have no vb6 anymore and this is only more like a hack than an actual patch. But... hopefully this will work out and get it to work for now.

Good luck!

Posted 29-Sep-11 9:58am

E.F. Nijboer

Comments

adagio62 29-Sep-11 18:35pm

Thank You E.F. Would have a sample xml you think would do the job ?

E.F. Nijboer 30-Sep-11 8:23am

Check these links for more info:
http://stackoverflow.com/questions/5755426/how-do-i-create-a-manifest-file-in-visual-basic-6-0
http://csi-windows.com/toolkit/manifest-template

adagio62 30-Sep-11 9:14am

Ok.. Thanks I'll give it a try.

adagio62 30-Sep-11 17:43pm

No success thus far.. Is it possible to set logging levels to see what is actual happening? I did run a trace using Microsoft network monitor but I do not have the expertise to interpret.. Is it possible to take another approach ? I would like to be able to confirm exactly why the the server in unable to talk to the client, just not sure on how to go about it.

E.F. Nijboer 1-Oct-11 13:03pm

I read the following that looks plausible. It's about adding it to the trusted sites.
http://www.sevenforums.com/system-security/189232-connectivity-legacy-vb6-dcom-client-server-application.html

Maybe the following link is also helpful.
http://support.microsoft.com/kb/241896

And there is also something on this on stackoverflow.
http://stackoverflow.com/questions/4244078/running-activex-dll-fromvb6-under-windows-7

adagio62 1-Oct-11 13:36pm

Thank you.. I will give those a try..