Troubleshooting

This section describes some known issues and possible solutions.

• When running a model in Windows, a dialog is shown with title 'Unable to locate component' and content 'The application has failed to start because Rlapack.dll was not found...'.
  This may occur with Windows 2003. Please add your R binary directory (usually 'C:\Program Files\R\R-3.x.x\bin\i386' or 'C:\Program Files\R\R-3.x.x\bin\x64' to the system PATH environment variable.
• When an R session is initialized in Windows, R installs a console handler to detect Ctrl-C events which may prevent Mosel from properly detecting these same events itself.
• In Linux, R may fail to load if the dynamic libraries in $R_HOME/lib cannot be found by the dynamic linker. In this case, please add $R_HOME/lib to the LD_LIBRARY_PATH environment variable.
• This module is not compatible with Mosel security restrictions, therefore it would fail to load if Mosel is run in restricted mode.
• On Mac OS X, if the R release being used is linking the Apple CoreFoundation library, then this module can only be successfully initialized from the main thread of the process in which Mosel is running (because the CoreFoundation library can only be loaded from the main thread of a process). So, for example, the module would fail to load R from an mmjobs submodel and would display an error like 'R: this module requires CoreFoundation framework to be loaded from main thread'. In this case, it is possible to overcome this issue by setting the environment variable DYLD_INSERT_LIBRARIES to /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation (use the correct path to the CoreFoundation library on your system) before launching the Mosel process, thus forcing an anticipated loading of the CoreFoundation library at process creation.