Error Number Tables

Error Number	Severity	Description	Solution/Action
1102 1103	ERROR	Read Error Write Error There was an error reading or writing from TRAN.DAT. This could be a one time occurrence, or it could indicate a hard drive problem.	Reboot once. If problem persists, contact service representative.
1206 1207	ERROR	r=vtlight_on(state=s,extn=e), mailbox=m r=vtlight_off(state=s,extn=e), mailbox=m The MWI could not be turned on/off. r is the reason the light could not be turned on/off with the following meanings: The task was successful, so this is probably being called in TRACE mode. The state was bad; this is highly unlikely to be the case since this stated should explicitly be passed in by the software. The extension, e, that was used does not resolve to a valid extension. This is usually the case when a single digit mailbox still has the single digit assigned as the extension. Hence we are trying to turn the light on for extension 5, for example. The queue which hold the MWI requests is full. For the DK, this queue size is 240.	No action required unless you think the extension really is valid
1208	WARNING	vtlight_extn: no dextens for mailbox m, state=s The MWI could not be turned on(s=1)/off(s=0) for mailbox m because of an invalid mailbox extension.	Check/set the mailbox extension by using the VM Mailboxes form in the System Administration Tool, or the Group Administration Tool.
1210	WARNING	vta_s9: entered undefined state The application entered a state in its state machine, which is undefined.	Contact your service representative
1216	INFO	An Administrator has logged in. The system administrators mailbox has been logged into using the BOX_ADMIN passcode	No action required.
1219	ERROR	A privilege violation has occurred. This is a result of a Class of Service option not enabled correctly. For example, users on 5140/5240 IP Phones who wish to program their sets using the Desktop Tool must have the HCI/CTI/TAPI Call Control Allowed option set to"Yes". This permit the user's station to be controlled by the host computer.	Update the Class of Service options
1221	ERROR	Error calling VTGSERVICE, channel=channel Unable to start service function to initiate modem answer tone on port channel	Contact service representative.
1502	FATAL	vtapplqh - Message Queue Memory Could Not be Allocated	Contact service representative
1504	WARNING	Message Queue file, HQ.DAT, is not opened This was a result of 2 attempts to open HQ.DAT. The first assuming the file already existed, and the second using the O_CREAT mode.	Contact service representative
1505	WARNING	Message Queue file, HQ.DAT, not initialized properly This was a result of an attempts to write to the HQ.DAT.	Contact service representative
1506	WARNING	Message Queue not updated properly from HQ.DAT The message queue file, HQ.DAT, is a backup file in case the system reboots after a message is accepted but before the message is physically delivered to the mailbox. This is a very small window. Regardless, at every boot up, we try to read this HQ.DAT file and deliver any undelivered messages. This warning occurs when the HQ.DAT file is not of the proper length. This could happen if the system was changed from a 4 port to an 8 port system.	No action required
1507	ERROR	Message Queue file, HQ.DAT, not updated properly An attempt to write to the HQ.DAT file failed during the queuing process.	Try rebooting To reboot the system, press the Reset button on the Controller. . If this does not help, contact service representative
1508	ERROR	Message Queue file, %s, is not updated properly An attempt to write to the HQ.DAT file failed during the "de-queuing" process.	Try rebooting To reboot the system, press the Reset button on the Controller. . If this does not help, contact service representative
1511	ERROR	vthq: Message for mailbox *mbox* was not delivered: size=*size* There was not room in the HQ.DAT file for another record. The result of this is that a message will never be delivered. The size is the size of the queue. A message is appended to header queue in two situations: (vthq() is called to append to header queue) Call is instigated from outside caller Message is being sent/transferred from internal caller, and the destination mbox is locked. Messages are removed from header queue every time vtserve() (periodic service function) calls vthdq(). It dequeues a maximum of P.channel ( 4 in a 4 port system) every time around. vthdq() will only dequeue a message if the destination mailbox is free. Error 1511 could be manually generated by logging into a mailbox, keeping it busy and sending it more messages than header queue size. The size of header queue is dependent on P86 parameter. If this parameter is zero (default), the size of header queue was made equal to number of channels in system. We have changed the size of header queue to default to TWICE the number of channels in system. All this is done in file vtapplhq.c.	Contact service representative
1513	ERROR	vthdq: Transaction file handle is invalid: fh=fh	Contact service representative
1803	FATAL	vtappl2 - Failed to create index space	Contact service representative
1804	FATAL	vtappl2 - Failed to create space for names	Contact service representative
1808	ERROR	MASTER.DAT can not be opened more than once at any one time	Contact service representative
1809	INFO	cal_get - Business hours have not been set This is an informational message that appears at reboot if the business hours have not been set by the system administrator.	No action required
1811	INFO	sg_get - No alternate greetings have been set This is an informational message that appears at reboot if there have not been any alternate greetings set by the system administrator.	No action required
1812	INFO	MASTER.DAT was not open, but the 'close' will be executed. A request was made to close MASTER.DAT, but it was not open in the first place.	No action required
2207	ERROR	keypad table full,extra lines ignored	The keypad.tab file is too big and cannot be read completely. This should never happen and indicates a programming error. Contact service representative.
2213	ERROR	vtsrr_greet: rename(*from,to*) error	Unable to rename a temporary (new) greeting file to its permanent name. Try the operation again. If this still does not work, contact service representative
2214	FATAL	keypad.tab or keypad2.tab not found	Could not find keypad.tab or keypad2.tab for TUI
2215	FATAL	keypad.tab not found	Could not find keypad.tab.
2216	ERROR	vtadm_enable_disable: Can't update parm.bin While trying to enable or disable a feature, the file PARM.BIN could not be opened or written to.	Try retrieving PARM.BIN. If it is there, reboot To reboot the system, press the Reset button on the Controller. the system and try a fresh install. If the file is not there, send a fresh version over, then try a fresh install. If this still does not work, contact service representative
2217	INFO	vtadm_enable_disable: Updated parm.bin
2218	ERROR	vtadm_set_dialplan: Can't copy master.bak	Contact service representative.
2219	ERROR	vtadm_set_dialplan: Can't update parm.bin While trying to set the dialplan during installation, the file PARM.BIN could not be opened and/or written to.	Try retrieving PARM.BIN. If it is there, reboot To reboot the system, press the Reset button on the Controller. the system and try a fresh install. If the file is not there, send a fresh version over, then try a fresh install. If this still does not work, contact service representative
2219	ERROR	vtadm_set_dialplan: Can't restore parm.bin While trying to set the dialplan during installation, the file PARM.BIN could not be opened and/or written to.	Try retrieving PARM.BIN . If it is there, reboot To reboot the system, press the Reset button on the Controller. the system and try a fresh install. If the file is not there, send a fresh version over, then try a fresh install. If this still does not work, contact service representative.
2219	ERROR	vtadm_number_mailboxes=*errflag, errno=errno*	Contact service representative.
2219	WARNING	wakeup_notify_PBX:no dextens for mbox= *boxno* No extension has been configured for mailbox boxno.
2229	WARNING	Write Error Rec_no=nn Write to MASTER.DAT failed.	Log the message in diag.dat and continue.
2230	WARNING	Write Error Rec_no=nn Write to MASTER.DAT failed.	Log the message in diag.dat and continue.
2230	ERROR	Cant update parm.bin	Contact service representative.
2403	INFO	VT_RECDONE:v Indicates that a recording has terminated. The value v tells how the termination happened: 2 - A terminating DTMF was detected. 5 - End of data reached (?) 7 - Timed out, rarely happens 10 - Terminated due to silence 12 - Terminated due to loop current dropping. 13 - Terminates on EOF, very rare 31 - Terminated due to non-silence; i.e. sound is constantly above a certain threshold. VT_ON:v The port has gone on-hook. VT_OFF:v The port has gone off-hook VT_BUSY:v An outdial (page) has resulted in a busy signal. VT_NOAN:v An outdial (page) has resulted in no answer. VT_CONN:v An outdial (page) has resulted in a connection being made and the recipient hears/sees the result of the page. VT_INTER:v Operator intercept&will be treated as a no answer. These are informational messages that come out to help give an idea as to the traffic of the system and how recordings were terminated. v only has meaning when on the VT_RECDONE line:	No action required
3001	ERROR	vtalist:ret=r,total_boxes=tb The attempt build a list of mailbox records from MASTER.DAT failed. r = reason write failed: -1 = could not open MASTER.DAT -2 = could allocate space (malloc) tb = total number of records in MASTER.DAT	Contact service representative.
3201	FATAL	vtv40 error,file=[*filename] The prompt filename* cannot be found/opened.	Contact service representative
3207	INFO	vtspeak - Prompt pp File VTP.VAP Missing This means that a requested prompt could not be played. The reason is most likely that the VAP file is corrupt, this usually means truncated. If the prompt number is between 1 and 100, the file in question is VTP.VAP. If the prompt number is greater than 100, the file is VTE.VAP.	Contact service representative
3209	ERROR	Prompt *num* File VTP.VAP Missing Prompt number, num, does not exist in file VTP.VAP.	Contact service representative
3210	ERROR	MBox size incorrect File=f There is something wrong with the MSG file, f. The most likely reason is that it is full and can not accept new messages. If there is another reason, it would be shown in error message 4706	Check how many messages are in the mailbox. If OK, see message 4706.
3213	ERROR	Default Language *nnn* prompts missing, substituting English The prompts for the configured default language are not installed. English is being substituted. The value of nnn indicates the configured language: 1 = English 2 = Spanish 3 = French 4 = Dutch 5 = UK English	Select a different default language.
3214	ERROR	Alternate language *nnn* prompts missing. Language ignored. The prompts for the configured alternate language are not installed. No alternate language has been loaded. The value of nnn indicates the configured language as defined above for message 3213.	Select a different alternate language.
4001	ERROR	utxopen(path=p,handle->h)=*ret,errno=err,cid=cid* Error opening the file p. cid represents the function that called utxopen().	Contact service representative to determine if this call was for a critical file.
4002	ERROR	utxclose(hd=hd,handle=*handle)=ret* Error closing file originally pointed to by hd	Contact service representative
4005	ERROR	File Handle Error	Contact service representative
4312	WARNING	vtxd40: Incorrect File Handle for Record The file handle passed into Record_Msg_Enter() is invalid. That is, it is less than 5 or greater than 59. This most likely means that too many files were left in the open state.	In order to get back up and running so that messages can be left, reboot To reboot the system, press the Reset button on the Controller. the system. Then contact your service representative so that logs can be retrieved.
4313	WARNING	vtxd40: Invalid event during record d40event=*event* While a message was being recorded, a Dialogic event was returned that was unexpected. For details on the event, look up the event code in the Dialogic reference guide.	Note the event and contact your service representative.
4314	ERROR	vtxd40: Incorrect file handle after Record While in Record_Msg_Exit(), there was an error returned from the function utxcheck(). This check is done before the attempt to close the file. Note that error message 4005 should also have been logged.	Contact service representative
4316	INFO	vtxd40: Voice Mail is gracefully shutting down This message occurs when Contact is rebooted remotely via the System Administration Tool or the Group Administration Tool.	No action required
4319	ERROR	vtxd40: Dos Error Encountered DOS code=c cstate=s On a record or playback, there was a problem writing to or reading from the voice file. c is the _doserrno value that is set when a write, seek or read fails.	Contact service representative
4320	INFO	stopch() issued Indicates port is being stopped as part of application shutdown.
4321	INFO	T_STOP received Indicates port is being stopped as part of application shutdown.	No action required
4323	ERROR	vtxd40: Event Error Code=*error* There was an error when calling the Dialogic get event function (getevt). For details on the error, look up the error code in the Dialogic reference guide.	Contact service representative
4324	FATAL	vtxd40: D/40 Driver Not Installed	Make sure the VOXDRV started. Watch the bootup via a serial cable and PCPlus. Otherwise, contact service representative
4326	WARNING	vtxd40 - Unable to set Parameters Dialogic call to setxparm() failed.	Contact your service representative
4327	INFO	vtxd40 - intlevel=*irq* rc=rc The function startsys() failed. This is because there is something wrong with the VBPC interface.	Make sure phone system is up. If problem persists, contact your service representative.
4328	INFO	vtxd40: p ports available, a installed, hourlim=h, vm_model_no=m p - The number of ports as indicated by the model number. a - The number of ports that the voice driver detected. 0 = no limit. h - The total number of storage hours available as indicated by the model number. 0 = no limit. m - This is the model number. If 0, then the model has not been set. This message is displayed on system startup, when the phone system is configured, when the fax finder is set (with phone or CGM), when a technician uses the technicians users interface to reset the ports, when the D40 token is manually sent from CGM.	No action required
4338	WARNING	vtxd40: Seek Error This seek occurs while a voice file is being queued up to be played.	If this is not an isolated incident, contact your service representative.
4341	WARNING	vtxd40: Error in Voice Code This happens when the seek error from message 4338. It should not happen for any other reason.	Contact your service representative.
4342	WARNING	vtxd40: action=*action* rc=rc Error occurred while trying to play a file.	Contact your service representative, noting the action and rc values.
4344	ERROR	vtxd40: Mailbox *mbox* unlocked for slot *slot* If all ports are idle there should not be any mailboxes that are locked. Therefore, this message is issued when a mailbox was unlocked.	No action required. If this happens frequently, contact service representative.
4350	WARNING	vtxd40: Call to vb_get_cpid failed vb_get_cpid() is a call to the VBPC driver that is done through a vtgservice call to the VOXDRV. To examine the exact reason why this failed, look at the VBPC log file which is located in c:\vbpc\log\vbpclog.dat.	If vbpclog.dat does not give enough information, contact your service representative.
4501	FATAL	System Parameters have FAILED to be set This can come out in the same situation as above only if there is a problem with the PARM.BIN file.	Contact service representative
4503	FATAL	vtxinit - Error starting the Voice Board	Contact service representative
4702	ERROR	file_name=n, rr=r The message file n is not valid, the reason is indicated by r. The side affect is that any new or saved messages are lost.	No action required, the situation recovers itself.
4704	ERROR	file_name=*file, d40derr=error* There was an error attempting to open or write to the named file. It has to do with recording, but the actual filename dictates which part of the recording process was affected.	Contact your service representative
4706 4707 4708	ERROR	Mbox size Error ret=*ret* Mbox size Error ret=*ret* x_size_folders:Error ret=*ret, tag=tag* These messages occur when there is something wrong a particular mailboxs MSG file. ret is the return value of x_size() and has the following meanings. -2 = The mailbox is full -3 = The tag value in the file is not correct -4 = The file handle passed in was invalid	Make sure the mailbox is not full. If not full, try renaming the MSG file. Regardless of the results of the above, contact your service representative
4709	ERROR	MBox Dir Error fname=n Code=c The message file n is not valid, the reason is indicated by c.	Contact service representative; the situation does not recover by itself.
4711	ERROR	Corrupt MBox handle=*handle* msg_no=*msg_no* ret=*ret* Playing a message failed. The reason is dictated by the return code ret. Below are possible values of ret. Message is too short and will not be played The actual playing of the file failed. it probably doesnt exist File handle bad The message number is bad (out of range with respect to the system wide max), or the MSG file tag is bad.	If the return code is -3 or -4, contact your service representative. If the return code is -2, it may have been purged. Otherwise, no action is required.
4714	ERROR	I/O Read Problem An error occurred while trying to read an MSG file. There is no reason as to why except that the amount of bytes that was read was less than what was expected.	Even though there is no extra information associated with this message, there may be other messages at the same time that indicate which file was having a problem. If this is an isolated incident, no action required. Otherwise, contact your service representative.
4715	ERROR	I/O Read Problem An error occurred while trying to write to an MSG file. There is no reason as to why.	Even though there is no extra information associated with this message, look at error message 4704 for the filename and associated error. Contact your service representative.
4716	ERROR	x_record:prev(.\grp\nnnnnnnn.nnn) not closed,cur=.\MSG\msgnn.vox This has only been seen with the current file being a mailbox file (msgnn.vox). The previous file has been noted to be either a grp, name, or int file - i.e. an actual message file, a name file or a greeting file. Listed below are the scenarios of when each has been reproduced. \grp When logged into the mailbox noted in the error message, if 3 is entered to leave a memo, and the prompt begins, but the user hangs up before recording begins. When logged into the mailbox noted in the error message, if 2 is entered to send a message, and the destination list is complete, and the prompt has begun, and the user hangs up before recording begins. \name No scenarios have been determined. \int No scenarios have been determined.	This has not been noted to cause any other problems, so no action is required by the technician.
4717	ERROR	Previous File not closed While attempting to append to a message, there was a problem opening or writing to the existing file. This includes but is not restricted to the previous file not being closed.	If this is an isolated incident, no action required. If this continues and prevents messages from being appended to, reboot To reboot the system, press the Reset button on the Controller. the system. If it still persists, contact your service representative.
4718	ERROR	Dir Error There is an error with the MSG file. Note that there should be other error messages with more description as to what the problem is.	Contact your service representative.
4719	ERROR	x_erase(%d,%d) returning %d	Contact your service representative
4720 4721 4722	ERROR	Incorrect File Handle for Erase In all cases, a message could not be deleted due to one of the following with respect to the corresponding MSG file: bad file handle message number is out of range of the system default MSG tag is incorrect	Contact your service representative.
4723	ERROR	x_keep(handle,msg_no,function) returning ret This error is displayed if something goes wrong with saving a message after it has been listened to. handle DOS handle to the MSG file of the mailbox in question. msg_no - Which message do we want to keep for the mailbox in question function 0=Keep, 1=Mark Unread ret return value of x_keep() -1 = lseek() or read() into MSG file failed -2 = file handle bad, or bad tag in MSG file	If isolated incident, no action required. If it continues with only the same mailboxes, listen to all messages in mailbox and then delete the MSG file. Leave a new message to test. If this does not help, contact your service representative
4724	ERROR	x_stamp Corrupted Directory The attempt to time stamp a message failed because the associated MSG file did not have the proper tag inside of it.	If isolated incident, no action required. If it continues with only the same mailboxes, listen to all messages in mailbox and then delete the MSG file. Leave a new message to test. If this does not help, contact your service representative
4726	INFO	deleting 0 length file: f This message is generated when a file that was opened to receive a recording is closed and is of zero length. For example, when leaving a message, if the user hangs up before the beep, this will leave around a zero length file. Hence when this file is deleted, the above message occurs.	No action required
4718	ERROR	x_copy(*filename,start,len,dfh,dstart),r=bytes_read,w=bytes_written* This function is used to copy parts of a message from one file to another. Mostly in the case of adding a comment to a forwarded message or appending to a message just recorded. This error occurs if the number of bytes_read does not equal the number of bytes_written. Or if the the number of bytes_written does not equal the length.	Contact your service representative
4728		x_copy(*filename,start,len,dfh,dstart),r=bytes_read,w=bytes_written* This function is used to copy parts of a message from one file to another. Mostly in the case of adding a comment to a forwarded message or appending to a message just recorded. This error occurs if the number of bytes_read does not equal the number of bytes_written. Or if the number of bytes_written does not equal the length.
4729	INFO	Msg f for b When a message is left for a mailbox, the name of the file that holds the voice data is logged. f - file name b - mailbox receiving message	No action required
4900	INFO	Application successfully initialized This message comes out every time the system is booted. It indicates that we have gotten past most initialization routines.	No action required
4901	WARNING	Heap Problem code=rc Call to _heapchk() failed with a return code of rc.	Contact your service representative
4906	FATAL	vtxmain - System memory heap problem	Contact service representative
4907	FATAL	vtxmain: vtxinit failure	Contact service representative
4908	FATAL	Application Program Failed	Contact service representative
4913	INFO	MEM:main=ms:mo,psp=psp MEM,end_alloc=ea,malloc=as:ao This is an informational message for Contact Systems engineers that gives memory allocation information.	No action required
4915	FATAL	vtg_malloc(*size) Unable to allocate memory block of size* bytes.	Contact your service representative
4916	INFO	ptr=vtg_malloc(size) System successfully allocated size bytes of memory at location ptr
5301	WARNING	File=*filename* Length=*length* The MSG file, filename, is greater than 10,000,000 bytes. The length is noted in the message	In order to get the mailbox up and running, rename the MSG file in question and then contact your service representative.
5302	INFO vta\vtutilc. ERROR vtx\vtxutil.c	Total files deleted from [grp/msg/name] = n code description -3 This means that the length of the msgnn.vox file is not long enough. -4 There is a special code which must be present in the file in order for the file to be valid. If that code is gone, there most likely was some sort of file corruption. The second reason this error code could come out is if enough bytes could not be read from the file. We try to read the first 5024 bytes. -5 TBD -6 TBD -7 We were unable to seek to the beginning of the file. This too could indicate a problem with the file. -8 This means there was something wrong with the mailbox file. The rc value in the error message will give you further details on what was wrong. Below is a list of the possible values for rc and what they mean: -1,-2,-3 The msgnn.vox file is somehow corrupt. It is not known how it could get into this state. This probably means that the msgnn.vox file is indicating that there are more than 250 messages.	No action required. No action required, the situation recovers itself.
5303	ERROR	Copy Error *source* to *destination* code=*ret* An error occurred while copying file source to destination.	Contact your service representative
5304	INFO	vtclean: deleted f, age exceeded d days Every morning at 2:00 A.M., message files are checked to determine if their age has exceeded the configured limit. If it has, they are deleted. For each file that is deleted, this message is issued. The files name is f and the number of days it was checked against is d.	No action required
5304	WARNING	*seekid* Seek Error fh=fh ptr=*offset* origin=*origin* An error occurred while performing a seek on a file. Where :seekid indicates who called this function	Contact your service representative
5309	ERROR vtx\vtxutil.c	x_delete_tmsg: read error, mbox=*mailbox* This function will delete the message file that is referenced in a transaction record of the mailboxs MSG file. Could not read the correct number of bytes from the mailboxs MSG file.	Contact service representative
5310 5311	ERROR ERROR	vtbox_full(Box_Num=b)=r, tot_msgs=tm, box_msgs=am fh=fh, f_size=fs, rc=rc, s/c=s/c Every time a message or memo is left for a mailbox, we first check to make sure there is room for the message/memo in the recipients mailbox. If there is not, the user is vocally informed and this message is logged. am is the maximum number of messages that the mailbox in question can contain. Note that these two messages always come out together.	The user must delete some messages before new ones can be left.
5311	ERROR	mark_erased_descriptor error=*error, file=box_num* An error occurred while trying to mark a descriptor file. A descriptor file is one that contains all the mailbox numbers that are to receive a group message. To determine the descriptor file, the mailboxs MSG file must be examined. The reason the function failed is stored in error: lseek() into the MSG file failed could not read() the appropriate number of bytes from the MSG file the box_num was not found in the descriptor file	Contact your service representative
6001	INFO	Msg f (*mm/dd hh:mm*) for b deleted A voice message sent to a single mailbox has been deleted from the disk f = filename, mm = month, dd = day, hh = hour, mm = minute, b = mbox #	No action required
6002	INFO	Msg f (*mm/dd hh:mm*) for b deleted A voice message sent to a multiple mailboxes has been deleted from the disk f = filename, mm = month, dd = day, hh = hour, mm = minute, b = mbox #	No action required
6003	INFO	Msg f (*mm/dd hh:mm*) for b is old A saved voice message is older than the limit specified for the mailbox. The file will be deleted when it has been erased or has exceeded the age limit for all mailboxes the message was sent to. f = filename, mm = month, dd = day, hh = hour, mm = minute, b = mbox #	No action required
6004	INFO	Msg f (*mm/dd hh:mm*) for b saved A voice message was saved by the mailbox owner. This message appears only the first time a message is saved. f = filename, mm = month, dd = day, hh = hour, mm = minute, b = mbox #	No action required
6005	INFO	Msg f (*mm/dd hh:mm*) for b erased A voice message was erased by the mailbox owner. f = filename, mm = month, dd = day, hh = hour, mm = minute, b = mbox #	No action required
6006	INFO	Logged in to mailbox b A mailbox owner has logged in to a mailbox, b, by providing the proper mailbox/passcode combination.	No action required
6007	INFO	Mailbox b added The system administrator has added a mailbox, b, to the system.	No action required
6008	INFO	Mailbox b deleted The system administrator has deleted a mailbox, b, from the system. All associated messages and recorded greetings are deleted.	No action required
6013	WARNING	Rename from msg.vox to msg.vox failed	No action required. May need to restore from and to box information
6014	WARNING	Rename from nam.vox to nam.vox failed	No action required. May need to restore from and to box information
6015	WARNING	Rename from int\int.vox to int\int.vox failed	No action required. May need to restore from and to box information
6016	WARNING	Rename from int2\int.vox to int2\int.vox failed	No action required. May need to restore from and to box information
8008	WARNING	Request by CGM to seek opened file failed	Contact your service representative
8009	WARNING	Request by CGM to write to file failed This is a request to write data to the currently opened file on the Messenger side.	Contact your service representative
8013	WARNING	Bad mailbox select location indicator: code The System Administration Tool or Group Administration Tool made a bad mailbox request. This error should never occur.	Contact your service representative
8015	ERROR	CGM requesting too many bytes for packet size	Contact service representative
8016	WARNING	Request by CGM to set time of *filename* to *time* failed; errno=errno This is an attempt by the System Administration Tool or Group Administration Tool to change the time of a file on the application side. This is a very obscure request and is rarely done.	Contact your service representative
8017	WARNING	Bad mailbox command: errno This is an attempt by the System Administration Tool or Group Administration Tool to issue a command that is not valid.	Take note of the error, and contact your service representative
8201	WARNING	Trying to shift a negative number of bytes This is an error that can occur during the communications protocol. It should never happen.	Contact your service representative
8301	WARNING	Bad return value from 'valid_packet()'	No action required.