User's Guide
 |
 |
 |
|
 |
Get Adobe Reader |
Alarm and Fault Handling
The following sections describe WebLogic Network Gatekeeper alarms:
Interpreting alarms
An alarm in the alarm list provides different types of information according to the table below.
Clear alarms
Some of the alarms have clear alarms indicating when the condition that caused the alarm has ceased. That is, the condition has gone back to normal. The following combinations of alarms and clear alarms exist:
Alarm numbering overview
SLEE and SLEE utility alarms
1200-1249 Servlet engine manager
95000-95099 Subscription handler
ESPA service capability alarms
2600-2699 ESPA user interaction
2800-2899 Network initiated call handler
Protocol plug-in alarms
5400-5499 Protocol plug-in messaging/SMPP
5500-5599 Protocol plug-in user location/MPP
5600-5699 Protocol plug-in user status/MPP
5700-5799 Protocol plug-in messaging/CIMD
5800-5899 Protocol plug-in messaging/MM7
5900-5999 Protocol plug-in messaging/MLP
22000-22099 Protocol plug-in OSA access
22200-22299 Protocol plug-in OSA MPCC
22400-22499 Protocol plug-in OSA call UI
SESPA alarms
12200-12299 SESPA user location
12400-12499 SESPA messaging UI
12800-12899 SESPA call control
12900-12999 SESPA subscriber profile
Resolving Alarms
1001 SLEE: Service deactivated
Severity
Description
The indicated service has been deactivated because it has raised more critical alarms than allowed. That is, in a service's deployment descriptor it is defined how many critical alarms the service is allowed to raise before it is taken out of service.
What to do
If the service keeps raising critical alarms, analyse the reason for those alarms. Trouble report the service to the service supplier if the analyses of the alarms show that the service is faulty.
1002 SLEE: Service data storage failed
Severity
Description
The SLEE was not able to store service data in the database.
- Neither the master nor the slave database is running
- There is a network communication problem between the SLEE and the databases.
What to do
Enter command
ps -ef|grep safe_mysqldin a command window. If the database is running,safe_mysqldis returned.- If the database is not running, start the database on the indicated URL. On the database server, do the following:
For more information, see MySQL Reference Manual.
1003 SLEE: Service deactivation exception
Severity
Description
The SLEE had to force the deactivation of the indicated service because an exception was caught from the service when the SLEE tried to deactivate the service.
What to do
Trouble report the service to the service supplier.
1004 SLEE: Service stop exception
Severity
Description
The SLEE had to force the stopping of the indicated service because an exception was caught from the service when the SLEE tried to stop the service.
What to do
Trouble report the service to the service supplier.
1005 SLEE: Database replication connect failure
Severity
Description
Unable to connect to both databases when verifying replication of databases.
What to do
Verify that both databases are running.
1006 SLEE: Database replication files differ
Severity
Description
Database replication files differ more than the maximum allowed value.
The replication mechanism is not able to write data fast enough, or not at all.
What to do
Check the connection between the two databases.
Verify that both databases are running.
1007 SLEE: Database replication file names differ
Severity
Description
The internal file names used by the database replication process are mismatching. This may occur when changing log file names explicitly, for example during backup.
What to do
If this alarm is generated when not explicitly resetting the logging, the replication files may be out of synchronization. Verify that the replication has not halted due to an error. If the replication has halted, restore the failed database.
1008 SLEE: Database replication status check error
Severity
Description
Error during check of database replication status. Internal error during database replication check.
What to do
Make sure both databases are running. Restart or restore failed database.
1009 SLEE: Database replication file too large
Severity
Description
Database replication file is too large.
What to do
Free up disk space. Explicitly change to a new log file by running the reset script
/usr/local/slee/bin/dbrunReset.sh
1010 SLEE: Database replication files explicitly reset
Severity
Description
Size of database replication files have reached 90% of maximum allowed size. The files will be gracefully reset.
What to do
1011 SLEE: Faulty username-password combination
Severity
Description
A user tried to perform a OAM method with inadequate user-password combination.
What to do
Examine if there is a fraud attempt.
1012 SLEE: CORBA thread-pool overloaded
Severity
Description
The CORBA thread pool utilization exceeds 80%.
What to do
Increase the CORBA thread pool size or extend the systems capacity. The thread pool size is increased through the slee_properties.xml file (corba_thread_pool attribute in the <SLEE_PROPERTIES> tag). Run the SLEEConfig.sh and restart the SLEE.
1013 SLEE: CORBA thread-pool overload - alarm ceased
Severity
Description
The CORBA thread pool utilization has decreased so it is now below 78%.
What to do
1014 SLEE: Un-reachable listener object detected
Severity
Description
The SLEE cannot reach an object that has a listener registered.
What to do
Verify that the service owning the listener is activated, that all involved SLEE processes are running, and that there is no network communication problem between the indicated SLEE's server and the server where the un-reachable object executes.
1015 SLEE: Un-reachable listener object removed
Severity
Description
The SLEE has not been able to reach an un-reachable listener object during the configured retry interval and the listener has been removed.
What to do
See alarm1014 SLEE: Un-reachable listener object detected.
1016 SLEE: SLEE task could not be scheduled due to full task queue
Severity
Description
A SLEE task could not be scheduled because the SLEE task manager queue was full.
What to do
Increase the SLEE task manager queue size or extend the system capacity. To increase the task queue, select the SLEE service in the Network Gatekeeper Management Tool and use commands:
1017 SLEE: UNHANDLED exception raised by a SLEE task
Severity
Description
A SLEE task raised an UNHANDLED exception during method doTask.
What to do
Trouble report the service that raised the exception to the service supplier.
1018 SLEE: Un-reachable plug-in object removed
Severity
Description
The SLEE has not been able to reach an un-reachable plug-in object during the configured retry interval and the plug-in has been removed.
What to do
Verify that the plug-in is activated, that all involved SLEE processes are running, and that there is no network communication problem between the indicated SLEE's server and the server where the un-reachable object executes.
1019 SLEE: SLEE task pool empty
Severity
Description
All threads in the SLEE task pool are currently busy.
What to do
Increase the SLEE task manager thread pool size or extend the system capacity. To increase the task manager thread pool size, select the SLEE service in the Network Gatekeeper Management Tool and use commands:
1020 SLEE: SLEE task pool empty - alarm ceased
Severity
Description
Threads are available in the task pool again.
What to do
1021 SLEE: Duplicate SLEE timer reference
Severity
Description
A scheduled timer has failed due to a duplicate timer reference.
What to do
Trouble report the service that raised the exception to the service supplier.
1022 SLEE: Database table replaced
Severity
Description
The indicated database table has been automatically replaced by the service. May occur when the service is updated and the format of the database table has been changed.
What to do
1023 SLEE: Database replication error
Severity
Description
The database replication has halted due to an error in the slave database.
What to do
Log in to the master database and execute the MySQL command SHOW SLAVE STATUS. Refer to the MySQL manual to correct the indicated error.
1024 SLEE: SLEE start-up in progress
Severity
Description
The indicated SLEE is starting up.
What to do
1025 SLEE: SLEE graceful shutdown in progress
Severity
Description
The indicated SLEE is performing a graceful shutdown.
What to do
1026 SLEE: Priority task manager warning level reached
Severity
Description
Priority task queue utilization level exceeds alarm level.
What to do
Decrease the number of requests sent through the system or increase the system capacity.
1027 SLEE: OAM runtime exception
Severity
Description
A service OAM method threw a RunTimeException.
What to do
Contact BEA Support and provide the trace information provided in the alarm.
1028 SLEE: Product expiring alarm
Severity
Description
This product will expire within x hours. It will then automatically shutdown.
What to do
Update the license key for the product. Contact BEA Support.
1029 SLEE: Product expired alarm
Severity
Description
This product has expired, shutting down.
What to do
Update the license key for the product. Contact BEA Support.
1040 SLEE global counter: Counter handler creation failed
Severity
Description
An internal error occurred when the SLEE global counter service tried to create the counter handler for handling volatile counters.
- The database is not running
- There is a network communication problem between the SLEE and the databases.
What to do
See the What to do section in 1002 SLEE: Service data storage failed.
1041 SLEE global counter: Periodic cleanup set-up at counter handler creation failed
Severity
Description
Internal error setting up periodic cleanup when the slee global counter service tried to create the counter handler for handling volatile counters.
- The database is not running
- There is a network communication problem between the SLEE and the databases.
What to do
See the What to do section in 1002 SLEE: Service data storage failed.
1090 SLEE: CORBA warning received
Severity
Description
A warning message has been received from the ORB. The complete message can be read in the SLEE trace file /usr/local/slee/bin/trace/.
What to do
Analyse the message in the SLEE trace file and take actions accordingly. For more information, refer to section 18 Exceptions and Error Messages in ORBacus for C++ and Java.
1091 SLEE: CORBA alarm received
Severity
Description
An alarm has been received from the ORB. The complete message can be read in the SLEE trace file /usr/local/slee/bin/trace/.
What to do
Analyse the message in the SLEE trace file and take actions accordingly. For more information, refer to section 18 Exceptions and Error Messages in ORBacus for C++ and Java.
1095 SLEE: Database master changed
Severity
Description
The database master has changed. The change was caused by a failure to create a connection with the previous database master on the indicated URL.
- The database is not running
- There is a network communication problem between the SLEE and the databases.
What to do
See the What to do section in1002 SLEE: Service data storage failed.
1096 SLEE: Database connection failed
Severity
Description
The SLEE has failed to create a connection with the database on the indicated URL.
- The database is not running
- There is a network communication problem between the SLEE and the databases.
What to do
See the What to do section in1002 SLEE: Service data storage failed.
1097 SLEE: Database low on disk space
Severity
Description
The database host's database partition is beginning to run low on available disk space.
What to do
Make more space available on the database partition of the disk. Check the size of the ic_slee_charging, ic_slee_statistics, ic_slee_event and ic_slee_alarm tables in the slee_db and delete unused data.
If the database uses the same partition as the SLEE, check the number trace files stored in the /usr/local/slee/bin/trace/ directory.
When the alarm has been received, the low disk space threshold value must be changed to initiate the function again, see List of Configuration Parameters - SLEE and SLEE utility services.
1098 SLEE: Database critically low on disk space, database engine stopped
Severity
Description
The database was stopped because the database host's database partition was running critically low on available disk space.
What to do
Clean up the file system on the host's database partition and restart the database.
As a first measure, make more space available on the database partition of the disk. Check the size of the ic_slee_charging, ic_slee_statistics, ic_slee_event and ic_slee_alarm tables in the slee_db and delete unused data.
If the database uses the same partition as the SLEE, check the number trace files stored in the /usr/local/slee/bin/trace/ directory.
When the alarm has been received, the critically low disk space threshold value must be changed to initiate the function again, see List of Configuration Parameters - SLEE and SLEE utility services.
1099 SLEE: Database partition critically low on disk space, database engine stop failed
Severity
Description
The indicated database failed to stop when the database host's database partition was running critically low on available disk space.
There is a risk that the system will keep writing data to the database even though it is running out of disk space. This may corrupt the data in the database.
What to do
Clean up the file system on the host's database partition.
As a first measure, make more space available on the database partition of the disk. Check the size of the ic_slee_charging, ic_slee_statistics, ic_slee_event and ic_slee_alarm tables in the slee_db and delete unused data.
If the database uses the same partition as the SLEE, check the number trace files stored in the /usr/local/slee/bin/trace/ directory.
Investigate why it was not possible to stop the database.
When the alarm has been received, the critically low disk space threshold value must be changed to initiate the function again, see List of Configuration Parameters - SLEE and SLEE utility services.
1100 SLEE charging: Charging data storage failed
Severity
Description
The SLEE charging service has failed to write charging data to the database.
- Neither the master nor slave database is running
- There is a network communication problem between the SLEE and the databases.
What to do
See the What to do section in1002 SLEE: Service data storage failed.
1101 SLEE charging: Charging service initialization failed
Severity
Description
The alarm is raised if the charging service is activated before the database. That is, at installation or system restart, the database has to be started before the SLEE.
What to do
Start BEA WebLogic Network Gatekeeper database before the SLEE at system installation or restart.
1102 SLEE charging: Charging table creation failed
Severity
Description
An error occurred when trying to create the charging table in the database. The error occurs if the charging service is started before the database. That is, at installation or system restart, the database has to be started before the SLEE.
What to do
Start BEA WebLogic Network Gatekeeper database before the SLEE at system installation or restart.
1350 Time server manager: Time server connection failed
Severity
Description
It was not possible to connect to the network time server through the time server manager.
What to do
Verify the time server configuration parameters, that the network time server is started, and that network time server has access to the network.
1351 Time server manager: Time synchronization failed
Severity
Description
The SLEE has no connection with the network time server. Either is the network time server not running, or a network error/overload has occurred.
What to do
Make sure that the time server is running and can be reached from the SLEE.
1352 Time server manager: Time difference is too large
Severity
Description
The time difference is too large.
What to do
Correct the time manually. Note that this may have influences in, for example, charging records.
1452 Plug-in manager: Request rate could not be re configured according to new node SLA
Severity
Description
This alarm can only be raised if BEA Network Gatekeeper is used together with BEA WebLogic Network Gatekeeper.
The allowed request rate through the plug-in manager could not be updated according to the new node SLA.
What to do
Verify the data in the node SLA and load the SLA again.
1500 SLEE SCS manager: No SCS found
Severity
Description
What to do
In SCS_Manager, select getSCSList and check that the required SCS exists and is active. For MESSAGING_TYPE, check that a criteria has been added.
1501 SLEE SCS manager: SCS overload
Severity
Description
All matching SCSes are overloaded.
What to do
1700 SLEE backup: Snapshot backup executed OK
Severity
Description
What to do
Refer to backup restoration procedure documentation.
1701 SLEE backup: Unable to perform backup
Severity
Description
What to do
1702 SLEE backup: Un-handled error during backup
Severity
Description
Un-handled error during backup.
What to do
Contact BEA Support, include all alarm information.
1703 SLEE backup: Unable to create master database connection
Severity
Description
Unable to perform backup, unable to create master database connection.
What to do
2101 ESPA messaging: Incoming message storage failed
Severity
Description
The ESPA messaging service could not store an incoming message in the database.
- The mailbox is not created
- Neither the master nor slave database is running
- There is a network communication problem between the SLEE and the databases.
What to do
- See the What to do section in1002 SLEE: Service data storage failed.
2102 ESPA messaging: No incoming destination address
Severity
Description
The ESPA messaging service received an incoming message without a destination address.
What to do
Notify the originator of the message. The originators address is provided in the alarm printout.
2104 ESPA messaging: Plug-in not found
Severity
Description
The ESPA messaging service could not find a messaging protocol plug-in when activated, or an outgoing message has an address format that is not supported by any messaging plug-in.
What to do
If the alarm is raised at service activation, verify that the messaging protocol plug-ins are installed and activate the messaging plug-ins before the ESPA messaging service is activated.
If the alarm is raised when a message with an unsupported address format is received, notify the originator of the message. The originators address is provided in the alarm printout.
2107 ESPA messaging: Charging data storage failed
Severity
Description
The ESPA messaging service could not write charging data to the database.
- The SLEE charging service is not installed
- The SLEE charging service is installed but not activated
- Neither the master nor slave database is running
- There is a network communication problem between the SLEE and the databases.
What to do
Verify that the charging service is installed and in the state activated using the getServices method in the SLEE service. If the charging service is working properly, continue with the What to do section in1002 SLEE: Service data storage failed.
2108 ESPA messaging: Status update failed
Severity
Description
The ESPA messaging service failed to change the status of a message stored in the database.
- Neither the master nor slave database is running
- There is a network communication problem between the SLEE and the databases.
What to do
See the What to do section in1002 SLEE: Service data storage failed.
2110 ESPA messaging: No outgoing originating address
Severity
Description
The ESPA messaging service received an outgoing message without an originating address. That is, the message will not be sent because it cannot be charged and not be replied to.
What to do
Notify the enterprise operator.
2111 ESPA messaging: No outgoing destination address
Severity
Description
The ESPA messaging service received an outgoing message without a destination address.
What to do
Notify the enterprise operator.
2112 ESPA messaging: Message not found in database
Severity
Description
The ESPA messaging service could not find a message with the specified ID in the database. The connection with the database is broken.
What to do
See the What to do section in1002 SLEE: Service data storage failed.
2113 ESPA messaging: Message status update failed
Severity
Description
The ESPA messaging service could not find a message with the specified ID in the database. The message has been deleted from the database before the status update notification has been received.
What to do
The problem is resolved by the system.
2114 ESPA messaging: Mailbox not found
Severity
Description
The ESPA messaging service could not find a mailbox for the received message. That is, the message is addressed to BEA WebLogic Network Gatekeeper, but the actual mailbox does not exist. That is, the address of the message is faulty. The message is automatically returned to the sender with a notification.
What to do
The problem is resolved by the system.
2115ESPA messaging: Mailbox existence verification failed
Severity
Description
The ESPA messaging service could not verify if the specified mailbox exists in the database. That is, the connection with the database is broken.
What to do
See the What to do section in1002 SLEE: Service data storage failed.
2118 ESPA messaging: Plug-ins severely overloaded
Severity
Description
All protocol plug-ins of the requested type are severely overloaded. That is, messages cannot be sent to the network.
What to do
Install a new instance of the requested protocol plug-in in a server with lower load level. If all servers are running with high load level, it is time to expand the system with more servers. Contact BEA Support.
2122 ESPA messaging: Incoming message without ID
Severity
Description
The Parlay messaging service received a message without an ID from a protocol plug-in.
What to do
The protocol plug-in that delivered the message to the messaging service is faulty.
2127 ESPA messaging: Mailbox closed due to inactivity
Severity
Description
The indicated mailbox has been closed due to inactivity. The allowed inactive time period is configurable using the setMailboxTimeout method in the ESPA_messaging service.
What to do
2128 ESPA messaging: Unexpected error message received
Severity
Description
An unexpected error message was received from the plug-in when sending an outgoing message.
What to do
Identify the original alarm from the plug-in and take actions accordingly.
2129 ESPA messaging: Failed to make notification callback
Severity
Description
Callback to the application failed.
What to do
This alarm could occur when there are temporary network problems.
If the alarm is constantly recurring, you need to verify that the network connection to the application is functioning properly.
Verify that the application is running.
2208 ESPA call control: Database connection failed
Severity
Description
The ESPA call control service could not use the database. Possible reasons:
- Neither the master nor slave database is running
- There is a network communication problem between the SLEE and the databases.
What to do
See the What to do section in1002 SLEE: Service data storage failed.
2213 ESPA call control: Plug-in not found
Severity
Description
The ESPA call control service could not find a call control protocol plug-in when activated, or a create call leg request has an address format that is not supported by any call control plug-in.
What to do
If the alarm is raised a service activation, verify that the call control protocol plug-ins are installed and activated before the ESPA call control service is activated.
If the alarm is raised when a create call leg request with an unsupported address format is received, notify the originator of the request.
2214 ESPA call control: Plug-ins severely overloaded
Severity
Description
All protocol plug-ins of the requested type are severely overloaded. That is, call set up requests cannot be sent to the network.
What to do
Install a new instance of the requested protocol plug-in in a server with lower load level. If all servers are running with high load level, it is time to expand the system with more servers. Contact BEA Support.
2216 ESPA call control: routeReq timeout detected
Severity
Description
The ESPA call control has issued a routeReq and no response has been received within the default timeout. The call session will be released.
What to do
2217 ESPA call control: release call timeout detected
Severity
Description
The ESPA call control has issued a release request and no response has been received within the default timeout. The call session will be released.
What to do
2218 ESPA call control: Application supervision timeout detected
Severity
Description
The ESPA call control has issued an eventReportReq and no response has been received within the default timeout. The call session will be released.
What to do
2219 ESPA call control: Failed to setup Network Initiated Call Handler Service
Severity
Description
Failed to connect to the Network Initiated Call Handler Service (NICHS).
What to do
Verify that the NICHS is started and in active mode. See SLEE and SLEE Service Operation.
Note: The call control service will not be activated if it cannot connect itself to the NICHS.
2220 ESPA call control: Failed to notify application about call event
Severity
Description
Failed to notify the application of the arrival of a call-related event.
What to do
Verify that the NICHS is started and in active mode. See SLEE and SLEE Service Operation.
Note: The call control service will not be activated if it cannot connect itself to the NICHS.
2300 ESPA user location: Plug-ins severely overloaded
Severity
Description
All protocol plug-ins of the requested type are severely overloaded. That is, location requests cannot be sent to the network.
What to do
Install a new instance of the requested protocol plug-in in a server with lower load level. If all servers are running with high load level, it is time to expand the system with more servers. Contact BEA Support.
2301 ESPA user location: Plug-in not found
Severity
Description
The service could not find a call control protocol plug-in when activated, or a location request has an address format that is not supported by any user location plug-in.
What to do
If the alarm is raised a service activation, verify that the user location protocol plug-ins are installed and activated before the Parlay user location service is activated.
If the alarm is raised when a location request with an unsupported address format is received, notify the originator of the request.
2302 ESPA user location: Charging data storage failed
Severity
Description
The ESPA user location service cannot write charging data to the database.
- The SLEE charging service is not installed
- The SLEE charging service is installed but not activated
- Neither the master nor slave database is running
- There is a network communication problem between the SLEE and the databases.
What to do
Verify that the charging service is installed and in the state activated. If the charging service is working properly, continue with the What to do section in1002 SLEE: Service data storage failed.
2309 ESPA user location: Periodic location report delivery failed
Severity
Description
A periodic location report delivery failed because the client was un-reachable.
What to do
It is up to the client to request a new location request.
2400 ESPA user status: Plug-ins severely overloaded
Severity
Description
All protocol plug-ins of the requested type are severely overloaded. That is, status requests cannot be sent to the network.
What to do
Install a new instance of the requested protocol plug-in in a server with lower load level. If all servers are running with high load level, it is time to expand the system with more servers. Contact BEA Support.
2401 ESPA user status: Plug-in not found
Severity
Description
The ESPA user status service could not find a user status protocol plug-in when activated, or a status request has an address format that is not supported by any user status plug-in.
What to do
If the alarm is raised a service activation, verify that the user status protocol plug-ins are installed and activated before the ESPA user status service is activated.
If the alarm is raised when a status request with an unsupported address format is received, notify the originator of the request.
2402 ESPA user status: Charging data storage failed
Severity
Description
The Parlay user status service cannot write charging data to the database.
- The SLEE charging service is not installed
- The SLEE charging service is installed but not activated
- Neither the master nor slave database is running
- There is a network communication problem between the SLEE and the databases.
What to do
Verify that the charging service is installed and in the state activated. If the charging service is working properly, continue with the What to do section in1002 SLEE: Service data storage failed.
2502 ESPA charging: Plug-ins severely overloaded
Severity
Description
All protocol plug-ins of the requested type are severely overloaded. That is, charging requests cannot be sent to the network.
What to do
Install a new instance of the requested protocol plug-in in a server with lower load level. If all servers are running with high load level, it is time to expand the system with more servers. Contact BEA Support.
2503 ESPA charging: Plug-in not found
Severity
Description
The ESPA charging service could not find a charging protocol plug-in when activated, or a charging request has an address format that is not supported by any charging plug-in.
What to do
If the alarm is raised a service activation, verify that the charging protocol plug-ins are installed and activated before the ESPA charging service is activated.
If the alarm is raised when a charging request with an unsupported address format is received, notify the originator of the request.
2602 ESPA user interaction: Plug-ins severely overloaded
Severity
Description
All protocol plug-ins of the requested type are severely overloaded. That is, user interaction requests cannot be sent to the network.
What to do
Install a new instance of the requested protocol plug-in in a server with lower load level. If all servers are running with high load level, it is time to expand the system with more servers. Contact BEA Support.
2603 ESPA user interaction: Plug-in not found
Severity
Description
The ESPA user interaction service could not find a user interaction protocol plug-in when activated, or a user interaction request has an address format that is not supported by any user interaction plug-in.
What to do
If the alarm is raised a service activation, verify that the user interaction protocol plug-ins are installed and activated before the ESPA user interaction service is activated.
If the alarm is raised when an interaction request with an unsupported address format is received, notify the originator of the request.
2605 ESPA user interaction: Found no matching request or notification
Severity
Description
Found no enabled notification or outstanding sendInfoAndCollect-request matching the arrived message properties. The message will be discarded.
What to do
2606 ESPA user interaction: Failed to report notification
Severity
Description
Failed to notify an application of an network initiated UI-event.
What to do
This alarm could occur when there are temporary network problems.
If the alarm is constantly recurring, you need to verify that the network connection to the application is functioning properly.
Verify that the application is running.
2607 ESPA user interaction: Failed to log charging info
Severity
Description
Failed to log charging info in charging database.
What to do
See the What to do section in1002 SLEE: Service data storage failed.
2608 ESPA user interaction: Delete old request
Severity
Description
Because of a collision with the primary key in the database an unanswered sendInfoAndCollectRequest was deleted.
What to do
This alarm can be disregarded if it occurs seldom.
If the alarm is constantly recurring, you may need to change the Sequence number range end ID parameter, through the Plugin_messaging_SMPP_SMS service management interface, see List of Configuration Parameters.
2609 ESPA user interaction: Message with no destination address
Severity
Description
A message arrived with no destination address set. The message will be discarded.
What to do
2702 ESPA subscriber profile: Plug-ins severely overloaded
Severity
Description
All protocol plug-ins of the requested type are severely overloaded. That is, subscriber profile requests cannot be sent to the network.
What to do
Install a new instance of the requested protocol plug-in in a server with lower load level. If all servers are running with high load level, it is time to expand the system with more servers. Contact BEA Support.
2703 ESPA subscriber profile: Plug-in not found
Severity
Description
The ESPA user interaction service could not find a subscriber profile protocol plug-in when activated, or a subscriber profile request has an address format that is not supported by any subscriber profile plug-in.
What to do
If the alarm is raised a service activation, verify that the user profile protocol plug-ins are installed and activated before the ESPA user profile service is activated.
If the alarm is raised when an subscriber profile request with an unsupported address format is received, notify the originator of the request.
2802 Network initiated call handler: No service registered
Severity
Description
What to do
Check that there are call control capabilities installed in the system, that is, multiparty call control (mpcc) and generic call control (gcc) and that the corresponding services are running.
2803 Network initiated call handler: No enabled notification for event
Severity
Description
Received event in interrupt mode with no matching enabled notification request in mode interrupt. Policy service will take control of call.
What to do
Check the enabled notifications (listNotification in gccs and/or mpccs in modules) and verify that they are consistent with the expected client notification state.
2805 Network initiated call handler: Overload
Severity
Description
Service is severely overloaded.
What to do
2806 Network initiated call handler: Unknown error
Severity
Description
What to do
2807 Network initiated call handler: Suspend error
Severity
Description
The service is suspended and cannot process any events.
What to do
Use Network Gatekeeper Management Tool to resume it, see Changing SLEE state.
3001 Policy service: Parsing of retraction rule file failed
Severity
Description
The rule engine cannot parse the rule file that retracts all not service-specific objects from the context.
What to do
Verify that the rule file exists.
Verify that the syntax in the rule file is correct. See the log file for the policy service (policy.log) for information on the error.
3002 Policy service: Parsing of service-specific rule file failed
Severity
Description
The rule engine cannot parse the service-specific rule file.
What to do
Verify that the rule file exists and that the path to the rule is correct.
Verify that the syntax in the rule file is correct. See the log file for the policy service (policy.log) for information on the error.
3005 Policy service: Parsing of service-specific rule file failed at load time
Severity
Description
The policy service cannot parse the service-specific rule file when it is about to be loaded into the database. Probably this is a syntax error in the rule file.
What to do
Verify that the rule file exists and that the path to the rule file is correct.
Verify that the syntax in the rule file is correct. See the log file for the policy service (policy.log) for information on the error.
3006 Policy service: Alarm raised from policy rule
Severity
Description
Failed to match whitelist for service provider.
What to do
Verify that the specified whitelist exists in the SLEE.list.matcher service.
3007 Policy service: Denial of service request
Severity
Description
The policy service denied a service request.
What to do
3008 Policy service: Failed to parse node rule file
Severity
Description
Failed to parse node rule file.
What to do
Verify that the node rule file exists and that the path to the node rule file is correct.
Verify that the syntax in the node rule file is correct. See the log file for the policy service (policy.log) for information on the error.
3100 Policy service: Total request rate warning level reached
Severity
Description
The total request rate from WebLogic Network Gatekeeper towards a network node has reached the warning level (default 80%).
What to do
Check the global contract data for the node in the total traffic SLA.
Investigate if it is possible to get access to more capacity in the network node. If that's not possible, decrease the allowed request rate towards the network node in one or more of the service provider traffic SLAs.
3110 Policy service: Total request rate exceeded
Severity
Description
The total request rate from WebLogic Network Gatekeeper towards a network node has exceeded the maximum allowed level defined in the total traffic SLA.
What to do
See alarm 3100 Policy service: Total request rate warning level reached.
3200 Policy service: Service provider request rate warning level reached
Severity
Description
The request rate from a specific service provider towards a network node reached the warning level (default 80%).
What to do
Check the node contract data in the service provider traffic SLA.
Consider upgrading the service provider. That is, move the service provider to a service provider group with a SP traffic SLA allowing a higher request rate towards the node.
3210 Policy service: Service provider request rate exceeded
Severity
Description
The request rate for a specific service provider towards a node exceeded the maximum allowed level for that service provider.
What to do
See alarm 3200 Policy service: Service provider request rate warning level reached.
3300 Policy service: No valid global contract in the Total traffic SLA
Severity
Description
No valid global contract for the node is found in the total traffic SLA.
What to do
Add a valid global contract in the total traffic SLA.
For updating the total traffic SLA, see Updating the total traffic SLA.
3310 Policy service: No node contract in the Service Provider traffic SLA
Severity
Description
No node contract for the node found in the service provider traffic SLA.
What to do
Add a valid node contract in the service provider traffic SLA.
For updating the service provider traffic SLA, see Updating a service provider traffic SLA.
5401 Plug-in messaging-SMPP: Plug-in registration failed
Severity
Description
The protocol plug-in failed to register itself in the plug-in manager. The alarm occurs if the plug-in manager is not installed or if it is not in active state.
What to do
Verify that the plug-in manager is active and restart the plug-in.
5403 Plug-in messaging-SMPP: Message sending failed
Severity
Description
The protocol plug-in failed to send the short message to the SMSC.
What to do
Verify the physical connection with the SMSC and that the plug-in is configured properly.
5404 Plug-in messaging-SMPP: Plug-in removal failed
Severity
Description
The protocol plug-in failed to unregister itself from the plug-in manager. The alarm occurs if the plug-in manager is not in active state.
What to do
Verify that the plug-in manager is active and restart the plug-in.
5405 Plug-in messaging-SMPP: Listener notification failed
Severity
Description
The plug-in failed to notify a listener of the result when sending or receiving a message.
What to do
Verify that the generic messaging SCS proxy (Parlay_messaging service) owning the listener object is active, that all SLEE processes are running, and that there are no network communication problems between the SLEEs.
5409 Plug-in messaging-SMPP: SMSC transmitter connection established
Severity
Description
The plug-in has established a connection to the SMSC.
What to do
5410 Plug-in messaging-SMPP: SMSC transmitter reconnect procedure timeout
Severity
Description
The plug-in has failed to reconnect to the SMSC during the configured duration and terminates the reconnection procedure.
What to do
Verify the network connection. Restart the reconnection procedure using the resetSMPPConnection method in the Plugin_messaging_SMPP service.
5411 Plug-in messaging-SMPP: SMSC transmitter reconnect attempt failed
Severity
Description
A reconnection attempt in the reconnection procedure has failed.
What to do
The plug-in will keep on trying to connect until it succeeds or until the reconnection procedure times out.
5412 Plug-in messaging-SMPP: SMSC receiver connection lost
Severity
Description
The plug-in has lost connection with the SMSC.
What to do
Make sure the network connection to the SMSC is working properly.
The plug-in will automatically try to reconnect to the SMSC again. The total reconnection procedure duration and the interval between individual reconnection attempts depends on configuration settings in the Plugin_messaging_SMPP service.
5413 Plug-in messaging-SMPP: SMSC receiver connection established
Severity
Description
The plug-in has established a connection to the SMSC.
What to do
5415 Plug-in messaging-SMPP: SMSC receiver reconnect procedure timeout
Severity
Description
The plug-in has failed to reconnect to the SMSC during the configured duration and terminates the reconnection procedure.
What to do
Verify the network connection. Restart the reconnection procedure using the resetSMPPConnection method in the Plugin_messaging_SMPP service.
5416 Plug-in messaging-SMPP: SMSC receiver reconnect attempt failed
Severity
Description
A reconnection attempt in the reconnection procedure has failed.
What to do
The plug-in will keep on trying to connect until it succeeds or until the reconnection procedure times out.
5417 Plug-in messaging-SMPP: Storing message data in database failed
Severity
Description
The plug-in failed to store message data in the database.
What to do
See the What to do section in1002 SLEE: Service data storage failed.
5418 Plug-in messaging-SMPP: Updating message delivery status in database failed
Severity
Description
The plug-in failed to the message delivery status in the database.
What to do
See the What to do section in1002 SLEE: Service data storage failed.
5419 Plug-in messaging-SMPP: Message delivery processing in database failed
Severity
Description
The plug-in failed to store message data in the database.
What to do
See the What to do section in1002 SLEE: Service data storage failed.
5420 Plug-in messaging-SMPP: No listener available for incoming message
Severity
Description
No registered listener was found for the incoming message. The plug-in was unable to deliver the incoming message.
What to do
Verify that the generic messaging SCS proxy (Parlay_messaging service) owning the listener object is active, that all SLEE processes are running, and that there are no network communication problems between the SLEEs.
5421 Plug-in messaging-SMPP: SMSC transmitter connection lost
Severity
Description
The plug-in has lost connection with the SMSC. That is, it failed to send a heartbeat to the SMSC.
What to do
Make sure the network connection to the SMSC is working properly.
The plug-in will automatically try to reconnect to the SMSC again. The total reconnection procedure duration and the interval between individual reconnection attempts depends on configuration settings in the Plugin_messaging_SMPP service.
5502 Plug-in user location-MPP: Failed to create provider
Severity
Description
The plug-in failed to connect to the MPC node.
What to do
Verify that the MPC node is running.
Verify that the configuration parameters are correct, see User location/MPS.
5503 Plug-in user location-MPP: Plug-in registration failed
Severity
Description
The protocol plug-in failed to register itself in the plug-in manager. The alarm occurs if the plug-in manager is not installed or if it is not in active state.
What to do
Verify that the plug-in manager is installed and activated.
5505 Plug-in user location-MPP: Removal failed
Severity
Description
The protocol plug-in failed to unregister itself from the plug-in manager. The alarm occurs if the plug-in manager is not in active state.
What to do
Verify that the plug-in manager is activated.
5506 Plug-in user location-MPP: Connection established
Severity
Description
The plug-in established connection to the MPC Node.
What to do
5507 Plug-in user location-MPP: Reconnection procedure ended
Severity
Description
The plug-in stopped trying to connect to the MPC Node.
What to do
Restart the reconnection procedure.
Also, see 5502 Plug-in user location-MPP: Failed to create provider.
5602 Plug-in user status-MPP: Failed to create provider
Severity
Description
The plug-in failed to connect to the MPC node.
What to do
Verify that the MPC node is running.
Verify that the configuration parameters are correct, see User location/MPS.
5603 Plug-in user status-MPP: Registration failed
Severity
Description
The protocol plug-in failed to register itself in the plug-in manager. The alarm occurs if the plug-in manager is not installed or if it is not in active state.
What to do
Verify that the plug-in manager is installed and activated.
5605 Plug-in user status-MPP: Removal failed
Severity
Description
The protocol plug-in failed to unregister itself from the plug-in manager. The alarm occurs if the plug-in manager is not in active state.
What to do
Verify that the plug-in manager is activated.
5606 Plug-in user status-MPP: Connection established
Severity
Description
The plug-in established connection to the MPC Node.
What to do
5607 Plug-in user status-MPP: Reconnection procedure ended
Severity
Description
The plug-in stopped trying to connect to MPC node.
What to do
Restart the reconnection procedure.
Verify that the MPC node is running.
Verify that the configuration parameters are correct, see User location/MPS.
5700 Plug-in messaging-CIMD: SMSC login failed
Severity
Description
The protocol plug-in failed to log in to the SMSC due to a faulty user name and/or password.
What to do
Verify the registered SMSC login parameters with the SMSC responsible.
5701 Plug-in messaging-CIMD: SMSC login succeeded
Severity
Description
The protocol plug-in has successfully logged in to the SMSC.
What to do
5702 Plug-in messaging-CIMD: SMS delivery failed
Severity
Description
No messaging SCS proxy could be obtained for SMS delivery.
What to do
Verify that messaging SCS proxies are installed in the system and that they are activated.
5703 Plug-in messaging-CIMD: SMSC connection failed
Severity
Description
The protocol plug-in failed to connect to the SMSC.
What to do
Verify the SMSC addressing parameters registered in the plug-in and the SMSCes status with the SMSC responsible.
5704 Plug-in messaging-CIMD: Login request sending failed
Severity
Description
The protocol plug-in failed to send the Login request to the SMSC.
What to do
Verify the SMSC addressing parameters registered in the plug-in and the SMSCes status.
5705 Plug-in messaging-CIMD: Plug-in not connected to SMSC
Severity
Description
The protocol plug-in has detected that it is not connected to the SMSC. The alarm is raised at plug-in start up or if the connection is lost.
What to do
If the alarm is raised at startup, it will automatically cease then the connection is successfully established.
If the alarm is raised during operation, the plug-in will try to re-establish the connection during the specified reconnection time. If this is successful the alarm will cease. Otherwise, the status of the SMSC has to be verified and the connection has to be manually restored through the plug-in's reconnect OAM method.
Alarm 5706 is received as an acknowledgment on the successful connection in all the above cases.
5706 Plug-in messaging-CIMD: Plug-in connected to SMSC
Severity
Description
The protocol plug-in has successfully connected to the SMSC.
What to do
5707 Plug-in messaging-CIMD: Exception when notifying listener
Severity
Description
What to do
Verify that the SCS ESPA is running.
5708 Plug-in messaging-CIMD: Exception when adding data to database
Severity
Description
Failed to add data to message info database.
What to do
Verify that the database is running.
5710 Plug-in messaging-CIMD: CIMD protocol error in submit response
Severity
Description
Parameter pair mismatch for destination addresses and service center timestamps.
What to do
Report protocol error to SMSC vendor.
5801 Plug-in messaging-MM7: Unable to create SOAP sender
Severity
Description
The protocol plug-in plug-in could not create a SOAP sender.
What to do
Verify the MMSC addressing parameters registered in the plug-in.
5802 Plug-in messaging-MM7: No stored message ID matched message ID in received delivery report
Severity
Description
The protocol plug-in has received a delivery report from the MMSC that could not be be associated with a message ID of previously sent message.
What to do
5803 Plug-in messaging-MM7: No message ID contained in received delivery report
Severity
Description
The protocol plug-in has received a delivery report from the MMSC without a message ID.
What to do
5804 Plug-in messaging-MM7: Plug-in unable to parse delivery report request
Severity
Description
The protocol plug-in has received a delivery report request from the MMSC that could not be parsed.
What to do
5805 Plug-in messaging-MM7: Plug-in unable to parse delivery request
Severity
Description
The protocol plug-in has received a deliver request from the MMSC that could not be parsed.
What to do
5806 Plug-in messaging-MM7: No recipient address found in deliver request
Severity
Description
The protocol plug-in could not find a recipient address in a deliver request received from the MMSC.
What to do
5807 Plug-in messaging-MM7: Unrecognised address type in deliver request
Severity
Description
The protocol plug-in could not recognise the address type in a deliver request received from the MMSC.
What to do
5808 Plug-in messaging-MM7: SOAP request parsing error
Severity
Description
The protocol plug-in has detected an error when parsing a SOAP request from the MMSC.
What to do
5809 Plug-in messaging-MM7: SOAP request handling error
Severity
Description
The SOAP engine has reported that it failed to handle a SOAP request from the MMSC.
What to do
5810 Plug-in messaging-MM7: Retrieving simple content data from SOAP message failed
Severity
Description
The protocol plug-in failed to retrieve a content/attachment data of a MIME simple type from a SOAP message because the data was corrupt.
What to do
5811 Plug-in messaging-MM7: Retrieving multiparty content data from SOAP message failed
Severity
Description
The protocol plug-in failed to retrieve a content/attachment data of a MIME multiparty type from a SOAP message because the data was corrupt.
What to do
5812 Plug-in messaging-MM7: SOAP request sending failed
Severity
Description
There was an error trying to send a SOAP request.
What to do
5813 Plug-in messaging-MM7: Listener notification failed
Severity
Description
There was an error trying to notify a plug-in listener.
What to do
5814 Plug-in messaging-MM7: MM7 server connection lost
Severity
Description
An error was encountered when checking the remote MM7 server using heartbeats. The plug-in has been deactivated.
What to do
Make sure there are no network problems.
5815 Plug-in messaging-MM7: MM7 server connection established
Severity
Description
The connection with the remote MM7 server is OK again and the plug-in has been activated again.
What to do
5900 Plug-in messaging-MLP: Reading or writing configuration data failed
Severity
Description
The protocol plug-in failed to read or write configuration data to the database.
What to do
See the What to do section in1002 SLEE: Service data storage failed.
5902 Plug-in messaging-MLP: Request sending error
Severity
Description
The protocol plug-in failed to send a request to the MLP server.
What to do
Verify the network connection and the MLP server connection data configured in the plug-in.
5903 Plug-in messaging-MLP: Response retrieving error
Severity
Description
The protocol plug-in failed to parse the XML result retrieved from the MLP server.
What to do
Verify the network connection and the MLP server connection data configured in the plug-in. Verify the MLP version used.
7001 SLEE statistics: Failed to store statistics data
Severity
Description
Failed to store statistics data.
What to do
Check the status of the database and check if the disk is full.
11100 ESPA access: User locked
Severity
Description
An ESPA user has failed to log in three times and has been locked.
What to do
Unlock the user through the ESPA access OAM interface.
11130 ESPA access: Wrong application ID
Severity
Description
The application was not allowed to log in. Tried to login with the wrong ID credentials (that is, a non existing service provider account/application account/application instance ID combination) will cause this alarm.
What to do
Make sure the application is provided with the correct ID combination. Note that this alarm may indicate an intrusion attempt.
11131 ESPA access: Wrong application password
Severity
Description
The application tried to log in with the wrong password.
What to do
Make sure the application is provided with the correct credentials. Note that this alarm may indicate an intrusion attempt.
11132 ESPA access: Locked application log in attempt
Severity
Description
The application tried to log in after being blocked. Consecutive calls to login after initial lock will cause this alarm.
What to do
Unlock the application. Make sure the application is provided with the correct credentials. Note that this alarm may indicate an intrusion attempt.
11133 ESPA access: Non active application account
Severity
Description
The application tried to log in on non active account (service provider account, application account or service instance group level).
What to do
Activate the acount on the relevant level if it should be active.
12100 SESPA access: ESPA session logged out
Severity
Description
ESPA has logged out a SESPA session (application instance) due to too many logged in application instances for the application instance group. The maximum number of concurrent logged in application instances is specified in the application instance group's SLA. The oldest session is logged out first.
What to do
If ESPA logs out active sessions, the SLA has to be re-negonitiated with the service provider. That is, the maximum number of concurrent logged in application instances in the SLA has to be increased.
If an application creates a lot of sessions that are logged out by ESPA, the application might be faulty. That is, the application does not log out un used sessions.
12101 SESPA access: ESPA session error
Severity
Description
SESPA was unable to recover an ESPA session. That is, the ESPA object was unreachable.
What to do
The application is notified and will log in again and a new session is created.
12200 SESPA user location: Application error
Severity
Description
Error occurs when invoking an application.
What to do
Check the network connection between the WebLogic Network Gatekeeper and the client.
Check that the client is not overloaded and thereby fails to respond in a timely fashion.
12300 SESPA messaging: Enable Parlay X incoming message notification failed
Severity
Description
SESPA was unable to enable the Parlay X incoming message notification for the application at restart of the server.
What to do
Manually remove the old notification and create a new notification through the SESPA messaging OAM interface. For more information on how to create a Parlay X incoming message notification, see Creating an application instance group.
12301 SESPA messaging: Parlay X incoming message notification failed
Severity
Description
SESPA was unable to notify an application that a new message is available.
What to do
Verfy that the application is up and running.
12302 SESPA messaging: Parlay X incoming message notification destroyed
Severity
Description
A Parlay X incoming message notification for an application was destroyed (disabled).
What to do
Create a new notification through the SESPA messaging OAM interface. For more information on how to create a Parlay X incoming message notification, see Creating an application instance group.
12400 SESPA messaging UI: Application error
Severity
Description
What to do
Make sure that the application is running and is accessible from the WebLogic Network Gatekeeper.
12401 SESPA messaging UI: Notification error
Severity
Description
Failed to re-enable notification after service restart.
What to do
The application must manually enable this notification.
12500 SESPA user status: Application error
Severity
Description
What to do
Make sure that the application is running and is accessible from the WebLogic Network Gatekeeper.
12600 SESPA call UI: Application error
Severity
Description
What to do
Make sure that the application is running and is accessible from the WebLogic Network Gatekeeper.
12800 SESPA call control: Notification error
Severity
Description
Failed to re-enable notification after service restart.
What to do
The application must manually enable this notification.
12801 SESPA call control: Application error
Severity
Description
What to do
Make sure that the application is running and is accessible from the WebLogic Network Gatekeeper.
12900 SESPA subscriber profile: Application error
Severity
Description
What to do
Make sure that the application is running and is accessible from the WebLogic Network Gatekeeper.
22000 Plug-in OSA access: OSA gateway authentication failed
Severity
Description
The OSA access plug-in failed to authenticate with the OSA gateway.
What to do
Verify the OSA gateway connection data registered in OSA Gateway Connection with the OSA gateway operator. Verify that the user certificate is still valid.
22001 Plug-in OSA access: OSA gateway service manager unreachable
Severity
Description
The OSA manager object obtained from the OSA gateway is considered dead. Might be a network problem.
What to do
The OSA gateway plug-in will automatically try to authenticate the OSA gateway at next service request.
22002 Plug-in OSA access: OSA gateway unreachable
Severity
Description
The OSA access plug-in could not reach any of the connected OSA gateways (OSA frameworks) defined. Might be a network problem.
What to do
Verify the network connection.
22003 Plug-in OSA access: No mapping available
Severity
Major
Description
The application requesting a service from the OSA gateway does not have a valid mapping towards the requested OSA service.
What to do
Verify the current mapping. If no mapping exists, create a mapping according to Connecting an application (account) to an OSA/Parlay gateway.
22004 Plug-in OSA access: Internal error
Severity
Description
An unexpected internal error has occurred.
What to do
22101 Plug-in generic UI-HOSA: Message delivery failed - undefined
Severity
Description
The HOSA gateway failed to deliver one or more SMSes. The following error message was provided by the HOSA gateway P_UI_ERROR_UNDEFINED.
What to do
Contact the HOSA gateway owner.
22102 Plug-in generic UI-HOSA: Message delivery failed - illegal info
Severity
Description
The HOSA gateway failed to deliver one or more SMSes. The following error message was provided by the HOSA gateway P_UI_ERROR_ILLEGAL_INFO.
What to do
Contact the HOSA gateway owner.
22103 Plug-in generic UI-HOSA: Message delivery failed - ID not found
Severity
Description
The HOSA gateway failed to deliver one or more SMSes. The following error message was provided by the HOSA gateway P_UI_ERROR_ID_NOT_FOUND.
What to do
Contact the HOSA gateway owner.
22104 Plug-in generic UI-HOSA: Message delivery failed - resource unavailable
Severity
Description
The HOSA gateway failed to deliver one or more SMSes. The following error message was provided by the HOSA gateway P_UI_ERROR_RESOURCE_
UNAVAILABLE.
What to do
Contact the HOSA gateway owner.
22105 Plug-in generic UI-HOSA: Message delivery failed - illegal range
Severity
Description
The HOSA gateway failed to deliver one or more SMSes. The following error message was provided by the HOSA gateway P_UI_ERROR_ILLEGAL_RANGE.
What to do
Contact the HOSA gateway owner.
22106 Plug-in generic UI-HOSA: Message delivery failed - improper user response
Severity
Description
The HOSA gateway failed to deliver one or more SMSes. The following error message was provided by the HOSA gateway P_UI_ERROR_IMPROPER_USER_
RESPONSE.
What to do
Contact the HOSA gateway owner.
22107 Plug-in generic UI-HOSA: Message delivery failed - abandon
Severity
Description
The HOSA gateway failed to deliver one or more SMSes. The following error message was provided by the HOSA gateway P_UI_ERROR_ABANDON.
What to do
Contact the HOSA gateway owner.
22108 Plug-in generic UI-HOSA: Message delivery failed - no operation active
Severity
Description
The HOSA gateway failed to deliver one or more SMSes. The following error message was provided by the HOSA gateway P_UI_ERROR_NO_OPERATION_
ACTIVE.
What to do
Contact the HOSA gateway owner.
22109 Plug-in generic UI-HOSA: Message delivery failed - no space available
Severity
Description
The HOSA gateway failed to deliver one or more SMSes. The following error message was provided by the HOSA gateway P_UI_ERROR_NO_SPACE_AVAILABLE.
What to do
Contact the HOSA gateway owner.
22110 Plug-in generic UI-HOSA: Message delivery failed - resource timeout
Severity
Description
The HOSA gateway failed to deliver one or more SMSes. The following error message was provided by the HOSA gateway P_UI_ERROR_RESOURCE_TIMEOUT.
What to do
Contact the HOSA gateway owner.
22200 Plug-in OSA MPCC: Internal callback error
Severity
Description
Callback communication between OSA MPCC plug-in and ESPA (internally in the WebLogic Network Gatekeeper) failed.
What to do
22201 Plug-in OSA MPCC: OSA error
Severity
Description
Communication between the plug-in and OSA gateway failed.
What to do
Check the OSA gateway logs to determine what caused the error.
22400 Plug-in OSA call UI: Internal callback error
Severity
Description
Callback communication between OSA call UI plug-in and ESPA (internally in the WebLogic Network Gatekeeper) failed.
What to do
22401 Plug-in OSA call UI: OSA error
Severity
Description
Communication between the plug-in and OSA gateway failed.
What to do
Check the OSA gateway logs to determine what caused the error.
95001 Subscription handler: Subscriber profile plug-in retrieval failed
Severity
Description
The subscription handler could not find a subscriber profile plug-in when trying to access the subscriber profile database.
What to do
Verify that an active subscriber profile plug-in is available.
95002 Subscription handler: Subscriber profile retrieval failed
Severity
Description
The subscription handler received an exception when trying to retrieve the subscriber profile for the specified subscriber. Possible cause could be that the subscriber does not have a subscriber profile specified.
What to do
Verify that the subscriber profile exists. Check for alarms from the subscriber profile plug-in.
95003 Subscription handler: Exception received when trying to write subscription data
Severity
Description
The subscription handler received an exception when trying to write subscription data to the specified subscriber's subscriber profile.
What to do
Make sure the correct database username and password combination is defined in the plug-in. Check the load on the subscriber profile database server.
Check for alarms from the subscriber profile plug-in to get more information.
95004 Subscription handler: Writing subscription data failed
Severity
Description
A set error was reported by the subscriber profile plug-in or the set request timed out when trying to write subscription data to the specified subscriber's subscriber profile.
What to do
Make sure the correct database username and password combination is defined in the plug-in. Check the load on the subscriber profile database server.
Check for alarms from the subscriber profile plug-in to get more information.
95005 Subscription handler: Exception received when trying to read subscription data
Severity
Description
An exception occurred when trying to read subscription data from the specified subscriber's subscriber profile.
What to do
Make sure the correct database username and password combination is defined in the plug-in. Check the load on the subscriber profile database server.
Check for alarms from the subscriber profile plug-in to get more information.
95006 Subscription handler: Exception received when verifying a subscription
Severity
Description
An exception occurred when trying to verify if the specified subscriber has a subscription to the specified application.
What to do
Make sure the correct database username and password combination is defined in the plug-in. Check the load on the subscriber profile database server.
Check for alarms from the subscriber profile plug-in to get more information.
95007 Subscription handler: Reading subscription data failed
Severity
Description
A get error was reported by the subscriber profile plug-in or the get request timed out when trying to read subscription data from the specified subscriber's subscriber profile.
What to do
Make sure the correct database username and password combination is defined in the plug-in. Check the load on the subscriber profile database server.
Check for alarms from the subscriber profile plug-in to get more information.
