Installing Abaqus Subroutines

Arguably one of the most difficult steps in using User Subroutines in Abaqus is installing them correctly, and getting them to work! To help you overcome this first obstacle, we have produced a guide to walk you through the process.

In the following example, MS Visual Studio 2010 Professional and Intel Parallel Studio XE Composer editions were both installed. The install is correct for Abaqus 6.14-2, please adjust Step 3 for your applicable application version. Please see the recommended configurations in links below (some require 3DS login):

If you are using a different version or have any queries, don’t hesitate to contact us.


1. Download and install Microsoft Visual Studio 2010 Professional. You can use Community, Professional or Enterprise, but not the Express edition, that will not work. Visual Studio is your linker that links up your compiled code with the required libraries to use with the Abaqus solver.

The following links for Visual Studio 2010 Professional trial version are available for your evaluation:

a. ISO images (offline installers):

b. Web installers:


2. Download and install a Fortran Compiler

Intel® Parallel Studio XE Composer Edition for Fortran and C++ Windows* Intel® Parallel Studio XE 2016. Parallel Studio is your compiler, it translates your text subroutine into machine code that the computer understands.


3. Check your Microsoft Parallel Processing MPI Interface

The correct version of msmpi needs to be installed on your computer to successfully link your subroutines. It will always be available with your Abaqus installation media. It is important that a newer or older one is not used, as the linker is looking for the specific version! You MUST have the version installed which is available with the Abaqus version you are using. If the wrong version is installed, an error will be displayed during linking: (e.g. LINK : fatal error LNK1181: cannot open input file 'msmpi.lib')

  • For Abaqus 6-14-2 install mpi_3.0_x64.msi (Typically in …\Abaqus614-2\1\win86_64\product\Windows\Disk1\InstData\VM\resource)
  • If a later one is already installed, please uninstall it

Installing Abaqus Subroutines

4. Before you launch your simulation using User Subroutines, you have to set up the correct environmental variables for your compiler and linker. The recommended way is shown below:

a. Execution from command line. Please find your “Abaqus Command” shortcut and adjust as shown. You can usually find Abaqus Command in “Start/All Programs/Abaqus 6.14-2/Abaqus Command” (use the version you would like to set up). There are two additions to make, highlighted below. This is correct when you install everything using default paths on a Windows 64bit (x64) Intel based system.

  • C:\Windows\SysWOW64\cmd.exe /k ""C:\Program Files (x86)\IntelSWTools\compilers_and_libraries_2016.2.180\windows\bin\ifortvars.bat" intel64 vs2010 && "C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\vcvarsall.bat" x64"

Installing Abaqus Subroutines

  • Now your environment variables will be correctly set to run Abaqus with user subroutines from the command window.

b. Using Abaqus/CAE. Similarly to the command line version, please find the correct Abaqus/CAE shortcut and edit. You can usually find the shortcut in: “Start/All Programs/Abaqus 6.14-2/Abaqus CAE”. The settings are also for a Windows 64bit Intel based system.

  • "C:\Program Files (x86)\IntelSWTools\compilers_and_libraries_2016.1.146\windows\bin\ifortvars.bat" intel64 vs2010 && "C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\vcvarsall.bat" x64 && C:\SIMULIA\Abaqus\Commands\abq6142.bat cae || pause

Installing Abaqus Subroutines

  • Note that the syntax of the CAE and command line setup is slightly different. Most users can copy-paste the text provided, when everything is installed using default folders.
  • You have successfully set your environment variables and ready to use User Subroutines using Abaqus/CAE.

We hope this guide was helpful for everybody who’s trying to expand simulation capabilities using Abaqus User Subroutines.

Should you require more information, run into any issues, or require assistance in developing your subroutines, please leave a comment below or don’t hesitate to get in touch.