Usage Note 65191: Invoking SAS® or creating ODS Graphics output might result in "Error: Java repository file(s) are missing or inaccessible"
 |  |  |  |
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).
Operating System and Release Information
| Product Family | Product | System | SAS Release | |
| Reported | Fixed* | |||
| SAS System | Base SAS | Microsoft® Windows® for x64 | 9.3 TS1M0 | |
| Microsoft Windows Server 2003 Datacenter Edition | 9.3 TS1M0 | |||
| Microsoft Windows Server 2003 Enterprise Edition | 9.3 TS1M0 | |||
| Microsoft Windows Server 2003 Standard Edition | 9.3 TS1M0 | |||
| Microsoft Windows Server 2003 for x64 | 9.3 TS1M0 | |||
| Microsoft Windows Server 2008 | 9.3 TS1M0 | |||
| Microsoft Windows Server 2008 R2 | 9.3 TS1M0 | |||
| Microsoft Windows Server 2008 for x64 | 9.3 TS1M0 | |||
| Microsoft Windows XP Professional | 9.3 TS1M0 | |||
| Windows 7 Enterprise 32 bit | 9.3 TS1M0 | |||
| Windows 7 Enterprise x64 | 9.3 TS1M0 | |||
| Windows 7 Home Premium 32 bit | 9.3 TS1M0 | |||
| Windows 7 Home Premium x64 | 9.3 TS1M0 | |||
| Windows 7 Professional 32 bit | 9.3 TS1M0 | |||
| Windows 7 Professional x64 | 9.3 TS1M0 | |||
| Windows 7 Ultimate 32 bit | 9.3 TS1M0 | |||
| Windows 7 Ultimate x64 | 9.3 TS1M0 | |||
| Windows Vista | 9.3 TS1M0 | |||
| Windows Vista for x64 | 9.3 TS1M0 | |||
| 64-bit Enabled AIX | 9.3 TS1M0 | |||
| 64-bit Enabled HP-UX | 9.3 TS1M0 | |||
| 64-bit Enabled Solaris | 9.3 TS1M0 | |||
| HP-UX IPF | 9.3 TS1M0 | |||
| Linux | 9.3 TS1M0 | |||
| Linux for x64 | 9.3 TS1M0 | |||
| Solaris for x64 | 9.3 TS1M0 | |||
Invoking SAS or creating ODS Graphics output might result in the following error messages: "Error: Java repository file(s) are missing or inaccessible" and "Error: Unable to initialize the ODS classpath during SAS startup."
| Type: | Usage Note |
| Priority: |
| Date Modified: | 2019-12-04 15:15:27 |
| Date Created: | 2019-12-03 10:34:28 |