NEC Attendant Management System Operations Manual

							NDA-30046 Revision 4.0Page 159
Attendant Management System Operations Manual Process and Error Messages
AMS Error Messages 
(Cont.)Configured # of attendants must be below 50.
The configured number of attendants is too high. Enter the APM configuration 
menu and lower the number.
Could not monitor att.
The application cannot monitor the attendant. Make sure the extensions and logical 
numbers configured for this attendant are valid.
Could not monitor call queue.
The application cannot monitor the call queue. Make sure the call queue is 
correctly assigned via the AMNO command on the PBX MAT and that all 
Monitored Number Indices (MNIs) are unique for every monitored number in the 
switch.
Could not monitor joining station.
The application cannot monitor the joining station. Make sure the station is valid 
and not monitored by another application.
Could not monitor orbit number.
The application cannot monitor the orbit number. Make sure the orbit number is 
correctly assigned via the AMNO command on the PBX MAT and that all 
Monitored Number Indices (MNIs) are unique for every monitored number in the 
switch.
Could not obtain status of OMP queue.
The application cannot ascertain the status of the attendant station process. On an 
attendant station, enter the Call Processing function. From another CRT, initialize 
the Daemon component.
Could not send message to [%s], inactive (Could not send msg to [%s] 
because app is inactive).
The application named between the brackets is not receiving messages. Make sure 
it is initialized and running successfully.
Could not send msg to [%s] because no seq #’s available.
An application cannot send a message to the component named between the 
brackets. Log out of the menus and log back in. If this does not correct the problem, 
contact the system distributor.
Count of park timeouts out of bounds.
The OMP has a problem maintaining a count of parked caller timeouts and will 
attempt to recover automatically. If the problem persists, back the attendant out 
past the login screen using the Esc key and then log back in. 
						

							Page 160NDA-30046 Revision 4.0
Process and Error Messages Attendant Management System Operations Manual
AMS Error Messages 
(Cont.)Daemon has no association.
The Daemon cannot get an OAI association with the PBX. Recheck all OAI 
configurations at the MAT and all OAI configurations in the APM, and then re-
initialize the Daemon.
Database error.
This message is displayed only in menus. Check the error with this number in the 
log file for details.
Db error when finding speed dial.
An error occurred when the application tried to find a speed-dial assignment in the 
database. If it is a -9000 number, make sure the speed dial is configured. If it is, 
contact the system distributor. If it is a -10,000 number, check the Informix manual. 
Use the last three digits as the error code.
Enable timer expired but Enable count invalid.
While trying to recover, the Daemon had a problem bringing up the attendant 
stations.   Terminate the Daemon and re-initialize.
Error acking Attendant.
An attendant logged off before the OAI process could send an acknowledgment. 
No action is necessary.
Error adding call record.
An error occurred while the application was trying to add a call record to the 
database. If it is a -9000 number, contact the system distributor. If it is a -10,000 
number, check the Informix manual. Use the last three digits as the error code.
Error adding call record, no free recs.
The limit of 100 outstanding calls has been reached. Contact the system distributor.
Error allocating memory for [%d] orbit number.
An error occurred while the application was requesting memory from the system 
for the orbit number. Check UNIX kernel memory parameters.
Error attaching to the database (Error attaching to the database).
An error occurred while the application was trying to communicate with the 
database. If it is a -9000 number, contact the system distributor. If it is a -10,000 
number, check the Informix manual. Use the last three digits as the error code. 
Make sure Informix is on-line by entering the Informix command tbmmitor.
Error changing mode on %s.
This message is accompanied by a UNIX error number. Make sure that the file 
named (%s) actually exists. Check the error number for more information. 
						

							NDA-30046 Revision 4.0Page 161
