Since installing service pack 1 on my local version of Windows 2003 server I have been getting problems with the Machine Debug Manager (MDM.EXE). When the debug tries to run I get the error:
"The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {0C0A3666-30C9-11D0-8F20-00805F2CD064} to the user NT AUTHORITY\NETWORK SERVICE SID (S-1-5-20). This security permission can be modified using the Component Services administrative tool."
Where 0C0A3666-30C9-11D0-8F20-00805F2CD064 is the MDM.EXE installed by Visual Studio 2003.
Microsoft's answer seems to be to modify the security permissions, giving the following additional users launch and access permissions.
Interactive
IWAM_<ComputerName>
in addition to Administrators, debugger_users and system already given access by default.
I do this via the component library. I also added MDM.EXE to the exceptions list for the firewall with no problems.
However, I then get the following on boot up.
"The application-specific access security descriptor for the COM Server application C:\Program Files\Common Files\Microsoft Shared\VS7Debug\mdm.exe is invalid. It contains Access Control Entries with permissions that are
invalid. The requested action was therefore not performed. The application set this security permission programmatically; to modify this security permission contact the application vendor."
Iv'e tried regestering the MDM.exe, but this just puts the permissions back to Administrators, debugger_users and system only. It gets rid of the later error, but I then get the original back
Can anyone advise me how to set this up. Basically, most of the time I'm debugging ASP (server) and javascript (client) code on my laptop (to test before sending live), but occassionally have to go into Visual Studio to edit VB.Net code. I therefore have websites running locally but I don't really need DCOM or remote access of machines.
Thanks
Andy
"The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {0C0A3666-30C9-11D0-8F20-00805F2CD064} to the user NT AUTHORITY\NETWORK SERVICE SID (S-1-5-20). This security permission can be modified using the Component Services administrative tool."
Where 0C0A3666-30C9-11D0-8F20-00805F2CD064 is the MDM.EXE installed by Visual Studio 2003.
Microsoft's answer seems to be to modify the security permissions, giving the following additional users launch and access permissions.
Interactive
IWAM_<ComputerName>
in addition to Administrators, debugger_users and system already given access by default.
I do this via the component library. I also added MDM.EXE to the exceptions list for the firewall with no problems.
However, I then get the following on boot up.
"The application-specific access security descriptor for the COM Server application C:\Program Files\Common Files\Microsoft Shared\VS7Debug\mdm.exe is invalid. It contains Access Control Entries with permissions that are
invalid. The requested action was therefore not performed. The application set this security permission programmatically; to modify this security permission contact the application vendor."
Iv'e tried regestering the MDM.exe, but this just puts the permissions back to Administrators, debugger_users and system only. It gets rid of the later error, but I then get the original back
Can anyone advise me how to set this up. Basically, most of the time I'm debugging ASP (server) and javascript (client) code on my laptop (to test before sending live), but occassionally have to go into Visual Studio to edit VB.Net code. I therefore have websites running locally but I don't really need DCOM or remote access of machines.
Thanks
Andy
