- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I recently installed VS2019, but after installing the Intel Fortran compiler as an add-on, when I reopened VS2019, it displayed “failed to load correctly'IntelGfxDbgPackage”(see the picture).The ActivityLog.xml file shows "Failed to load the file or assembly 'Microsoft.VisualStudio.Threading, Version=16.10.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the specified file."
By the way, I'm performing the offline installation on a computer without internet connection. Is this related to it?
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The same problem is discussed in this thread https://community.intel.com/t5/Intel-Fortran-Compiler/Installation-issue/m-p/1720539#M177368
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thank you.
I read the thread and found it very helpful.
I checked and found that the “Microsoft.VisualStudio.Threading 16.10.0.0”file was missing.Maybe it is the reason.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I think the answer is to install the GDB stand-alone kit
That is part of the toolkits but there is a stand-alone GDB kit you can install: installer https://www.intel.com/content/www/us/en/developer/tools/oneapi/distribution-for-gdb-download.html you could try that.
If you have the oneAPI Base Toolkit, try a 'Repair' on that app.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks for your advice,I install the GDB stand-alone but it does not work.
I check I checked and found that the “Microsoft.VisualStudio.Threading 16.10.0.0”file was missing. Do you know how to install it?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I too have this problem.
A week or so back, I downloaded from the distribution-for-gdb, installed it, and that worked.
At least for a while.
Now the warning is back.
I do not know what happened (possibly a MS VS or Windows update)
Re installing the distribution-for-gdb did not work
Performing a Repair on the Intel oneAPI Base toolkit did not work
and performing Repair on the other Intel drivers did not work.
I'd rather not perform an uninstall of oneAPI, Intel drivers, and MS VS, then re-install everything.
If IntelGfxDbgPackage is used only for inserting break point within an offload region, then I can work around this for a while.
Jim
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I think the key issue might be related to the version of my "Microsoft.VisualStudio.Threading" file. If VS2019 can be updated, this problem should be resolved. However, I installed it on an offline workstation, so the problem has not been solved yet.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi jim:
I disabled the IntelGfxDbgPackage within VS2019, and It stopped reporting the error.
So I would like to know what the function of this package is. Can I work without opening this package?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
>>Can I work without opening this package?
I am ignoring the warning (but keeping displaying). I can work without the use of the package...
... build, run, debug with OpenMP
... but I am awaiting resolution of a different issue regarding allocators and device specification to get the integration of GPU code into my simulation code.
I prefer to use the allocators for persistent data and/or control the data migration between host and target.
Jim Dempsey
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I have solved this problem. I replaced Intel Fortran 2020 and no longer encounter this issue. I suspect that the original ifort2024 was incompatible with VS2019 16.3.3.
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page