Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / Visual Studio.NET / IDE / June 2006

Tip: Looking for answers? Try searching our database.

Debugger Users - Access is denied

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
CitiTech - 23 May 2006 21:13 GMT
I have just tightened the security in our domain so not all users are in the
Administrator Role.  I have a user that uses VS.NET 2003 and his projects
build, and he can run the EXE but if he chooses RUN from inside the IDE,
after it compiles, he gets the following:

Error while trying to run project: Unable to start debugging.
Access is denied. Verify that you are an administrator or a member of the
'Debugger Users' group on the machine you are trying to debug.  After being
added to the 'Debugger Users' group, you must log off and log back on for
the settings to apply.

I have several developers that are all setup the same exact way but just
this one has the problem.  The others are fine.  Yes, he is a member of the
Debugger User group.
"Gary Chang[MSFT]" - 24 May 2006 07:16 GMT
Hi,

>I have several developers that are all setup the same exact way
>but just this one has the problem.  The others are fine.  Yes, he
>is a member of the Debugger User group.

Another thing you can check is whether the 'Machine Debugger Manager'
service has been started properly or not in that machine.

If the Machine Debugger Manager service works well in that machine, I
suggest you can uninstall the mdm service and re-install it for a try:
------
instsrv mdm remove
instsrv mdm "c:\program files\common files\microsoft
shared\vs7debug\mdm.exe"

Thanks!

Best regards,

Gary Chang
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
CitiTech - 25 May 2006 16:48 GMT
The service is running ok.  I was going to try to un-install and re-install
as suggested but the file "instsrv" is not found on this computer.  I don't
think this would make a difference because on this same computer, another
user with the same exact access can log in and it works.  It is just this
one user login that has this problem.

The only idea I have not tried is to delete the user and re-create.  The
problem I have with this is his Exchange Email account is tied to this logon
and I am not sure what this will do to me.

Any other ideas?
Michael Viking - 25 May 2006 19:37 GMT
Just a small thought:  Perhaps you could enable some auditing of object
access failures and that would lead you to what particular right this person
is missing or something.  It might provide some clues anyway.

-Michael Viking

> The service is running ok.  I was going to try to un-install and re-install
> as suggested but the file "instsrv" is not found on this computer.  I don't
[quoted text clipped - 7 lines]
>
> Any other ideas?
CitiTech - 25 May 2006 22:42 GMT
Great idea!  I did this and here is what I found, he was getting a SYSTEM
event error as follows:

The application-specific permission settings do not grant Local Activation
permission for the COM Server application with CLSID
{2C44C9B1-CB5D-433F-B94C-A0CEAAE8CC20}
to the user CITITECH\StevenL SID (S-1-5.......).  This security permission
can be modified using the Component Services administrative tool.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

I followed the instructions on the link and found that the DCOM Config for
"Machine Debug Manager" did not have the security group "Debugger User" so I
added it.  This did not help!

There was another error exactly like this but for a diff CLSID.  When I
tried to follow it to the "MDM Runtime JIT Server Registrar" in DCOM Config,
it was not there.  So I searched for anything JIT and all I found was this:
"Just-In-Time Debugging Handler and CLR Remote Host".  The CLSID is diff but
the registry and the DCOM Config both point to the same EXE.  Needless to
say, the security for this already included the Debugger Users group.

This use has had no change and I still neep help with this.
"Gary Chang[MSFT]" - 26 May 2006 07:54 GMT
Hi,

>I followed the instructions on the link and found that the DCOM
>Config for "Machine Debug Manager" did not have the security
>group "Debugger User" so I added it.  This did not help!

After you did this, have you found any other system error while you cannot
launch the VS2003's debugger?

It sounds like an account configuration issue. I am afraid I am not
experienced in this field.

How about comparing this account's access configuration with another one
which works you mentioned?

Thanks!

Best regards,

Gary Chang
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
"Gary Chang[MSFT]" - 26 May 2006 08:38 GMT
Hi,

I think you can also remove and re-add that account in the Debugger User
group.

Another workaround is add that user account into the Activation and Access
permissions individually.

Both of the above workaround may need reboot.

Thanks!

Best regards,

Gary Chang
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
CitiTech - 26 May 2006 16:28 GMT
I got it.  In the DCOM Config, the previous document only mentioned "Launch
and Activate" security.  I noticed the next item, "Access" and went into it.
Debugger Users was not in there so I added it and now he works.

Thanks for all the help!
"Gary Chang[MSFT]" - 29 May 2006 06:53 GMT
Bingo!

Have a nice day!

Best regards,

Gary Chang
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
CitiTech - 05 Jun 2006 16:20 GMT
Jumped the gun on that one!

After the Domain Controler and computer were rebooted, no one can debug now!
Not even the administrators!

I will try to put all setting back the way they were but will not continue
down this path any longer since there are some obvious problems.

> Bingo!
>
[quoted text clipped - 10 lines]
> This posting is provided "AS IS" with no warranties, and confers no
> rights.

Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.