oneAPI Fortran compiler installation can't see VS2019

[mmb]

I'm trying to install the oneAPI Fortran compiler and it fails the prerequisites check. It says it can't find the IDE even though I do have a compatible version of Visual Studio 2019 installed. It works fine when I install on a standalone network machine but on the company networked machine with exactly the same VS2019 standard and using the same the oneAPI installer files it can't see VS2019 and fails the IDE prerequisites check.

[JohnNichols]

VS 2019 is getting long in the tooth, I would suggest 2022, as it is recommended obliquely by Intel.  There is a recent Fortran Post about this from Intel on this forum. 

[mmb]

Thanks for the reply. For the moment I'm tied to using VS2019. I don't think that's the problem though as the same version of VS2019 and the intel complier work fine on a standalone machine. So I think it must be something about the security policy of the network machine that is stopping the Intel install from recognising the IDE is actually there. I know if I throw it back to the IT support contractor  (DXC) they won't be able to solve it (another colleague already tried) - so I was trying if possible to understand the mechanism by which the Intel install identifies the presence of a suitable IDE. Visual studio is installed in the standard default location on C drive. I've tried all the suggestions I can find on the topic but failed to find anything that worked or anyone with exactly the same problem.

[Steve_Lionel]

Currently, the Intel compiler supports VS2019 and 2022, but not 2024.  I suggest checking Installing Microsoft Visual Studio* for Use with Intel® Compilers to make sure your VS install is set up correctly.

[JohnNichols]

There is no 2024, there is Preview 2022, which we can assume will be VS 2025 ultimately of some such.  Fortran has no problems with the preview will the code I run. 

[mmb]

Thanks Steve - I did check the approved list on the Intel website and the combination I'm using should be ok. As I said it works fine on a standalone machine but not on the networked machine. I'm assuming it must be something to do with the win10 build or security policy settings but unfortunately I don't have local control to change any of that. I was hoping if I could figure out what the problem was by knowing the route via which the compiler checks for Visual Studio then I could report that to the IT support group (contracted out) and might be able to get it resolved. Thanks for you advice though.

[Devorah_H_Intel]

The installer uses COM interface from a Microsoft’s DLL to detect what Visual Studio instances are available on the system. Each instance has its status, for example:

03/01/2023 17:53:20:327 : 14780 : MESSAGE : **************** Instance info *****************
03/01/2023 17:53:20:327 : 14780 : MESSAGE : InstanceId : 80496564
03/01/2023 17:53:20:327 : 14780 : MESSAGE : IsComplete : true
03/01/2023 17:53:20:327 : 14780 : MESSAGE : IsLaunchable : true
03/01/2023 17:53:20:327 : 14780 : MESSAGE : InstallationState : The instance represents a complete install
03/01/2023 17:53:20:327 : 14780 : MESSAGE : InstallationVersion: 17.5.33424.131
03/01/2023 17:53:20:327 : 14780 : MESSAGE : InstallationPath : C:\Program Files\Microsoft Visual Studio\2022\Professional
03/01/2023 17:53:20:327 : 14780 : MESSAGE : ProductId : Microsoft.VisualStudio.Product.Professional
03/01/2023 17:53:20:327 : 14780 : MESSAGE : ProductPath : Common7\IDE\devenv.exe
03/01/2023 17:53:20:327 : 14780 : MESSAGE : DisplayName : Visual Studio Professional 2022
03/01/2023 17:53:20:327 : 14780 : MESSAGE : ************************************************

The installer only considers V Studios which are IsComplete and IsLaunchable, so if something is wrong with VS, the installer may not detect it as suitable for integration. You can find similar output in the installer log file like %TEMP%\intel_oneapi_installer\<TIMESTAMP>\installer.<TIMESTAMP>.log

If you are able to provide the logs, we will take a look. Please use PM to provide your logs.

[mmb]

Thanks very much - I've PM'd you some excerpts from that installer file. Looks like it does see VisualStudio but 'IsComplete' is set to false and 'InstallationState' set to 'The instance state has not been determined'.