Community
cancel
Showing results for
Did you mean:
Beginner
1,000 Views

Hi,

I am trying to use the Intel compiler with visual studio 2019, but I always get the error:
error MSB6006: "xilink.exe" exited with code -1073741819.

I have found similar issues on the forum, but neither provided a solution for me. The same error occurs with VS2017, VS2019, and VS2019 preview. My VS2019 version is 16.6.5, while the Intel compiler version is 19.1. You can find the build log attached.

18 Replies
Beginner
988 Views

I have since uninstalled the Intel compiler, and all of my msvc versions, and I have reinstalled vs2019 and the Intel compiler. This did not fix the issue.

Moderator
953 Views

Hi,

Could you try creating a new C++ project with Intel C++ compiler and build/run a sample code (just print something) and see if it works?

Try it out with both debug and release modes.

Let me know if it helps.

--Rahul

Beginner
943 Views

I created a project with just int main() { return 0; } and got the exact same error. I tried it in both debug, release, x86, x64. As mentioned, I already reinstalled everything so I have the latest version of both vs2019 and parallel studio. Something noteworthy is that icl was not set in the environment path, so I had to go to "C:\Program Files (x86)\IntelSWTools\compilers_and_libraries_2020.2.254\windows\bin" and run "compilervars.bat intel64". Now I can compile code just fine from the command line, but I get the exact same error as before in vs2019.

Moderator
939 Views

can you run this from the command line to see if you still reproduce the xilink.exe error?

Beginner
905 Views

The above won't work since I have deleted the project since. I made a new project (which I will keep this time around), the log is attached below.

Moderator
899 Views

Thanks,

Can you try this from the command:

Then also run:

I wanted to see if the error came directly from "xilink.exe" or from executed "Tracker.exe"

Beginner
896 Views

I got the following error after running the second part:

TRACKER : error TRK0006: Failed to open cancel event "MSBuildConsole_CancelEvent30fdf23028884619ba1e73b9c04a6b12". The system cannot find the file specified.

Moderator
888 Views

Seems like that file had been deleted.

Will you able to run this?

Beginner
884 Views

I was able to run the above just fine, without any errors.

Moderator
879 Views

Seems like it works from the command line.

The VS2019 version you use is pretty new (released on Jul/21/2020) and Intel compiler 2020 update 2 ( built date Jul/1/2020). Is there a way you can try on VS2019 versions which released before the compiler built date (e.g. VS2019 version16.6.1) to see if the problem still occurs?

Beginner
874 Views
Before uninstalling and reinstalling VS my versions for both vs2017, vs2019, and vs2019 preview were ones that were released before the intel compiler version that I installed. If you can reproduce this, then maybe you could recommend to which version specifically this needs to be downgraded. On the other hand, if it is not reproducible, I would assume it's a different reason.
Moderator
869 Views

It is not recommended to use the VS versions that released after the compiler built date because we didn't have a way to validate that VS versions prior to releasing the compiler.

Beginner
867 Views
I understand this. That is why I clarified that I had the same problem with the older versions, and why I asked whether you can test this and see if it is reproducible on your side, and potentially recommend a specific version that can work with the Intel compiler.
Moderator
865 Views

Can you let us know which specific older VS versions you have tried and saw the same issue so that I can escalate it to the integration team?

Beginner
853 Views
I believe the older version for vs2019 which I tested with was 16.3.5. I don't remember the preview and vs2017 versions that I had.
Moderator
846 Views

Thanks,

I tested on VS2019 version 16.5.5. It worked fine.

Moderator
845 Views

Attached screenshot.

Moderator
295 Views

This issue has been resolved and we will no longer respond to this thread.

If you require additional assistance from Intel, please start a new thread. Any further interaction in this thread will be considered community only.

Thanks,