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 presists, contact customer support organization.
Technical Support Action If the problem presists after server reboot, the CallPilot server installation may not be complete. Contact CallPilot 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 Debug
Description This is a debug error code for internal use. Bad parameters passed in.
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 session ID.
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 RPC APIs call.
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 ODBC APIs call.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
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 No applicable.
Technical Support Action No 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 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. See additional information of this event.
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 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.