These events are related to the Event Scheduler.
Severity MAJOR
Description The registry may not be set up correctly after CallPilot server installation. Event Scheduler has problem locating a registry key or value.
Impact Event Scheduler may not be able to start scheduled jobs. Scheduled jobs include system defined audits and administrator scheduled backup, restore jobs. This event does not affect CallPilot messaging capability.
Recovery Action Registry setting may not be effective immediate after CallPilot server installation. A server reboot may correct the problem. If problem persists, contact customer support.
Technical Support Action If the problem persists after server reboot, the CallPilot server installation may not be complete. Contact Product Support to discuss recovery options 1) reinstall CallPilot server, 2) rebuild CallPilot server from image, 3) manually create missing registry keys and values.
Severity Major
Description An internal error occurred when accessing the database.
Impact Event scheduler cannot add, reschedule or delete jobs from the database. It cannot retrieve scheduled jobs and launching those jobs is not possible. Scheduled jobs include system defined audits and administrator scheduled backup, restore jobs. This event does not affect CallPilot messaging capability.
Recovery Action Ensure database and CallPilot LDAP service are running.
Technical Support Action Examine the return code reported by this event. To resolve this problem, restart NMAOS service. If problem remains, restart CallPilot LDAP Service. If the problem cannot be corrected, reboot the CallPilot server. Contact Product Support if the problem persists after reboot. A copy of the CallPilot server event log and trace of the nbschsrv.dll_<process number> component will help speed up problem investigation. The <process number> is the actual number of the process that uses event scheduler, and which is assigned by the operating system at run time; therefore, it cannot be specified here. The nbschsrv.dll_<process number> trace can be obtained from Trace Viewer support tool.
Severity Critical
Description Event Scheduler failed to be initialized. The (Event Scheduler thread) program cannot be started.
Impact Not Applicable
Recovery Action Restart NMAOS service. If problem cannot be corrected, contact customer support.
Technical Support Action Reboot the CallPilot server. If problem persists, contact Product Support.
Severity Major
Description Event scheduler failed to launch a job or execute a command on the CallPilot server.
Impact The scheduled job or the specified command cannot be executed on the CallPilot server. Scheduled jobs include system defined audits and administrator scheduled backup, restore jobs. This event does not affect CallPilot messaging capability.
Recovery Action Examine the additional information of the event and the return code. The command that cannot be executed may be included in the additional information. Examine scheduled job with this command and ensure the job has the right options chosen. Contact customer support.
Technical Support Action If the problem cannot be corrected by sanitizing scheduled jobs, collect the event log and contact Product Support.
Severity Major
Description There is an internal error reported from the operating system. Event scheduler is out of service.
Impact Event scheduler cannot add, reschedule or delete jobs from the database. It cannot retrieve scheduled jobs and launching those jobs is not possible. Scheduled jobs include system defined audits and administrator scheduled backup, restore jobs. This event does not affect CallPilot messaging capability.
Recovery Action If problem persists, contact customer support.
Technical Support Action This is an unusual problem. The operating system may be unstable. Reboot the CallPilot server. If problem persists, contact Product Support.
Severity Info
Description Event Scheduler Status Startup/Shutdown Report
Impact If event scheduler is shutdown, it cannot start scheduled jobs. Scheduled jobs include system defined audits and administrator scheduled backup, restore jobs. This event does not affect CallPilot messaging capability.
Recovery Action Not applicable.
Technical Support Action Not applicable.
Severity Debug
Description This is a debug error code for internal use. Internal function error.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Debug
Description This is a debug error code for internal use. Memory allocation failure.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Debug
Description This is a debug error code for internal use. Invalid job owner.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Debug
Description This is a debug error code for internal use. Invalid job tag.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Debug
Description This is a debug error code for internal use. Invalid server name.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Debug
Description This is a debug error code for internal use. Error from creating mutex.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Debug
Description This is a debug error code for internal use. Bad time in conversion.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Debug
Description This is a debug error code for internal use. Time before January 1, 1970. Not supported.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Debug
Description This is a debug error code for internal use. Bad time specified.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Debug
Description This is a debug error code for internal use. Unexpected empty bit map.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Debug
Description This is a debug error code for internal use. Error from shutting down server.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Debug
Description This is a debug error code for internal use. Error from NBsch_RPCBind/NBsch_RPCUnbind/NBsch_SetEnv.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Debug
Description This is a debug error code for internal use. Invalid database environment handle.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Debug
Description This is a debug error code for internal use. Database record not found.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Debug
Description This is a debug error code for internal use. Invalid Customer ID/CUSTID or Owner/PCUserID.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Description More than 1 session was obtained with a specific session ID.
Recovery Action Verify that the server has been properly installed.
Technical Support Action This return code occurs when more than 1 session is retrieved from the database with a specific session ID. It may be necessary to check the data in the tables for any inconsistency.
Description Cannot obtain user name who is logged onto the session.
Recovery Action Verify that the server has been properly installed and database is running.
Technical Support Action This return code occurs when the Configuration Server is unable to retrieve a user's information from the database. This may be due to an RPC (Remote Procedure Call) I.e. client/server communication problem. Or the information was missing from the database. It may be necessary to check the data in the database.
Description More than 1 user obtained with the specific UUID.
Recovery Action Verify that the server has been properly installed and database is running.
Technical Support Action This return code occurs when more than 1 user is retrieved from the nbuser table with a specific UUID. It may be necessary to check the data in the tables for any inconsistency, especially nbuser.
Description Failed to connect to server database because of incorrect ODBC information.
Recovery Action Bring up the ODBC Manager from the client's Control Panel, and verify that ODBC is properly installed. Verify that the client can login properly to the server.
Technical Support Action The DSN can be composed of the IP/IPX address of the server that is entered when configuring the client. Verify that this has been properly entered and that the client can login to the server. Verify that ODBC and the client have been properly installed, as well as the proper database ODBC driver that enables the client to connect to the server's database
Description This is an internal error. When reporting event, buffer overflow was detected. This has no impact to the CallPilot messaging capability.
Recovery Action Not applicable
Technical Support Action Not applicable
Description Unexpected exception while reporting error.
Recovery Action Not applicable
Technical Support Action Not applicable
Description Event scheduler (scanner thread) failed to start due to some internal problem. Event code will indicate if it is a database related problem.
Recovery Action Not applicable
Technical Support Action Not applicable
Description This is an internal error. Invalid parameter was submitted to event scheduler.
Recovery Action Not applicable
Technical Support Action Not applicable
Description Problem accessing the database.
Recovery Action Not applicable
Technical Support Action Not applicable
Description The requested job cannot be found.
Recovery Action Not applicable
Technical Support Action Not applicable
Description A (one shot) job has no date specified or the internal date bitmap is corrupted.
Recovery Action Not applicable
Technical Support Action Not applicable
Description The job is scheduled with an invalid time or date.
Recovery Action Not applicable
Technical Support Action Not applicable
Description Event scheduler failed to launch the specified command.
Recovery Action Not applicable
Technical Support Action Not applicable
Severity Not Applicable
Description The Configuration Server was unable to add an ACCESS DN record.
Impact Not Applicable
Recovery Action From the Services applet in the Control Panel, check to see whether the database and the Configuration Server are running.
Technical Support Action This return code occurs when the Configuration Server is unable to add an entry to the NBASDN database table. This may be due to a database-related problem or an RPC (Remote Procedure Call) I.e. client/server-related problem.
If the Configuration Server is running, and there is a database-related problem, then there will be a Debug event (40799) in the Windows NT Application Event Log that details the database problem further.
Severity Not Applicable
Description The Configuration Service was unable to read an ACCESS DN record.
Impact Not Applicable
Recovery Action From the Services applet in the Control Panel, check to see whether the database and the Configuration Server are running.
Technical Support Action This return code occurs when the Configuration Server is unable to read an entry from the NBASDN database table. This may be due to a database-related problem or an RPC (Remote Procedure Call) I.e. client/server-related problem.
If the Configuration Server is running, and there is a database-related problem, then there will be a Debug event (40799) in the Windows NT Application Event Log that details the database problem further.
Severity Not Applicable
Description The Configuration Server was unable to modify an ACCESS DN record.
Impact Not Applicable
Recovery Action From the Services applet in the Control Panel, check to see whether the database and the Configuration Server are running.
Technical Support Action This return code occurs when the Configuration Server is unable to modify an entry from the NBASDN database table. This may be due to a database-related problem or an RPC (Remote Procedure Call) I.e. client/server-related problem.
If the Configuration Server is running, and there is a database-related problem, then there will be a Debug event (40799) in the Windows NT Application Event Log that details the database problem further.
Severity Not Applicable
Description The Configuration Server was unable to delete an ACCESS DN record.
Impact Not Applicable
Recovery Action From the Services applet in the Control Panel, check to see whether the database and the Configuration Server are running.
Technical Support Action This return code occurs when the Configuration Server is unable to delete an entry from the NBASDN database table. This may be due to a database-related problem or an RPC (Remote Procedure Call) I.e. client/server-related problem.
If the Configuration Server is running, and there is a database-related problem, then there will be a Debug event (40799) in the Windows NT Application Event Log that details the database problem further.
Severity Not Applicable
Description The Configuration Server was unable to determine the Min/Max port values for an Access DN record.
Impact Not Applicable
Recovery Action From the Services applet in the Control Panel, check to see whether the database and the Configuration Server are running.
Technical Support Action This return code occurs when the Configuration Server is unable to determine the min/max values related to an Access DN record. This may be due to a database-related problem or an RPC (Remote Procedure Call) I.e. client/server-related problem.
If the Configuration Server is running, and there is a database-related problem, then there will be a Debug event (40799) in the Windows NT Application Event Log that details the database problem further.
Severity Not Applicable
Description The Configuration Server was unable to add an MMApp (Multi-Media Application) record.
Impact Not Applicable
Recovery Action From the Services applet in the Control Panel, check to see whether the database and the Configuration Server are running.
Technical Support Action This return code occurs when the Configuration Server is unable to add an entry to the NBMMApp database table. This may be due to a database-related problem or an RPC (Remote Procedure Call) I.e. client/server-related problem.
If the Configuration Server is running, and there is a database-related problem, then there will be a Debug event (40799) in the Windows NT Application Event Log that details the database problem further.
Severity Not Applicable
Description The Configuration Server was unable to read an MMApp (Multi-Media Application) record.
Impact Not Applicable
Recovery Action From the Services applet in the Control Panel, check to see whether the database and the Configuration Server are running.
Technical Support Action This return code occurs when the Configuration Server is unable to read an entry to the NBMMApp database table. This may be due to a database-related problem or an RPC (Remote Procedure Call) I.e. client/server-related problem.
If the Configuration Server is running, and there is a database-related problem, then there will be a Debug event (40799) in the Windows NT Application Event Log that details the database problem further.
Severity Not Applicable
Description The Configuration Server was unable to modify an MMApp (Multi-Media Application) record.
Impact Not Applicable
Recovery Action From the Services applet in the Control Panel, check to see whether the database and the Configuration Server are running.
Technical Support Action This return code occurs when the Configuration Server is unable to modify an entry to the NBMMApp database table. This may be due to a database-related problem or an RPC (Remote Procedure Call) I.e. client/server-related problem.
If the Configuration Server is running, and there is a database-related problem, then there will be a Debug event (40799) in the Windows NT Application Event Log that details the database problem further.
Severity Not Applicable
Description The Configuration Server was unable to delete an MMApp (Multi-Media Application) record.
Impact Not Applicable
Recovery Action From the Services applet in the Control Panel, check to see whether the database and the Configuration Server are running.
Technical Support Action This return code occurs when the Configuration Server is unable to delete an entry to the NBMMApp database table. This may be due to a database-related problem or an RPC (Remote Procedure Call) I.e. client/server-related problem.
If the Configuration Server is running, and there is a database-related problem, then there will be a Debug event (40799) in the Windows NT Application Event Log that details the database problem further.
Severity Not Applicable
Description The Configuration Server was unable to add a TN record.
Impact Not Applicable
Recovery Action From the Services applet in the Control Panel, check to see whether the database and the Configuration Server are running.
Technical Support Action This return code occurs when the Configuration Server is unable to add an entry to the NBTN database table. This may be due to a database-related problem or an RPC (Remote Procedure Call) I.e. client/server-related problem.
If the Configuration Server is running, and there is a database-related problem, then there will be a Debug event (40799) in the Windows NT Application Event Log that details the database problem further.
Severity Not Applicable
Description The Configuration Server was unable to read a TN record.
Impact Not Applicable
Recovery Action From the Services applet in the Control Panel, check to see whether the database and the Configuration Server are running.
Technical Support Action This return code occurs when the Configuration Server is unable to read an entry to the NBTN database table. This may be due to a database-related problem or an RPC (Remote Procedure Call) I.e. client/server-related problem.
If the Configuration Server is running, and there is a database-related problem, then there will be a Debug event (40799) in the Windows NT Application Event Log that details the database problem further.
Severity Not Applicable
Description The Configuration Server was unable to modify a TN record.
Impact Not Applicable
Recovery Action From the Services applet in the Control Panel, check to see whether the database and the Configuration Server are running.
Technical Support Action This return code occurs when the Configuration Server is unable to modify an entry to the NBTN database table. This may be due to a database-related problem or an RPC (Remote Procedure Call) I.e. client/server-related problem.
If the Configuration Server is running, and there is a database-related problem, then there will be a Debug event (40799) in the Windows NT Application Event Log that details the database problem further.
Severity Not Applicable
Description The Configuration Server was unable to delete a TN record.
Impact Not Applicable
Recovery Action From the Services applet in the Control Panel, check to see whether the database and the Configuration Server are running.
Technical Support Action This return code occurs when the Configuration Server is unable to delete an entry to the NBTN database table. This may be due to a database-related problem or an RPC (Remote Procedure Call) I.e. client/server-related problem.
If the Configuration Server is running, and there is a database-related problem, then there will be a Debug event (40799) in the Windows NT Application Event Log that details the database problem further.
Severity Not Applicable
Description Failed to get SUM of MinPorts for VOICE, FAX and ASR.
Impact Not Applicable
Recovery Action From the Services applet in the Control Panel, check to see whether the database and the Configuration Server are running.
Technical Support Action This return code occurs when the Configuration Server is unable to obtain the minports for voice, fax and ASR from the NBResourceParameter database table. This may be due to a database-related problem or an RPC (Remote Procedure Call) I.e. client/server-related problem.
If the Configuration Server is running, and there is a database-related problem, then there will be a Debug event (40799) in the Windows NT Application Event Log that details the database problem further.
Severity Not Applicable
Description The Configuration Server was unable to add a host record.
Impact Not Applicable
Recovery Action From the Services applet in the Control Panel, check to see whether the database and the Configuration Server are running.
Technical Support Action This return code occurs when the Configuration Server is unable to add an entry to the NBHOST database table. This may be due to a database-related problem or an RPC (Remote Procedure Call) I.e. client/server-related problem.
If the Configuration Server is running, and there is a database-related problem, then there will be a Debug event (40799) in the Windows NT Application Event Log that details the database problem further.
Severity Not Applicable
Description The Configuration Server was unable to read a host record.
Impact Not Applicable
Recovery Action From the Services applet in the Control Panel, check to see whether the database and the Configuration Server are running.
Technical Support Action This return code occurs when the Configuration Server is unable to read an entry to the NBHOST database table. This may be due to a database-related problem or an RPC (Remote Procedure Call) I.e. client/server-related problem.
If the Configuration Server is running, and there is a database-related problem, then there will be a Debug event (40799) in the Windows NT Application Event Log that details the database problem further.
Severity Not Applicable
Description The Configuration Server was unable to modify a host record.
Impact Not Applicable
Recovery Action From the Services applet in the Control Panel, check to see whether the database and the Configuration Server are running.
Technical Support Action This return code occurs when the Configuration Server is unable to modify an entry to the NBHOST database table. This may be due to a database-related problem or an RPC (Remote Procedure Call) I.e. client/server-related problem.
If the Configuration Server is running, and there is a database-related problem, then there will be a Debug event (40799) in the Windows NT Application Event Log that details the database problem further.
Severity Not Applicable
Description The Configuration Server was unable to delete a host record.
Impact Not Applicable
Recovery Action From the Services applet in the Control Panel, check to see whether the database and the Configuration Server are running.
Technical Support Action This return code occurs when the Configuration Server is unable to delete an entry to the NBHOST database table. This may be due to a database-related problem or an RPC (Remote Procedure Call) I.e. client/server-related problem.
If the Configuration Server is running, and there is a database-related problem, then there will be a Debug event (40799) in the Windows NT Application Event Log that details the database problem further.
Severity Not Applicable
Description The NBResourceParameter record was modified in the interim by someone else.
Impact Not Applicable
Recovery Action From the Services applet in the Control Panel, check to see whether the database and the Configuration Server are running.
Technical Support Action This return code occurs when the Configuration Server is unable to modify an entry from the NBResourceParameter database table. This may be due to a database-related problem or an RPC (Remote Procedure Call) I.e. client/server-related problem or another user modified it.
If the Configuration Server is running, and there is a database-related problem, then there will be a Debug event (40799) in the Windows NT Application Event Log that details the database problem further.
Severity Not Applicable
Description The Configuration Server was unable to retrieve the reporter database userid/login.
Impact Not Applicable
Recovery Action From the Services applet in the Control Panel, check to see whether the Configuration Server is running. Check that the server was properly installed.
Technical Support Action This return code occurs when the Configuration Server is unable to retrieve a database userid/login. This may be due to an RPC (Remote Procedure Call) I.e. client/server communication problem.
Severity Not Applicable
Description The ODBC driver required to communicate directly with the database on the server is not installed.
Impact Not Applicable
Recovery Action Verify that the client installation completed successfully.
Technical Support Action From the ODBC Manager in the Control Panel (on the client), verify that the ODBC driver for the database (SQLAnywhere or Sybase) has been properly installed.
Severity Not Applicable
Description Unable to configure ODBC Data Source Name (DSN).
Impact Not Applicable
Recovery Action Bring up the ODBC Manager from the client's Control Panel, and verify that ODBC is properly installed. Verify that the client can login properly to the server.
Technical Support Action The DSN can be composed of the IP/IPX address of the server that is entered when configuring the client. Verify that this has been properly entered and that the client can login to the server.
Verify that ODBC and the client have been properly installed, as well as the proper database ODBC driver that enables the client to connect to the server's database.
Severity Not Applicable
Description The Configuration Server did not have enough memory to perform the requested operation.
Impact Not Applicable
Recovery Action Check the available memory on the server.
Technical Support Action This is an indication of low memory on the server. It may be indicative of memory leaks or just lack of sufficient memory in general. Using the Windows NT Task Manager utility on the server, check memory usage of the server in general, and of Nortel processes, to see if any are using an excessive amount of memory. If this is the case, consider restarting the offending process(es).
Severity Not Applicable
Description Not enough CCR’s for the given SPC’s.
Impact Not Applicable
Recovery Action Verify that the server has been properly installed.
Technical Support Action This indicates improper installation of the server I.e. that there are insufficient CCR records for the required number of SPC records. Use the nbcfgtd support tool to check the number of CCR records. It may be necessary to reconfigure the middleware tables using this tool.
Severity Not Applicable
Description There was Insufficient hardware to satisfy the number of channels required.
Impact Not Applicable
Recovery Action Check that all necessary hardware has been installed properly.
Technical Support Action This return code occurs when the Configuration Server is unable to accommodate the CallPilot system with the desired configuration because there is not enough hardware. The middleware tables will still be setup, but the resources will be unavailable. Therefore, there is Insufficient resources to support requested number of channel types for each media. It may be necessary to reconfigure the middleware tables using this tool.
Check that all necessary hardware has been installed properly and tightly plugged in
Severity Not Applicable
Description Failed to launch a GUI during configuration of CallPilot.
Impact Not Applicable
Recovery Action Check that Nortel GUIs show up in the Server Control Panel. This will indicate whether the GUI executables exist in the system or not.
Technical Support Action This return code occurs when the Configuration Server is unable to create a process to launch a configuration GUI. Check that all the configuration GUI executables exist in D:\Nortel\bin.
Severity Not Applicable
Description Country Code is invalid or not defined.
Impact Not Applicable
Recovery Action Verify that the file flash_cp.out exists in D:\dsp. Verify that the server has been properly installed and the database is running.
Technical Support Action This return code occurs when the country code obtained from the database is not defined in the list of country codes in the flash_cp.out file. This may be due to corrupted flash_cp.out file or corrupted data in the table nbspc. Make sure the file flash_cp.out is not missing from D:\dsp.
Severity Not Applicable
Description Country Code is invalid or not defined.
Impact Not Applicable
Recovery Action Verify that the file flash_cp.out exists in D:\dsp. Verify that the server has been properly installed and the database is running.
Technical Support Action This return code occurs when the country code obtained from the database is not defined in the list of country codes in the flash_cp.out file. This may be due to corrupted flash_cp.out file or corrupted data in the table nbspc. Make sure the file flash_cp.out is not missing from D:\dsp.
Severity Not Applicable
Description Cannot retrieve a list of countries.
Impact Not Applicable
Recovery Action Verify that the file flash_cp.out exists in D:\dsp.
Technical Support Action This return code occurs when the Configuration Server is unable to retrieve a list of countries from the file D:\dsp\flash_cp.out. This may due to a corrupted or missing file. Make sure the file flash_cp.out is not missing from D:\dsp.
Severity Not Applicable
Description Cannot obtain a list of active Sessions for Admin Journaling.
Impact Not Applicable
Recovery Action Verify that the server has been properly installed and database is running.
Technical Support Action This return code occurs when the Configuration Server is unable to retrieve a session's information from the database. This may be due to an RPC (Remote Procedure Call) I.e. client/server communication problem. Or the information was missing from the database