10.2 Error Messages
This topic contains errors that can be seen in the Status Log or DSTrace screen. The Error Condition column contains the error text returned to Identity Manager. The Level column specifies the status level. The Description column describes situations that might cause the condition and possible actions you can take to fix the problem. The message text and status level are recorded in the Driver Identity Manager log.
A SIF Agent Name must be provided
Source:
The status log or DSTrace screen
Explanation:
The SIF Agent name is missing from the driver configuration.
Possible Cause:
The SIF Agent name was not provided during the configuration of the driver.
Level:
Fatal
A Zone URL must be provided
Source:
The status log or DSTrace screen.
Explanation:
A Zone URL is missing from the driver parameters.
Possible Cause:
A Zone URL was not provided during the configuration of the driver.
Level:
Fatal
Authentication level must 0-3
Source:
The status log or DSTrace screen.
Explanation:
There is no authentication level specified.
Possible Cause:
There is no authentication level specified.
Level:
Fatal
Connection to ZIS not yet established
Source:
The status log or DSTrace screen.
Explanation:
The Metadirectory engine sent a command to the driver Subscriber channel. The driver cannot handle the command at this time because it does not have a connection to the ZIS. The engine retries the operation every 30 seconds.
Possible Cause:
There is a communication problem between the driver and the ZIS.
Level:
Retry
Encryption level must be 0-4
Source:
The status log or DSTrace screen.
Explanation:
No encryption level is specified.
Possible Cause:
No encryption level is specified.
Level:
Fatal
Error connecting to Zone = java.io.FileNotFoundException: http://ZISserver/zone1
Source:
The status log or DSTrace screen.
Explanation:
The specified ZIS server cannot be located.
Possible Cause:
The DNS server is not configured properly.
Action:
Use the IP address of the ZIS server instead of a DNS name.
Level:
Error
Error connecting to Zone = java.net.MalformedURLException: no protocol: ...
Source:
The status log or DSTrace screen.
Explanation:
The URL is malformed.
Error connecting to Zone = java.net.SocketException: Connection refused: Connection refused
Source:
The status log or the DSTrace screen.
Explanation:
The driver cannot establish a connection to the ZIS.
Possible Cause:
The ZIS server is up but the ZIS is not running.
Action:
Start the ZIS.
Level:
Error
Error connecting to Zone = javax.net.ssl.SSLException: Received fatal alert: handshake_failure (no cipher suites in common)
Source:
The status log or DSTrace screen.
Explanation:
The SSL handshake failed.
Possible Cause:
The SSL connection is not configured properly.
Action:
Verify that the SSL certificates are valid.
Level:
Error
Error processing sifobjects.conf, code = xxx
Source:
The status log or DSTrace screen.
Explanation:
An error occurred processing the
sifobject.conf file. The status log or DSTrace screen contains additional information.
Possible Cause:
The
sifobject.conf file could not be accessed.
Possible Cause:
The
sifobject.conf file contains errors.
Action:
Verify that the
sifobject.conf file exists and is accessible.
Action:
Verify that the
sifobject.conf file contains no errors.
Level:
Fatal
Error processing sifschema.xml
Source:
The status log or DSTrace screen.
Explanation:
An error occurred processing the
sifschema.xml file. The
sifschema.xml file is required. The status log or DSTrace screen contains additional information.
Possible Cause:
The
sifschema.xml file cannot be accessed.
Possible Cause:
The
sifschema.xml file contains errors.
Action:
Verify that the
sifschema.xml file exists and is accessible.
Action:
Verify that there are no errors in the
sifschema.xml file.
Level:
Fatal
java.io.IOException: HTTPS hostname wrong: should be <x.x.x.x.x>, but cert says <y.y.y.y.y>
Source:
The status log or DSTrace screen.
Explanation:
The specified communications protocol is secure HTTP (HTTPS). The ZIS has sent its public key certificate to the driver for authentication. The certificate cannot be authenticated. The
jssecacerts keystore file contains the server’s CA trusted root certificate but the certificate contains the wrong hostname (cn=).
Possible Cause:
The
jssecacerts keystore file contain the server’s CA trusted root certificate but the certificate contains the wrong hostname (cn=).
Action:
Change the certificate to contain the correct hostname.
Level:
Error
java.net.SocketException: Connection reset by peer: JVM_recv in socket input stream read
Source:
The status log or DSTrace screen.
Explanation:
The driver is expecting a secure connection over HTTPS and the connection is HTTP.
Possible Cause:
The URL for the ZIS is incorrect.
Level:
Error
javax.net.SocketException: Connection timed out: Connection timed out
Source:
The status log or DSTrace screen.
Explanation:
The specified ZIS server cannot be reached.
Possible Cause:
An incorrect address for the ZIS server.
Possible Cause:
A firewall is blocking the connection.
Action:
Verify that the firewall allows the driver to connect to the ZIS server.
Level:
Error
java.net.SocketException: Network is unreachable
Source:
The status log or DSTrace screen.
Explanation:
The driver cannot communicate.
Possible Cause:
TCP/IP is not configured properly.
Action:
Verify that the gateway and subnet mask are correct.
Level:
Error
java.net.SocketException: Software caused connection abort:
Source:
The status log or DSTrace screen.
Explanation:
The driver cannot communicate.
Possible Cause:
TCP/IP is not configured properly.
Action:
Verify that the gateway and subnet mask are correct.
Level:
Error
javax.net.ssl.SSLException: Received fatal alert: bad_certificate
Source:
The status log or DSTrace screen.
Explanation:
The specified communications protocol is secure HTTP (HTTPS) with client authentication.
Possible Cause:
An incorrect or no driver keystore file is specified.
Possible Cause:
An incorrect or no driver certificate password is specified.
Level:
Error
javax.net.ssl.SSLException: Received fatal alert: certificate unknown
Source:
The status log or DSTrace screen.
Explanation:
The specified communications protocol is secure HTTP (HTTPS) with client authentication. The server could not authenticate the client’s key.
Possible Cause:
The client key in the agent keystore file is incorrect.
Possible Cause:
The client’s CA trusted root certificate is not contained in the server’s (ZIS) trusted keystore.
Action:
Generate a new client keystore file.
Action:
Generate a new client CA trusted root certificate with the ZIS server trusted keystore.
Level:
Error
javax.net.ssl.SSLException: Unrecognized SSL handshake.
Source:
The status log or DSTrace screen.
Explanation:
The contacted server is not expecting a secure connection.
Possible Cause:
The specified ZIS URL is not correct.
Action:
Use the ZIS server IP address instead of the DNS name.
Level:
Error
javaz.net.ssl.SSLException: untrusted server cert chain
Source:
The status log or DSTrace screen.
Explanation:
The ZIS has sent its public key certificate to the driver for authentication. The certificate cannot be authenticated.
Possible Cause:
The
jssecacerts keystore file does not contain the server’s CA trusted root certificate.
Action:
Generate a new
jssecacerts keystore file to contain the server’s CA trusted root certificate.
Manage existing users must be ‘yes’ or ‘no’
Source:
The status log or DSTrace screen.
Explanation:
The
field does not have a value.
Level:
Fatal
Migrate not supported when Match Existing Users is set to no
Source:
The status log or DSTrace.
Explanation:
The SIF driver does not process a
command when
is set to
.
Action:
If desired, change
to
.
Level:
Warning
No initialization parameters
Source:
The status log or DSTrace.
Explanation:
On driver initialization, the Metadirectory engine provided no parameters.
Action:
Verify that the Metadirectory engine is properly installed and configured.
Level:
Fatal
No publisher initialization parameters
Source:
The status log or DSTrace.
Explanation:
On driver initialization, the Metadirectory engine provided no parameters.
Action:
Verify that the Metadirectory engine is properly installed and configured.
Level:
Fatal
No subscriber initialization parameters
Source:
The status log or DSTrace.
Explanation:
On driver initialization, the Metadirectory engine provided no parameters.
Action:
Verify that the Metadirectory engine is properly installed and configured.
Level:
Fatal
Source:
The status log or DSTrace.
Explanation:
On driver initialization, the Metadirectory engine provided no parameters.
Action:
Verify that the Metadirectory engine is properly installed and configured.
Level:
Fatal
No Publisher Option Parameter
Source:
The status log or DSTrace screen.
Explanation:
On Publisher channel initialization, the Metadirectory engine provided no Publisher options.
Level:
Fatal
Source:
The status log or DSTrace screen.
Explanation:
No valid poll rate has been specified for the driver.
Level:
Fatal
Poll rate must be an integer value
Source:
The status log or DSTrace screen.
Explanation:
No valid poll rate has been specified for the driver.
Level:
Fatal
SAXException = Missing whitespace before SYSTEM literal URI. null response received
Source:
The status log or DSTrace screen.
Explanation:
The specified URL is not correct. The contacted server is not a ZIS.
Possible Cause:
An incorrect URL was specified during the configuration of the driver.
Level:
Error
SIF Category = xxx, SIF Code = xxx, SIF Description = xxx, yyy
Source:
The status log or DSTrace screen.
Explanation:
An error has been returned from the ZIS. This error is reported to Identity Manager.
Level:
Error
SIF does not support the Move operation
Source:
The status log or DSTrace screen.
Explanation:
The SIF Implementation Specification does not contain the notion of containers.
Level:
Warning
SIF does not support the Rename operation
Source:
The status log or DSTrace screen.
Explanation:
The SIF Implementation Specification does not provide for renaming objects.
Level:
Warning
SIF objects to process not provided
Source:
The status log or DSTrace screen.
Explanation:
The SIF objects to process are not specified in the driver parameters. The values are student, staff, or the names of defined SIF objects.
Level:
Fatal
SIF Schema not available, error processing sifobjects.conf, code=xxx
Source:
The status log or DSTrace screen.
Explanation:
The
sifobjects.conf file is missing or invalid.
Possible Cause:
The file could not be accessed or it contains errors and cannot be processed.
Action:
Verify the
sifobjects.conf file is available and valid.
Level:
Fatal
The Incomplete container must be specified
Source:
The status log or DSTrace screen.
Explanation:
The
field does not contain a valid DN of an organizational unit (container).
Level:
Fatal
The Incomplete container does not reference an Organization Unit
Source:
The status log or DSTrace screen.
Explanation:
The
field does not contain a valid DN of an organizational unit (container).
Level:
Fatal
Unable to add home directory: novell.jclient.JCException: licenseConnection -1 DSERR_IN SUFFICIENT_SPACE
Source:
The status log or DSTrace screen.
Explanation:
The NetWare® system must have sufficient user licenses installed.
Possible Cause:
An available license does not exist that can be used for creating the user home directory.
Action:
Add more user licenses.
Action:
Verify that the licenses for the NetWare server are functional.
Level:
Error
Unsupported Subscriber Channel operation =
Source:
The status log or DSTrace screen.
Explanation:
The Metadirectory engine has passed the driver a command that it cannot convert to a SIF operation.
Level:
Error
Source:
The status log or DSTrace screen.
Explanation:
The Metadirectory engine passed a null document to the Subscriber channel.
Possible Cause:
The Metadirectory engine is not configured properly.
Action:
Verify that the Metadirectory engine is properly installed and configured.
Level:
Error
ZIS connection operational. (This is not an error.)
Source:
The status log or DSTrace screen.
Explanation:
When the driver has established an operational connection with the ZIS, this message is logged. If the connection is lost, an error is logged. When the connection is reestablished, this message is logged. Because only error messages are logged, this message shows in the log file as an error.
Level:
Informational
Zone is not responding = java.net.ConnectException: Connection refused: connect
Source:
The status log or DSTrace screen.
Explanation:
The ZIS is not up or is not accepting connections.
Possible Cause:
The ZIS IP address or port is not correct.
Level:
Error
Zone is not responding = java.net.ConnectException: Operation timed out: connect
Source:
The status log or DSTrace screen.
Explanation:
The specified ZIS server cannot be reached.
Possible Cause:
The ZIS IP address is incorrect.
Level:
Error
novell.jclient.JCException: modifyEntry -672 ERR_NO_ACCESS
Source:
The status log or DSTrace screen.
Explanation:
Driver Security Equals is not defined or does not have sufficient rights to perform operation.
Action:
Verify that the driver has sufficient rights to perform the operations.
Level:
Error
provideUsers is not defined
Source:
The status log or DSTrace screen.
Explanation:
The driver Subscriber channel configuration is not set up correctly.
Action:
Remove the current driver object and add the driver again.
Level:
Fatal
modifyUsers is not defined
Source:
The status log or DSTrace screen.
Explanation:
The driver Subscriber channel configuration is not set up correctly.
Action:
Remove the current driver object and add the driver again.
Level:
Fatal
Source:
The status log or DSTrace screen.
Explanation:
The driver Subscriber channel configuration is not set up correctly.
Action:
Remove the current driver object and add the driver again.
Level:
Fatal
Driver parameter <schools> malformed
Source:
The status log or DSTrace screen.
Explanation:
The driver Subscriber channel configuration is not set up correctly.
Action:
Remove the current driver object and add the driver again.
Level:
Fatal
Driver parameter <schools> parameter is not available
Source:
The status log or DSTrace screen.
Explanation:
The driver Subscriber channel configuration is not set up correctly.
Action:
Remove the current driver object and add the driver again.
Level:
Fatal
School Information zone n does not reference an enabled zone
Source:
The status log or DSTrace screen.
Explanation:
The Zone number specified in the Subscriber channel section of the Global Configuration Values does not reference an enabled Zone.
Level:
Fatal
At least one School Information must be configured when providing users
Source:
The status log or DSTrace screen.
Explanation:
When
is set to
, one or more School information sets must be configured in the Subscriber channel section of Global Config Values.
Level:
Fatal
Connection to ZIS not yet established
Source:
The status log or DSTrace screen.
Explanation:
The driver has not yet established a connection the Zone when an event is received from the Metadirectory engine
Action:
Verify that communication between the driver and the Zone is working.
Level:
Retry
A Search Container must be provided
Source:
The status log or DSTrace screen.
Explanation:
A search container must be specified in the global configuration values.
Level:
Fatal
Zone n - Enabled zone must have a URL
Source:
The status log or DSTrace screen.
Explanation:
In the global configuration values, a Zone is enabled but a URL is not specified or is not correctly formed.
Level:
Fatal
Zone n - Malformed Zone URL =
Source:
The status log or DSTrace screen.
Explanation:
In the global configuration values, a Zone is enabled but a URL is not specified or is not correctly formed.
Level:
Fatal
Zone n - URL not http or https =
Source:
The status log or DSTrace screen.
Explanation:
In the global configuration values, a Zone is enabled but a URL is not specified or is not correctly formed.
Level:
Fatal
Zone n - Incomplete container must be configured for enabled zone
Source:
The status log or DSTrace message.
Explanation:
In the global configuration values, a Zone is enabled but an Incomplete container is not specified.
Level:
Fatal
Zone n - Staff container must be configured for enabled zone
Source:
The status log or DSTrace screen.
Explanation:
In the global configuration values, a Zone is enabled but a Staff container is not specified.
Level:
Fatal
At least one zone must be enabled
Source:
The status log or DSTrace screen.
Explanation:
In the global configuration values, at least one Zone must be enabled.
Level:
Fatal
Stopping driver because configured objects were not found in the Identity Vault
Source:
The status log or DSTrace screen.
Explanation:
One of the DNs specified in the global configuration values does not reference a valid object in the Identity Vault.
Possible Cause:
The DN is incorrect.
Level:
Fatal
Stopping the drive because nothing is on sendDocToEngine
Source:
The status log or DSTrace screen.
Explanation:
Internal driver error.
Level:
Fatal
Stopping the drive because doc = null
Source:
The status log or DSTrace screen.
Explanation:
Internal driver error.
Level:
Fatal
Stopping the drive because something is on sendDocToEngine
Source:
The status log or DSTrace screen.
Explanation:
Internal driver error.
Level:
Fatal
SIF objects to process not provided
Source:
The status log or DSTrace screen.
Explanation:
The driver Publisher channel configuration is not set up correctly.
Action:
Remove the current driver object and add the driver again.
Level:
Fatal
SIF objects must include StudentPersonal and/or StaffPersonal
Source:
The status log or DSTrace screen.
Explanation:
The driver Publisher channel configuration is not set up correctly.
Action:
Remove the current driver object and add the driver again.
Level:
Fatal
Driver parameter zone malformed
Source:
The status log or DSTrace screen.
Explanation:
The driver Publisher channel configuration is not set up correctly.
Action:
Remove the current driver object and add the driver again.
Level:
Fatal
zone parameter not available
Source:
The status log or DSTrace screen.
Explanation:
The driver Publisher channel configuration is not set up correctly.
Action:
Remove the current driver object and add the driver again.
Level:
Fatal
Driver parameter student malformed
Source:
The status log or DSTrace screen.
Explanation:
The driver Publisher channel configuration is not set up correctly.
Action:
Remove the current driver object and add the driver again.
Level:
Fatal
student parameter not available
Source:
The status log or DSTrace screen.
Explanation:
The driver Publisher channel configuration is not set up correctly.
Action:
Remove the current driver object and add the driver again.
Level:
Fatal
Source:
The status log or DSTrace screen.
Explanation:
Disregard this error message. It does not indicate a problem.