Debug Assertion Failed - 0x80004015 The class is configured to run as a security id different from the caller

Question

3.00/5 (1 vote)

See more:

The debug-win32 configurations of my ATL exe application getting crashed by "Debug asertion failed". The same ATL exe project of release configuration working fine.While debugging the HRESULT object returned as error"0x80004015 The class is configured to run as a security id different from the caller".But in release configuration also the same result returned,but it works fine. The working environment is Windows Server 2008 64 bit OS and Visual Studio 2008 solution. Any idea regarding this?

Posted 16-Nov-11 2:46am

JS 2008

Updated 16-Nov-11 2:51am

v2

Add a Solution

Comments

Albert Holguin 17-Jan-12 11:28am

FYI... Some assert() functions are setup to only trigger during debug execution, not during release execution, since they are meant for developers and not for the users. So even though you don't get an explicit problem statement in the release executable, the problem may still be there.

3 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)

JackDingler · Answer 1 · 2011-11-16T03:26:00

Solution 1

When running in the Debugger, your application inherits the security settings for the Dev Studio environment. When running standalone, it gets the security settings of the user, or those specified at startup.

Set Dev Studio to 'Run as Administrator' and see if this changes things.

Posted 16-Nov-11 3:26am

JackDingler

Comments

JS 2008 16-Nov-11 23:40pm

Thanks JackDingler for the solution.
Eventhough I have Set Dev Studio as 'Run as Administrator' also the error happend.

ronald62 · Answer 2 · 2012-01-08T23:16:00

JS,

I've the same issue. And I think that the reason is a change in the registry settings. If I install an old version of our product it works. Even if I build the latest version. But when I deinstall and install the lastest version of our product the the same option doesn't work.

I'm currently looking for the differences in the setup, but haven't found it yet.

Did you solve your issue?

ronald62 · Answer 3 · 2012-01-17T01:25:00

Solution 3

The solution for my problem was to disable the DEP in windows for my program.

I hope this helps.

Posted 17-Jan-12 1:25am

ronald62