The Notification Server is a part of the Application Base Subsystem.
This background process is responsible for performing post-message delivery activities, post-print activities, mailbox maintenance activities, login arbitration, and remote user audit.
The post-message delivery activities include:
sending MWI on/off request to the switch;
notifying the IVF application or the Desktop Client of new message arrival if the user is logged in to the mailbox;
scheduling remote notification if necessary;
submitting a print job to the MDS if auto-printing is turned on for fax/mixed-media messages.
The post-print activities include:
updating the mailbox log with the result of the print operation;
turning off auto-printing if an NDN referring to the default fax printing number is received.
The mailbox maintenance activities include:
performing nightly Garbage Daemon audit to delete expired messages from user’s mailbox;
performing nightly MWI audit to ensure MWI is turn on when unread message exists in user’s mailbox.
Other activities include:
providing the functionality for applications to report/query mailbox login/logout activities;
performing nightly Remote User audit to ensure the number of temporary remote users in the system is less than the defined limit.
performing alarm notification to the alarm mailbox
Severity Not Applicable
Description Notification server API request failed.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description The requested item is already locked.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description The requested item does not exist.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description General error Return Code: for System Manager.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description Remote Procedure Call error in communicating with the Notification Server.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description The requested audit is already in progress.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Minor
Description Failure to setup database connection. This is likely due to a database that is not ready to accept a request yet.
Impact The Notification service will use default settings to determine when to run the MWI, Garbage Daemon, and Remote User Audit (this may change the audit times). The Notification service will periodically retry to connect to the database.
Recovery Action Check to see if the database is running. If a problem persists, restart the Notification service (voice messaging will temporarily be unavailable while the Notification service is restarting). If the problem persists, contact Customer support.
Technical Support Action Check return code. Ensure that the database and database drivers are correctly configured and restart the Notification service.
Severity Debug
Description Provides debug information on database access.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Minor
Description Failed to modify Notification Server configuration using the Notification Server tool. This is likely due to the database not being ready to accept the request.
Impact Cannot write internal Notification service parameters to the database.
Recovery Action Check to see if the database is running. If the problem persists, restart the Notification service (voice messaging will be temporarily unavailable while the service is restarting). If the problem persists, contact customer support.
Technical Support Action Ensure that the database and database drivers are correctly configured and restart the Notification service. Check the return code. Check that the NMnsConfig table exists in the database.
Severity Minor
Description Failed to read Notification Server configuration using the Notification Server tool. This is likely due to the database not being ready to accept the request.
Impact Cannot view internal Notification service parameters. Default values will be used to start up the Notification service (audit times may be changed).
Recovery Action Check to see if the database is running. If the problem persists, restart the Notification service (voice messaging will be temporarily unavailable while the service is restarting. If the problem persists, contact customer support.
Technical Support Action Ensure that the database and database drivers are correctly configured and restart the Notification service. Check the return code. Check that the NMnsConfig table exists in the database.
Severity Not Applicable
Description No record found in the database.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description Error in SQL statement.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description Error in initializing SQL.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description Error in freeing the SQL connection.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description Error in allocation of SQL connection.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description Error in SQL connection.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description Error in initializing the disconnection from SQL.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description Error in executing SQL.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description Error in reading database data.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Description Error in allocating the SQL statement.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description Error in concurrent SQL access.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Information
Description Notification Server has started.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Critical
Description Notification Server failed to start.
Impact MWI updates, garbage daemon, remote user audit, desktop registration, mailbox login, and fax auto-printing will not function.
Recovery Action Restart the Notification service if it is not already running (voice messaging will be temporarily unavailable while the service is restarting). .If the problem persists, contact customer support.
Technical Support Action Ensure that another Notification service has not already started. If more than one service has started, stop all services and then restart the Notification service. If this action is not successful, check the event log for events from lower-level components.
Severity Information
Description Notification Server is now ready to take requests from its clients.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Information
Description A request has been made to shutdown the Notification Server.
Impact The Notification service will terminate.
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Major
Description Failed to start the indicated thread to perform various Notification Server tasks.
Impact Depending on which thread fails to start, it will impact different functions:
Garbage daemon – no expired messages will be deleted
MWI audit – no MWI audit will run
Remote user audit – no remote user audit will run
Create BCR session – no remote notification will be sent out
RN schedule – no remote notification will be scheduled
RN audit – Hang remote notification outcalling agent cannot be detected
Recovery Action Restart the Notification service (voice messaging will be temporarily unavailable while the service is restarting). If the problem persists, contact customer support.
Technical Support Action Check the return code. If the problem persists, reboot the server.
Severity Critical
Description The main Notification Server Remote Procedure Call (RPC) thread failed to start.
Impact The Notification service will not process any requests from its clients. MWI updates, remote user audit, desktop registration, mailbox login, and fax auto-printing will not function.
Recovery Action Restart the Notification service (voice messaging will be temporarily unavailable while the service is restarting). If the problem persists, contact customer support.
Technical Support Action Ensure that another Notification service has not already started. If more than one service is started, stop all of them, and then restart the Notification service. Check the event logs for events from lower-level components.
Severity Information
Description The daily Message Waiting Indicator (MWI) audit has started.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Information
Description The daily Message Waiting Indicator (MWI) audit has completed.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Minor
Description The Message Waiting Indicator (MWI) audit failed to run because of a setup error.
Impact Inconsistency in MWI lamps will not be corrected until the next audit.
Recovery Action Make sure the database is running. If the problem persists, restart the Notification service (voice messaging will be temporarily unavailable while the service is restarting). If the problem persists, contact customer support.
Technical Support Action Check the database. Check the return code. Start on-demand MWI audit if you want.
Severity Information
Description Daily garbage daemon audit has started.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Information
Description The daily garbage daemon has completed.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Minor
Description The garbage daemon audit failed to run because of a setup error. This is probably because the database is not yet ready to accept a request.
Impact Expired messages will not be deleted until the next audit.
Recovery Action Ensure the database is running. If the problem persists, restart the Notification service (voice messaging will be temporarily unavailable while the service is restarting). If the problem persists, contact customer support.
Technical Support Action Check the database. Check the return code. Start on-demand garbage daemon audit is you want.
Severity Information
Description The daily remote user audit has started.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Information
Description The daily Remote User audit has completed.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Minor
Description The Remote User audit failed to run because of a setup error. This is probably because the database was not ready to accept requests.
Impact Temporary remote users will not be deleted until the next audit.
Recovery Action Ensure the database is running. If the problem persists, restart the Notification service (voice messaging will be temporarily unavailable while the service is restarting). If the problem persists, contact customer support.
Technical Support Action Check the database. Check the return code. Start on-demand remote user audit if you want.
Severity Major
Description Failed to obtain the indicated semaphore.
Impact Unpredictable system behavior.
Recovery Action Restart the Notification service (voice messaging will be temporarily unavailable while the service is restarting). If the problem persists, contact customer support.
Technical Support Action Check to make sure that another Notification service has not already been started. If more than one service is started, stop all services, then restart the Notification service. Check the event logs for events from lower-level components.
Severity Major
Description Failed to allocate required memory for lock/registration operation.
Impact Mailbox login and desktop registration will fail.
Recovery Action Shutdown any unnecessary applications running on the system. If the problem persists, contact customer support.
Technical Support Action Look for memory leaks. Adjust virtual memory size. Check the event logs for events from lower-level components.
Severity Minor
Description Failed to write to the specified mailslot.
Impact Not Applicable
Recovery Action Locate the Desktop client PC and restart the Desktop Messaging program.
Technical Support Action Not Applicable
Severity Minor
Description After several attempts, the owner of the mailslot did not acknowledge the notification of message status changes.
Impact Not Applicable
Recovery Action No action is required. It is likely that the mailbox user did not terminate the desktop program when powering off the PC.
Technical Support Action Not Applicable
Severity Minor
Description Failed to obtain temporary remote user count or data from the system.
Impact Old remote users will not be deleted until the next audit.
Recovery Action Problem may clear up by the next audit. If the problem persists, contact customer support.
Technical Support Action Check return code. Look for event logs regarding object modules.
Severity Minor
Description Failed to obtain an object handle internal resource.
Impact Alarm notification, fax auto-print, fax print status update, and remote notification may be affected.
Recovery Action Make sure the database is running. If the problem persists, restart the Notification service (voice messaging will be temporarily unavailable while the service is restarting). If the problem still persists, contact customer support.
Technical Support Action Check the database. There is likely some base system problems. Check the event logs for events from lower-level components.
Severity Minor
Description Failed to obtain Message Waiting Indicator (MWI) information for the indicated user.
Impact MWI updates will not occur for the indicated user’s DN.
Recovery Action Make sure the database is running. If the problem occurs for one user only, delete and add the user. If the problem persists, restart the Notification service (voice messaging will be temporarily unavailable while the service is restarting). If the problem still persists, contact customer support.
Technical Support Action Check the database and the return code. Check the database to verify that the indicated user exists and has user entries in the MWIView
Severity Minor
Description Failed to set the Message Waiting Indicator (MWI) lamp for the indicated user.
Impact MWI updates will not occur for the indicated user’s DN.
Recovery Action Verify that the user’s DN is configured in the TAPI and switch database. For more information on this procedure, refer to Part 3 in the CallPilot Installation and Configuration binder.
Technical Support Action Check the return code and the TAPI service. Run the Notification Server tool to turn MWI On and Off.
Severity Minor
Description Failed to obtain Message Waiting Indicator (MWI) message information for the indicated user.
Impact MWI updates will not occur for the indicated user’s DN.
Recovery Action Delete and add the user to try and fix the problem. If the problem persists, contact customer support.
Technical Support Action Attempt to open the message folder using the message package. Check the database to verify that the indicated user exists and has user entries in the MWIView.
Severity Minor
Description Notification of a new message arrival failed for a currently logged in user.
Impact New message arrival will not be announced to the user.
Recovery Action If the problem persists, contact customer support.
Technical Support Action Check the return code.
Severity Minor
Description Because of the failure to obtain user directory information, subsequent users will not be audited.
Impact Expired messages will not be deleted until the next audit.
Recovery Action If problem persists, contact customer support.
Technical Support Action Turn on the GD audit trace using the Notification Server tool. Start an on-demand GD audit (audit will start within one minute), look for the user that is causing the problem. Check that the directory in the Meridian Application Server Multimedia Volume is working using the user package. Delete and add the user again. Turn trace off.
Severity Not Applicable
Description Failed to find the Message Waiting Indicator (MWI) DN in the TAPI database.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Not Applicable
Description Failed to initialize the TAPI database.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Description Failed to read the TAPI database.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Minor
Description Failed to obtain disk usage information for Operational Measurement pegging.
Impact Disk usage OM will not be pegged for the indicated mailbox.
Recovery Action Ensure the Meridian Application Server Multimedia Volume is running. Delete and add the mailbox to fix the problem. If the problem persists, contact customer support.
Technical Support Action Program in Object Modules.
Severity Minor
Description Failed to delete the indicated message.
Impact The indicated expired message was not deleted.
Recovery Action If problem persists, contact customer support.
Technical Support Action Check the message using the Message Package tool. Delete the message manually. If the problem occurs often, contact Product Support.
Severity Minor
Description Failed to obtain profile data about the indicated user.
Impact Expired messages will not be deleted for the indicated user.
Recovery Action If problem persists on next garbage daemon audit, delete and add a user to fix the problem. If an error occurs on more than one user, contact customer support.
Technical Support Action Check to make sure the user’s profile data exists in the database. Look for object module related event codes. Check user profile using the user package.
Severity Minor
Description Failed to update the fax printing status of a message.
Impact Printed fax message will not be marked as printed.
Recovery Action Make sure the database is running. If the problem persists, restart the Notification service (voice messaging will be temporarily unavailable while the service is restarting). If the problem still persists, contact customer support.
Technical Support Action Check return code and take appropriate action.
Severity Minor
Description Failed to read the administrator’s alarm notification properties.
Impact No alarm messages will be delivered to the alarm mailbox until the Alarm notification properties can be read.
Recovery Action Make sure the MAS Multimedia Volume is running. Make sure the alarm mailbox is set to a valid mailbox. If the problem persists, restart the Notification service (voice messaging will be temporarily unavailable while the service is restarting). If the problem still persists, contact customer support.
Technical Support Action Check return code. Check to see if the alarm mailbox can be read using the system package.
Severity Minor
Description Failed to deposit alarm message into the alarm mailbox. The alarm mailbox may be invalid, corrupted, or the Multimedia Volume is full.
Impact The administrator will not receive an alarm notification.
Recovery Action Perform the following:
Ensure that the alarm mailbox is a valid mailbox that the administrator can access to hear the alarm messages.
Ensure that the MAS Multimedia volume is not full.
Delete and add the alarm mailbox again. If the problem persists, contact customer support.
Technical Support Action Check return code and take appropriate action.
Severity Minor
Description Failed to send a remote notification to a user.
Impact Remote notification will be rescheduled for the message.
Recovery Action Check remote notification configuration. If the problem persists, contact customer support.
Technical Support Action Check the return code. Check the remote notification outcalling agent.
Severity Minor
Description Remote Notification Agent failed to register within the timeout limit.
Impact Remote notification will be rescheduled for the message.
Recovery Action If problem persists, contact customer support.
Technical Support Action Check remote notification agent or increase the registration timeout limit using the Notification service tool.
Severity Minor
Description Remote Notification Agent failed to cancel the registration within the timeout limit.
Impact Remote notification will be rescheduled for the message.
Recovery Action If problem persists, contact customer support.
Technical Support Action Check remote notification agent or increase the registration timeout limit using the Notification service tool.
Severity Minor
Description Failed to retrieve remote notification user data.
Impact No remote notification will be sent out for this message. This does not affect other messages.
Recovery Action Make sure the database is running. If problem persists, contact customer support.
Technical Support Action Check the return code. Check the user’s remote notification data. Delete and add the user again.
Severity Major
Description Failed to obtain the indicated event.
Impact Remote notification will not function properly.
Recovery Action Restart the Notification service (voice messaging will be temporarily unavailable while the notification service is restarting). If the problem persists, contact customer support.
Technical Support Action Check the return code. Reboot the server.
Severity Minor
Description Failed to add a recovery record to the database.
Impact User will miss a remote notification if the Notification service has terminated before the user receives a remote notification for the message.
Recovery Action Make sure the database is running. If the problem persists, restart the Notification service (voice messaging will be temporarily unavailable while the service is restarting). If the problem still persists, contact customer support.
Technical Support Action Check the return code and database. Make sure that NMnsRN table exists in the database.
Severity Minor
Description Failed to delete a recovery record from the database.
Impact When the Notification service is restarted, one extra remote notification will be sent out for that message if it is unread.
Recovery Action Make sure the database is running. If the problem persists, restart the Notification service (voice messaging will be temporarily unavailable while the service is restarting). If the problem still persists, contact customer support.
Technical Support Action Check the return code and database. Make sure that NMnsRN table exists in the database.
Severity Major
Description Failed to initialize the routing subsystem for remote notification.
Impact Remote notification cannot be started until the routing subsystem is initialized properly.
Recovery Action Make sure the CTMS server is running. If problem persists, contact customer support.
Technical Support Action Check for CTMS-related problems.
Severity Information
Description The MAS Multimedia Volume is full. Additional alarms will not be delivered to the alarm mailbox.
Impact No new alarm messages will be deposited into the alarm mailbox until space is recovered. Once sufficient space is restored, alarm notification will continue.
Recovery Action Cleanup the MMFS by deleting old messages.
Technical Support Action Run on-demand GD audit and audits for the volume.
Severity Major
Description Unable to register with the Fault Server for alarm notification.
Impact No alarm messages will be sent to the alarm mailbox until the Notification service is registered with the Fault Manager.
Recovery Action Make sure the Fault Manager is running. If the problem persists, contact customer support.
Technical Support Action Use the Task Manager to do an End Process on the nbflt. Check that the Fault Manager is running.
Severity Minor
Description Unable to submit a print batch for auto-printing.
Impact Auto-printing will be attempted again when a new fax message is deposited intot he mailbox. The failed fax message must be manually printed.
Recovery Action For user complaint, manually login to the mailbox and print the fax. If the problem persists, contact customer support.
Technical Support Action Check the return code. If the problem involves only one user, delete and add the user again. For many users, check the object modules event codes.
Severity Critical
Description Unable to initialize the object modules. The Notification service cannot startup.
Impact MWI updates, remote user audit, desktop registration, mailbox login, and fax auto-printing will not function.
Recovery Action Reboot the server. If the problem persists, contact customer support.
Technical Support Action Check return code. Replacing the object modules dll (nmobj.dll) may fix the problem.
Severity Minor
Description Failed to read remote notification recovery records from the database.
Impact Remote notification saved from previous Notification Service sessions will not be sent out until the Notification service is restarted.
Recovery Action Make sure the database is running. If the problem persists, restart the Notification service (voice messaging will be temporarily unavailable while the service is restarting). If the problem still persists, contact customer support.
Technical Support Action Check return code and the database. Check that the NMnsRN table exists in the database.
Severity Minor
Description Failed to create a session for remote notification.
Impact Remote notification cannot be started until a call routing session is created.
Recovery Action If the CTMS server and EMCI service are running, contact customer support. If they are not running, wait for 20 minutes and if it is still not up, reboot the server.
Technical Support Action Check for Blue Call Router (BCR) and CTMS-related problems.
Severity Major
Description The DN does not correspond to a defined mailbox in CallPilot.
Impact The MWI light for the user will not be updated. The mailbox is not defined in the CallPilot system.
Recovery Action Verify that the mailbox has been defined.
Technical Support Action Not Applicable