FAQ - Frequently Asked Questions


 Browse FAQ      Browse Documentation Wiki   movie Browse EigenGuide Videos
SearchSearch for Keyword(s):

Issue:

    Solo fails with "mclstart: Unable to initialize PLS_toolbox library check for missing plstoolbox.ctf file" or requires re-installation each startup.

Possible Solutions:

    This error message is most likely due to Windows having invoked one of its user account control safety features which creates a copy of parts of applications in a folder called "virtualstore". This works for some applications but not all. Applications that rely on relative folder paths (as does Solo's underlying library technology) will sometimes fail.

    To resolve the issue:


    1. Go to the Start Menu and type the following in the "Start Search" box: 
         %userprofile%\AppData\local\VirtualStore
      and press Enter to open the folder.

    2. In the VirtualStore folder, navigate to the "Program Files" directory and from there to the "EVRI" folder. Delete the entire EVRI folder. (Note: if you are running a 32-bit version of Solo in 64-bit Windows, you will need to locate the "Program Files (x86)" folder and delete the EVRI folder there)

    3. ONCE: run Solo as administrator (right-click the shortcut and say "run as administrator")



    This should resolve any issues with starting. If it doesn't we've had a user report that the following steps solved the problem:

    1. Search where the plstoolbox.crf file is located. In my case it was in : C:\Program Files\EVRI\Solo\application\runtime\win64

    2. In the same folder right click the "extractCTF64.exe" file and click on run as administrator.

    3. It comes up with several error, saying that some .dll files are missing (e.g. ctfarchiver.dll, etc)

    4. Locate the folder that contains the missing files (it's usually one folder that contains them).

    5. Copy paste ALL the files from the folder (step 4) into the folder from step 1.

    6. Go to C:\Program Files\EVRI\Solo, Solo file and click run as admin again.


Still having problems? Check our documentation Wiki or try writing our helpdesk at helpdesk@eigenvector.com