Intel® oneAPI DPC++/C++ Compiler
Talk to fellow users of Intel® oneAPI DPC++/C++ Compiler and companion tools like Intel® oneAPI DPC++ Library, Intel® DPC++ Compatibility Tool, and Intel® Distribution for GDB*
777 Discussions

The 'CompatibilityToolPackage' package did not load correctly.

cean
New Contributor II
5,384 Views

Hi, 

Just installed VS2022 & Fortran 2022.2.

When trying to open an old project, this error message pops up. 

Follow the message, opened ActivityLog.xml and found some error entries, like these:

 

 

  <entry>
    <record>1211</record>
    <time>2022/08/19 12:59:01.761</time>
    <type>Error</type>
    <source>VisualStudio</source>
    <description>Error loading UI library for package ICXOneAPIPackage. HrLoadNativeUILibrary failed with 0x800a006f.</description>
  </entry>
  <entry>
    <record>1212</record>
    <time>2022/08/19 12:59:01.792</time>
    <type>Error</type>
    <source>VisualStudio</source>
    <description>Loading UI library</description>
    <guid>{BFE74C3F-A2E9-43C0-811E-2794CB8AC0A3}</guid>
    <hr>0x800a006f</hr>
    <errorinfo>Cannot find the requested resource: 'VSPackage.ctmenu'.</errorinfo>
  </entry>

 

What's this ICXOneAPIPackage package ?

 

Cheers,

Cean

0 Kudos
9 Replies
Steve_Lionel
Honored Contributor III
5,369 Views

I think that's part of Intel C++.

0 Kudos
cean
New Contributor II
5,351 Views

Created a new project. But when trying to reopen it, a new error message pops up (attached).

 

After disable it as suggest, it could be reopened.

0 Kudos
cean
New Contributor II
5,346 Views

Tried to reopen again, this time it says one source file has problem to open. (error msg attached. 0x80004005)

That source file is added as existing into the newly created project. But I can see it is listed in the solution tree. Double click it and it is opened without problem.

And I have to do it every time when reopen.

 

If it is old project, nothing is in the solution tree.

0 Kudos
Steve_Lionel
Honored Contributor III
5,321 Views

I haven't seen that "oneAPI menu" issue before. The file opening issue is allegedly fixed in the next Fortran update - I find it annoying, but not a deal-breaker.

0 Kudos
gib
New Contributor II
3,923 Views

I have encountered a similar problem.  After resetting Windows 10 I found that VS 2019 and oneAPI HPC, which I'd been using for a couple of years, had been removed (thanks Microsoft).  I reinstalled VS 2019, then oneAPI base, then one API HPC.  When I try to open the project that I've been working on for years it fails to open.  The message says that CompatabilityToolPackage did not load correctly.  What should I do?

Thanks.

 

PS it also tells me that it might help to view C:\users\gib\appdata\roaming\Microsoft\Visual Studio\16.......\activitylog.hml.  It might help, if such a file existed.  In fact I do not even have the folder C:\gib\users\appdata.

0 Kudos
andrew_4619
Honored Contributor III
3,914 Views

I get that message all the time. I ignore it. I haven't noticed any ill effects. But if anyone know how to fix/silence it then please tell!

0 Kudos
gib
New Contributor II
3,825 Views

I don't think the CompatibilityToolPackage is the real problem in my case.  VS 2019 thinks my project file is incompatible, even though it was created with VS 2019.  I can't ignore the problem - it is preventing me from working on this project.  

0 Kudos
gib
New Contributor II
3,911 Views

I found the DPC++ Compatibility Tool on the Intel site and installed it, but it made no difference.  No surprise, since it has something to do with CUDA, which I am not using.

When I open my project,  the Solution Explorer shows <project name> (incompatible).  Below the toolbar I see the names of all the source files, but they can't be opened.

This is a real PITA.

0 Kudos
RBWGEV
Beginner
3,026 Views

FWIW, I was getting the CompatibilityToolPackage message consistently.  I had updated from VS2017 to VS2022, and to a newer Fortran compiler.  Every time I viewed the solution in VS22, it was displayed as incompatible.

 

I was able to circumvent the problem by going to the Solution Explorer, right-clicking on the solution, and selecting 'Resolve Errors'.  This caused VS22 to recognize/accept compatibility with the solution, and I was then able to build.  I hope this helps.

0 Kudos
Reply