Does anyone get this message box when starting VS2022 after installing OneAPI 2024.1?

[Mark_Lewy]

This is what I'm getting:

---------------------------
Microsoft Visual Studio
---------------------------
The 'OneApiPackage' package did not load correctly.

The problem may have been caused by a configuration change or by the installation of another extension. You can get more information by examining the file 'C:\Users\lewym\AppData\Roaming\Microsoft\VisualStudio\17.0_42808e7e\ActivityLog.xml'.

Restarting Visual Studio could help resolve this issue.

Continue to show this error message?
---------------------------
Yes No
---------------------------

Re-starting VS doesn't resolve this.

This doesn't seem to have any effect on my ability to open and build Fortran projects, but I wonder what it might be affecting elsewhere.

This is after a custom install (install everything except VS2019 integration) of the base and HPC 2024.1 toolkits over an existing install of 2024.0.  The VS version is 17.7.5 (as validated with 2024.0).

The offending message in the ActivityLog.xml file is this:

SetSite failed for package [OneApiPackage]Source: 'OneAPI' Description: Could not load file or assembly 'Microsoft.VisualStudio.Threading, Version=17.8.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified. System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.VisualStudio.Threading, Version=17.8.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified. File name: 'Microsoft.VisualStudio.Threading, Version=17.8.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' at OneApi.OneApiPackage.InitializeAsync(CancellationToken cancellationToken, IProgress`1 progress) at Microsoft.VisualStudio.Shell.AsyncPackage.<>c__DisplayClass21_0.<<Microsoft-VisualStudio-Shell-Interop-IAsyncLoadablePackageInitialize-Initialize>b__1>d.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at Microsoft.VisualStudio.Services.VsTask.RethrowException(AggregateException e) at Microsoft.VisualStudio.Services.VsTask.InternalGetResult(Boolean ignoreUIThreadCheck) WRN: Assembly binding logging is turned OFF. To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1. Note: There is some performance penalty associated with assembly bind failure logging. To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].

Does this suggest I install a later version of VS2022?

[andrew_4619]

Yes I get that message on the last few updates and it will persist until to say "no". I have not found any adverse effects...

[Stephen_Sutcliffe]

I also got this message and put it on this forum yesterday along with numerous other issues but my post got moved to Intel Installation forum by Ron Green without any reason thus blocking anyone from accessing it. I must have written something controversial and been cancelled!

The reply I got on this matter on the installation was to get onto Microsoft or try Repairing by reinstalling. I tried the repair but it didn't fix it and I have no desire to contact Microsoft on this matter. So far I've not had any adverse effects though not fully tested it yet.

Does your x64 IFX & IFORT compiler selection dialogs in Tools-Options menu look OK? Mine have very small boxes making it impossible to see which version is selected.

My post also highlighted some IFX FORTRAN issues relating to ICEs in release mode with optimisation set (only fixed by turning it off with /Od for offending files) and a warning to say that /check:uninit (set in my debug version) is not currently available on Windows.

Steve

[Ron_Green]

@Stephen_Sutcliffe I moved your issue to the Startup Support team who have a lot more experience with VS integration issues.  I thought you have a better chance of getting it resolved over there.  I will see if they have made any progress.  I'm happy to move it back to this Forum if you want.

[Stephen_Sutcliffe]

@Ron_Green My post was in 2 parts, the first relating to VS integration and second to IFX Fortran specific issues which are the more critical for me. I mentioned the VS observations to just see if anyone else had seen similar behaviour and point out that VS seems to update itself without you, the user, having any control even if it is not deemed validated for the Intel integration. Why doesn't the Intel installer warn you if your current VS version has not been validated for the OneAPI version being installed? This check should maybe be added to the installer page relating to VS version.

The Fortran IFX ICE issues were investigated on previous version via Premier Support and as they are still there, I wondered if/when these are due to be fixed. The suggested workaround, by Barbara, was to disable optimisation /Od in affected files which did work, but is not ideal as it may affect performance and would have to be reset once a fix has been completed.

The Fortran related part of my original post is reproduced below:

