Error messages and problem solving

A warning or error message might be displayed in the user interface to provide information about the adapter or when an error occurs.

The following table contains warnings or errors that might be displayed on the user interface if the adapter is installed on your workstation.

Table 1. Error messages, warnings, and corrective actions
Error message or warning	Additional warnings, messages, or information	Corrective action
CTGIMU107W The connection to the specified service cannot be established. Verify the service information, and try again.	An IO error occurred while sending a request. Error:`Connection refused: connect`	Ensure that the adapter service is running. For more information about starting the adapter service, see Restarting the adapter service.
	The adapter returned an error status for a bind request. Status code: invalid credentials adapter error message: `Authentication Failed`	Check the adapter authentication ID and password match the installed values. See the screen for Adapter-specific parameters in Running the ISPF dialog.
	An IO error occurred while sending a request. Error: `com.ibm.daml.jndi. JSSESocketConnection. HANDSHAKE_FAILED:`	If SSL is enabled, check the configuration. See Configuring SSL authentication. The adapter log contains details about the certificates loaded during initialization.
caacfAdd: User userid add Successful. Some attributes could not be modified.		This warning occurs when a user is created, however, some additional attributes failed. For more information, see the adapter log file.
caacf2Modify: Some attributes unsuccessful.		This warning occurs when a user is modified, however, some additional attributes failed. For more information, see the adapter log file.
caacf2Modify: All attributes unsuccessful.		The modify request failed to set the attributes on the managed resource. For more information, see the adapter log file.
caacf2Search: Reconciliation did not return at least 1 Logonid.		During the reconciliation request, no Logonids were returned. For more information, see the MVS system log and the adapter log.
LDAP: error code 92		Increase the size of the transaction log. See DB2 transaction log size
`*BPXI040I PROCESS LIMIT MAXPROCUSER HAS REACHED XX % OF ITS CURRENT CAPACITY OF XX FOR PID=XXX IN JOB ISIAGNT`		Increase the amount of processes available to the adapter's CA ACF2 logonid.
`ACF04056 ACCESS TO RESOURCE BPX.SRV.<SURROGATID> TYPE RSUR BY <ADAPTERID>`		`set res(sur) comp $KEY(BPX.SRV.<SURR OGATID>) TYPE(SUR) UID(<ADAPTERID>) ALLOW SERVICE(READ) store f acf2,rebuild(sur) end`
`BSE:_ermAlloc: ERROR: malloc FAILED: size 60`: The adapter stops processing when it encounters errors during memory allocation.	The following messages are displayed to indicate that the adapter is aborting from the process: After which, this final error message is written to the adapter log:`ERR: "FATAL memory error encountered, shutting down now"` TheIBM Security Identity server displays `Fatal error` encountered Memory allocation errors might be caused from inadequate Language Environment (LE) HEAP size settings.	The HEAP size settings can be diagnosed when you enable the following options in the adapter start script: `export _CEE_RUNOPTS='RPTOPTS(ON),RPTSTG(ON)’` This script ensures that the adapters started task log displays the current heap size allocations and suggested minimal sizes. For more information regarding storage tuning, see Tuning heap storage.