New Post: R.NET failing on library(RODBC) call (and other external libraries)

As skyguy94 says, this sounds like the RODBC package is not on the library search path (distinct from PATH and R_HOME). If R_HOME was incorrectly set/detected, the default packages would not even be be loaded, but they appears to be. If we intuit correctly it is very likely you can fix this issue soon.

Below is an explanation that you may well already know all about, but bear with me that's for completeness for other potential readers.

You may want to report what .libPaths() says from R console and run from your .NET app. via R.NET.

For instance if I logged with local Administrators group privilege, I get the following output. the first entry is because I set a machine-wide R_LIBS environment variable. Being admin, install.packages() would install by default in the first available library path.

> .libPaths()
[1] "c:/Rlib"                            "C:/Program Files/R/R-3.1.0/library"

I think that if I were logged in with standard user-level privilege, I'd get something like the following. install.packges() would install by default in my user specific library, and not be available to other accounts.

> .libPaths()
[1] "c:/Users/username/R/win-library/x.y"                            "c:/Rlib"                            "C:/Program Files/R/R-3.1.0/library"

A relevant section of the R FAQ should offer comprehensive options as to how to manage multiple library locations.

BTW I am not personally doing any work using R.NET from IIS, so for more IIS specific advice you should take knowledgeable advice from skyguy94 and others.

Hope this helps!

Cheers,
J-M