Create Instance failed: 0x80080005 with Windows 7

[VMugnier]

Hello,

We have our OPC server and we use it without any problem under Windows XP. But with Windows 7, it is impossible to connect remotly to it, we always have this message (see subject). In local, no problem.

We have the same installation as with Windows XP with the same OPC, DCOMCFNG config, same user...

When we try to connect to our server with Advosol OPC Security Analyzer, it says that "The user must have DCOM server launch rights."

What is different between Windows XP and 7 about that ?

thanks

[Fred_Loveless]

What OPC Server are you using?
Are you runing as a service or on the desktop?
What are your UAC and Windows Defender settings?

These are good questiosn to start with, we may have more once we get answers to these.

Fred Loveless
Kepware Technologies

[Randy]

Windows 7 always has User Access Control enabled (UAC).
This will create problems for applications that try to update the registry on start.

[VMugnier]

Thanks for your answer.

We use our own OPC server developped with the Wintech OPC source code kit.
It is not running as a service.
The application server is already running when I try to connect to it.

I've just done a new test with the following parameters :
- Windows defender disabled.
- UAC turned to "never notify"
I still have the 0x80080005 error and the message "The user must have DCOM server launch rights."

Here is the whole diagnostic of the OPC Security Analyzer :

[Fred_Loveless]

When you compile your programs have you created a security manifest? Try running the server as and Administrator, then try running the server and client as administrators and see what happens. this is a WAG but if DCOM is set the same the next issue is going to be application runtime privilages.

Fred Loveless
Kepware Technologies

[VMugnier]

Well, about the manifest, I have doubt :
In our VC++2005 settings we have :
For Linker / Manifest File :
- generate a manifest : no
- manifest file : Kronos.exe.manifest
For Manifest tool , Input and Output :
- embed manifest : no
- Output manifest file : Kronos.exe.generated.manifest

In the result directory, I have 2 manifests, Kronos.exe.manifest and Kronos.exe.generated.manifest.

[VMugnier]

I've also done the test running the server and the client as administrator or not. I've install another Windows 7 PC to do it (for our previous tests, OPC clients are on XP computer).

I've seen no differences between each cases, always the same error and diagnose :

[VMugnier]

I've just done a new test from my XP PC with a more recent version of OPC Security Analyzer... maybe more info...

[VMugnier]

A little step in my problem : I've correctly declared our server in registry. I've also tried another server declared as local server like ours, and not as service, to compare results.

Now differences in the diagnose of OPC Security Analyzer are :

for my reference server :

[VMugnier]

Finally a first result !
I've managed to connect to our server after having modify its specifing DCOM settings as following :
- In dcomcnfg, I've openned the Properties of my server in Console Root/Component Services/Computers/My Computer/DCOM Config
- In the identity tab, I've change the user account from "the lauching user" to "The interactive user".

With this additionnal settings, I've managed to connect remotly to our server running on Windows 7.

Any idea why it doesn't work with "The launching user" while whith a demo server or on Windows XP it works fine ?

Anyway, thanks for your informations.