search

Azure / usql

U-SQL Examples and Issue Tracking
http://usql.io
MIT License
234 stars 685 forks source link

Visual Studio: Local runs fail #160

Open simra opened 4 years ago

simra commented 4 years ago

Hi, I'm attempting to run some scripts locally from my project and I'm not sure how to troubleshoot this issue. I'm using the (local-project) option for the ADLA account when I submit. One script launches but produces this error:


Start '1_SV1_Extract_Split' : 12/23/2019 4:26:28 PM
End '1_SV1_Extract_Split(Error)' : 12/23/2019 4:26:28 PM
Completed with 'Error' : 12/23/2019 4:26:28 PM
Execution failed with error '1_SV1_Extract_Split Error : 'Failed to execute step, return code is : -1073740023
 StdOut: LocaVertexHost Runtime engine initialized
!!OS detected bad memory!!, Terminating the process with exit code 0xc0000709

StdErr: '
'
Execution failed !

The other script, which has worked fine in the past fails to launch and produces a different error:

   UsqlSDKBuild.targets(47,5): error : Account is not Azure Data Lake Analytics account : DataLakeLocalCA:projectlocal_623c5235-603a-422e-9427-47339678f75f

Restarting Visual Studio hasn't resolved the issue. What can I do to troubleshoot?

MKadaner commented 4 years ago

I can say nothing about the second issue, but exit code 0xc0000709 strongly suggests that physical memory in your machine is unreliable. Do you get this error each time you run your script? Can you run thorough memory test? Do you see memory errors in Windows log?

If the memory has ECC, memory errors could be correctable, and OS and application mostly work. However, correctable memory errors are still reported, and SCOPE deliberately fails when such error happens. While this makes less sense in local run, the approach is the same as in cluster execution.