Comments on: The class is configured to run as a security id different from the caller http://www.suver.com/blog/2003/06/22/the-class-is-configured-to-run-as-a-security-id-different-from-the-caller/ Fri, 29 Aug 2008 18:59:04 +0000 http://wordpress.org/?v=2.6.1 By: Homer http://www.suver.com/blog/2003/06/22/the-class-is-configured-to-run-as-a-security-id-different-from-the-caller/#comment-256780 Homer Mon, 28 Apr 2008 21:29:15 +0000 http://www.suver.com/blog/?p=101#comment-256780 I had the same problem. I was trying to run a COM+ component in debug but the DLL was already set up in a package in Componenet Services. I just removed the component from the package and now debugging works fine. I had the same problem. I was trying to run a COM+ component in debug but the DLL was already set up in a package in Componenet Services. I just removed the component from the package and now debugging works fine.

]]> By: Samar http://www.suver.com/blog/2003/06/22/the-class-is-configured-to-run-as-a-security-id-different-from-the-caller/#comment-226506 Samar Thu, 03 Jan 2008 14:22:52 +0000 http://www.suver.com/blog/?p=101#comment-226506 Thanks Jamie, your suggestion solved my problem, I was working on the VM and not accessing the application remotely. Thanks Jamie, your suggestion solved my problem, I was working on the VM and not accessing the application remotely.

]]> By: Jamie http://www.suver.com/blog/2003/06/22/the-class-is-configured-to-run-as-a-security-id-different-from-the-caller/#comment-128515 Jamie Tue, 06 Feb 2007 16:45:19 +0000 http://www.suver.com/blog/?p=101#comment-128515 I had this problem and temporaily fixed it by changing the identity of the package my dll was in to "System Account: Interactive User - The current logged on user", rather than the application user it had been set up as. Hope this fixes someones problem somewhere! I had this problem and temporaily fixed it by changing the identity of the package my dll was in to “System Account: Interactive User - The current logged on user”, rather than the application user it had been set up as.

Hope this fixes someones problem somewhere!

]]> By: solai http://www.suver.com/blog/2003/06/22/the-class-is-configured-to-run-as-a-security-id-different-from-the-caller/#comment-99999 solai Wed, 10 May 2006 18:16:21 +0000 http://www.suver.com/blog/?p=101#comment-99999 hi i have gone thro the suggestions which the previous friends gave but i am unable to work iwht debugger and its throwin the same error box becoz i have done my project in Admin login of XP plz help me regarding this hi
i have gone thro the suggestions which the previous friends gave
but i am unable to work iwht debugger and its throwin the same error box
becoz i have done my project in Admin login of XP
plz help me regarding this

]]> By: nate http://www.suver.com/blog/2003/06/22/the-class-is-configured-to-run-as-a-security-id-different-from-the-caller/#comment-203 nate Fri, 16 Jan 2004 16:41:33 +0000 http://www.suver.com/blog/?p=101#comment-203 Thanks for the advice. I'll try that next time the problem creeps up. Thanks for the advice. I’ll try that next time the problem creeps up.

]]> By: Mike http://www.suver.com/blog/2003/06/22/the-class-is-configured-to-run-as-a-security-id-different-from-the-caller/#comment-200 Mike Thu, 15 Jan 2004 17:20:58 +0000 http://www.suver.com/blog/?p=101#comment-200 I had the same problem and here's the easiest answer: when you remote access your workstation, run this from the start button: "mstsc /console" and then log in as normal. Then, when you start VB remotely, all will be well. You need to have a console session running, and if you reboot and remote access your workstation, you won't ever get one started. COM services packages run in the context of the console. I had the same problem and here’s the easiest answer: when you remote access your workstation, run this from the start button: “mstsc /console” and then log in as normal. Then, when you start VB remotely, all will be well. You need to have a console session running, and if you reboot and remote access your workstation, you won’t ever get one started. COM services packages run in the context of the console.

]]> By: jenny http://www.suver.com/blog/2003/06/22/the-class-is-configured-to-run-as-a-security-id-different-from-the-caller/#comment-164 jenny Sun, 30 Nov 2003 16:46:08 +0000 http://www.suver.com/blog/?p=101#comment-164 i know that this is an old post, but i thought you might be interested to know that there is a much easier fix for this problem. log out of the computer and back in as another user, preferably as an administrator though im not certain it makes a difference. run your dll and run something that accesses it to make sure that all of the registry entries related to debugging are cleared and replaced with settings for the new user. when you log back in as yourself, you should be able to debug as normal. if you check the event log you may see some entries, as well, related to unsuccessful unloading of the registry that help explain why this works.<br /> <br /> thanks -- your post helped me get on the right track! i know that this is an old post, but i thought you might be interested to know that there is a much easier fix for this problem. log out of the computer and back in as another user, preferably as an administrator though im not certain it makes a difference. run your dll and run something that accesses it to make sure that all of the registry entries related to debugging are cleared and replaced with settings for the new user. when you log back in as yourself, you should be able to debug as normal. if you check the event log you may see some entries, as well, related to unsuccessful unloading of the registry that help explain why this works.

thanks — your post helped me get on the right track!

]]> By: Nate Suver http://www.suver.com/blog/2003/06/22/the-class-is-configured-to-run-as-a-security-id-different-from-the-caller/#comment-118 Nate Suver Wed, 16 Jul 2003 18:27:33 +0000 http://www.suver.com/blog/?p=101#comment-118 This problem is particularly nasty, no doubt. Want to know what I found out? If I leave work, and reboot my computer before I leave, I get the problem (consistently). If I DON'T reboot my computer before I leave, and at some point before my last reboot I ran the VB debugger logged in directly to my workstation, I won't get the problem at home. It's the weirdest, stupidist, most annoying thing ever. Just never reboot your computer, and you won't ever have a problem. ha. This problem is particularly nasty, no doubt. Want to know what I found out? If I leave work, and reboot my computer before I leave, I get the problem (consistently). If I DON’T reboot my computer before I leave, and at some point before my last reboot I ran the VB debugger logged in directly to my workstation, I won’t get the problem at home. It’s the weirdest, stupidist, most annoying thing ever. Just never reboot your computer, and you won’t ever have a problem. ha.

]]> By: Dan http://www.suver.com/blog/2003/06/22/the-class-is-configured-to-run-as-a-security-id-different-from-the-caller/#comment-117 Dan Wed, 16 Jul 2003 13:49:06 +0000 http://www.suver.com/blog/?p=101#comment-117 I had the same problem you had and the same solution. Thanks I was totaly stumped. Now when I attempt to debug the web app athat calls my COM object gets "Permission denied". It works when I am not trying to debug. Whats up with that? I had the same problem you had and the same solution. Thanks I was totaly stumped. Now when I attempt to debug the web app athat calls my COM object gets “Permission denied”. It works when I am not trying to debug. Whats up with that?

]]>