> 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?
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.