Attendant Management System Operations Manual Process and Error Messages
AMS Error Messages 
(Cont.)Error closing facilities
The application cannot close the OAI facilities in the PBX, probably because of an 
error in the PBX. The PBX error code value (xxxx) gives further detail about this 
error.   Refer to the PBX manuals for this information. Check OAI assignments on 
the PBX MAT and verify the OAI application configurations that were entered 
during installation. No action is needed if this occurs when the link between the 
PBX and UAP is down.
Error connecting to Informix database
An error occurred while the application was trying to communicate with the 
database. If it is a -9000 number, contact the system distributor. If it is a -10,000 
number, check the Informix manual. Use the last three digits as the error code. 
Make sure Informix is on-line by entering the Informix command tbmmitor.
Error deleting a record from the database (Database deletion error)
An error occurred while the application was trying to delete a call record from the 
database. If it is a -9000 number, contact the system distributor. If it is a -10,000 
number, check the Informix manual. Use the last three digits as the error code.
Error deleting a timer
The application cannot delete a timer, generally because of an interprocess 
communication failure. Terminate all AMS processes and halt the APM system. 
Log into the AMS Platform Management Menu with amsadm and select the UNIX 
option. Type the command /oai/utils/rmipc at the prompt, then press Enter. 
Restart the APM system, then restart the application processes.
Error deleting call record
An error occurred while the application was trying to delete a call record from the 
database.   If it is a -9000 number, contact the system distributor. If it is a -10,000 
number, check the Informix manual. Use the last three digits as the error code.
Error deleting tty record.
An error occurred while the application was trying to delete a tty record from the 
database. For error detail and required recovery, find the message in this chapter if 
it is a -9,000 number or in the Informix manual if it is a -10,000 number. If the 
number is in the 10,000 series, the last three digits are the Informix error code.
Error finding name of paged party
An error occurred while the application was trying to find the name of the paged 
party in the database. If it is a -9000 number, contact the system distributor. If it is 
a -10,000 number, check the Informix manual. Use the last three digits as the error 
code.
Error finding speed dial rec in database
An error occurred while the application was trying to find the speed-dial record in 
the database. If it is a -9000 number, contact the system distributor. If it is a -10,000 
number, check the Informix manual. Use the last three digits as the error code. 
						

							Page 162NDA-30046 Revision 4.0
Process and Error Messages Attendant Management System Operations Manual
AMS Error Messages 
(Cont.)Error getting AMS Daemon name from file.
An error occurred while the application was retrieving the Daemon application 
name.   Make sure that the file configured for the Daemon within the APM Amsfile 
directory exists, that the name itself exists, and that the directory exists. Check the 
UNIX error number for more detail.
Error getting call records.
An error occurred while the application was trying to generate statistics from call 
records. Check the error log for the error number. For error detail and required 
recovery, find the message in this chapter if it is a -9,000 number or in the Informix 
manual if it is a -10,000 number. If the number is in the 10,000 series, the last three 
digits are the Informix error code.
Error getting queue call records.
An error occurred while the application was trying to generate statistics from queue 
call records. For error detail and required recovery, find the message in this chapter 
if it is a -9,000 number or in the Informix manual if it is a -10,000 number. If the 
number is in the 10,000 series, the last three digits are the Informix error code.
Error in menu command (Error in menu command)
An error occurred while the application was attempting to implement a menu 
command such as displaying a file.
Error in type returned from database lookup (Wrong type returned from 
dblookup)
An error occurred while the application was performing a directory lookup in the 
AMS Informix database. If it is a -9000 number, contact the system distributor. If 
it is a -10,000 number, check the Informix manual. Use the last three digits as the 
error code.
Error initializing. AMS Server is exiting
An error occurred during initialization processes. Check application configurations 
in the APM file, making sure the logical names are correctly entered. Then retry.
Error initializing multiple screen program (Error in multiple screen prog.)
Ask the administrator to make sure that a file exists for this monitor so that screen 
switching is possible. (This error is displayed as “Error initializing multiple screen 
program in errlog” in the error log. Refer to the APM error log through the APM 
Operations Menu.) This file will be in /oai/app/ams/cfg/scrn. It will be the name of 
the tty. Make sure it exists and has appropriate read/write permissions for the AMS 
user. 
						

							NDA-30046 Revision 4.0Page 163
