Remote debugging setup/help NEEDED

[Jensemann2]

Please help!

I can't get the Virtual Debugger to work.

A while ago (VS2005+WS6.5) it did work. But now with VS2008SP1 + WS7 + XP guest, it won't work: the remote debugger starts, logs me into the guest and after a few seconds the error screen comes up.

Here is the log:

11.11.2009 22:08:37: Debugging started...

11.11.2009 22:08:37: ERROR: *ppVCProj

11.11.2009 22:08:37: An error occurred in .\utils.cpp at line 2683. Error code is 0x80004005.

11.11.2009 22:08:37: An error has occurred in the application. For more information please see the log file. Its path is listed in the About box.

11.11.2009 22:08:37: ERROR: GetVCInterfaces(m_targetProject, (void **)&m_pVCDbgSettings, (void **)&pVCCfg, (void **)&pVCProj)

11.11.2009 22:08:37: An error occurred in .\Connect.cpp at line 7424. Error code is 0x80004005.

11.11.2009 22:08:37: An error has occurred in the application. For more information please see the log file. Its path is listed in the About box.

11.11.2009 22:08:37: Starting the virtual machine.

11.11.2009 22:08:37: Waiting for VMware Tools to start...

11.11.2009 22:08:37: VMware Tools has started.

11.11.2009 22:08:37: Waiting for login to complete...

11.11.2009 22:08:37: Login succeeded.

11.11.2009 22:08:37: Checking for running Remote Debug Monitor in the virtual machine.

11.11.2009 22:08:37: Sharing Remote Debug Monitor directory:

11.11.2009 22:08:37: C:\Program Files\Microsoft Visual Studio 9.0\Common7\IDE\Remote Debugger\x86\ as .RemoteDebugMonitor12609

11.11.2009 22:08:37: Enabling shared folders succeeded

11.11.2009 22:08:38: Adding share folder succeeded.

11.11.2009 22:08:38: Starting the Remote Debug Monitor:
vmware-host\Shared Folders\.RemoteDebugMonitor12609\msvsmon.exe /nowowwarn /name:VMware@USPTO

11.11.2009 22:08:40: Preparing the project's configuration properties for live debugging.

11.11.2009 22:09:41: Debugging Failed.

11.11.2009 22:09:42: The Remote Debug Monitor running in the virtual machine has been stopped. Process ID: 2864.

11.11.2009 22:09:42: Removing Remote Debug Monitor share: .RemoteDebugMonitor12609.

11.11.2009 22:09:42: Removing share folder succeeded

Under 'Live Debugging in VM' I can't use the setting <Use host's Visual Studio project command> (Error: "A valid executable name has not been specified in Debugger settings"). If I miss configured the Virtual Debugger (what I would guess), I'd like to get some usefull debug output.

Hope this helps.

Jens

[ColoradoKind]

I have the exact same problem with Live Debugging. I'm using Vista with Workstation 7.0.0 build-203739 and trying to debug on XP virtual.

I get the error:

"A valid executable name has not been specified in Debugger settings. You can change this in Project > Properties > Debugging."

However, there is no such option in Visual Studio 2008 (maybe this refers to Visual Studio 2005?)

Anyway, I'm sure is something simple. Any Ideas?

Thanks,

Tim

P.S. I am able to "Attach to Process in Live VM" without any problems.

[Jensemann2]

Hi Tim.

You can get around this problem by setting "
vmware-host\Shared Folders\<Share-Name>\<Executable>" as "Run guest command" in Virtual Debugger settings and sharing your projects Debug-Folder (i.e. "C:\VSProjects\<Solution-Name>\<Project-Name>\bin\x86\Debug") as <Share-Name> in Workstation 7.

On the other hand, this may lead to the error described in my first post. If you try it, we'll see.

Meanwhile I'll try to setup regulat remote debugging. That might give some additional clues.

Jens

[grossag]

Did you skip installing of Visual C++ when installing Visual Studio? Basically this error is coming from the fact that we can't find the VCProject interface in the registry, which Visual Studio should be registering. I would suggest going to the registry, highlighting HKEY_CLASSES_ROOT\Interface, and doing a search for "VCProject" (without the quotes). Skip the first entry (VCProjectEngine), and the second result should be HKEY_CLASSES_ROOT\Interface\{3990034A-3AF2-44C9-BD22-7B10654B5721}. That GUID in the {} is what I am looking for. Does it match the one I listed above? Does that full registry path exist?

[grossag]

This is talking about Visual Studio's project properties. What programming language are you using? If you highlight your startup project, go to the actual toplevel menu item Project and select Properties > Debugging, you can enter a valid executable name.

[Jensemann2]

Hi.

Tough I only program in c#, c++ is installed. That full registry path and the GUID you mentioned above do exists (talking about the host, right?).

I started to reinstall VS now (just in case...)

Thanky you for your support,

Jens

[Jensemann2]

Since I have this problem also I have to push in here: the setting you refer to is not an option for me (us?).

Please see my attached screen-shot. Did I miss something here?

Jens

[grossag]

What programming language is this?

[grossag]

Yeah, talking about the host. Honestly, I'm puzzled about why you would get the original error here:

11.11.2009 22:08:37: ERROR: *ppVCProj

11.11.2009 22:08:37: An error occurred in .\utils.cpp at line 2683. Error code is 0x80004005.

When you have that registry key. Not sure what your host is, but if it's permissions issues and you're on Vista or Win7 you could always try as an experiment to right-click on the Visual Studio shortcut and select "Run as Administrator" and see if that fixes it. But that's just another guess.

[ColoradoKind]

I have the problem with C# in Visual Studio 2008, Workstation 7.0.0 build-203739 on Windows Vista. C++ is also installed in Visual Studio 2008

We do not have the same menu options in Visual Studio.......

~Tim

[grossag]

Ok the issues with using is likely a bug. Just do what people have always done with C#, which is to use a Host Command, but explicitly specify the path on the host to your created .exe. Let me know if that fails too.

[Jensemann2]

It's c#.

Jens

[Jensemann2]

Tried to run Visual Studio as admin - did not fix it.

Jens

[Jensemann2]

Here comes something new to this case.

After reinstalling Visual Studio with no success, I tried to initiate a remote debug session directly from Visual Studio.

No surprise that didn't work. This time the error was a little bore specific: "A security package specific error occurred".

The workaround that fixed it (even on my system) is described here: http://social.msdn.microsoft.com/Forums/en-US/vsdebug/thread/54f62bca-0d4b-4a64-82e2-ab6d60f859c9, answer by Dave Wheeler.

And here is my solution on how to apply this to the Virtual Debugger:

Preparation

- create local accounts for debugging on host and guest (need to be in admin group), i.e. DebugUser.

In Virtual Debugger Settings change following settings:

- 'Virtual Machine' is set to your VM (obvious)

- 'Remote Debug Monitor Path' is set to my 'x86' msvsmon.exe. It's not used ( i guess) but Virtual Debugger wants something in that field.

- 'Remote Debug Monitor Name' is set to your local account name, ie. DebugUser. 'Guest'

- 'Guest Command' is set to my VM Shared Folder named "Debug" with it's host path set directly to my Visual Studio Debug folder. i.e.
vmware-host\Shared Folders\Debug\ run as) on guest. That should log something like: "Msvsmon started a new server named 'DebugUser@guestmachine'. Waiting for new connections."

- start virtual debugging. There should be a pop-up, complaining about an already running Remote Debug Monitor already running in the virtual machine. Use the existing instance!

I still don't know why it didn't work in the first place. Might have something to do with Vista/Win7 UAC.

Jens