CreateProcess + ADODB, where is the catch?

Question

0.00/5 (No votes)

See more:

Hello great minds! Happy new year to all!

Once again I come to you for help. I was asked to make some changes to an existing vb6 set a apps where the main app, triggers the other ones in sequence and depending on each previous app results, and for this purpose, each .exe is invoked using the CreateProcess API.

Our new "child" .exes are failing to open connections to any of our DB servers; we get an "Unknown error" message from the Provider. We have successfully tested our connection strings, objects, etc. Even the child .exe(s) works perfectly when executed by themselves or when triggered by the SHELL command.

Is there any parameter we should be passing to the CreateProcess command to allow children processes to open DB connections? where is the catch? What´s is the difference between CreateProcess and Shell commands?

Thank you all very much for your guidance and may this new year bring you many opportunities for success!

Alex.

Posted 5-Jan-11 3:37am

alexvw

Add a Solution

2 solutions

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)

Manfred Rudolf Bihy · Accepted Answer · 2011-01-05T04:30:00

Is your main app running under the same user account as your "Child".exes? Please give us an example of the connection strings you are using for your database.
Is your main app run from a scheduled job or a windows service? If yes with what account.
With some accounts (for instance "Local System") it will not be possible to make a network connection to your database server, if said server isn't on the same machine.

Best Regards,
Manfred

alexvw · Accepted Answer · 2011-01-16T13:12:00

Hello Manfred,

Thank you for you contribution; connection strings are standard, and the are 100% operational "child .exe(s) works perfectly when executed by themselves or when triggered by the SHELL command."

The Main app is run manually by the user who not only has full administrative privileges on the machine, but also is a Domain Administrator. Child .exe(s) are run with the current user account. Anyhow, I asked the management for the reason of this architecture, and since they could offer a logical answer, I merged the two offending child .exe(s) into the main app, thus solving the problem.

Once again, thank you for your contribution.

CreateProcess + ADODB, where is the catch?

2 solutions

Solution 1

Solution 2

Add your solution here

Preview 0