Attendant Management System Operations Manual Process and Error Messages
AMS Error Messages 
(Cont.)Error initializing shared memory
The application cannot initialize recall shared memory. Terminate all AMS 
processes. Check the AMS configuration database values for the shared memory 
keys and make sure they are unique among applications running on the system. 
Reinitialize. If the problem persists, check UNIX kernel shared memory 
parameters. Then, if the problem still persists, terminate all application processes 
and halt the APM system. Log into the AMS Platform Management Menu with 
amsadm, and select the UNIX option. Type the command /oai/utils/rmipc at the 
prompt, then press Enter. Restart the APM system, then restart the application 
processes.
Error initializing. AMS Server is exiting
An error occurred during initialization processes. Check application configurations 
in the APM file, making sure the logical names are correctly entered, then retry.
Error initializing the OMP Daemon.
An error occurred while the application was either reading the AMS database 
configuration files or writing process information to the disk. Verify that AMS 
databases were correctly installed in the APM database directories. Check file 
permissions in the AMS directories so that they are writeable by the AMS user. If 
the problem persists, reinstall AMS.
Error initializing the OMP Park Manager.
An error occurred while the application was either reading the AMS database 
configuration files or writing process information to the disk. Verify that AMS 
databases were correctly installed in the APM database directories. Check file 
permissions in the AMS directories so that they are writeable by the AMS user. If 
the problem persists, reinstall AMS.
Error inserting a record into the database (Error inserting record).
The application cannot insert a record into the database. If it is a -9000 number, 
contact the system distributor. If it is a -10,000 number, check the Informix manual. 
Use the last three digits as the error code.
Error inserting the record into the database.
An error occurred while the application was trying to add a record to the given 
database. For error detail and required recovery, find the message in this chapter if 
it is a -9,000 number or in the Informix manual if it is a -10,000 number. If the 
number is in the 10,000 series, the last three digits are the Informix error code.
Error locking a record in the database (Error locking a record in the db).
The application cannot lock a record in the database.   If it is a -9000 number, 
contact the system distributor. If it is a -10,000 number, check the Informix manual. 
Use the last three digits as the error code. 
						

							Page 164NDA-30046 Revision 4.0
Process and Error Messages Attendant Management System Operations Manual
AMS Error Messages 
(Cont.)Error locking record in tidx table. Db & automated rpt gen discrepancy.
An error occurred because two people have attempted to add, change, or delete a 
time index at the same time. This has caused a difference between the Informix 
database and other internal system tables that must be in agreement. This is a rare 
but significant error occurring between Informix and the operating system. When 
this message is displayed, it is necessary to add, modify, or delete a time index 
record. In the process, Informix and the system “clean up” the results of the 
previous error.
Error locking semaphore.
The application cannot lock the call records semaphore. Terminate all AMS 
processes. Check the AMS configuration database values for the shared memory 
keys, make sure they are unique among applications running on the system, then 
reinitialize. If the problem persists, check UNIX kernel shared memory 
parameters. If the problem still persists, terminate all application processes and halt 
the APM system. Log into the AMS Platform Management Menu with amsadm 
and select the UNIX option. Type the command /oai/utils/rmipc at the prompt, 
then press Enter. Restart the APM system, then restart the application processes.
Error modifying a record in the database (Database error modifying record).
The application cannot modify the record in the database. If it is a -9000 number, 
contact the system distributor. If it is a -10,000 number, check the Informix manual. 
Use the last three digits as the error code.
Error modifying record in time index table.
An error occurred while the application was changing a record in the time index 
table.   For error detail and required recovery, find the message in this chapter if it 
is a -9,000 number or in the Informix manual if it is a -10,000 number.
Error opening association.
The application cannot get an OAI association with the PBX. Recheck all OAI 
configurations at the MAT and all OAI configurations in the APM. Then terminate 
and reinitialize the application.
Error opening facilities.
The application cannot open the OAI facilities in the PBX, probably because of an 
error in the PBX. The PBX error code value (xxxx) gives further detail about this 
error. Refer to the PBX manuals for this information. Check OAI assignments on 
the PBX MAT and verify the OAI application configurations that were entered 
during installation.
Error opening OMP queue.
The Daemon cannot open the queue that is configured for the OMP. Verify that the 
OMP queue key configured for the AMS configuration database is valid. 
						

							NDA-30046 Revision 4.0Page 165
