none
Cannot debug local C# code used in U-SQL script since VS2017 15.7.1 upgrade yesterday

    Question

  • I have a custom extractor, as well as a custom assembly that have been working for the past several weeks+ - I have been able to debug locally stepping into the code.  I am still able to Submit the U_SQL script locally and it successfully runs producing a local output file, but when I F5 to debug I "Local run failed or was terminated" and the output file is not created.

    Is there a detailed log somewhere to see what exception is being thrown?  Nothing in the event viewer. 

    I did get a message at the end of the VS2017 upgrade that stated "Anaconda program could not be uninstalled" (something to that effect) - Googling seems to suggest its Python, don't know if that would affect things as I'm not using Python at all.


    Bill Blakey

    Friday, May 18, 2018 6:44 PM

Answers

  • Bill,

    The fix was release yesterday as version 2.3.4000.3 of ADL Tools.   You will need to upgrade it in VisualStudio 2017 -> Tools -> Extension and Updates -> Updates -> Visual Studio Marketplace

    For users who use VS2015, the correspondent update is here: https://www.microsoft.com/en-us/download/details.aspx?id=49504

    Please let us know if that solve your problem and I'm really appreciate your patience.

    Sincerely,

    Yu Dong



    Wednesday, July 11, 2018 2:36 AM

All replies

  • Bill,

    There are logs of each local vertex under PROJECTDIR \bin\Debug\SCRIPT_FILENAME.   You could check there to get more info.  Please let us know if the log files couldn't help.

    Also, there are debug logs in the "Output" tab of Visual Studio, please make sure to enable these in VS->Tools->Options -> Debugging -> Output Window

    In addition, I suggest you to make sure that the VS can still debug a normal C# project by creating a simple C# project and debug it.   If not, reinstall of VS will be needed.

    Thanks a lot,

    Yu Dong


    Monday, May 21, 2018 4:53 AM
  • Thank you  - I enabled and am able to view the output files.  In each of the [N]_vertexthost.txt files I have this error:

    [Info] (entry.cpp, ScopeEngine::`anonymous-namespace'::RegisterBadMemoryHandler:208) (RegisterBadMemoryHandler) Bad memory notification handler installed

    However I cannot find any entry.cpp file.  Also in my [1]_vertexthost.txt file I have this additional line:

    [Error] (d:\dbs\sh\c2rm2\0223_010827\cmd\44\private\cosmos\scope\localrun\localvertexhost\localvertexhost.cpp, ReportError:92) (LocaVertexHost) Failed because 'Debug mailslot initialization error :53'

    Any thoughts on how to resolve this, or what I may need to remove and reinstall?

    PS - I *am* able to debug other C# code without issue, including UnitTests in my Data Analytics Solution.


    Bill Blakey

    Tuesday, May 29, 2018 5:20 PM
  • Bill,

    It looks like that this issue is related to a bug (or 'feature' ?) in Windows 10 update 1803.  We use local mailslot for debugging messaging. But this update breaks that.   There are discussions regarding similar issues here.   I will check with Windows team to see what could be done than rolling back.

    https://social.technet.microsoft.com/Forums/windows/en-US/79768e50-928c-43d4-8f34-b9fb1dae4e59/windows-10-1803-cannot-open-mailslot-using-computer-name-or-ip-address-fails-error-53?forum=win10itpronetworking

    Thanks a lot,

    Yu Dong

    Monday, June 4, 2018 3:09 AM
  • Ok that's good news that there is now a known issue, thank you for following thru on this.

    I'll wait to see a follow-up post once you hear back from the Windows team on a rollback or fix.

    Thanks!


    Bill Blakey

    Monday, June 4, 2018 3:21 PM
  • Bill,

    I checked with Windows team and they are working on the fix as high priority task.  I will post here once there's a solution. 

    Thanks a lot,

    Yu Dong

    Tuesday, June 5, 2018 1:41 AM
  • Status update:  Instead of waiting for Windows fix, we will release a new version of Azure Data Lake and Stream Analytics Tools that fixes the issue alternatively.   The new release will be available soon.
    Thursday, June 21, 2018 7:46 AM
  • Yangyd, thank you so much for posting the update and to the ADLA team for taking this on.

    Any rough estimate on timeframe, is soon still this week or next, or ...?

    Again, thank you!


    Bill Blakey

    Thursday, June 21, 2018 3:49 PM
  • Bill,

    The build is in internal preview stage.  I would expect that to be available for public release in one or two weeks if no release blocking issues are found.  I'm really sorry for the inconveniences caused.

    Sincerely,

    Yu Dong

    Friday, June 22, 2018 1:28 AM
  • Yu, thank you for the follow-up and timeline, I'll plan accordingly.

    Bill Blakey

    Friday, June 22, 2018 3:35 PM
  • Is the fix to address this in Visual Studio 2017 version 15.7.5  which was released today?

    Bill Blakey

    Tuesday, July 10, 2018 11:58 PM
  • Bill,

    The fix was release yesterday as version 2.3.4000.3 of ADL Tools.   You will need to upgrade it in VisualStudio 2017 -> Tools -> Extension and Updates -> Updates -> Visual Studio Marketplace

    For users who use VS2015, the correspondent update is here: https://www.microsoft.com/en-us/download/details.aspx?id=49504

    Please let us know if that solve your problem and I'm really appreciate your patience.

    Sincerely,

    Yu Dong



    Wednesday, July 11, 2018 2:36 AM
  • We also had to re-write the communications to workaround mailslots in our software. However that does nothing for all users of previously existing versions which worked fine.  You guys internally have a better hope of getting this fixed to work correctly again.  Please keep lobbying.    

    Could the Windows team just check to see what may have changed in the name validation? It seems like \\computername\mailslot\slotName or \\ipaddress\mailslot\slotName just get rejected immediately without even trying them, so it's more like a path validation error rather than some change to mailslots.

    Thursday, July 12, 2018 9:58 PM
  • Slight problem here.  I use vs 2013.  No updates in years,  Please advise.

    Boyd


    BDM

    Sunday, July 15, 2018 12:07 AM
  • Yu, the updated VS2017 15.7.5 and Data Lake Analytics Tools extension 2.3.4000.3 combination - appears to be working ok now, I am able to step into and thru the debugger successfully.

    Please thank the VS and ADL teams for a fairly quick turnaround on this break, it's much appreciated!


    Bill Blakey

    Monday, July 16, 2018 6:36 PM