Issues relating specifically to IFX vs IFORT are:

I have still to successfully compile and link my full project solutions without compromises (which contains 36 projects) in IFX so will have to keep on using IFORT until these get resolved. I am only using the x64 compilers.

1) The Release build won't compile many files unless the Optimisation (/Od) is fully disabled in some (though not all of the files). None of the other optimisation options work. I have previously reported these ICEs (with example reproducer) after trying previous issue back in December to Premier Support, so sadly it appears that this issue has still not been resolved. I did use the suggested workaround (to disable the optimisation) so some progress of sorts. The change in this setting could well have a detrimental affect the speed of the program compared to IFORT. After changing to /Od the program does actually link and run in Release mode from within VS.

As Intel should be already aware of such issues, it would be useful to know if they have made any progress on a fix, or at least identified what is causing the ICE. Maybe my coding is to blame but I don’t see any obvious pattern. I don’t use any multi-core stuff.

2) The Debug compilation build is issuing messages saying that the /check:uninit is not currently available on Windows. Is there an alternative to this compiler option in IFX or will it be made available in a later release or has it been deprecated?

3) During the linking phase of the Debug configuration I get seemingly random messages which quote odd individual files within libraries like:

fatal error LNK1220: 'resolving static reference symbol' requires '/WOWA64' specification

The sooner I can successfully migrate to IFX the better as I won't have to waste time and space having to maintain the IFORT version as a backup.

Any feedback from Intel would be much appreciated?

I don't believe having to go through the pain of creating a reproducer (again) will be of much benefit in these cases as they seem to relate to potentially unsupported features or issues I have had looked at before (with reproducer etc.) via Premier Support.

The /WOWA64 errors in Debug linking, I hope can be explained by the compiler specialists.  I have tried a full clean/rebuild cycle but this has no effect.

Thanks

Steve

[Stephen_Sutcliffe]

Contrary to my earlier response relating to the Installation warning I since have noticed that the VS Option to change Intel Compilers is now greyed out. 

[Devorah_H_Intel]

To resolve the 'warning' issue - please open the installer.exe located in C:\Program Files (x86)\Intel\oneAPI\Installer. Then click Modify inside HPC Toolkit Box and select Repair to run.

[Mark_Lewy]

@Devorah_H_Intel I tried repairing the HPC Toolkit to no avail.  I note from the log message that it's looking for Microsoft.VisualStudio.Threading, Version=17.8.0.0.  My version of Visual Studio is 17.7.5 (too early?).  I was planning to upgrade to 17.9.2, which is the validated version for OneAPI 2024.1, rather than the latest available version.

[Devorah_H_Intel]

---

@Mark_Lewy wrote:

This is what I'm getting:

---------------------------
Microsoft Visual Studio
---------------------------
The 'OneApiPackage' package did not load correctly.

The problem may have been caused by a configuration change or by the installation of another extension. You can get more information by examining the file 'C:\Users\lewym\AppData\Roaming\Microsoft\VisualStudio\17.0_42808e7e\ActivityLog.xml'.

Restarting Visual Studio could help resolve this issue.

Continue to show this error message?
---------------------------
Yes No
---------------------------

Does this suggest I install a later version of VS2022?

---

If you decide to upgrade Visual Studio, please be aware that version 17.9.5 has not been validated and reportedly has issues with window sizing on laptops.

[Barbara_P_Intel]

@Stephen_Sutcliffe, when you post multiple issues in a single message, issues get lost.

Regarding 2) The Debug compilation build is issuing messages saying that the /check:uninit is not currently available on Windows. Is there an alternative to this compiler option in IFX or will it be made available in a later release or has it been deprecated?

There is a feature request to get /check:uninit working on Windows. It is available on Linux.

[Barbara_P_Intel]

@Stephen_Sutcliffe, regarding "The Fortran IFX ICE issues were investigated on previous version via Premier Support and as they are still there, I wondered if/when these are due to be fixed." Please post a comment on the Premier Support ticket. The TCE (Technical Consulting Engineer) who is assigned can give you an update. 

AND there are a number of bug fixes coming in the release planned for mid 2024.