Attendant Management System Operations Manual Process and Error Messages
AMS Error Messages 
(Cont.)Error opening semaphore.
The application cannot open the call records semaphore. Terminate all AMS 
processes. Check the AMS configuration database values for the shared memory 
keys, make sure they are unique among applications running on the system, then 
reinitialize. If the problem persists, check UNIX kernel shared memory 
parameters. If the problem continues, terminate all application processes and halt 
the APM system. Log into the AMS Platform Management Menu with amsadm 
and select the UNIX option. Type the command /oai/utils/rmipc at the prompt, 
then press Enter. Restart the APM system, then restart the application processes.
Error performing status check on att.
An error occurred while the application was checking the status of an attendant 
station (i.e., the heartbeat that the Daemon sends to the attendant). Check the APM 
log for more error detail. If possible, validate the status of the ipc queues.
Error querying att recs.
An error occurred while the application was querying the attendant records in the 
database. If it is a -9000 number, contact the system distributor. If it is a -10,000 
number, check the Informix manual. Use the last three digits as the error code.
Error querying database for tty record.
An error occurred while the application was querying the database for a tty record. 
For error detail and required recovery, find the message in this chapter if it is a -
9,000 number or in the Informix manual if it is a -10,000 number. If the number is 
in the 10,000 series, the last three digits are the Informix error code.
Error querying orbit database.
An error occurred while the application was querying the orbit numbers in the 
database. If it is a -9000 number, contact the system distributor. If it is a -10,000 
number, check the Informix manual. Use the last three digits as the error code.
Error querying queue database.
An error occurred while the application was querying the queue records in the 
database. If it is a -9000 number, contact the system distributor. If it is a -10,000 
number, check the Informix manual. Use the last three digits as the error code.
Error querying timer recs.
An error occurred while the application was querying the timer records in the 
database. If it is a -9000 number, contact the system distributor. If it is a -10,000 
number, check the Informix manual. Use the last three digits as the error code.
Error querying the database.
An error occurred while the application was querying the database. If it is a -9000 
number, contact the system distributor. If it is a -10,000 number, check the 
Informix manual. Use the last three digits as the error code. 
						

							Page 166NDA-30046 Revision 4.0
Process and Error Messages Attendant Management System Operations Manual
AMS Error Messages 
(Cont.)Error querying tty table.
An error occurred while the application was querying the tty table. For error detail 
and required recovery, find the message in this chapter if it is a -9,000 number or 
in the Informix manual if it is a -10,000 number. If the number is in the 10,000 
series, the last three digits are the Informix error code.
Error reading APM database.
The application cannot read the AMS/APM database. Check the file permissions 
set on AMS/APM databases. Use the APM to verify that changes to these databases 
have been processed and installed using the APM Database Administration menu 
options. If the problem persists, reinstall the application.
Error reading from association
This is a PBX error. The PBX error code value (xxxx) means further detail about 
this error. Refer to the PBX manuals for this information.
Error reading OMP database
The application cannot read the OMP database. Check the file permissions that are 
set on AMS/APM databases. Use the APM to verify that changes to these databases 
have been processed and installed using the APM Database Administration menu 
options. If the problem persists, reinstall the application.
Error reading shared stats database
The application cannot read the AMS/Attendant Statistics shared configuration 
database. Check the file permissions set on AMS/APM databases. Use the APM 
Database Administration menu options to verify that changes to these databases 
have been processed and installed. If the problem persists, reinstall the application.
Error releasing association
The application has been unable to release an OAI association, generally due to a 
communication failure between the UAP and the PBX. Terminate the application 
using the Kill option on the APM menus. The number specified in the message is 
the error detail from the PBX which should explain why the application could not 
release the association.
Error retrieving employee message (Error retrieving employee’s msgs)
An error occurred while retrieving an employee message. If it is a -9000 number, 
contact the system distributor. If it is a -10,000 number, check the Informix manual. 
Use the last three digits as the error code.
Error saving report.
A system error occurred while the report was being saved. 
						

							NDA-30046 Revision 4.0Page 167
