Solo Troubleshooting

The following sections may be of assistance if you are having problems with Solo.

Downloading Problems

If you have trouble downloading Solo, make sure you're using a current version of a web browser with packet checking. We suggest Firefox 3 or newer.

http://www.mozilla.com/en-US/firefox/

Installation / Starting Problems

Windows

Not Responding

Try starting Solo using the "Solo_console" shortcut which is located in the main C:/Program Files/EVRI/Solo folder (32-bit only). For 64-bit systems, try starting with the Solo_debug mode, locate the solo_debug.log which is located in the temporary directory. Search for "solo_debug" in your C:/Users/{your username}/ folder.

Fail to Initialize

If Solo doesn't start correctly and or you receive an error similar to "The application failed to initialize properly (0xc0000135)..." (or similar numerical code), or "This application has failed to start because the application configuration is incorrect. Reinstalling the application may fix this problem." Use one of the following links:

32-Bit Windows

Version 6.3 and later

Try installing this Microsoft Library package:

• MVC 2005 SP1 Redistributable Package (VCREDIST_x86.exe)

If Solo still does not start, follow the directions for older versions (below).

Version 6.2 and earlier

Try installing the .NET framework 1.1:

• The .NET 1.1 package for 32-bit windows (x86)

64-Bit Windows

Try installing this Microsoft Library package:

• MVC 2005 SP1 Redistributable Package (VCREDIST_x64.exe)

For other situations, contact Eigenvector at helpdesk@eigenvector.com

MAC

If Solo does not launch properly, follow the instructions listed below for error and bug reports, and provide answers to the following questions to helpdesk@eigenvector.com

• Does the X11 application launch?
• In addition to the X11 application, do any additional icons show up in the Dock after attempting to launch?
• Is the CPU in your Mac computer of the Intel architecture, rather than PowerPC?

LINUX

If when staring Solo on Fedora Linux I you the message: "SELinux is preventing .../EVRI_lib from performing execstack access on a process", then the SELinux security application is preventing Solo (or other stand-alone application) from running parts of its library.

To enable the application to run as expected, set the current directory to be the folder where the 'EVRI_lib' file resides (usually the top-level Solo, Solo_Predictor, or Solo+MIA folder) and use the command:

chcon -t execmem_exec_t EVRI_lib

Running this command will usually require you to be logged in as root or to use "sudo".