-
Notifications
You must be signed in to change notification settings - Fork 683
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
E_CSC_SYSTEM_INTERNAL: Internal error! A procedure imported by 'ScopeEngineManaged.dll' could not be loaded. #66
Comments
Summarized the fix for Windows 7 as this:
|
Hello yangyud-cn and jonstaten, I have experienced the same issue under the same environment described by jonstaten, I have done the mentioned update and the same error still happens. The submission to the cloud to execute works fine. The issue is when trying to submit to (local). Is there any other thing that I can do to run locally? Thanks. |
Hello, I am experiencing the same error condition described in this thread. I too have made sure that I have the 5 requirements as outlined by yangyud-cn, but I am still get this error when I attempt to create a database or table or resister an assembly locally. Help! |
You will need the 64 bit version of vc runtime. Please choose https://www.microsoft.com/en-us/download/details.aspx?id=53587 And for none Windows 10 users, please also install the x64 version of UCRT here: https://support.microsoft.com/en-us/help/2999226/update-for-universal-c-runtime-in-windows |
I followed these instructions but received the same error. I have Window 7. It was working fine before I upgraded to 2.2.5000.0 this morning. You will need the 64 bit version of vc runtime. Please choose |
This looks to be a newly introduced dependency of some system API not available on Windows 7. We are still investigating this issue. As a temporary solution, you will need to downgrade the U-SQL SDK to a lower version.
|
This did fix the problem above as I can now submit a local job without error via Data Lake -> Submit Job Unfortunately the drop down menu's in USQL script are no longer present. And I see the message "Cannot start build task due to null compute account." Until after I submit the first job. |
@melpcollins |
One thing I noticed is that in the Project's references section, it came out as empty (no reference to any DLLs). Is this normal? I even created a new project, and still found the References empty. Uninstalled, and re-installed ADL tools v2.2.5000.0 a couple of times, and still the same outcome. Would you be interested in checking any of my registry keys, or log files, or anything that might give a clue? |
I have same as @sqlaz The downgrade solution you provided did work except I'm missing the drop down lists and get "Cannot start build task due to null compute account." in 2015. It works correctly with downgraded system in "2017 RC" |
@sqlaz, The references section is empty by default, This is expected. The root cause of the failure "ScopedEngineManaged.dll" is because in the newer versions of runtime, some newly added code refer to APIs not existing in Windows 7. @melpcollins, I still can't reproduce the error. Could you please help to check the log here to see if there are issues related to this error ? You should be able to open the file and look for error messages there. C:\Users\YOUR_ACCOUNT\AppData\Roaming\Microsoft\DataLake\log Thanks a lot, |
@melpcollins , regarding the issue, could you please try to reset the VS MEF cache by deleting the following folder before you start VS ? This can become corrupted and cause issues. It will recreate by VS automatically if you delete it. C:\Users\YOUR_ACCOUNT\AppData\Local\Microsoft\VisualStudio\14.0\ComponentModelCache |
Deleting ComponentModelCache brought back drop down menu's. Logs show this: DataLake$$.svclog |
I am also facing the same issue. I am trying to Create a Local U-SQL Database (Under Data Lake Analytics) using Server Explorer. My OS is Windows 7 X64 with Visual Studio 2017 (RTM) installed. I was facing the same issue in Visual Studio 2013 also. I upgraded to Visual Studio 2017 today but the Issue Remains. [Job Error] |
@itsjai, Please use the older runtime as described before. Thanks, |
@melpcollins , it's good to know that your problem is resolved. We don't need the logs in this case as it is a known issue of MEF cache corruption. Thanks a lot, |
@yangyud-cn Just to be clear. Everything works if I use the workaround of rolling back the version you suggested "Please get the package here: http://www.nuget.org/packages/Microsoft.Azure.DataLake.USQL.SDK/1.2.5169224" The latest version 2.2.5000.0 does not work on my machine. I always get 'ScopeEngineManaged.dll' could not be loaded with version 2.2.5000.0 |
Hello, thanks for the response. I was able to rollback to the previous installed version and I can now compile and run USQL. Thanks |
Is there a plan to get the latest version of this working on Windows 7? Or will it just be fixed in 2.2.6000.0 ? ? |
@yangyud-cn @MikeRys Hi guys. This bug here got closed. Are you working on a fix to get the ADLA tools working again on Windows 7? (Or will it be Win 10 only?) Cheers. |
The failure is due to that some recent code made use of an ODBC32 API that is only available on Windows 8 or later. We understand that many users are still using Windows 7. However, it is also not feasible for us to revert back the change as that improvement is important for performance of related functions. I will update here once we have agreed on the solution. |
@yangyud-cn you never did update this thread "once we have agreed on the solution" |
@yangyud-cn I hope that you can reconsider making it compatible with Windows 7 |
This should now be working on Windows 7 for the current version 2.2.7000.3 and higher |
Hello,
After installing the latest version of the ADLA tool I am now receiving the following error when building the usql script.
Version: 2.2.4000.0
MSI: Microsoft.Azure.DataLakeToolsForVS2015.msi
E_CSC_SYSTEM_INTERNAL: Internal error! A procedure imported by 'ScopeEngineManaged.dll' could not be loaded.
Is there anything I can do to resolve this error?
I'm running on windows 7 with VS 2015.
Thanks
The text was updated successfully, but these errors were encountered: