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.
Installation / Starting Problems
Windows
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
- "The application failed to initialize properly (0xc0150002)..." (or similar numerical code), or
- "This application has failed to start because the application configuration is incorrect. Reinstalling the application may fix this problem." or
- "The application has failed to start because its side-by-side configuration is incorrect."
This generally implies a library is missing or corrupt on your system. Use the following links to install the appropriate library for your operating system and Solo version. For other situations, contact Eigenvector at helpdesk@eigenvector.com
32-Bit Windows
Solo 6.3 and later
- (If Solo still does not start, follow the directions for older versions, below.)
Solo 6.2 and earlier
64-Bit 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.
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
- Is X11 installed? The version of Matlab we use to build Solo requires the X11 window system to be installed. X11 is totally separate from OS X. X11 used to be distributed by Apple as a part of their developer tools but is no longer included. You need to download and install it from the XQuartz project.
- 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?
Trouble installing on OS X 10.8 (Mountain Lion): The Mac Gatekeeper technology can cause Solo to not start ("OSStatus error 100030" or "OSStatus error -67049"). Try the following steps.
- Open System Preferences: Security and Privacy: General
- Unlock the lock to make changes
- Select "Anywhere" from "Allow applications downloaded from"
- Now start Solo
- If it starts, try restarting the computer and confirm Solo continues to start.
- Open System Preferences: Security and Privacy: General
- Unlock the lock to make changes
- Change the setting back to "Mac App Store and Identified developers"
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".