Security error

[chiph]

I was trying to run an ActiveX EXE under Windows 2000 (just double-clicking on it to get it to register), and I got the following error:

System error &H80004015(-2147467243). The class is configured to run as a security ID different from the caller.

I've checked the MS knowledgebase (

http://support.microsoft.com/support/kb/articles/Q228/4/87.asp)

and it just talks about running inside the IDE (which I'm not). I did check the registry key that it suggested, and it was OK.

Does anyone have any experience with this?

Thanks.
Chip H.

 

[jmarler]

chip,
I don't have a lot of experience with 2000 (yet, but I'm working on it), but is there something similar to DCOMCNFG that you need to run to establish the permissions for each class on ActiveX Exes? I would probably look specifically at who has launching permission. Hope that helps you out . . . If not, let me know . . . - Jeff Marler

http://www.JeffMarler.com

(please note, that the page is under construction)

 

[chiph]

Hi Jeff -

I've already run DCOMCNFG and I suspect it made things worse.

We did find a workaround -- we added the DLL to COM+, and was able to set permissions on it in there. I'm not happy with this solution, as I feel it should have run OK just by registering it (like any other A-X dll). But it seems to work (yuck).

Chip H.

 

[jmarler]

Chip, when you were running this, the ActiveX exe was on a windows 200 machine? Workstation or Server? And what OS was the calling client using? I'm just trying to better understand your problem. - Jeff Marler B-)

 

[chiph]

Jeff -
Sorry it's taken me so long to get back to you (been out sick).

This happened on a Win2k Server (not "Advanced&quot. I was using Terminal Client to telnet-in and register my component. The component is not a DCOM component, per se, but is really an ordinary ActiveX EXE. I was using DCOMCNFG in an attempt to find out what the security permissions were.

The irritating part is that the error pops up during the register process, not during instantiation. As long as you have administrator priveledges on the machine (and I do), you should be able to register components.

Chip H.

 

[jmarler]

You mean that Logged in as Admin, you get an error when registering the ActiveX exe? Does the error happen when you are registering ActiveX exe directly on the machine and not through Terminal Server/Terminal Client? - Jeff Marler B-)

 

[chiph]

Jeff -

Yes, the problem ocurred on the console, as well as through terminal server client.

I spent some time on the phone with Microsoft ($245 later...), and they had me run though dcomcnfg.

Basically, I added the Interactive user to the launch and access permissions. Then removed it. And it worked afterwards. So basically, something was funked up in Windows, and setting security, then clearing it, solved the problem.

I'm not happy about the solution. And I'm not real happy about how security works in COM, either. One thing that I discovered was that if the launch/access permissions block is empty, anyone can use the component. Once you've added someone, they get their assigned permissions and everyone else is locked out. Bizarre.

In any case, thanks for your help.

Chip H.