locked
Unable to attach to a Windows RT Remote Debug session

    Question

  • I have installed VS2012 Update 4 Remote debugging Tools for ARM, on my Nokia Lumia 2520 RT 8.1 Device.  Installed as Administrator, and set running. (Listed as Version 11.0.61030.0)  But this Remote Service still cannot be seen from my VS2012 session running also on W8.1 Pro.  My Developer VS2012 session cannot see the service, when I configure Remote Machine :"MyLumiaTablet:4016"  with or without port id, and with or without Authentication set up on both ends etc.

    I have checked my network connections, by also ensuring a File share from my RT device  form  settin the 'Server' service going on my RT device to file share. This enables my RT device to be seen from my development machine.  So I can share files, and I have checked that I can ping both ways.

    But I am still stuck with No Debug Session Connections. My RT Remote debugging Monitor service is simply not seen, even if I switch Authentication On/ off at both ends etc.  I don't have a (VS 2012) Remote debugger Configuration Manager App on my RT machine.

    Unable to develop on Nokia Tablets.  So any help would really be appreciated before I give up !

    Cheers

    Julian


    Silverlight an XNA Fan


    • Edited by JulesW Thursday, December 12, 2013 7:21 PM
    Thursday, December 12, 2013 7:20 PM

Answers

  • Hi Jules,

    It sounds like the network connection is getting dropped somewhere. Can you collect a network trace when you see this behavior and share it via Skydrive? That way we can check how the connection gets created and where it is apparently getting dropped - TCP-RST.

    Here are the steps to collect a network trace on your Visual Studio machine:

    Download and Install Network Monitor:
    http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=983b941d-06cb-4658-b7f6-3088333d062f

    Steps for capturing with network monitor

    1.      Open Network Monitor
    2.      Click on Create a new capture tab.
    3.      In the Select Networks window, ensure that the "Local Area Connection" or the correct network adapter is selected with a check mark.
    4.      Click on Capture menu and then select Start.
    5.      Reproduce the issue. Please see Windows RT Network tracing steps below to start a simultaneous trace on your RT machine.
    6.      Click on Capture menu and then select Stop.
    7.      Click on File menu, Save As.. and then save the file.

    To collect a network trace on your Windows RT machine where you are running the Remote Debugger, use this blog to collect a trace: http://blogs.msdn.com/b/wsdevsol/archive/2013/10/10/tracing-network-activity-on-windows-rt.aspx

    At the end of this, you should have a:

    Network trace from your Visual Studio machine

    ETW trace (NetTrace.etl) from your Windows RT machine.

    Please zip and share these files on SkyDrive. That way we can correlate both the traces and check what is going on.

    Thanks,

    Prashant.


    Windows Store Developer Solutions, follow us on Twitter: @WSDevSol|| Want more solutions? See our blog

    Saturday, December 14, 2013 1:00 AM
    Moderator

All replies

  • Hi Julian,

    That general setup should work (we just confirmed). You might have better luck using the IP address rather than the name, especially if they aren't on the same network (for example if one is wired and the other is wireless).

    --Rob

    Friday, December 13, 2013 1:09 AM
    Owner
  • Hello Rob,

    Yes I have tried the IP Address, with and without Port number. Cannot see my Device.  I have VS2012 Remote Tools Update 4, and corresponding to VS2012 Update 4 applied to my Development Machine.

    What I have noticed, is if I am in Project Properties/ Debug: Find...    i.e. Monitoring the possible Remote Debug connections, and then Restart The Remote Debugger App on my Device is that it does then appear briefly as a viable Connection listed.  I can Select it, to bring up it details (Address, License, Architecture, Authentication etc). However if I hit Refresh, or deploy the Connection is then lost.

    So the Connection is briefly established upon Starting the Remote Debugger App (But not when a new MSvsmon service is created), but fails upon second try.   I note by default the MSvsmon always starts with Authentication, but the default Maximum idle Time is zero seconds.  So maybe it recognises the connection but then times out after the first message from the remote service.

    I cannot configure the Max Idle Time, as I don't have a Remote Debugger Config tool, with the VS2014 Update 4 download version (I note that I did when I tried VS2013 remote debug tool by mistake) 

    So its a bit frustrating

    Jules


    Silverlight an XNA Fan

    Friday, December 13, 2013 2:56 AM
  • Hi Jules,

    It sounds like the network connection is getting dropped somewhere. Can you collect a network trace when you see this behavior and share it via Skydrive? That way we can check how the connection gets created and where it is apparently getting dropped - TCP-RST.

    Here are the steps to collect a network trace on your Visual Studio machine:

    Download and Install Network Monitor:
    http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=983b941d-06cb-4658-b7f6-3088333d062f

    Steps for capturing with network monitor

    1.      Open Network Monitor
    2.      Click on Create a new capture tab.
    3.      In the Select Networks window, ensure that the "Local Area Connection" or the correct network adapter is selected with a check mark.
    4.      Click on Capture menu and then select Start.
    5.      Reproduce the issue. Please see Windows RT Network tracing steps below to start a simultaneous trace on your RT machine.
    6.      Click on Capture menu and then select Stop.
    7.      Click on File menu, Save As.. and then save the file.

    To collect a network trace on your Windows RT machine where you are running the Remote Debugger, use this blog to collect a trace: http://blogs.msdn.com/b/wsdevsol/archive/2013/10/10/tracing-network-activity-on-windows-rt.aspx

    At the end of this, you should have a:

    Network trace from your Visual Studio machine

    ETW trace (NetTrace.etl) from your Windows RT machine.

    Please zip and share these files on SkyDrive. That way we can correlate both the traces and check what is going on.

    Thanks,

    Prashant.


    Windows Store Developer Solutions, follow us on Twitter: @WSDevSol|| Want more solutions? See our blog

    Saturday, December 14, 2013 1:00 AM
    Moderator