0x8007007e error upon deployment - native C++

I installed VS 2005 machine that had VS 2003 on it, but NEVER a beta of VS 2005. At first I could not even connect to an emulator with VS 2005 (VS 2003 worked fine), but then I was told to delete all the files in the %USERPROFILE%\local
settings\application data\Microsoft\CoreCon\1.0 directory and that allowed me to connect. The new problem is I still cannot debug. I select debug with VS 2005 and I can see all the files being deployed, but when it goes to run the application that was deployed, it seems like the debugger cannot find it. The entire application is there, because I can select with the file manager in the emulator and actually run it. I ran sysinternals filemon to look at the files, and VS 2005 was trying to run d:\microsoft visual studio
8\common7\ide\%CSIDL_PROGRAM_FILES%\UnitTest\UnitTest.exe. The path from program files on is correct but the prefix is pointing to my local installation, not the emulator.

Any Ideas

Thanks,

Juan Foegen

Answer this question

0x8007007e error upon deployment - native C++

darthziv
Hi Juan,

I am not able to figure out the issue :(

Can you try attaching the debugger to the running process and let me know the results. For this you need to enable the managed attach. Steps can be found at http://msdn2.microsoft.com/en-us/library/ms228818.aspx

Till then I will try to sycn up with other guys for figuring out the exact issue.

Thanks
Gaurav
a.d.m
I captured registry activity with sysinternals Regmon utility and didn't see a single line on Icordbg.dll, so if that's really the problem (for native code projects), there must be something failing upstream from that in the registry access food chain.

Any ideas for what else could be involved

-Mike
Jarrado
Hi Juan,

At our end we are not able to figure out the problem. Can you send us the simple managed project and send it to gauravsi[AT]microsoft.com

Thanks
Gaurav
SilvanG
I created a native MFC application and I can deploy and debug it in the emulator with no problems. I set a breakpoint in onInitDialog and was able to step through code like you would expect.

I then opened up my skeleton C# managed project and tried to debug to the same emulator and still get the error when trying to debug, saying it cannot find the application. Previously, I started the app after deployment via the file manager on the emulator, but Start without debugging (Ctrl-F5) from inside VS 2005 works fine too.

So my only real problem is I cannot debug managed applications. Troubling.

Thanks,

Juan Foegen
ronnotel
Hi Juan,

Thanks!!
Can you check if native debugging works fine or you are getting the same error You said that app runs fine without debugging, just want to double check that u tried Ctril-F5 for that

Regards
Gaurav
arkiboys
I created a PPC 2003 managed dummy application and I get the same error when trying to run using the 2003 emulator. I also tried this same application on my Mobile 5.0 device and get the same error. I just don't know why the debugger is looking for the wrong exe to debug and where it is getting that path.

Thanks,

Juan Foegen
Matt Falzon
I'm having the same problems, but it seems as tho the registry is correct. I believe there were 4 or 6 entries, half for VS03 and the other half for VS05. Are you suggesting that all should be replaced with the VS05 path
Samant B Jain
Start project is selected under my debug tab for my managed app. I just created a totally new Mobile 5 app with a checkbox. The application comes up fine if the application is started without the debugger. Yes, edm is running on the emulator according the remote process viewer.

Thanks,

Juan Foegen
darkwarrior0404
I am also getting the 0x8007007e error, though on C++ native PPC'03 and WM5 projects. Four projects behave identically, so it would seem that it's a registry problem, not a project setting.

I tried reinstalling, but nothing changed

A short time passed and my hard disk crashed, so I really reinstalled from scratch. The projects still wouldn't deploy, so it would seem that it's truly an install issue.

I searched for Icordbg.dll, but it's not in my registry. Maybe that's what's wrong with my install. As to the cause, I suspect a security update may have done something. How else can you get from a working install to one that doesn't deploy

If the Icordbg.dll is really the problem, where does it's registry entry go

-Mike
SQLServer2050
Hi Michael,
If I m correct then your managed debugging is broken on VS2005 but its working fine for VS2003.

Moral of the story is that if VS2005 managed debugging is not working fine then edit the registry enteries for Icordbg.dll (VS2005) . If VS2003 managed debugging is not working then edit the registry enetries for Icordbg.dll (VS2003). By editing I mean that make it point to the correct path where corresponding dll is stored

Hope it helps.

Regards
Gaurav
Sabrecat
Sorry for getting back late because I was OOF

I haven't seen/faced similar problem before so it is really difficult. Can you do couple of more things
- Check if managed debugging is working fine on Windows Mobile 5.0 PPC physical device
- Check if managed debugging is working fine on Pocket PC 2003 emulator
- If it is working on other emulators then please reinstall Windows Mobile 5.0 PPC SDK on your PC and give a try.
Thanks for showing patience.

Regards
Gaurav
Lerxst193952
Hi Juan,
Lets narrow down the problem to solve it quickly. For this please answer the following
- If its managed app, can you check if anything is mentioned in Project Properties -> Debug -> Start External Program text box.
- If its native app, can you check if anything is mentioned in Project Properties -> Debugging -> Remote Executable.
- Are you abe to run the application without debugging. In other words Ctrl-F5 is working fine or not
- Check if edm.exe is running on the device after doing F5. You can verify this using Remote Process Viewer.
Regards
Gaurav
Toni Greco
After talking to Juan issue and resolution has been figured out. Thanks to Juan for providing information.

Issue: Couple of the registry enteries for Icordbg.dll were having incorrect path mentioned. This was the reason that managed debugging was completely broken

Resolution: Search out for Icordbg.dll on the machine and note the path of Icordbg.dll corresponding to VS2005. Now modify the registry enteries of Icordbg.dll corresponding to VS2005 with the figured out path

Regards
Gaurav
WindowsObserver
I get the same error when trying to attach after making the registry change and launching my application. The application is in the list but when I select it says:

Unable to attach to the process. An error occurred that usually indicates a corrupt installation (code 0x8007007e). If the problem persists, repair you Visual Studio installation via 'Add or Remove Programs' in the Control Panel"

When I first got the message, I tried the repair and it did not make any difference.

Thanks for thinking about the problem. If you want me to try something else, let me know.

Thanks again,

Juan Foegen
0x8007007e error upon deployment - native C++

Answer this question