Invoking SAS or attempting to create ODS Graphics output might result in the following errors in the SAS log:
Error: Java repository file(s) are missing or inaccessible.
Error: Unable to initialize the ODS classpath during SAS startup.
Error: Exception text: For one or more plug-in requests, no matching plug-ins were found in repository.
In most situations, performing the following steps can circumvent the issue.
- Shut down any running SAS sessions.
- Open one of the following directories, depending on your operating system:
Microsoft Windows: !SASROOT\SASVersionedJarRepository\eclipse
UNIX: !SASROOT/SASVersionedJarRepository/eclipse
In the directory path, !SASROOT is your default SAS installation directory. For most installations of SAS on a Windows system, this directory is typically the following Windows directory: C:\Program Files\SASHOME.
- In the directory, locate the following file:
com.sas.app.launcher.cacheFile
Rename this file as follows:
com.sas.app.launcher.old
- Restart SAS. However, restart SAS as an administrator. Note that you have to run as administrator only this first time. After you restart SAS, SAS should then re-create the com.sas.app.launcher.cacheFile file.
If these steps do not circumvent the issue, in most cases you either need to do a complete re-installation of SAS or upgrade to the latest production release of SAS (if you are not currently running the latest production release). Note: The latest production release of SAS is SAS® 9.4M7 (TS1M7).