Can't debug deploy WM5.0 mobile app

I have a Windows Mobile 5.0 application that I can copy to and run on a target device, however when I try to start debug under VS2005 says "Deploy started ...." then after about a minute comes up with the error:

"Returned by WSARecv or WSARecvFrom to indicate the remote party has initiated a graceful shutdown sequence."

I am connected via ActiveSync 4.1.0 and can access the device as well as open sockets in either direction (using IP addresses 169.254.2.1/2 - where are these documented!) so I have connectivity.

What am I doing wrong Any suggestions welcome.

Mark

I have been doing some more testing and find I get the same error if I try to run any of the VS2005 Remote Tools. ActiveSync is still fine however. I am running VS2005 in a VMware virtual machine but don't see how this would be a problem if ActiveSync is ok.

More research: Selecting "Tools>Options>Device Tools>Devices>Windows Mobile 5.0 Pocket PC Device>Properties" gives an error "Error retrieving information from user datastore. Property not found."




Answer this question

Can't debug deploy WM5.0 mobile app

  • de_Stan

    Hello.

    I am having this same issue also, but I cannot fix the problem using the steps listed above. Is there any other advice anyone can give to help me

    On the final step of trying to connect to the device I get the same error:

    "Connection failed. Returned by..."

    Thanks,

    B


  • Naveeeen

    Did what you said, it connected succesfully and the I ran Debug and got:

    ------ Build started: Project: XXX, Configuration: Debug Any CPU ------
    XXX-> C:\Users\ XXXXX\Documents\Visual Studio 2005\Projects\XXX\XXX\bin\Debug\XXX.exe
    ------ Deploy started: Project: XXX, Configuration: Debug Any CPU ------
    Error: The operation could not be completed
    ========== Build: 1 succeeded or up-to-date, 0 failed, 0 skipped ==========
    ========== Deploy: 0 succeeded, 0 failed, 0 skipped ==========

    That's all I got, now what Sad and running Vista Ultimate...

  • QSI-Inc

    Hi Wim,

    Did you already have a solution for your problem, for I'm experiencing the same #183 error.

    When debugging on an earlier version of Windows Mobile, things go OK (or am I missing some special debug dlls on the PDA)

    Thanks,

    Marco


  • JinFan

    It looks like your datstore has got corrupted.

    Can you try the following,

    • Close all the instances of VS, Emulator and device emulator manager.
    • Goto <sysdrive>:\Documents and Settings\<User Name>\Local Settings\Application Data\Microsoft\CoreCon
    • Take a backup of the 1.0 directory. Delete the 1.0 directory.
    • Open Visual studio and try to access the properties now (you should be able access now).
    • Cradle your device
    • Click the connect to device menu item in Tools menu, Select the PPC 05 device. Dialog should say 'Connection succeeded'

    Now try your debugging.



  • Surjeet Thakur

    The solution I found was to connect VS2005 to the PDA first (Tools-->Connect to Device...) before attempting to deploy or debug, otherwise it always fails.

    In order to connect it also seems as though I need to poke ActiveSync, e.g. explore remote directories on the PDA, until VS2005 connects successfully. This mirrors a problem I have with TCP/IP connections from the PDA to the host, which tend to stall unless some other program such as ActiveSync is also actively accessing the device.

    Don't you just love these guys!

    Mark

  • Brian C. Barnes

    I've the same (likely) problem

    I can deploy and debug but when i use our other Mobile device it won't work.

    VS does build and deploy but won't start the application!

    i get an error #183 . more not no explanation or wathever !

    any solutions

    thanks

    Wim


  • Mallyk

    Sorry, I had a bit of trouble replying as this site is no longer compatible with Firefox (good old MS). You should check your device display as I found that the components that VS downloads to initiate debugging are not signed and need to be explicity accepted on the device.
  • Can't debug deploy WM5.0 mobile app