Attendant Management System Operations Manual Process and Error Messages
AMS Error Messages 
(Cont.)Error sending ack to att [%d]
An error occurred while the application was attempting to send an 
acknowledgment to the attendant.   Terminate all application processes and halt the 
APM system. Log into the AMS Platform Management Menu with amsadm and 
select the UNIX option. Type the command /oai/utils/rmipc at the prompt, then 
press Enter. Restart the APM system, then restart the application processes. If the 
problem persists, halt and restart the APM system.
Error sending Att [%d] a “go online” message
There is an interprocess communication problem between processes. Terminate all 
application processes and halt the APM system. Log into the AMS Platform 
Management Menu with amsadm and select the UNIX option. Type the command 
/oai/utils/rmipc at the prompt, then press Enter. Restart the APM system, then 
restart the application processes. If the problem persists, halt and restart the APM 
system.
Error sending Att [%d] a handshake message.
There is a communication problem among processes. Terminate all application 
processes and halt the APM system. Log into the AMS Platform Management 
Menu with amsadm and select the UNIX option. Type the command /oai/utils/
rmipc at the prompt, then press Enter. Restart the APM system, then restart the 
application processes. If the problem persists, halt and restart the APM system.
Error sending message to OMP queue.
There is a communication problem among processes. Terminate all application 
processes and halt the APM system. Log into the AMS Platform Management 
Menu with amsadm and select the UNIX option. Type the command /oai/utils/
rmipc at the prompt, then press Enter. Restart the APM system, then restart the 
application processes. If the problem persists, halt and restart the APM system.
Error sending problem message to Att.
There is a communication problem among processes. Terminate all application 
processes and halt the APM system. Log into the AMS Platform Management 
Menu with amsadm and select the UNIX option. Type the command /oai/utils/
rmipc at the prompt, then press Enter. Restart the APM system, then restart the 
application processes. If the problem persists, halt and restart the APM system.
Error sending SCF[%d] for att [%d] [err=0x%x].
This error message is probably caused by a non-critical event such as trying to 
answer an abandoned call, but it is provided in case of a more consistent OAI 
communication problem. The number given in the message is a PBX error code; 
check the PBX manuals for more detail.
Note:
If this site does direct transfers to a hunt group, the error “Error sending 
SCF[103.[err=0x913a]” will occur often. This means that a no-answer recall 
was both impossible and unnecessary. 
						

							Page 168NDA-30046 Revision 4.0
Process and Error Messages Attendant Management System Operations Manual
AMS Error Messages 
(Cont.)Error sending SMFR[%d] for att [%d] [err=0x%x].
An error occurred while the application was trying to stop or start monitoring a 
number. The number given in the message is a PBX error code. Check the PBX 
manuals for more detail. This is usually non-critical and occurs in a race condition.
Error setting announcement retry timer.
An error occurred while the application was attempting to set an announcement 
retry timer. Terminate all application processes and halt the APM system. Log into 
the AMS Platform Management Menu with amsadm and select the UNIX option. 
Type the command /oai/utils/rmipc at the prompt, then press Enter. Restart the 
APM system, then restart the application processes. If the problem persists, halt 
and restart the APM system.
Error setting enable timer.
An error occurred while the application was attempting to set an enable timer. 
Terminate all application processes and halt the APM system. Log into the AMS 
Platform Management Menu with amsadm and select the UNIX option. Type the 
command /oai/utils/rmipc at the prompt, then press Enter. Restart the APM 
system, then restart the application processes. If the problem persists, halt and 
restart the APM system.
Error setting heartbeat timer.
An error occurred while the application was attempting to set a heartbeat timer. 
Terminate all application processes and halt the APM system. Log into the AMS 
Platform Management Menu with amsadm and select the UNIX option. Type the 
command /oai/utils/rmipc at the prompt, then press Enter. Restart the APM 
system, then restart the application processes. If the problem persists, halt and 
restart the APM system. 
Error setting monitoring on rt/trk.
An error occurred while the application was attempting to initiate monitoring on a 
route/trunk. The number provided in the message gives the PBX error detail. Refer 
to the PBX system manuals for that information.
Error setting monitoring on sta.
An error occurred while the application was attempting to initiate monitoring on a 
route/trunk. The number provided in the message gives the PBX error detail; refer 
to the PBX system manuals for that information.
Error setting oldage timer.
An error occurred while the application was attempting to set an oldage timer. 
Terminate all application processes and halt the APM system. Log into the AMS 
Platform Management Menu with amsadm and select the UNIX option. Type the 
command /oai/utils/rmipc at the prompt, then press Enter. Restart the APM 
system, then restart the application processes. If the problem persists, halt and 
restart the APM system.