Windows debugger for windows server 2003
Sign up or log in Sign up using Google. Sign up using Facebook. Sign up using Email and Password. Post as a guest Name. Email Required, but never shown. The Overflow Blog. Stack Gives Back Safety in numbers: crowdsourcing data on nefarious IP addresses.
Featured on Meta. New post summary designs on greatest hits now, everywhere else eventually. Please clarify which machine step 3 should be done on. Client or Server? What I did on the past was logon to the Server machine with my matching account and then started the remote debugger. I would then go back to the client and from VS attempt to set a breakpoint or attach to a remote process. That is the point at which I would get the error message. Let me know if you are still experiencing problems Just to be clear; in your situation Vista is the client and Server is the server.
Not sure how relevant this is but in my situation I'm not logging into a domain. I do not log into either machine using the 'DebugUser' account. Both my client and server are in the same Windows domain and I log into both machines using my domain account. This domain account is also a member of the local administrators group on both the client and server.
You need to tell me how your client is able to see your server on the network? Yes all the machines are in a workgroup. Windows Home Server based on Small Business Server doesn't support joining a domain at least not natively.
Hmm, didn't work for me. Access is denied. No, I start VS normally. However, it runs with administrator privileges because my domain user account [which I log in with] is a member of the local administrator group. Wednesday, August 12, AM.
Things to try IOW, they are in the local administrators group on both machines. Also remember that at one point this was working for me. What I don't know is what happened to stop it from working nor do I know exactly when it stopped working since I don't debug every time I run my program. We have sql server on that server so I can loose any data.
When I rebooted and looked at the system logs here is what I found. So, it is perfectly normal that you see such event appearing. Office Office Exchange Server. Not an IT pro? Windows Server TechCenter. Sign in. United States English. Please rate your experience Yes No. Any additional feedback? Submit and view feedback for This product This page. View all page feedback. In this article.