RStudio 1.2.1335, Windows Server 2012 R2, Microsoft R Open 3.5.3 issue

The combination of RStudio 1.2.1335 and Microsoft R Open (MRO) 3.5.3 works fine on Windows 10. However, on Windows Server 2012 R2, this same combination produces the following error (multiple times):

along with the following information and warnings:

Using the Intel MKL for parallel mathematical computing (using -1 cores).
1: In Revo.warning(e$message, ignore = isUnix()) :
  unable to load shared object 'E:/Program Files/Microsoft/R Open/R-3.5.3/library/RevoUtilsMath/libs/x64/RevoUtilsMath.dll':
  LoadLibrary failure:  The operating system cannot run %1.

2: In value[[3L]](cond) :
  "getThreads" not available for .C() for package "RevoUtilsMath"
3: In value[[3L]](cond) :
  "getThreads" not available for .C() for package "RevoUtilsMath"
4: In value[[3L]](cond) :
  "getThreads" not available for .C() for package "RevoUtilsMath"
Error: package or namespace load failed for ‘stats’ in inDL(x, as.logical(local), as.logical(now), ...):
 unable to load shared object 'E:/Program Files/Microsoft/R Open/R-3.5.3/library/stats/libs/x64/stats.dll':
  LoadLibrary failure:  The operating system cannot run %1.

During startup - Warning message:
package ‘stats’ in options("defaultPackages") was not found 
Error in inDL(x, as.logical(local), as.logical(now), ...) : 
  unable to load shared object 'E:/Program Files/Microsoft/R Open/R-3.5.3/library/stats/libs/x64/stats.dll':
  LoadLibrary failure:  The operating system cannot run %1.

Launching Rgui.exe directly from the installation folder does not result in any issues. In particular, the number of available cores (16) is correctly detected.

Initially this seemed like installing a new Visual C++ redistributable package (https://aka.ms/vs/16/release/VC_redist.x64.exe) might fix it, but this was tried with no success. However, replacing the bundled Rlapack.dll in the E:/Program Files/Microsoft/R Open/R-3.5.3/bin/x64 folder with the corresponding one from MRO version 3.5.1 appears to mitigate this, but it is unclear why this interaction happens only on Server 2012 R2 and not Windows 10.

Upon further investigation, this was caused by an old version of libiomp5md.dll in the C:\Windows\System32 folder on the Server 2012 R2 system that should not have been there. Removing it resolved the issue.

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.