In the windows service to call the COM interface function error

Question

1.00/5 (1 vote)

See more:

My development tool is VS2010, development language is C#, and operating system is WINDOWS7 64-bit. I need to call interface functions of COM service (OPC DA Automation Wrapper 2.02) in my windows service application, while the COM service and windows service are on the same computer. It turns out that calling some of the COM interface functions successes, but some have errors(System.Runtime.InteropServices.COMException was caught).

errors is:
System.Runtime.InteropServices.COMException was caught
Message=Exception from HRESULT: 0xC0040007
Source=GWOPC.NET
ErrorCode=-1073479673

I created a normal application(not a windows service program) to call the COM service, there was no problem. So I think the problem is due to using of windows service, and I suspect are some permission setting problem of windows service. Then I tried these steps:
1. I log in my computer using an administrator account.
2. In the windows service properties -> Log On tab, select "Local System account" by default.
3. Run my windows service application to call COM interface functions, error exists.
4. In the windows service properties -> Log On tab, select "This Account" and enter a user name and password (the user is an administrator).
5. Run my windows service application to call COM interface functions, the error still exists.

Same code, the general application（e.g. EXE） call, there will be no errors. Only in the service call, will have errors.

Posted 22-Jun-11 23:53pm

szbc99

Updated 24-Jun-11 15:11pm

v7

Add a Solution

Comments

JV9999 23-Jun-11 7:07am

I would rephrase your question, because after reading it 10 times I still don't get it what you want from us...

Richard MacCutchan 24-Jun-11 4:59am

What is the exception you receive? without that information it will be quite difficult to figure out your problem.

szbc99 24-Jun-11 6:12am

errors is:
System.Runtime.InteropServices.COMException was caught
Message=Exception from HRESULT: 0xC0040007
Source=GWOPC.NET
ErrorCode=-1073479673

Richard MacCutchan 24-Jun-11 8:55am

http://msdn.microsoft.com/en-us/library/dd542643(VS.85).aspx

CO_E_INIT_SHARED_ALLOCATOR
0x80004007
Get shared memory allocator failure

szbc99 24-Jun-11 21:10pm

Same code, the general application（e.g. EXE） call, there will be no errors. Only in the service call, will have errors.

Richard MacCutchan 25-Jun-11 4:03am

It looks like you are trying to allocate some shared memory and that is failing.

szbc99 25-Jun-11 6:18am

how to do?

Richard MacCutchan 25-Jun-11 6:45am

I have no idea; it's your code so you will need to run it through the debugger.

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)

Pete O'Hanlon · Accepted Answer · 2011-06-23T03:03:00

Solution 1

It sounds like you are attempting to call some COM functionality from within a windows service. By default, the service will run in a highly locked down account - what you need to do is create an account (with a strong password), for the service to run in. Give it appropriate privileges (such as access the registry), and it should be able to work.

Posted 23-Jun-11 3:03am

Pete O'Hanlon

Comments

fjdiewornncalwe 23-Jun-11 10:24am

Agreed, but as an addition: If the code is capable of executing some of the COM methods, but not others, then it could be that his call arguments are not being formatted correctly in the calls. (Assuming that the COM methods work at all).