Component 007
Subgroup 01: Package com.novell.jcc.cert
Subgroup 02: Package com.novell.jcc.client
Subgroup 03: Package com.novell.jcc.handler
Subgroup 04: Package com.novell.jcc.proxy
Subgroup 05: Package com.novell.jcc.schedule
Subgroup 06: Package com.novell.jcc.server
Subgroup 07: Package com.novell.jcc.servlet
Subgroup 08: Package com.novell.jcc.sockets
Subgroup 09: Package com.novell.jcc.util
|
Event Code |
Description |
Remedy |
|---|---|---|
|
100701002 |
Cannot interpret PKCS12 data for CertCommand |
Cause: The PKCS12 package was corrupted in transit or contained a certificate with a unsupported level encryption for the Java security provider (such as 4096 bit support). Action: Verify that you are using a supported certificate size and try the operation again. |
|
100701003 |
Set key entry failed on [store name] |
Cause: The Java keystore password became out of sync with the admin server, or an IO error occurred. Action: Try operation again, otherwise submit the app_sc.0.log and jcc-0.log.0 files for resolution. |
|
100701004 |
KeyStoreException - set certificate entry failed |
Cause: The Java keystore password became out of sync with the admin server, or an IO error occurred. Action: Try operation again, otherwise submit the app_sc.0.log and jcc-0.log.0 files for resolution. |
|
100701005 |
KeyStoreException - delete entry failed |
Cause: A keystore entry for the specified alias does not exist. Action: Verify the previous key import commands were successful. Otherwise, submit the app_sc.0.log and jcc-0.log.0 files for resolution. |
|
100701006 |
Exception - key usage extension failed |
Cause: The key usage extension specified by the administration console was invalid. Action: Submit the app_sc.0.log and jcc-0.log.0 files for resolution. |
|
100701007 |
Exception - get alternate name extension failed |
Cause: Alternate name format specified by the administration console was invalid. Action: Submit the app_sc.0.log and jcc-0.log.0 files for resolution. |
|
100701008 |
KeystoreInfo class has not been initialized |
Cause: Likely a previous error occurred during keystore initialization. Action: Submit the jcc-0.log.0 file for resolution. |
|
100701009 |
[key file] is missing required information for keystore named [keystore name] |
Cause: The keystore information supplied at installation is missing or corrupt. Action: Reinstall. Otherwise submit the jcc-0.log.0 file for resolution. |
|
100701010 |
[key file] is missing |
Cause: The keystore information supplied at installation is missing or corrupt. Action: Uninstall and reinstall the server component. Otherwise submit the jcc-0.log.0 file for resolution. |
|
100701011 |
Exception - close keystore (persisting) failed |
Cause: Could not write the key to the keystore. Action: Try the operation again. Otherwise, submit the jcc-0.log.0 file for resolution. |
|
100701012 |
Exception - eDirectory keystore initialization failed |
Cause: Could not connect to the config store. Action: Restart the server. |
|
100701013 |
Exception - Java keystore initialization failed |
Cause: The password to the keystore was incorrect, or the keystore file could not be opened. Action: Verify the keystore exists, and try the operation again. Otherwise, submit the jcc-0.log.0 file for resolution. |
|
100701014 |
Exception PKCS12 keystore initialization failed |
Cause: The password to the PKCS12 key was incorrect. Action: Submit the jcc-0.log.0 file for resolution. |
|
100701015 |
Exception - loading keystore failed |
Cause: The encrypted keystore_info.xml file could not be read. Action: Reinstall the server component. Otherwise, submit the jcc-0.log.0 file for resolution. |
|
Package com.novell.jcc.client |
||
|
100702001 |
Exception sending alert |
Cause: Alert could not be sent to the Admin Console. Action: Make sure the server can communicate with the administration console. Otherwise, submit the jcc-0.log.0 file for resolution. |
|
100702002 |
Could not create default response XML |
Cause: A problem occurred creating the default XML document. Action: Submit the jcc-0.log.0 file for resolution. |
|
100702003 |
Exception while building alert request: [exception], retrying |
Cause: The alert information was not saved in XML correctly. Action: Submit the jcc-0.log.0 file for resolution. |
|
100702004 |
Configuration for Device Manager not set |
Cause: The settings file determining where to send the alert was not found. Action: Restart the novell-jcc service. Otherwise, submit the jcc-0.log.0 file for resolution. |
|
100702005 |
Error getting configuration for Device Manager |
Cause: There was a problem reading the settings file. Action: Restart the novell-jcc service. Otherwise, submit the jcc-0.log.0 file for resolution. |
|
100702006 |
Alert could not be sent |
Cause: The response from the administration console was not successful. Action: The system will try indefinitely to resend the alert. Make sure the administration console is functioning. Otherwise, submit the jcc-0.log.0 file for resolution. |
|
100702007 |
Bad health URL |
Cause: The IP address or port setting for the administration console has been corrupted. Action: Make sure the settings.properties file contains correct information. Restart the novell-jcc service. |
|
100702008 |
Error sending alert |
Cause: The system cannot communicate with the administration console. Action: Make sure the system can communicate with the administration console and that it is functioning properly. |
|
100702009 |
Error sending alert |
Cause: The system cannot communicate with the administration console, or some other communication error occurred. Action: Make sure the system can communicate with the administration console and that it is functioning properly. |
|
100702010 |
Exception - connection disconnect failed |
Cause: An error occurred with reading the alert response or a disconnect error occurred. Action: Make sure the system can communicate with the administration console and that it is functioning properly. |
|
100702011 |
Queued alerts cannot be saved |
Cause: The class structure has likely changed or the alertdispatch.dat file could not be created. Action: The error is non-fatal, continue running service. |
|
100702012 |
Queued alerts cannot be restored |
Cause: The code has likely changed or the alertdispatch.dat file could not be read. Action: The error is non-fatal, continue running service. |
|
100702013 |
Exception - setting keystore or trust store failed |
Cause: The keystore_info.xml file was corrupt or does not exist. Action: Reinstall the server component. Otherwise, submit the jcc-0.log.0 file for resolution. |
|
100702014 |
Exception getting health from [service name] |
Cause: Could not communicate to obtain the health from named component. Action: Restart the service. Otherwise, submit the jcc-0.log.0 file for resolution. |
|
100702015 |
Exception creating health XML |
Cause: A problem occurred reading health data while creating the health XML. Action: The operation will retry. If it persists, submit the jcc-0.log.0 file for resolution. |
|
100702016 |
MalformedURLException - Bad health URL |
Cause: The IP address or port setting for the administration console has been corrupted. Action: Make sure the settings.properties file contains correct information. Restart the novell-jcc service. |
|
100702017 |
Error sending periodic health |
Cause: The system cannot communicate with the administration console. Action: Make sure the system can communicate with the administration console and that it is functioning properly. |
|
100702018 |
Error sending periodic health |
Cause: The system cannot communicate with the administration console, or some other communication error occurred. Action: Make sure the system can communicate with the administration console and that it is functioning properly. |
|
100702019 |
Crypto key not found |
Cause: The jcc.keystore file was not found. Action: Make sure the installation completed successfully, and that the novell-jcc service is running. Otherwise, submit the jcc-0.log.0 file for resolution. |
|
100702020 |
Error calling initializationComplete/serviceStopComplete |
Cause: An RMI error occurred communicating with the novell-jcc service. Action: Make sure the installation completed successfully, and that the novell-jcc service is running. Otherwise, submit the jcc-0.log.0 file for resolution. |
|
100702021 |
Server is not connected |
Cause: The novell-jcc service is not running. Action: Make sure the installation completed successfully, and that the novell-jcc service is running. Otherwise, submit the jcc-0.log.0 file for resolution. |
|
100702022 |
Error binding to RMI port |
Cause: The novell-jcc service is not running, or the RMI ports are already bound by some other process. Action: Make sure the installation completed successfully, and that the novell-jcc service is running. Otherwise, submit the jcc-0.log.0 file for resolution. |
|
100702023 |
Error registering with server |
Cause: The component could not register with the novell-jcc service. Likely and RMI communication error. Action: Restart the novell-jcc service. If the problem persists, submit the jcc-0.log.0 file for resolution. |
|
100702024 |
Cannot contact server; retrying |
Cause: The novell-jcc service was stopped, likely temporarily. Action: Make sure that the novell-jcc service is running. Otherwise, restart it. If the problem persists, submit the jcc-0.log.0 file for resolution. |
|
100702025 |
Error sending alert to server |
Cause: An RMI communication error likely occurred while sending an alert to the novell-jcc service. Action: Make sure that the novell-jcc service is running. Otherwise, restart it. If the problem persists, submit the jcc-0.log.0 file for resolution. |
|
100702026 |
Queued alerts cannot be saved |
Cause: An RMI communication error likely occurred while saving alerts through the novell-jcc service. Action: Make sure that the novell-jcc service is running. Otherwise, restart it. If the problem persists, submit the jcc-0.log.0 file for resolution. |
|
100702027 |
Queued alerts cannot be restored |
Cause: The [name]-alerts.dat file was corrupted. Action: The error is non-fatal, but monitor the file system for further problems. |
|
Package com.novell.jcc.handler |
||
|
100703001 |
Exception - Response creation failed |
Cause: A problem occurred creating the default XML document. Action: Submit the jcc-0.log.0 file for resolution. |
|
100703002 |
Exception - Response creation failed |
Cause: The default response information was not saved in XML correctly. Action: Submit the jcc-0.log.0 file for resolution. |
|
100703003 |
Error executing command: response is null |
Cause: Command response from a server component was not set. Action: Submit the jcc-0.log.0 file for resolution. |
|
100703004 |
Bad URL from Device Manager "+responseURL+ |
Cause: The URL given by the administration server was incorrect. Action: Submit the jcc-0.log.0 and app_sc.0.log files from the admin console for resolution. |
|
100703005 |
Command error |
Cause: The protocol used in response to the command was malformed. Action: Submit the jcc-0.log.0 file for resolution. |
|
100703006 |
Command response error, retry # |
Cause: The Administration Console is likely temporarily down or restarting. Action: Allow for retry to occur. If all retries fail, ensure that the Administration Console is up and functioning. |
|
100703007 |
Major or minor version not supplied [version] |
Cause: A server component did not supply the required version information. Action: Submit the jcc-0.log.0 file for resolution. |
|
100703009 |
Content-Length header [total] and actual data length [read] mismatch |
Cause: The data read did not match the expected length. Action: Restart the server component. If the problem persists, submit the jcc-0.log.0 file for resolution. |
|
100703010 |
Could not connect to [URL] |
Cause: Could not communicate with the Administration Console or the server component. Action: Make sure the system can communicate with the Administration Console and is operating. If the URL is 127.0.0.1, restart the server component. |
|
100703011 |
Exception - stats response creation failed |
Cause: Could not convert stats XML to be sent to the Administration Console. Action: Submit the jcc-0.log.0 file for resolution. |
|
100703012 |
Exception - version response creation failed |
Cause: Could not convert version XML to be sent to the Administration Console. Action: Submit the jcc-0.log.0 file for resolution. |
|
Package com.novell.jcc.proxy |
||
|
100704001 |
Exception - Cipher socket create key failed |
Cause: Could not create socket cipher key. Action: Submit the jcc-0.log.0 file for resolution. |
|
100704002 |
AGProxy has not initialized as client is null |
Cause: The proxy subcomponent is not initialized. Action: Restart the novell-jcc service. Otherwise, submit the jcc-0.log.0 file for resolution. |
|
100704003 |
Command returned: [response code] [response message], Retry # |
Cause: The Access Gateway is processing a previous command. Action: Allow the retry to occur. If it persists, restart the server. |
|
100704004 |
Error sending [name] command |
Cause: Could not send the command to the Access Gateway. Action: If the problem persists, restart the server. Otherwise submit the jcc-0.log.0 file for resolution. |
|
100704005 |
Could not send alert |
Cause: A problem occurred while sending alert. Action: This is a non-fatal error. If the problem persists, submit the jcc-0.log.0 file for resolution. |
|
100704006 |
Exception - update password failed |
Cause: Could not read the config user password. Action: Restart the server. Otherwise, submit the jcc-0.log.0 file for resolution. |
|
100704007 |
ecc.cfg does not exist! |
Cause: A problem during the installation process occurred. Action: Submit the jcc-0.log.0 file for resolution, then reinstall the server. |
|
100704008 |
Error loading ecc.cfg |
Cause: Could not read the ecc.cfg file. Action: Allow the operation to retry, otherwise, submit the jcc-0.log.0 file for resolution. |
|
100704009 |
Stopped waiting for JCC server |
Cause: The server didn't initialize in a timely manner. Action: Restart the novell-jcc service. |
|
100704010 |
Cannot write ecc.cfg |
Cause: Could not write the specified config file. Action: Allow the operation to retry. If it persists, restart the server. |
|
100704011 |
Error reading configuration |
Cause: Could not parse Access Gateway configuration data. Action: Allow the operation to retry. If it persists, submit the jcc-0.log.0 file for resolution and restart the server. |
|
100704012 |
Cannot write ecc.cfg |
Cause: Could not write specified file. Action: Allow the operation to retry. If it persists, submit the jcc-0.log.0 file for resolution and restart the server. |
|
100704013 |
Exception - check esp status failed |
Cause: An RMI error occurred while communicating to the ESP component. Action: Allow the operation to retry. If it persists, submit the jcc-0.log.0 file for resolution and restart the server. |
|
100704014 |
Error reading password |
Cause: Could not read the config user password. Action: Restart the server. Otherwise, submit the jcc-0.log.0 file for resolution. |
|
100704015 |
Exception - Cipher socket create key failed |
Cause: Could not create socket cipher key. Action: Submit the jcc-0.log.0 file for resolution. |
|
100704016 |
Load settings failed |
Cause: The settings could not be loaded for Linux AG. Action: Restart the novell-jcc service. Otherwise, submit the jcc-0.log.0 file for resolution. |
|
100704017 |
LAGProxy has not initialized as client is null |
Cause: The proxy subcomponent is not initialized. Action: Restart the novell-jcc service. Otherwise, submit the jcc-0.log.0 file for resolution. |
|
100704018 |
Could not send alert |
Cause: An error occurred while sending an alert. Action: This is a non-fatal error. If it persists, restart the novell-jcc service. |
|
100704019 |
Stopped waiting for JCC server |
Cause: The server didn't initialize in a timely manner. Action: Restart the novell-jcc service. |
|
100704020 |
Error reading configuration |
Cause: Could not parse Access Gateway configuration data. Action: Allow the operation to retry. If it persists, submit the jcc-0.log.0 file for resolution and restart the server. |
|
100704021 |
Exception - setting VCC ID failed |
Cause: Could not write the config.xml file with the original ID. Action: This error would occur during the re-import process. Click on the Administration Console to resolve. Otherwise, submit jcc-0.log.0 file for resolution. |
|
100704022 |
Linux Proxy is not running |
Cause: The proxy novell-vmc service has stopped responding. Action: to restart the proxy service, enter the following command as root user: /etc/init.d/novell-vmc restart |
|
100704023 |
SSL VPN load settings failed |
Cause: The settings could not be loaded for SSLVPN. Action: Restart the novell-jcc service. Otherwise, submit the jcc-0.log.0 file for resolution. |
|
100704024 |
Exception - Cipher socket create key failed |
Cause: Could not create socket cipher key. Action: Submit the jcc-0.log.0 file for resolution. |
|
100704025 |
Stopped waiting for JCC server |
Cause: The server didn't initialize in a timely manner. Action: Restart the novell-jcc service. |
|
100704026 |
Exception - setting change failed |
Cause: The settings could not be loaded for SSLVPN. Action: Restart the novell-jcc service. Otherwise, submit the jcc-0.log.0 file for resolution. |
|
100704027 |
Exception - override settings failed |
Cause: The settings were changed on the Linux AG, which were to override the SSLVPN settings, but did not. Action: Restart the novell-jcc service. Otherwise, submit the jcc-0.log.0 file for resolution. |
|
100704028 |
Error reading sslvpn.id |
Cause: Could not find the sslvpn.id file for reading. Action: The system should have recovered from this error automatically. If it persists, submit the jcc-0.log.0 file for resolution. |
|
100704029 |
Error writing sslvpn.id |
Cause: An IO error occurred while writing the sslvpn.id file. Action: Restart the novell-jcc service. Otherwise, submit the jcc-0.log.0 file for resolution. |
|
100704030 |
Error writing [file name] |
Cause: An IO error occurred while writing the sslvpn.id file during the reimport process. Action: Restart the novell-jcc service. Click in the Administration Console to resolve. Otherwise, submit jcc-0.log.0 file for resolution. |
|
100704031 |
Error getting SSLVPN stats |
Cause: Could not communicate with SSLVPN service to obtain statistics. Action: To restart the SSLVPN service, enter the following commands: /etc/init.d/novell-sslvpn stop /etc/init.d/novell-sslvpn start |
|
100704032 |
Error getting SSLVPN health |
Cause: Could not communicate with SSLVPN service to obtain the health. Action: To restart the SSLVPN service, enter the following commands: /etc/init.d/novell-sslvpn stop /etc/init.d/novell-sslvpn start |
|
100704033 |
Cannot communicate with SSLVPN |
Cause: Could not communicate with SSLVPN service, which may affect auto-import and other functions from working correctly. Action: To restart the SSLVPN service, enter the following commands: /etc/init.d/novell-sslvpn stop /etc/init.d/novell-sslvpn start You might need to kill the process manually. Do this, enter the following commands: ps ax grep connman If you see any entries displayed other than grep connman, enter the following command: killall -9 connman Then restart the SSL VPN service with the following command: /etc/init.d/novell-sslvpn start |
|
Package com.novell.jcc.schedule |
||
|
100705001 |
Error getting client details |
Cause: An RMI communication error likely occurred. Action: Allow the system to retry the operation. If it persists, submit the jcc-0.log.0 file for resolution. |
|
100705002 |
Error getting client details |
Cause: An RMI communication error likely occurred. Action: Allow the system to retry the operation. If it persists, submit the jcc-0.log.0 file for resolution. |
|
100705003 |
Exception getting stats from [name] |
Cause: The periodic statistics subsystem was not able to get the stats from the server component. Action: Make sure the component is running. If it persists, restart the component. |
|
100705004 |
Exception creating stats XML |
Cause: An error occurred while creating statistics XML data. Action: Submit the jcc-0.log.0 file for resolution. |
|
100705005 |
Bad stats URL |
Cause: The IP address or port setting for the Administration Console has been corrupted. Action: Make sure the settings.properties file contains correct information. Restart the novell-jcc service. |
|
100705006 |
Error sending periodic stats |
Cause: The system cannot communicate with the Administration Console. Action: Make sure the system can communicate with the Administration Console and that it is functioning properly. |
|
100705007 |
Error sending periodic stats |
Cause: The system cannot communicate with the Administration Console, or some other communication error occurred. Action: Make sure the system can communicate with the Administration Console and that it is functioning properly. |
|
100705008 |
Error sending statistics |
Cause: The system cannot communicate with the Administration Console, or some other communication error occurred. Action: Make sure the system can communicate with the Administration Console and that it is functioning properly. |
|
Package com.novell.jcc.server |
||
|
100706001 |
[service name] not registered |
Cause: The server component was already disconnected. Action: This is a non-fatal error. |
|
100706002 |
[service name] not found in registry |
Cause: The specified server component was not found so it could not be unregistered. Action: This is a non-fatal error. |
|
100706003 |
Client list cannot be saved |
Cause: An IO error occurred while saving the list of registered server components. Action: Make sure the file has write access. If the problem persists, submit the jcc-0.log.0 file for resolution. |
|
100706004 |
Client list cannot be restored |
Cause: An IO error occurred while reading the list of registered server components. Action: Make sure the file has read access. If an upgrade has been performed, make sure all components on the system have also been upgraded. If the problem persists, submit the jcc-0.log.0 file for resolution. |
|
100706005 |
Could not stop connector |
Cause: The embedded HTTP server could not be stopped. Action: Allow the system to retry the operation. If it persists, submit the jcc-0.log.0 file for resolution. |
|
100706006 |
No HTTP connectors were added |
Cause: An internal software problem occurred. Action: Submit the jcc-0.log.0 file for resolution. |
|
100706007 |
Exception - setting keystore properties on http connector failed |
Cause: The keystore_info.xml file could not be read, or was corrupted. Action: Submit the jcc-0.log.0 file for resolution. Reinstall if necessary. |
|
100706008 |
Could not start HTTP server. Retry Number: [n] |
Cause: Some other application may be using the port we require to be open. Action: Allow the system to retry the operation. If it persists, submit the jcc-0.log.0 file for resolution. |
|
100706009 |
Exception during jcc shutdown |
Cause: A problem shutting down the embedded HTTP server occurred. Action: This is a non-fatal error. If the problem persists, submit the jcc-0.log.0 file for resolution. |
|
100706010 |
Exception in testing HTTP server |
Cause: An error testing the HTTP server occurred. Action: This is a non-fatal error. |
|
100706011 |
MalformedURLException - HTTP server |
Cause: An error testing the HTTP server occurred. Action: This is a non-fatal error. |
|
100706012 |
Failed to load eDirectory keystore provider |
Cause: Service could not register handler into keystore Java environment handler set. Action: This is a non-fatal error. If the problem persists, submit the jcc-0.log.0 file for resolution. |
|
100706013 |
Missing keystore information file: [key information file]. Certificate Management functions are unavailable |
Cause: An install-time problem occurred where the keystore information file was not created, or was deleted after installation. Action: Submit the jcc-0.log.0 file for resolution. |
|
100706014 |
Exception - command failed |
Cause: The post-keystore update command failed. Action: Try the operation again. Otherwise, submit the jcc-0.log.0 file for resolution. |
|
100706015 |
Exception - cert command failed |
Cause: A certificate operation was unsuccessful. Action: Try the operation again. Otherwise, submit the jcc-0.log.0 file for resolution. |
|
100706016 |
Error during execution |
Cause: The external command did not execute properly. Action: Try the operation again. Otherwise, submit the jcc-0.log.0 file for resolution. |
|
100706017 |
Exception - delete info failed |
Cause: A problem occurred deleting internal information. Action: This is a non-fatal error. |
|
100706018 |
JCC Server startup failed |
Cause: A critical error occurred during the startup of the novell-jcc service. Action: To restart the novell-jcc service, enter the following command: /etc/init.d/novell-jcc restart If the problem persists, submit the jcc-0.log.0 file for resolution. |
|
100706019 |
Embedded HTTP Server already started |
Cause: The internal HTTP server was already started when asked to start. Action: This is a non-fatal error. |
|
100706020 |
Error starting embedded tomcat |
Cause: Another process is likely using the novell-jcc service port (default 1443). Action: Make sure there are no other processes using this port, then restart the service. |
|
100706021 |
RMI problem |
Cause: An error occurred during the shutdown process. Action: This is a non-fatal error. |
|
100706022 |
RMI exception |
Cause: An error occurred during the shutdown process. Action: This is a non-fatal error. |
|
100706023 |
Server did not initialize within 60 seconds |
Cause: A server component initialization message could not be completed as the novell-jcc service is not finished initializing. Action: To restart the novell-jcc service, enter the following command: /etc/init.d/novell-jcc restart If the problem persists, submit the jcc-0.log.0 file for resolution. |
|
100706024 |
Exception - JCC server initialization failed |
Cause: A server component initialization message could not be completed. Action: To restart the novell-jcc service, enter the following command: /etc/init.d/novell-jcc restart If the problem persists, submit the jcc-0.log.0 file for resolution. |
|
100706025 |
Error binding to RMI [port] |
Cause: Another process is likely using the novell-jcc service port (default 1197). Action: Make sure there are no other processes using this port, then restart the service. |
|
100706026 |
Error registering remote object |
Cause: A problem occurred during the RMI bind process. Action: Make sure that all components are of the same build of Access Manager. Then restart novell-jcc service. |
|
100706027 |
Error sending alert |
Cause: A problem occurred sending the import command to the Administration Console. Action: Allow the system to retry the operation. If it persists, submit the jcc-0.log.0 file for resolution. |
|
100706028 |
Error getting client details for import |
Cause: An RMI communication error has occurred between the server component and the novell-jcc service. Action: Make sure the server component is functioning properly and try the operation again. If the problem persists, submit the jcc-0.log.0 file for resolution. |
|
100706029 |
Error sending alert command |
Cause: Problem sending a command-type alert to the Administration Console. Action: Make sure the Administration Console is running. Allow the system to retry the operation. If it persists, submit the jcc-0.log.0 file for resolution. |
|
100706030 |
Exception - get keystore information failed |
Cause: A problem occurred sending the keystore information from the keystore_info.xml file. Action: If the server shows up in the Administration Console, click Otherwise, submit jcc-0.log.0 and app_sc.0.log files for resolution. |
|
100706031 |
Error getting key [key name] to [key file] |
Cause: A problem occurred receiving the assigned keys during a reimport operation. Action: Ensure the Administration Console is operational, perform the steps to re-trigger an auto-import. Otherwise, submit the jcc-0.log.0 and app_sc.0.log files for resolution. |
|
100706032 |
Could not get keystore information for reimport of [service name] |
Cause: A problem occurred receiving the assigned keystore information during a reimport operation. Action: Ensure the admin console is operational, perform the steps to re-trigger an auto-import. Otherwise, submit the jcc-0.log.0 and app_sc.0.log files for resolution. |
|
100706033 |
Exception |
Cause: A problem occurred during a reimport operation. Action: Ensure the admin console is operational, perform the steps to re-trigger an auto-import. Otherwise, submit the jcc-0.log.0 and app_sc.0.log files for resolution. |
|
100706034 |
Exception - get key failed |
Cause: An assigned key could not be obtained during a reimport operation. Action: Allow the operation to retry. Ensure the admin console is operational, perform the steps to re-trigger an auto-import. Otherwise, submit the jcc-0.log.0 and app_sc.0.log files for resolution. |
|
100706035 |
RMI exception during execution of [command name] |
Cause: An RMI communication error occurred while executing a command from the administration console. Action: Try the operation again. If the problem persists, submit the jcc-0.log.0 file for resolution. |
|
100706036 |
RMI exception |
Cause: An RMI communication error occurred while executing a command from the administration console. Action: Try the operation again. If the problem persists, submit the jcc-0.log.0 file for resolution. |
|
100706037 |
Error collecting health from [service name] |
Cause: An RMI communication error occurred while obtaining the health information from a server component. Action: Allow the operation to try again. Make sure the server component is running properly. If the problem persists, submit the jcc-0.log.0 file for resolution. |
|
100706038 |
Error collecting stats from [service name] |
Cause: An RMI communication error occurred while obtaining the stats information from a server component. Action: Allow the operation to try again. Make sure the server component is running properly. If the problem persists, submit the jcc-0.log.0 file for resolution. |
|
100706039 |
RMI exception |
Cause: A communication error occurred. Action: Make sure the server component is running properly. If the problem persists, submit the jcc-0.log.0 file for resolution. |
|
100706040 |
RMI exception |
Cause: A communication error occurred. Action: Make sure the server component is running properly. If the problem persists, submit the jcc-0.log.0 file for resolution. |
|
100706041 |
RMI exception |
Cause: A communication error occurred. Action: Make sure the server component is running properly. If the problem persists, submit the jcc-0.log.0 file for resolution. |
|
100706042 |
RMI exception |
Cause: A communication error occurred. Action: Make sure the server component is running properly. If the problem persists, submit the jcc-0.log.0 file for resolution. |
|
Package com.novell.jcc.servlet |
||
|
100707001 |
Servlet error in [handler name] |
Cause: An error occurred responding to a administration console request. Action: Try the operation again. If the problem persists, submit the jcc-0.log.0 file for resolution. |
|
100707002 |
IO error in [handler name] |
Cause: An IO error occurred while responding to a administration console request. Action: Try the operation again. If the problem persists, submit the jcc-0.log.0 file for resolution. |
|
100707003 |
No client found with ID [service name] |
Cause: The specified server component known to the administration console is not currently running, or cannot communicate with the novell-jcc service. Action: Make sure the server component is running properly. Ensure all components on the system are of the same version and build. Restart the server component. If the problem persists, submit the jcc-0.log.0 file for resolution. |
|
100707004 |
[appliance id] header missing from [IP address] |
Cause: An invalid request was submitted to the novell-jcc service. Action: This is likely an un-authorized login attempt. Locate the remote IP address and follow proper security procedures. |
|
100707005 |
No handler is registered for [query string] |
Cause: An invalid request was submitted to the novell-jcc service. Action: This is likely an un-authorized login attempt. Locate the remote IP address and follow proper security procedures. |
|
100707006 |
Exception registering handler |
Cause: A problem occurred during start up of the novell-jcc service. Action: Make sure the jcc/webapps/jcc/WEB-INF/web.xml file is not corrupt. |
|
Package com.novell.jcc.sockets |
||
|
100708001 |
Could not initialize the cipher |
Cause: The cipher could not be initialized. Action: Try restarting the novell-jcc service. |
|
100708002 |
Could not initialize the cipher |
Cause: The cipher could not be initialized. Action: Try restarting the novell-jcc service. |
|
100708003 |
Error creating socket factory |
Cause: A possible security problem has been attempted, or the jcc.keystore file is corrupt. Action: Check the jcc.keystore timestamp of last the modification, and if it is different than install-time, you might have a security problem. |
|
100708004 |
Could not find keystore_info.xml |
Cause: The install process did not complete successfully. Action :Restart the novell-jcc service. Otherwise, submit the jcc-0.log.0 file for resolution and reinstall the server component. |
|
Package com.novell.jcc.util |
||
|
100709001 |
Error saving settings |
Cause: An IO error occurred while saving install-time settings. Action: Submit the jcc-0.log.0 file for resolution and reinstall the server component. |
|
100709002 |
Error loading settings |
Cause: An IO error occurred while reading install-time settings. Action: Submit the jcc-0.log.0 file for resolution and reinstall the server component. |
|
100709003 |
Error creating JCC key |
Cause: A critical error occurred while creating the certificate for communicating with the administration server. Action: Submit the jcc-0.log.0 file for resolution and reinstall the server component. |
|
100709004 |
Error saving settings |
Cause: An IO error occurred while saving install-time settings. Action: Submit the jcc-0.log.0 file for resolution and reinstall the server component. |
|
100709005 |
Exception - install trusted roots failed |
Cause: A communication error occurred while sending trusted roots to the administration server. Action: Ensure the admin console is running properly. Otherwise, submit the jcc-0.log.0 file for resolution and reinstall the server component. |
|
100709006 |
Could not get keys |
Cause: The default keys could not be obtained from the administration server. Action: Allow the system to retry the operation. If the problem persists, make sure the admin console is operational. Otherwise, submit the jcc-0.log.0 and app_sc.0.log files for resolution. |
|
100709007 |
Error getting esp ID |
Cause: The server component install likely terminated before completion. Action: Reinstall server component. |
|
100709008 |
Exception - configure LAG failed |
Cause: A problem occurred while setting up keystore information for the Access Gateway. Action: Reinstall the server. |
|
100709009 |
Could not get admin name/password from NW |
Cause: An install-time error occurred during the CD-install process. Action: Reinstall the server. |
|
100709010 |
Could not create keystores |
Cause: An error occurred while creating the keystore information during the configuration process. Action: Reinstall the server component. |
|
100709011 |
Exception - get key failed |
Cause: The default key could not be obtained from the administration console during the initial configuration. Action: Ensure the Administration Console is operational, and reinstall the server component. |
|
100709012 |
Exception - Cert not valid |
Cause: The default trusted root obtained from the Administration Console is not yet valid. Action: Make sure the system time and time zone matches that of the Administration Console, then reinstall. |
|
100709013 |
Exception - Cert not valid |
Cause: The default trusted root obtained from the Administration Console is not yet valid. Action: Make sure the system time and time zone matches that of the Administration Console, then reinstall. |
|
100709014 |
Error creating key |
Cause: A critical error occurred writing the jcc.keystore file. Action: Submit the jcc-0.log.0 file for resolution, reinstall the server component. |
|
100709015 |
Exception during configuration |
Cause: A fatal problem occurred during installation. Action: Submit the jcc-0.log.0 file for resolution, reinstall the server component. |
|
100709016 |
Could not open [jcc log file] |
Cause: Make sure the installation succeeded. Action: Restart the server. If the problem persists, submit the jcc-0.log.0 file for resolution. |
|
100709017 |
[path]/settings.properties file does not exist |
Cause: An install-time error occurred. Action: Submit the jcc-0.log.0 file for resolution, reinstall the server component. |
|
100709018 |
No remote management address is set. |
Cause: An IP address has not been specified for the administration console. Action: On the server command-line, set an administration console IP address. |
|
100709019 |
JCC server certificate was not found in: [keystore file] |
Cause: An install-time error occurred. Action: Submit the jcc-0.log.0 file for resolution, reinstall the server component. |
|
100709020 |
Exception reading keystore information |
Cause: The keystore_info.xml file is missing, or corrupt. Or, the internal keystore has been tampered with, or the certificate is expired. Action: Submit the jcc-0.log.0 file for resolution, reinstall the server component. |
|
100709021 |
Exception - get JCC keystore information failed |
Cause: The keystore_info.xml file is missing, or corrupt. Action: Submit the jcc-0.log.0 file for resolution, reinstall the server component. |
|
100709022 |
IllegalArgumentException |
Cause: An internal component made an invalid call. Action: Submit the jcc-0.log.0 file for resolution. |
|
100709023 |
IllegalStateException |
Cause: An internal component made an invalid call. Action: Submit the jcc-0.log.0 file for resolution. |
|
100709024 |
Object could not be saved |
Cause: A system setting file cannot be saved. Action: Submit the jcc-0.log.0 file for resolution. |
|
100709025 |
Object cannot be restored |
Cause: A system setting file cannot be restored. Action: Submit the jcc-0.log.0 file for resolution. |