RE: Debugging a remote service fails
- From: dwaine <dwaine@xxxxxxxxxxxxx>
- Date: Tue, 1 Apr 2008 11:33:03 -0700
Jeffrey,
I appreciate the effort, but I must stop dead in my tracks and point out ....
REMOTE DCOM default access and launch perms at Machine Level includes
EVERYONE??!!
Isn't that a little dangerous? If that's what's required to debug on a
server (even DEV or TEST servers) I'm not interested.
""Jeffrey Tan[MSFT]"" wrote:
Hi Dwaine,.
Sorry for the late response. I will continue to help you on this issue.
Micosoft MSDN newsgroup support is providing replies in 24 hours excluding
the weekend. Since it is weekend, you did not get follow-up reply till now.
Thanks for your understanding.
The link below contains more details of MSDN subscription FAQ:
"MSDN Subscriptions FAQ"
http://msdn2.microsoft.com/en-us/subscriptions/aa948864.aspx
As I know WinXP SP2 Windows Firewall is turned on by default, do you turn
it off yourself? Have you tried to add "ANONYMOUS LOGON" "Remote Access"
permission in the dcomcnfg? As "Configure DCOM on the computer that is
running Visual Studio .NET" section described in the KB below:
http://support.microsoft.com/default.aspx?scid=kb%3BEN-US%3B833977
Also, I would recommend you to try one more setting related to dcomcnfg.
You can just go to the "Machine Debug Manager" node through dcomcnfg and
then check that the following accounts should be added "remote" permissions
in both the default access and default launch permissions :
SYSTEM
INTERACTIVE
Everyone
Administrators
Then you can just change the identity from system to interactive in the
properties of Machine Debug Manager. This you need to do both on the server
and the client and then you can reboot both the boxes and then try to
debug. I hope the error which we were getting right now should go away with
this. Either we should be able to do the debugging then or get a new error
by this.
Additionally, I will contact VS debugger team to collaborate on your issue.
Thanks.
Best regards,
Jeffrey Tan
Microsoft Online Community Support
=========================================
Delighting our customers is our #1 priority. We welcome your comments and
suggestions about how we can improve the support we provide to you. Please
feel free to let my manager know what you think of the level of service
provided. You can send feedback directly to my manager at:
msdnmg@xxxxxxxxxxxxxx
This posting is provided "AS IS" with no warranties, and confers no rights.
- Follow-Ups:
- RE: Debugging a remote service fails
- From: "Jeffrey Tan[MSFT]"
- RE: Debugging a remote service fails
- From: "Jeffrey Tan[MSFT]"
- RE: Debugging a remote service fails
- From: "Jeffrey Tan[MSFT]"
- RE: Debugging a remote service fails
- Prev by Date: Re: Attach to Process does not work?
- Next by Date: VB.net 2005: Breakpoint in click event of button causes progr cras
- Previous by thread: Re: Attach to Process does not work?
- Next by thread: RE: Debugging a remote service fails
- Index(es):
Loading