Problem/Error: Abaqus 2019 with Visual Studio and Intel OneAPI

[Alex98]

Hey,

I've installed Abaqus 2019 with Visual Studio 2019 and the recent Intel OneAPI Base Toolkit and HPC Toolkit (as I can't access an older version of them).
Running the checks to verify the link of Abaqus and the Fortran Compiler, I get confirmation that the Fortran Compiler is there upon entering "abaqus info=system" in the Abaqus Command.
However, running "abaqus verify -user_std" triggers an error for all the tests using a subroutine. All the other test pass.
I get the following output in the .log file:

"

Analysis initiated from SIMULIA established products
[...]
Begin Compiling Abaqus/Standard User Subroutines
10/7/2024 4:27:24 PM
Intel(R) Fortran Intel(R) 64 Compiler Classic for applications running on Intel(R) 64, Version 2021.13.1 Build 20240703_000000
Copyright (C) 1985-2024 Intel Corporation. All rights reserved.

ifort: remark #10448: Intel(R) Fortran Compiler Classic (ifort) is now deprecated and will be discontinued late 2024. Intel recommends that customers transition now to using the LLVM-based Intel(R) Fortran Compiler (ifx) for continued Windows* and Linux* support, new language support, new language features, and optimizations. Use '/Qdiag-disable:10448' to disable this message.
End Compiling Abaqus/Standard User Subroutines
Begin Linking Abaqus/Standard User Subroutines
Creating library standardU.lib and object standardU.exp
End Linking Abaqus/Standard User Subroutines
10/7/2024 4:27:25 PM
Begin Analysis Input File Processor
10/7/2024 4:27:25 PM
Run pre.exe
10/7/2024 4:27:28 PM
End Analysis Input File Processor
Begin Abaqus/Standard Analysis
10/7/2024 4:27:28 PM
Run standard.exe
10/7/2024 4:27:29 PM
Abaqus Error: Abaqus/Standard Analysis exited with an error - Please see the
message file for possible error messages if the file exists.
Begin Convert MFS to SFS
10/7/2024 4:27:31 PM
Run SMASimUtility.exe
10/7/2024 4:27:31 PM
End Convert MFS to SFS
Abaqus/Analysis exited with errors
"

Can somebody help me resolve this problem? I already lost 2-3 days on this.
Thanks in advance.
Alex

[Ron_Green]

Caveat: I do not run Abaqus.  But an older thread

https://community.intel.com/t5/Intel-Fortran-Compiler/How-to-Use-Intel-s-Fortran-Compiler-with-Abaqus/m-p/1359606

had this intriguing clue ( scroll down 2/3 of the page):

Another developer suggests:

I had trouble running Abaqus with a “user subroutine” that I had built using oneAPI (on Windows in this case).  The simulation would start and then abruptly end without any error message.

The root cause was as follows.  I had (incorrectly) used a Fortran “stop” statement in my Abaqus user subroutine instead of the vendor-recommended XIT() procedure (I should have used “call XIT()”).

In oneAPI versions of ifort, the “stop” statement is linking to a for_stop_quiet() procedure in the runtime libs.  Apparently, older compilers called for_stop() and it seems for_stop_quiet() is new to oneAPI versions so the new procedure does not exist in older ifort runtime libs.

The problem is that recent versions of Abaqus are still distributed with older (pre-oneAPI) versions of the ifort runtime which do not contain the needed for_stop_quiet() procedure.  As a result, if you compile your user subroutine with oneAPI but then do not make sure the oneAPI runtime libs are first in the Abaqus path, the dll will try to link to the older ifort runtime that is missing the needed for_stop_quiet() procedure so the code just aborts.

I believe the newest versions of Abaqus finally have a oneAPI version of the ifort runtime libs.

The forum user may be able to resolve their issue by eliminating any “stop” or “error stop” statements and replacing with “call XIT()”.  Alternatively, they could also make sure that the oneAPI “setvars” is properly integrated into the Abaqus environment.

[Alex98]

Hey Ron,

thanks for getting back to me with this post.
I read through it but I'm not sure if I understood it correctly.
As I'm only running the verification subroutine of Abaqus std_user.for, I couldn't find a "stop" statement in the Fortran file, so I don't think that is the problem.
Or do I have to check somewhere else/another file, if there is a "stop" statement.

It's so weird bcs the compiler seems to be correctly linked according to the screenshot...

Thanks in advance.
Alex

[Ron_Green]

This may be something that Abaqus has to answer.  I don't see anything helpful in the log file.