Banyan Return Codes
The return codes in this module are listed in numerical order, followed by the message name in parentheses. When writing source code, you should test for the message name, rather than the error code number. Banyan reserves the right to change the numbers without notice.
The following return code is common to all functions:
0 (BYCALLOK) - The function returned without error.
Note: Return codes in the range 1 through 99 are platform specific. Refer to the appropriate documentation for a description of these codes.
The following NetRPC return codes can occur during any remote procedure call. Since most API functions involve Remote Procedure Calls, these return codes are common to many functions.
100 (BYMM) - A NetRPC error number bias occurred.
101 (BYBADPROCNUM) - The procedure does not exist. The service reached does not support the type of Remote Procedure Call on which this error is returned. This can happen when a client issues a call specifying the IPCPORT of a service other than the one with which the client is supposed to communicate.
102 (BYBADVERSION) - The version number is out of range. This code is returned on a Remote Procedure Call to a service that does not support this version. This can happen when a client issues a call that specifies the IPCPORT of a service other than the one with which the client is supposed to communicate.
103 (BYTOOMANY) - Too many calls are outstanding. The service reached is busy processing other requests and cannot handle additional requests. This can happen during peak traffic periods for the service. If it occurs consistently, there may be a problem with the service.
104 (BYNOSPACE) - There is insufficient heap space. If this error occurs consistently, there may be a problem with the service.
When a client or service application encounters one of the following tasker errors, it prints a return code message and exits immediately. Client errors usually appear on the console and service errors are written to the service's log file. These errors are never sent across the network. The return code message names are defined in the banyerr.h header file.
121 (BYTASKINIT) - The tasking system is not initialized. A tasking system function call was made before calling VnsInitTasking. The program prints the error message and exits immediately with a core dump.
122 (BYTASKSTACK) - The task stack size is too small. A task was created with a stack size smaller than the minimum necessary for a task on this machine.
123 (BYTASKHEAP) - The tasking system is out of heap space. The tasking system could not allocate any more memory to handle a new task. This happens if the program does not free memory when it is no longer needed.
124 (BYTASKARGS) - Too many arguments were passed to task, exceeding the number the task expected.
Communication errors are returned by socket communication functions. These return code messages are defined in the banyerr.h header file.
With reliable IPC messages, return codes can return even if the message successfully reaches its destination. This can result from timing problems, LAN idiosyncrasies, and machine failures that affect successful acknowledgment of a completed request. The only return code message indicating certain failure is 157 (BYNOEXIST).
151 (BYBADSO) - A socket call was made with an invalid socket descriptor. Socket descriptors are returned by VnsOpenSocket and VnsInitDaemon.
152 (BYINUSE) - An attempt was made to open a well-known port that is already open.
153 (BYINVAL) - An attempt was made to perform an invalid operation. For example, more than four vectored I/O structures were specified in a send or receive request.
154 (BYFAULT) - An address specified in a UNIX socket call is not in the address space of the user process.
155 (BYUNREACH) - The net/host is unreachable. The destination specified in the IPCPORT is not known to the server acting as the communications router. The destination may be unreachable for the following reasons:
![]() |
The destination is off the network. |
![]() |
Network problems such as link or router failures occurred. |
![]() |
A process supplied an invalid destination address in the IPCPORT. |
156 (BYMSGSIZE) - The message size exceeds the limit on an IPC send request. The incoming message is larger than the receive buffer space on a receive request.
157 (BYNOEXIST) - The destination machine specified in the IPCPORT was reached, but no socket is open on the port.
158 (BYAFNOSUP) - The address family field in VnsOpenSocket is invalid.
159 (BYSONOSUP) - The socket type requested in VnsOpenSocket is invalid.
160 (BYPRNOSUP) - The protocol requested in VnsOpenSocket is invalid.
161 (BYNOSODES) - No more sockets are available. Reconfigure the workstation or server to add more sockets.
162 (BYNOBUFS) - The communication layer does not have enough memory space to process the request. This error can result from local conditions, including a temporary heavy communication load, a communications buffer size configured too low, or wasteful use of socket calls. Increase the communications buffer size for the server or workstation, or close unneeded sockets.
A process can also receive this error when sending data to a process whose input buffer is full. The receiving process is too busy to handle the data flow. Try the request again later. If the condition persists, the receiving process may be hung.
163 (BYTIMEOUT) - The time limit on a socket receive or wait request expires before a message is received. This error also occurs when a reliable IPC send request does not complete within a reasonable amount of time. Each Remote Procedure Call uses a similar time limit to receive the reply. This error returns if the service exceeds this limit.
164 (BYOPNOSUP) - Vectored I/O is requested on a socket type that does not support vectored I/O.
165 (BYNOTAVAIL) - A serial communications line is not available or is specified incorrectly. Specify the line number again. If this action fails, check the configuration of the serial communications card to which the line is connected.
166 (BYFAILURE) - An internal failure occurred. Reload the software on the serial communications card.
167 (BYHWRESET) - A communications driver on the server failed to perform a hardware reset of a communications card successfully. This problem can result from a hardware failure or a bad card configuration parameter such as an incorrect I/O address. To check card configuration parameters:
1. Go to the server console.
2. From the Operator Menu, choose System Maintenance.
3. Select Configure/Diagnose Server from the System Maintenance menu.
4. Choose Add Cards/Change Card Configuration. The card configuration appears on the next screen.
168 (BYNBUSY) - This message appears in DOS environments only. A terminate-and-stay-resident (TSR) program failed to submit requests to the socket interface to the VINES communications system successfully. If this error persists, reboot the workstation.
172 (BYADDRESS) - A service node (server) has not assigned a client node (workstation) a VINES internet address. This situation occurs when all servers that are neighbors of the workstation on the workstation's LAN are down. Two nodes are neighbors when they share the same physical medium.
173 (BYABORT) - A process running under UNIX (for example, a service) receives a UNIX KILL signal from an administrator while the process has socket send or receive requests outstanding. The outstanding requests are then torn down. This message is not common.
174 (BYLRESET) - A protocol reset occurred on an SDLC or BISYNC line. This reset is a normal function of the SDLC and BISYNC protocols and requires administrative action unless the message coincides with the disruption of communication. The problem tends to result from typical events such as the IBM host resetting the connection. For example, on SDLC lines, the host can send a Set Normal Response Mode (SNRM) command.
175 (BYLDISC) - A protocol disconnection occurred on an SDLC or BISYNC line. This disconnection is a normal function of the SDLC and BISYNC protocols. This message results from events such as the IBM host going down on the other side of the connection.
176 (BYMABORT) - An aborted socket request is issued by an application. If the request is aborted by a NetBIOS application, this message is remapped to a NetBIOS error.
177 (BYRDISC) - VINES SPP terminates an SPP virtual connection. Causes can involve serial line or LAN failures, lack of sufficient communications buffers, or an insufficient limit on the number of concurrent SPP connections. Increase communications buffers and SPP connection limits from the server console. See Monitoring and Optimizing Servers for more information.
This message may also appear during termination of a TCP connection. Causes can involve serial line or LAN failures, or lack of sufficient communications buffers. Other causes relate to the TCP/UDP toolkit.
250 (BYHOSTDOWN) - The destination IP host is either down or off the network. Wait for the host to come up or back before communicating with it.
251 (BYNETDOWN) - The network in which the destination IP host resides cannot be reached. The gateway to the network may be down or there may be problems with physical links along the path to the network.
252 (BYHOSTUNREACH) - No route is defined to the destination host. Your network administrator must use the TCP/IP configuration program to set up a route. See the Banyan TCP/IP Guide for information on setting up routes.
253 (BYNETUNREACH) - No route is defined to the destination network. This error message occurs on a TCP VnsSocketSend of type SO_CONNECT or a UDP VnsSocketSend of type SO_DATA. The network administrator must use the TCP/IP configuration program to set up a route. See the Banyan TCP/IP Guide for information.
254 (BYPERM) - The destination port cannot be reached due to network problems or because the port address is incorrectly specified. The application should try to connect to the destination port later.
255 (BYEXIST) - An attempt was made to create a route that already exists. Create a unique route to the destination.
256 (BYADDRNOTAVAIL) - When this error message occurs on a TCP VnsSocketSend of type SO_CONNECT or a UDP VnsSocketSend of type SO_DATA, an application tried to connect to a destination process over a local IP interface for which the Address Resolution Protocol (ARP) was disabled. The network administrator must use the TCP/IP configuration program to enable ARP for the interface or to create an ARP entry for the destination.
This error message can also mean that a port number of 0 is specified in the port address of the destination port. Use a port number other than 0.
When this error message returns on a VnsSocketSend of type SO_BIND, it indicates that either an attempt was made to bind a local port address containing an invalid IP address to a socket or that the address family is incorrect.
257 (BYACCES) - The application attempted a broadcast without first setting the SO_BROADCAST option for the socket. This error message occurs for UDP applications only. Before an application issues a broadcast, it must issue VnsSocketSend of type SO_SETSOCKOPT and enable the SO_BROADCAST option.
258 (BYISCONN) - A VnsSocketSend of type SO_CONNECT on a TCP socket is already connected, or a UDP socket is set up for dedicated datagram exchanges with another UDP socket. An application should not issue VnsSocketSend of type SO_CONNECT while the socket is connected or involved in dedicated datagram exchanges. To issue another VnsSocketSend of type SO_CONNECT, the application must first terminate the TCP connection or UDP dedicated datagram exchange.
This error message also returns on a VnsSocketSend of type SO_SETSOCKOPT, which the application issues after a VnsSocketSend of type SO_CONNECT. Options should be set for a socket before issuing VnsSocketSend of type SO_CONNECT.
259 (BYNOTCONN) - A VnsSocketSend of type SO_DISCONNECT is issued on a socket that is not connected or involved in a dedicated datagram exchange. Issue VnsSocketSend of type SO_DISCONNECT only following a connection or a dedicated datagram exchange.
This error message also returns when an attempt is made to send or receive data on a TCP socket that is not connected. Issue VnsSocketSend of type SO_CONNECT before sending or receiving data.
260 (BYCONNREFUSED) - The peer TCP software sent a TCP reset message during the connection attempt, refusing the connection. This error message occurs on a VnsSocketSend of type SO_CONNECT on a TCP socket. Re-issue a VnsSocketSend of type SO_CONNECT. This does not guarantee that the connection will be established. The peer TCP software decides when you can and cannot connect.
261 (BYCONNRESET) - The peer TCP software abruptly reset the connection. This error message occurs on synchronous VnsSocketSend and VnsSocketReceive requests.
The following print service return codes can return during calls to Print Service functions:
501 (BPS_NOPERMISSION) - You do not have appropriate access to the print service or print job.
502 (BPS_NOQUEUE) - The specified print queue does not exist, or the VNS_PRINT_SESSION structure is not appropriately initialized.
503 (BPS_NOFORMAT) - The print service format is unknown.
505 (BPS_NOJOB) - The specified print job does not exist.
506 (BPS_CLOSEDQUEUE) - The print queue is closed to new jobs. Try again later.
507 (BPS_OPENQUEUE) - The print queue is open. This error message is not returned by any 5.x print service.
508 (BPS_OFFPRINT) - The print service is stopped. This error message is not returned by any 5.x print service.
509 (BPS_ONPRINT) - The print service is started. This error message is not returned by any 5.x print service.
510 (BPS_BADFILENUMBER) - Your job exceeds the 20-file maximum. This error message is not returned by any 5.x print service.
511 (BPS_BADJOBHANDLE) - The job handle is not recognized by the print service. Try again. This error message is not returned by any 5.x print service.
512 (BPS_ERROR) - A print service internal error occurred. Check the print service logs for more information. Contact support personnel if necessary.
513 (BPS_FILEERROR) - The print service cannot find the error translation file. This error message is not returned by any 5.x print service.
514 (BPS_NOTIMPLEMENTED) - The print service will not accept the command sent.
515 (BPS_PROTOCOLERROR) - The print service cannot process the job in its current state. This error message is not returned by any 5.x print service.
516 (BPS_WRITEERROR) - A print service write error occurred while writing to the server's disk. There may be server disk problems or insufficient disk space.
517 (BPS_BUSY) - The print service cannot accept your job now. Try later.
518 (BPS_JOBBUSY) - Try again after the job completes printing.
519 (BPS_PORTBUSY) - Another service is using the printer port. This error message is not returned by any 5.x print service.
520 (BPS_NOTYPE) - Your job's form type is unknown. Try again. This error message is not returned by any 5.x print service.
521 (BPS_CFGREADERROR) - The print service configuration cannot be read. Try later. This error message is not returned by any 5.x print service.
522 (BPS_INAPPROPRIATE) - The job state is inappropriate for the specified operation. This error message is not returned by any 5.x print service.
551 (BPS_NODEST) - The destination specified is not found.
552 (BPS_NOFILT) - The filter is not found.
553 (BPS_NOMEMORY) - The request failed due to insufficient memory of either the client or the server.
554 (BPS_RANGEERROR) - A parameter is out of range.
555 (BPS_DATALIMIT) - The job size exceeds the print service limit. This message occurs during spooling.
556 (BPS_LIMIT) - A print service limit is exceeded. There may be too many paper formats or destinations.
557 (BPS_DUPLICATE) - An attempt to create an object failed because an object of the same name already exists. This message applies to objects such as paper formats and destinations.
Of all the StreetTalk return codes listed in sterr.h, only the following errors are likely to occur during normal functions:
1001 (ERSTBADNAME) - Incorrect syntax appeared in a StreetTalk name. StreetTalk names can include letters, numbers, spaces, and other punctuation such as periods (.), commas (,), and dashes (-). Avoid other special characters, especially the at-sign (@), which separates item names, group names, and organization names, and the asterisk (*), which is the StreetTalk wildcard character.
1002 (ERSTORGLONG) - The organization name is too long. Organization names cannot exceed 15 characters. An organization name is the third part of a StreetTalk name. For example, in the StreetTalk name, John@Finance@WCTUS, WCTUS is the organization name.
1003 (ERSTDOMLONG) - The group name is too long. Group names cannot exceed 15 characters. A group name is the second part of a StreetTalk name. For example, in the StreetTalk name, John@Finance@WCTUS, Finance is the group name.
1004 (ERSTOBJLONG) - The item name is too long. Item names cannot exceed 31 characters. An item name is the first part of a StreetTalk name. For example, in the StreetTalk name, John@Finance@WCTUS, John is the item name.
1005 (ERSTNAMELONG) - The StreetTalk name is too long. A StreetTalk name cannot exceed 63 characters. A StreetTalk name includes an item name (31 characters maximum), a group name (15 characters maximum), and an organization name (15 characters maximum). A StreetTalk name also includes two at-signs (@), which separate the item, group, and organization names.
1006 (ERSTNOMEM) - The server does not have sufficient memory to process a StreetTalk request. The request is processed as soon as memory is available.
1007 (ERSTNOTORGNAME) - The name specified is not the name of an organization. Obtain organization names through MORG.
1008 (ERSTORGEXISTS) - The organization already exists on the specified server. An organization that already exists cannot be added.
1009 (ERSTNOTDOMNAME) - The specified name is not the name of a group. Obtain group names through MORG and MGROUP.
1010 (ERSTDOMEXISTS) - The group already exists. A group that already exists cannot be added. Specify a unique group.
1011 (ERSTORGNF) - StreetTalk cannot find this organization. Either the organization's name was typed incorrectly or the organization did not exist in the network. Retype the organization name.
1012 (ERSTDOMNF) - StreetTalk cannot find this group. You specified the group's name incorrectly, the group does not exist in the network, or the server on which the group is maintained is down or unreachable. Retype the group name. If this fails, check for server or network failures.
1013 (ERSTNOSUCHOBJ) - StreetTalk cannot find this item. Either the item name was typed incorrectly or the item does not exist in the network.
1014 (ERSTINVCLASS) - An invalid class was specified. Three types of errors can cause this message to appear:
![]() |
A program, such as an application written with the Banyan Applications Toolkit, specifies an invalid class of items during a search for an item, such as a StreetTalk user name. Valid item classes include users, services, lists, nicknames, aliases, and groups. |
![]() |
A program specifies a StreetTalk name that does not have an entry for an item, group, or organization name field. |
![]() |
StreetTalk receives a request for an associated record that does not exist. This is an internal error. |
1015 (ERSTOBJEXISTS) - You tried to create a StreetTalk name that already exists in the network. Specify a unique name.
1016 (ERSTNOTOBJNAME) - The name specified is not a name StreetTalk knows. Either you typed the name incorrectly or the name does not exist in the network. Retype the name.
1017 (ERSTINVSESHAN) - This message appears when one of the following errors occurs:
![]() |
A program tries to access StreetTalk illegally, for example, to modify StreetTalk information without appropriate authorization. |
![]() |
A program, such as a client, loses its session with StreetTalk due to server failure. When the server recovers, the program tries to communicate with StreetTalk using the old session handle, which identifies a session. |
If a client program at the workstation displays this error, exit from the client and run the program again.
1018 (ERSTENUMCONSIST) - A name search inconsistency occurred during the processing of calls made to VnsListSStNames. This function lets clients specify criteria that StreetTalk uses to search for objects, such as user names. For example, users can specify the pattern *@Finance@WCTUS to obtain a list of all objects in the group Finance@WCTUS. The error message appears for the following reasons:
![]() |
An error occurs during the processing of multiple requests. |
![]() |
The object being searched for changes between the first and final enumerate request. |
![]() |
Any objects within a StreetTalk list cannot be validated, such as the name of a user deleted from the network. |
![]() |
A network error occurs during the search. |
1019 (ERSTTOOMANYMEM) - The maximum number of members that exist in a list is reached. Members cannot be added to the list until existing members are deleted.
1020 (ERSTALREADYMEM) - The item is already a member of the list. You cannot add an item to a list if that item is already a member.
1021 (ERSTNOTMEMBER) - An error, such as a server failure, occurred when you tried to delete an item from a list, but the item is not a member of that list. This results in corrupted StreetTalk records associated with the list. Delete the list and re-create it.
1022 (ERSTLSTDEPTH) - The maximum number of lists that StreetTalk can search at once is reached. Try again.
1023 (ERSTNOTLIST) - The name you specified is not a list. Use MLIST or NAMES to find list names.
1024 (ERSTLSTCONSIST) - A list search inconsistency occurred. Try later. This error message appears when StreetTalk resolves a list. The error occurs for the following reasons:
![]() |
StreetTalk tries to process multiple Remote Procedure Calls (RPCs) that are not in the proper sequence. For example, when StreetTalk attempts to resolve a list, it has to process three RPCs. StreetTalk receives the second and third RPCs but not the first. A typical cause of this error is a network failure. |
![]() |
As StreetTalk receives information concerning the list, it could not successfully write the information to a file on disk. |
1025 (ERSTNOTSVRNAME) - The name specified is not the name of a server.
1026 (ERSTSVRNF) - StreetTalk could not find the server specified. The server was specified incorrectly or network problems caused the search to fail.
1027 (ERSTPASSLONG) - The password is too long. Try again with a new password that is less than 15 characters.
1028 (ERSTINVUPPAIR) - An invalid user name/password pair was specified.
1029 (ERSTAONUMINV) - The program specified an associated record number that is either not in the allowed range (001 - 999) or is within the range reserved for StreetTalk (675 - 699). This error occurs as the result of an error in a program that issues calls to StreetTalk.
1030 (ERSTNOTRUEOBJ) - The associated record has no true item, such as a user name. This error typically occurs when a server failure coincides with a delete operation, such as deleting a user from the network.
1031 (ERSTAOTOOBIG) - The associated record is too big to add. A program issued either VnsAddSStAssocRecord or VnsSetSStAssocRecord, which specified an associated record larger than 1024 bytes.
1032 (ERSTERRUNK) - An unknown StreetTalk error occurred. This error is caused by unusual network or server problems.
1033 (ERSTACCESSDEN) - Modify access is denied. A user or program tried to change StreetTalk information without the proper authorization, such as membership on the appropriate AdminList.
1034 (ERSTINCOPFLG) - An incorrect operation indicator was specified. A program tried to perform an illegal operation on a StreetTalk group. Programs can only add or delete groups. All other operations are illegal.
1035 (ERSTALIASLIM) - Too many nicknames were encountered. A StreetTalk name was nested under more than 10 nicknames.
It is possible to create a hierarchy of nested nicknames. For example, suppose that a nickname, Doug, is created for a user, Doug Jones@Finance@WCTUS. A second VINES user creates a nickname, Doug2, to refer to the first nickname, Doug. The original StreetTalk name is nested under two nicknames. If Doug Jones@Finance@WCTUS is nested under 11 nicknames, the STK1035 error appears whenever the 11th nickname refers to Doug Jones.
1036 (ERSTCLSMISMATCH) - There is a class mismatch between the record and input parameter. A program issued a request to the StreetTalk Service with a record that described the requestor, but the record is not of a user or a user's associated record.
1037 (ERSTSTNOTAVAIL) - The appropriate StreetTalk Service is not available. The StreetTalk Service on a server is not running or cannot be reached due to network failures or other problems. This prevents other services on the server from communicating with the rest of the network until the StreetTalk Service on the server is started or becomes reachable.
1038 (ERSTWRONGSVR) - The group is not found on the server specified. Either the group exists on another server or does not exist at all.
1039 (ERSTTRYLATER) - StreetTalk cannot answer the request. Try later. This error message occurs for the following reasons:
![]() |
Two servers exchange requests for information on the same group, which is in the process of moving from one of the servers. The servers cannot answer each other's request. However, each server expects the other to answer the request. The error should not occur once you complete the move. |
![]() |
The StreetTalk Service issues a request for information about an item's group to a StreetTalk service residing on a server that is just powered on. The service has no prior knowledge of the group. |
![]() |
An attempt to power on the server on which the StreetTalk Service resides fails. |
1040 (ERSTTOOMANYDOMS) - The maximum number of groups for this server is reached. Another group cannot be added to this server until at least one is deleted through MGROUP.
1041 (ERSTECOMPLETE) - The list of matching names is complete. StreetTalk successfully processed wildcards. For example, StreetTalk can resolve all the names and groups specified by *@*@WCTUS.
1042 (ERSTEINCOMPLETE) - The list of matching names is possibly incomplete. StreetTalk did not successfully process wildcards. For example, StreetTalk cannot resolve all the names and groups specified by *@*@WCTUS. This error occurs for the following reasons:
![]() |
The groups specified in the wildcards are unavailable due to network failures. |
![]() |
The servers that maintain the groups are not running. |
1043 (ERSTPWDREUSED) - The new password is not different from the last ten used. The new password must be different from the last 10 passwords.
1044 (ERSTSECCONSIST) - Security records are inconsistent. A memory flushing error on the StreetTalk Service's server occurred. The error modifies a user record to indicate that a security record is associated with the user record. However, no security record exists. To correct this problem, an administrator should use the MUSER program.
1045 (ERSTUNAUTH) - This is an unauthorized internal StreetTalk request. The message appears when one of the following errors occurs:
![]() |
A program tries to make a request to StreetTalk that is reserved for the Server Service. |
![]() |
A program makes a request to StreetTalk that requires the program to present a valid VINES security nonce, which the program fails to present. |
1046 (ERSTRACCDEN) - Read access is denied. A user or program tried to read StreetTalk information without the proper authorization, such as membership on the appropriate AdminList.
1047 (ERSTEXPIRED) - A user account expired on the expiration date that the administrator set through MUSER. See your administrator.
1048 (ERSTDISABLED) - The administrator disabled the user account through MUSER. See your administrator.
1049 (ERSTNOTVS) - A program issued a call to StreetTalk that is reserved for the VINES Security Service.
1050 (ERSTPWDSHORT) - The password is shorter than required minimum length. The administrator sets the minimum length for your password through MUSER.
1051 (ERSTPWDSAME) - The new password is the same as the current password. The PASSWORD command does not let a user specify the current password as the new password. Specify a different password.
1052 (ERSTDESCLONG) - The description entered exceeds 63 characters. Object descriptions are limited to 63 characters.
1053 (ERSTBUFSHORT) - The return buffer provided is too short to hold the entire result and the result is truncated to fit. Try the operation again with a larger buffer to obtain the complete return value.
1054 (ERSTATTRSZMISMATCH) - The attribute byte and item count do not match. Attributes are represented as sequences of primitive elements such as bytes or integers. This error occurs when the byte count does not match the item count multiplied by the primitive element size.
1055 (ERSTATTRNOTFOUND) - The attribute is not found. The requested attribute does not exist for the object in question.
1056 (ERSTATTRWRITEPASTEND) - An attempt was made to write past the end of an attribute. Attributes may only be appended to by writing to the location immediately after the current end of attribute. Attribute values may not contain holes.
1057 (ERSTATTRBADNULLSIZE) - An attempt was made to write data with a NULL attribute. NULL-type attributes are used as BOOLEAN values where the existence of the attribute implies TRUE and its absence implies FALSE. NULL-valued attributes may not have data associated with them.
1058 (ERSTATTREXISTS) - This attribute already exists. Delete and re-create the attribute or it can be overwritten.
1059 (ERSTOPENFAILED) - StreetTalk cannot open the data file. All objects and attributes associated with a StreetTalk group are stored in data files on the server. These files be unavailable due to system failures or because the group is being moved.
1060 (ERSTATTRBADREAD) - An error occurred while reading the requested attribute from the database.
1061 (ERSTATTRBADWRITE) - An error occurred while writing the requested attribute to the database.
1062 (ERSTOBJBADREAD) - An error occurred while reading an object's base record from the database.
1063 (ERSTOBJBADWRITE) - An error occurred while writing an object's base record to the database.
1064 (ERSTATTRARINUSE) - Associated record 762 is being used by another application. Revisions of StreetTalk prior to Revision 5.5 stored attributes in associated record 762. This record does not have the expected attribute format and most likely is being used by another application for other purposes.
1065 (ERSTATTRBADTYPE) - An attempt was made to write an attribute whose data type is not supported by StreetTalk. Refer to the StreetTalk and STDA Programming Interface for a list of supported attribute types.
1066 (ERSTATTRCOMPAT) - A pre-5.5 attribute compatibility error occurred. Revisions of StreetTalk prior to Revision 5.5 provided limited attribute support, restricted to:
![]() |
Attributes in the range <0:100> through <0:255> only |
![]() |
String values only |
![]() |
50 attributes or 1000 bytes total, whichever limit is met first |
The target object whose attribute is written is on a pre-5.5 StreetTalk service and therefore cannot support the attribute operation requested.
1067 (ERSTATTRBADFLAGS) - An invalid operation flag was presented on an attribute operation such as read or write. Refer to VINES toolkit documentation for the proper flag values.
1068 (ERSTBADPARAMETER) - An invalid parameter such as a NULL pointer or out of range value was presented on a call to StreetTalk.
1069 (ERSTATTRBADINDEX) - The attribute value index requested is out of the actual value's range.
1070 (ERSTUNSUPPORTED) - A request made for a StreetTalk feature is either not implemented or is disabled on the service from which it was requested.
1071 (ERSTLOCMISMATCH) - A "move group" request was made that specified the same server for the source and destination. Old and new groups must be on different servers.
1072 (ERSTBADGROUP) - This group cannot be moved. Some groups, such as those in the organization "Servers," may not be moved.
1073 (ERSTBADPROCID) - A remote StreetTalk service cannot process the request. A remote StreetTalk service does not support the operation in question.
1074 (ERSTBADCLASS) - A bad class value was supplied. A request specified an object class that StreetTalk does not support. Refer to VINES toolkit documentation for a listing of supported class values.
1075 (ERSTNOTALLOWED) - The operation does not make sense with the arguments supplied.
Note: The following values are returned by the client API and not the server.
1076 (ERSTDESCINV) - The description contains invalid characters. Refer to VINES documentation for the set of characters supported in object descriptions.
1077 (ERSTTIMEINV) - The values for login time or day restriction are invalid. Refer to Managing VINES Security for a description of legal values and formats.
1078 (ERSTLOCINV) - The values for login location restriction are invalid. Refer to VINES documentation for a description of legal values and formats.
1079 (ERSTPWDLONG) - The password exceeds 15 characters. StreetTalk passwords must be 15 characters or less.
1080 (ERSTNAMEBUFSHORT) - The output buffer is shorter than the return value. The return buffer provided is too short to hold the entire result. Try the operation again with a larger buffer to obtain the complete return value.
1081 (ERSTATTRREADONLY) - The attribute is read-only. Attributes within the range <0:0> through <0:100> are read-only and must be modified by some other mechanism. Examples of such attributes are:
<0:1> Object description
<0:2> User SETMAIL profile entry
<0:3> Inclusion name remote address
<0:4> Nickname's associated real name
<0:5> StreetTalk group
<0:6> StreetTalk class
<0:7> StreetTalk category
<0:8> STDA class
<0:11> Rename/move status
1082 (ERSTNOWRTSHADOW) - Shadow groups are read only.
1083 (ERSTREMINV) - REM names are excluded from the list.
1084 (ERSTTEMPLATESINV) - Templates are excluded from the list.
1085 (ERSTUSERSINV) - Users are excluded from the list.
1086 (ERSTSERVICESINV) - Services are excluded from the list.
1087 (ERSTLISTSINV) - Lists are excluded from the list.
1088 (ERSTALIASESINV) - Aliases are excluded from the list.
1089 (ERSTPROFILETOOBIG) - The user profile is too large to set. User profiles on a VINES Release 6.0 server can have a maximum size of 4096 bytes. Releases prior to 6.0 support a profile size of 1024 bytes.
1102 (VENOENT) - No such file or directory.
1104 (VEINTR) - interrupted system call.
1105 (VEIO) - I/O error.
1106 (VENXIO) - No such device or address.
1109 (VEBADF) - Bad file number.
1113 (VEACCES) - Permission is denied.
1114 (VEFAULT) - Bad address.
1116 (VEBUSY) - Mount device is busy.
1117 (VEEXIST) - File exists.
1118 (EBFSUNAVAIL) - File service is unavailable.
1119 (EBFSNOROOTACC) - Root directory invalid or network access denied. This can be returned after a failed drive mapping operation.
1120 (EBFSNEWREV) - No VINES Files to match workstation software.
The following Attribute View Definition return codes are common to many AVD functions:
1201 (AVD_ERRNOFILEOPEN) - An AVD operation was attempted without first opening an AVD file using VnsOpenAvdFile.
1202 (AVD_ERRFILTERNOTFOUND) - The filter specification requested by VnsMapAvdFilter does not match any filters in the current AVD file.
1203 (AVD_ERRBADCMD) - An unknown AVD command code was requested in one of the following commands: VnsGetAvdFilters, VnsGetAvdCollections, or VnsGetAvdAttributes. Valid command codes are itemized in the toolkit header file vnsavd.h.
1204 (AVD_ERRBADVERSION) - The AVD library and AVD file version numbers do not match. This may either indicate a mismatch between the library routines and the AVD file operated upon, or a corrupt AVD file.
1205 (AVD_ERRFILEISOPEN) - An attempt was made to open an AVD file without closing the currently active AVD file. Only one AVD file at a time may be opened with VnsOpenAvdFile.
1206 (AVD_ERRONOPEN) - An error occurred while opening an AVD file with VnsOpenAvdFile. This is usually due to a file I/O error.
1207 (AVD_ERRBADFORMAT) - The AVD library cannot interpret the packing format of the AVD file. AVD files are packed in a self-describing, architecture-independent format to ensure that they can be read without regard for architecture-specific byte alignment rules.
1208 (AVD_ERRFILEIO) - A file system error occurred while reading the AVD file.
1209 (AVD_INEXACTMATCH) - VnsMapAvdFilter maps a partial filter specification to the corresponding complete filter record. In cases where the partial filter specification does not identify any filters, a "best guess" is attempted. Applications are alerted to this condition by return of the AVD_INEXACTMATCH message from VnsMapAvdFilter. Applications should not regard this as an error condition and should consider the returned filter value valid.
The VINES Security Service remote procedure errors can be returned by library calls such as VnsGetNonce and VnsVerifyNonce. These return code names are defined in the VSERR.h header file.
1801 (VAN1801) - The nonce for the current session is valid, but the user has not logged in. The VINES Security Service assigns a unique identifier (nonce) to a client's session with VINES. The user must log in.
1802 (VAN1802) - The nonce for the current session is valid, but the port used does not match the port VINES assigned when the current session was established.
1803 (VAN1803) - The syntax for the StreetTalk name you created is not correct. A StreetTalk name for an item, group, or organization can use standard alphanumeric characters and some special characters. An item name is 31 characters maximum, while group or organization names are 15 characters maximum. An at-sign (@) separates an item, group, or organization name.
1804 (VAN1804) - The VINES Security Service cannot determine whether the nonce it received from a service is valid.
1805 (VAN1805) - The VINES Security Service discovered a keyword it did not recognize when it compared the entries in a user profile to a list of recognized VINES keywords. Check that entries and commands in the user profile adhere to the rules for user profiles.
1806 (VAN1806) - The VINES Security Service is starting up and cannot respond to a request. Try your request again later.
1807 (VAN1807) - The VINES Security Service is not currently in operation.
1808 (VAN1808) - The StreetTalk group name you entered is too long. A group name is a maximum of 15 characters.
1810 (VAN1810) - The VINES Security Service does not recognize a command in a user's profile. Check the spelling and syntax of the command. All profile commands are described in the VINES Command Reference.
1812 (VAN1812) - The VINES Security Service cannot respond to your request now. Enter your request again later.
1817 (VAN1817) - Your request failed a security check. Your password or user name may be invalid.
1823 (VAN1823) - You entered too many characters for a StreetTalk name. An item name is a maximum of 31 characters. Group and organization names are a maximum of 15 characters each.
1824 (VAN1824) - An item name is a maximum of 15 characters. Check the item name and enter it again.
1825 (VAN1825) - An organization name is a maximum of 15 characters. Check the organization name and enter it again.
1827 (VAN1827) - The VINES Security Service cannot contact a StreetTalk service required to perform the task requested.
1831 (VAN1831) - You cannot log out a user if you are not an administrator of that user's group.
1832 (VAN1832) - You cannot log out a user who is not logged in to the network.
1834 (VAN1834) - You cannot log in because the maximum number of users that your version of VINES supports are logged in. You must wait until a user logs out before you can log in.
The following STDA return codes are common to many STDA functions:
1901 (STDA_MAX_LINE_LENGTH_EXCEEDED) - The inclusion file line is too long.
1902 (STDA_MAX_ADDR_LENGTH_EXCEEDED) - The inclusion ADDR field exceeds 512 bytes.
1903 (STDA_MAX_DESC_LENGTH_EXCEEDED) - The inclusion DESC field exceeds 64 bytes.
1904 (STDA_MAX_LABEL_LENGTH_EXCEEDED) - The inclusion LABEL field exceeds 32 bytes.
1905 (STDA_NO_LABEL) - The inclusion entry is missing the LABEL field.
1906 (STDA_NO_KEYWORD) - The inclusion entry has an unknown or missing keyword.
1907 (STDA_FILE_INVALID) - A bad filename or error was encountered during a file operation.
1908 (STDA_FILE_NOTCREATE) - An error was encountered opening or creating a file.
1909 (STDA_ATTR_NOT_SUPPORTED) - The requested attribute is not supported.
1910 (STDA_SESS_ALREADY) - An STDA session already exists.
1911 (STDA_SESS_INVALID) - The specified STDA session is invalid.
1912 (STDA_NONCE_INVALID) - The specified nonce is invalid.
1913 (STDA_PORT_INVALID) - The specified IPC port is invalid.
1914 (STDA_NAME_NOT_FOUND) - The requested STDA name is not found.
1915 (STDA_ATTR_NOT_FOUND) - The requested attribute is not found.
1950 (STDA_BADTYPE) - An operation was attempted with invalid type parameter.
1951 (STDA_BADCMD) - An operation was attempted with invalid command code.
1952 (STDA_BADLOC) - The service does not support the requested language code.
1953 (STDA_BADFILTER) - The specified attribute filter is unknown or not applicable.
1956 (STDA_NOINDEX) - No index exists for this attribute.
The following codes are returned to a client when Server Service and the clients service are unavailable due to network errors:
2030 () - No error.
2031 () - Translation not available.
2032 () - Bad error code
2033 () - Service is not responding.
2034 () - Service is not available.
2035 () - Software version unavailable.
2036 () - System error %d, see your administrator.
2037 () - Server is down.
The following return codes are common to many of the Directory Synchronization functions:
2221 (STDA_GNERROPEN) - An error occurred opening a file.
2222 (STDA_GNNOINCSES) - No active inclusion session exists.
2223 (STDA_GNWRONGNONCE) - The nonce does not match the session.
2224 (STDA_GNWRITEERR) - A write error occurred.
2225 (STDA_GNREADERR) - A read error occurred.
2226 (STDA_GNINVSES) - Invalid session.
2227 (STDA_GNNOINCS) - No inclusions are available.
2228 (STDA_GNBUSY) - The service is busy. Try again later.
2229 (STDA_GNBADSEQNUM) - Bad sequence number.
2230 (STDA_GNNOFILE) - The file requested does not exist.
2275 (DA_NONEW) - The sequence number of the requested change file is the newest one that exists at the service.
2276 (DA_NOCNG) - The namespace or item class requested does not exist at this service.
2277 (DA_BADFILE) - The file requested could not be created or opened for access.
2278 (DA_BADSVC) - The service name was not found in the StreetTalk Service.
2279 (DA_COMMERR) - The service does not respond or is otherwise unavailable.
2280 (DA_FILEERR) - An I/O error occurred while reading from or writing to a file.
2281 (DA_BADDBID) - The database ID of the CNG request does not match that of the current service.
2282 (DA_BADREV) - The header revision of the CNG file is not within the acceptable range.
2283 (DA_CORRUPT) - The internals of the indicated file or memory structure appear to be corrupt.
2284 (DA_BADSESS) - The session handle is invalid. The session memory block may be corrupt. This error message also returns if the file is opened with VnsDaOpenCngFile and the mode is set to DA_READING.
2285 (DA_BADPARAM) - One of the parameters for this call is incorrect or outside the permissible range.
2286 (DA_NOMEM) - Insufficient memory is available to complete the current request.
2287 (DA_SIZE) - The caller-allocated memory block is not large enough to complete the current request.
The following return codes are returned by the Intelligent Messaging Mail Service, the Intelligent Messaging Mail Client API, or the Intelligent Messaging Mail Gateway API:
3001 (MS_BADNAME) - A mail client called a function with an incorrect user name, folder name, or recipient name. The name may be NULL, contain an illegal character (such as /), not match the name of the user who started the session, or not match the name of the shared mailbox user specified by the last VnsShareMailSession.
3002 (MS_NAMELONG) - The StreetTalk name is too long.
3007 (MS_STNOTAVAIL) - The StreetTalk Service does not respond.
3008 (MS_MSNOTAVAIL) - The message service does not respond. Check the status of the mail service on the server on which it resides. Either the server or the mail service is down.
3009 (MS_MSNOTIMP) - You tried to perform an operation that is not supported by the version of the mail service you are currently running.
3010 (MS_BYMSNOSPACE) - Not enough memory is available. This error can occur when Windows cannot complete allocation of memory required to issue a function. You may need to reboot your client if this error returns.
3011 (MS_UNKNOWN) - An unexpected failure condition occurred. Check for error conditions in the mail service log and the server log of the server that maintains the mail service.
3012 (MS_BADRECIPIENT) - At least one recipient is incorrect. A mail client tried to call a function with an invalid or unsupported cRecipientClass parameter. For example, revisions before 5.00 (6) do not support recipient classes RECIPIENTCC or RECIPIENTBCC for forwarded messages.
3013 (MS_TOOMANYADDR) - Too many addresses are specified. A mail client tried to start a mail session with a mail service, but specified an incorrect mail service organization name.
3014 (MS_NONAMEADDR) - Either a name or address must be provided.
3015 (MS_BADFORMADDR) - The format of a recipient's address was not correct. This usually indicates an undeliverable message.
3016 (MS_BADFORMSVC) - A specified service name is incorrect.
3017 (MS_BADSESS) - The session handle is no longer valid. A mail client tried to access a mail service, but the connection between the client and the service was interrupted. Exit and re-enter the service. If necessary, log out and back in. As a final option, reboot the workstation, pressing CTRL-ALT-DELETE.
3018 (MS_FILENOTFOUND) - The specified file is not found. Check the mail service log for the name of the file that could not be found.
3019 (MS_ENVNOTFOUND) - A mail client tried to access an envelope that was not found. Either the specified message ID is invalid or the required initial call, such as VnsInitNewMailEnvelope or VnsGetMailEnvelope, was not made.
Access the message again, or exit and re-enter the mail utility.
3020 (MS_CONTNOTFOUND) - A mail client tried to access a content file or a message body part that was not found. This problem can result from a communication interruption between the client and the server on which your mail service resides. Access the message again, or exit and re-enter the mail utility.
3023 (MS_ADDRDIRLOST) - The address directory is not found. Verify that the mailbox is stored in the mail service to which you are currently connected.
3024 (MS_DBNOTFOUND) - The service database is corrupt.
3025 (MS_BADPROFILE) - The profile entry for mail is missing or incorrect. A mail client called a function, but the user profile entry that grants access to the mail service either contained an error or was missing entirely.
3026 (MS_NOTLOGGEDIN) - You are not logged in.
3027 (MS_ATTNOTFOUND) - The attachment file for this message is missing. This problem can also occur if a mail client calls a function that is not supported by the mail service.
3028 (MS_TOOMANYATT) - You tried to attach more than the maximum number of attachments with a mail message.
3029 (MS_OBSOLETE) - A revision mismatch was specified.
3030 (MS_FOLDEREXISTS) - A mail client user tried to name a new folder or rename an existing folder to a folder name that already exists. Enter a different name.
3031 (MS_FOLDERNOTFOUND) - A mail client tried to access a mail folder that was not found. This problem can result from an attempt to move a mail message to a destination folder that does not exist.
3032 (MS_SORTFAILED) - An attempt to sort folders failed.
3033 (MS_REQUESTCANCELED) - A request to perform an operation was canceled before it completed.
3034 (MS_ROUTEAGAIN) - The mail service cannot route the message. Try again.
3036 (MS_TIMEOUT) - A mail client user sent a message that was not delivered before the message expiration period elapsed. This problem can occur when the message contains an unverifiable address.
Check and correct the address on the message. If the address is correct, verify that the connections to the recipient work properly and the recipient's group still exists.
3037 (MS_INDNOTFOUND) - The folder index cannot be found.
3038 (MS_MVINPROGRESS) - A move mailbox operation is in progress. A mail client called VnsVerifyMailboxMove to check the status of a move or rename mailbox request and the function returned this status for puStat, indicating that the operation is not complete.
3039 (MS_MVFAILED) - A move mailbox operation failed. A mail client called VnsVerifyMailboxMove to check the status of a move or rename mailbox request and the function returned this status for puStat, indicating that the operation failed.
3040 (MS_MVCOMPLETE) - A move mailbox operation completed successfully. A mail client called VnsVerifyMailboxMove to check the status of a move or rename mailbox request and the function returned this status for puStat, indicating that the operation successfully completed.
3041 (MS_WRITEERROR) - A mail client failed to write a message to disk because the disk was full, the disk was read-only, or an I/O error occurred. File the message on another disk. If that fails, check for disk errors in the mail service log and server log of the server that maintains the mail service.
3042 (MS_NAMEUNKNOWN) - A mail client user sent a message that was not delivered because the appropriate StreetTalk service was not available, or the recipient's user name was deleted or entered incorrectly. Verify the accuracy of the name entered. If the name is a user name, check to see if the user was deleted. If the name is correct and the user exists, check the connections between the recipient and the sender.
If the name is a list name, one of the names on the list may be incorrect or invalid.
3043 (MS_LIMITEXCEED) - A mail client user sent a message that was not delivered because the recipient's mailbox contains the maximum number of messages set by the system administrator. The recipient must delete some messages before the mailbox accepts any additional incoming messages.
3044 (MS_SYNTAXERR) - A mail client user sent a message that was not delivered because of a syntax error in the list of recipients. Recover the message and verify the addresses for correct syntax.
3045 MS_MSNOTFOUND - The mail service is not found. A mail client user sent a message that was not delivered, either because the recipient's user profile entry that grants access to the mail service contains an error, or the mail service is not available.
3046 (MS_NOWILDCARD) - A mail client user sent a message that was not delivered because the recipient's mailbox is restricted by the system administrator from receiving mail with wildcards. If necessary, the sender can recover the undelivered message and forward it to specific addresses.
3047 (MS_MAILSVCERR) - A mail client user sent a message that was not delivered because the recipient's user profile entry that grants access to the mail service is missing.
3048 (MS_MBXDISABLED) - A mail client user sent a message that was not delivered because the recipient's mailbox was disabled by the system administrator.
3049 (MS_TOOMANYLIST) - A mail client user sent a message that was not delivered because the recipient is a list name that contains more than three levels of list names nested within it.
For example, a user addresses a message to the list name MyList@Sales@WCTUS (first level). This list name contains the list name DeptList@Sales@WCTUS (second level). DeptList contains the list name, VPList@Sales@WCTUS (third level). VPList contains the list name, PRList@Marketing@WCTUS (fourth level). Mail cannot deliver the message to MyList because of this fourth-level list name.
3050 (MS_BADMESSID) - A mail client called a function with a mail message ID that exceeds 14 characters. The ID is specified in the MsgId parameter. This error appears for mail clients written only with the Intelligent Messaging Mail Client API.
3051 (MS_SUBERROR) - A mail client failed to submit all or part of a message body part to a mail service. For example, the error is returned when the last call to VnsStoreMailBodyPart for a body part did not have a 0 immediately after the last byte of data. This error appears for mail clients written only with the Intelligent Messaging Mail Client API.
3052 (MS_2NDINIT) - A mail gateway service called VnsInitializeGate twice. A mail gateway service may call this function only once when it initializes. This error appears for mail gateway services written with the Intelligent Messaging Mail Gateway API.
3053 (MS_BADDIR) - A mail gateway service called VnsInitializeGate with an invalid UNIX pathname in the Directory_Path parameter. This error appears for mail gateway services written with the Intelligent Messaging Mail Gateway API.
3054 (MS_OPENDIR) - A mail gateway service could not open the directory specified in VnsOpenGateMessageDir. This error can be caused by an invalid UNIX pathname in the Directory_Path parameter. This error appears for mail gateway services written with the Intelligent Messaging Mail Gateway API.
3055 (MS_TOOMANYOPEN) - A mail gateway service tried to open too many directories with VnsOpenGateMessageDir. The maximum number of open message directories (MAXOPENDIR) is defined in vnsgate.h. This error appears for mail gateway services written with the Intelligent Messaging Mail Gateway API.
3056 (MS_MESDIRNOTOPEN) - A mail gateway service called a function that specified an invalid directory handle in the dirhandle parameter. This error appears for mail gateway services written with the Intelligent Messaging Mail Gateway API.
3057 (MS_ENVREADERR) - A mail gateway service could not read an envelope or a recipient address within an envelope. This error is returned by VnsGetGateEnvelope, VnsGetGateOldEnvelope, and VnsGetGateRecipient. Typically, this error occurs when an envelope exists but is incorrectly constructed. This error appears for mail gateway services written with the Intelligent Messaging Mail Gateway API.
3058 (MS_INVALIDBP) - A mail client or a mail gateway service called a function that specifies an invalid body part. Valid body part designators are MAINBODY, ATTACH1, ATTACH2, and so on up to ATTACH10.
This error occurs for the following Intelligent Messaging Mail Client API functions:
VnsGetMailBodyPart - An invalid body part designator is specified for the PartNum parameter.
VnsGetMailBodyPartSize - A body part designator other than MAINBODY is specified for the PartNum parameter.
VnsStoreMailBodyPart - An invalid body part designator is specified for the PartNum parameter.
VnsStoreMailBodyPartList - The present field is not set to PRESENT in one of the bodyparts structures you stored, or the label field is empty in the bodyparts structure for one of your attachments.
This error occurs for the following Intelligent Messaging Mail Gateway API functions:
VnsGetGateBodyPart - An invalid body part designator is specified for the bodypart parameter.
VnsStoreGateBodyPart - An invalid body part designator is specified for the bodypart parameter.
3059 (MS_PMTIMEOUT) - A mail gateway service called VnsPendGateDaemon that times out. To avoid this error, try increasing the value of timeout. This error appears for mail gateway services written with the Intelligent Messaging Mail Gateway API.
3060 (MS_PM2NDPEND) - A mail gateway service called VnsPendGateDaemon for a task, and another task is already pending. This error appears for mail gateway services written with the Intelligent Messaging Mail Gateway API.
3061 (MS_INVALIDMSGTYPE) - A mail gateway service or a mail client processed a message with an invalid message type specified in the messageType field of the message's envelope. Valid message types defined by Intelligent Messaging mail are:
IPMES - A standard interpersonal message sent by an Intelligent Messaging user.
STATUSMES - A status message that informs a user of a particular status condition.
UNDELIVMES - A special type of status message that informs the sender of an IPMES that the message was undeliverable. When Intelligent Messaging mail cannot deliver a message, it generates an UNDELIVMES message and attaches the body parts and envelope of the original message to it. The sender can then recover the original message.
A mail client can define its own message types, but this is not recommended.
3062 (MS_LARGEMAINBODY) - The message main body is too large. A mail gateway service called VnsTransferGateMessage to transfer a message to an Intelligent Messaging mail service, and the function specified a value greater than 6000 bytes for MS_MAXMAINBODYSIZE. This error appears for mail gateway services written with the Intelligent Messaging Mail Gateway API.
3063 (MS_CANTMVMS) - The mail service's mailbox cannot be moved. A mail client user tried to perform an operation on the mail service's mailbox. The client calls a function that specifies the name of the mail service's mailbox for MailboxName. This parameter specifies the name of a user's mailbox only. This error occurs for the following Intelligent Messaging Mail Client API functions only:
VnsEmptyMailbox
VnsMoveMailbox
VnsRenameMailbox
VnsSetUserMailInfo
3064 (MS_NOTADMIN) - A mail client user tried to set user information; manage indexes on a mailbox; or move, empty, or rename a mailbox without having the appropriate administrator rights. This error appears for mail clients written only with the Intelligent Messaging Mail Client API.
3065 (MS_NOINTLREV) - An attempt was made to move a mailbox that has a name containing international characters, and the target server runs a VINES revision earlier than 4.0. Upgrade the target server to a revision of VINES that supports international characters. This error appears for mail clients written only with the Intelligent Messaging Mail Client API.
3066 (MS_INVBUFLEN) - The maximum buffer length is exceeded. A mail client call specified a buffer length greater than 1024 bytes. This error appears for mail clients written only with the Intelligent Messaging Mail Client API.
3067 (MS_ILLFORMADDR) - A mail client user specified a recipient address that is not either a StreetTalk or gateway address. Legal address formats are described in the Intelligent Messaging Mail User's Guide. If an address has more left than right brackets, the error also returns. This error appears for mail clients written only with the Intelligent Messaging Mail Client API.
3068 (MS_ADDRTOOBIG) - The address is too large. A mail service tried to parse or store a recipient address that exceeds 512 bytes. This error appears for mail clients written only with the Intelligent Messaging Mail Client API.
3069 (MS_TOOMANYBKTS) - A mail service tried to parse or store a recipient address with an unequal number of left ([) and right (]) brackets. Brackets are used in gateway addresses and force-routed addresses. For each left bracket in a recipient address, there must also be a corresponding right bracket. The error is only returned if an address has more right brackets than left brackets. This error appears for mail clients written only with the Intelligent Messaging Mail Client API.
3070 (MS_NAMETOOBIG) - The folder name exceeds 14 characters. A mail client user tried to create a folder name with more than 13 characters. Folder names can only be 13 characters or less. The buffers that hold folder names are 14 characters to hold the null terminator. This error appears for mail clients written only with the Intelligent Messaging Mail Client API.
3071 (MS_MESDELMARKED) - The message is marked for deletion.
3072 (MS_MESNOTFOUND) - The message is not found on the queue.
3073 (MS_ATTACHERR) - A mail client user tried to send a message with more attachments than the destination mail service supports. Split up the attachments among several messages, so that each message contains only a few attachments.
3074 (MS_MESNODELETE) - The message cannot be deleted. A mail client user tried to delete a special notification message sent by the mail service that only the message owner can delete.
3075 (MS_INVALIDTYPE) - An invalid forwarding address type is specified. A mail client tried to call a function with an invalid or unsupported cRecipientClass parameter. For example, revisions before 5.00 (6) do not support recipient classes RECIPIENTCC or RECIPIENTBCC for forwarded messages.
3076 (MS_UNAUTHUSER) - The user is unauthorized to perform the requested operation for this mail service.
3077 (MS_ZEROENUM) - A mail client user sent a message containing a list or template in the address field that was not delivered because mail determined that the list or template contained no recipients. Check and correct the address on the message. If necessary, send the message to specific addresses, rather than to a list or template.
3078 (MS_COMPFAIL) - A mail client user sent a message that was compressed by the mail service. The message was not delivered because the destination mail service failed when decompressing the message. Try sending the message again.
3079 (MS_REMCONVERT) - A mail client user sent a message that was not delivered because the remote destination mail service failed to convert the address as required. Check the address on the message for correct format. Try sending the message again.
3080 (MS_CONFIRMYES) - Receipt of message is confirmed. A mail client user sent a certified message that was read, filed, or printed by the recipient.
3081 (MS_CONFIRMNO) - The message was deleted before being read. A mail client user sent a certified message that was deleted by the recipient without reading, filing, or printing it.
3082 (MS_ENVWRITERR) - A mail client failed to write an envelope file to disk because the disk is full, the disk is read-only, or an I/O error occurred. File the message on another disk. If that fails, check for disk errors in the mail service log and server log of the server that maintains the mail service.
3083 (MS_MBNOTFOUND) - A mail client call attempted to access a mailbox that is not maintained by the mail service to which the current mail session is connected. Determine which mail service maintains the mailbox. Then, establish a mail session with that mail service. This error appears for mail clients written only with the Intelligent Messaging Mail Client API.
3084 (MS_PRINOTALLOWED) - A mail client user attempted to send or forward a message with a message priority higher than the user is authorized to use. Resubmit the message with a priority level that the user can use. The highest priority that the user can use is specified in the Cap2 structure. This error appears for mail clients written with the Intelligent Messaging Mail Client API and for mail gateway services written with the Intelligent Messaging Mail Gateway API.
3085 (MS_INVALIDFIELDTYPE) - A mail client call requested that the mail service send a certification message, but specified an invalid certification type. Resubmit the request with a valid type. This error appears for mail clients written only with the Intelligent Messaging Mail Client API.
3086 (MS_MISSINGREQFIELD) - A message submitted to the Banyan mail service is missing a required envelope field. This error appears for mail clients written with the Intelligent Messaging Mail Client API and for mail gateway services written with the Intelligent Messaging Mail Gateway API.
3087 (MS_FIELDTOOLARGE) - A message submitted to the Banyan mail service contains an envelope field that is larger than the maximum size allowed. The maximum size for each field is specified in vnsmafld.h. This error appears for mail clients written with the Intelligent Messaging Mail Client API and for mail gateway services written with the Intelligent Messaging Mail Gateway API.
3088 (MS_MBLOCKED) - This error code indicates that your mailbox is temporarily locked while it is being managed by your system administrator. You cannot access any of the messages in the mailbox, until your system administrator finishes using it.
3089 (MS_FOLDERLOCKED) - This error code indicates that one of the folders in your mailbox is temporarily locked while it is being managed by your system administrator. You cannot access any of the messages in the folder, until your system administrator finishes using it.
3090 (MS_BADINDEX) - Users should report the appearance of this message to their system administrators. System administrators should make sure that the databases containing indexed fields are synchronized. Check the mail service log for error conditions.
3091 (MS_DUPINDEX) - A mail client call attempted to add an index for an envelope field, but that field already has an index. This error appears for mail clients written only with the Intelligent Messaging Mail Client API.
3092 (MS_NOINDEX) - A mail client call attempted to add an index for an envelope field, but all the available indexes have been used. To add an index for this field, first remove one of the other existing indexes. This error appears for mail clients written only with the Intelligent Messaging Mail Client API.
3093 (MS_INVINDEX) - A mail client call attempted to remove an index for an envelope field, but that index cannot be deleted. The mail service maintains indexes on certain fields by default. These default indexes cannot be deleted. This error appears for mail clients written only with the Intelligent Messaging Mail Client API.
3094 (MS_DELIVERED) - The certified message was delivered to the recipient's mailbox.
3095 (MS_MESDELETED) - A message in your mailbox was deleted by your system administrator.
3096 (MS_INVPARAM) - A mail client attempted to issue a function, but did not correctly set up one of the parameters that is used by the function. This error appears for mail clients written only with the Intelligent Messaging Mail Client API.
3097 (MS_FIELDNOTFOUND) - A mail client attempted to issue a function to retrieve the ID of an envelope field, but specified a field name that is not pre-defined by the Intelligent Messaging Mail Client API. This error appears for mail clients written only with the Intelligent Messaging Mail Client API.
3098 (MS_ENTRYERROR) - A mail client attempted to issue a function to retrieve, add, update, or store envelope fields for a mail message, but an error occurred with one of the envelope fields. If a function returns this error, check the status field of the VNS_FIELD_ENTRY structure to determine which envelope field caused the error. This error appears for mail clients written only with the Intelligent Messaging Mail Client API.
3099 (MS_INVALIDQUERYID) - A mail client attempted to issue a function, but passed in an invalid query ID. Check the VNS_QUERY_ENTRY structure for incorrect syntax. This error appears for mail clients written only with the Intelligent Messaging Mail Client API.
3100 (MS_INVALIDQUERY) - A mail client attempted to issue a function, but passed in a query array that was incorrectly constructed. Check the VNS_QUERY_ENTRY structure for incorrect syntax. This error appears for mail clients written only with the Intelligent Messaging Mail Client API.
3101 (MS_WINMEMERROR) - An error occurred when manipulating a Windows memory handle. Windows could not complete the request to handle memory. This error appears for mail clients written only with the Intelligent Messaging Mail Client API.
3102 (MS_DBINUSE) - An attempt was made to open an envelope database, but that database is currently in use. This error appears for mail clients written with the Intelligent Messaging Mail Client API and for mail gateway services written with the Intelligent Messaging Mail Gateway API.
3103 (MS_FILENOTOPEN) - The mail service could not open a file. Users should report this message to their system administrators. System administrators should check the mail service log for the name of the file that could not be opened.
3104 (MS_FILEREADERR) - The mail service could not read a file for a message. Users should report this message to their system administrators. System administrators should check the mail service log for the name of the file that could not be read.
3105 (MS_INVALUE) - The mail service encountered a value outside the expected range for a parameter. This error appears for mail clients written only with the Intelligent Messaging Mail Client API.
The following Server Service return codes are common to many Server Service functions:
5001 (SSERRUNK) - The error code on the VNSERR command line is unknown. Known error codes begin with AVD (Attribute View Definition), COM (Communications), SER (Server Service), SNM (VINES Network System Management), STK (StreetTalk), VPS (VINES Print Service), VNM (VINES Network Mail), and VAN (VINES Security Service).
5002 (SSBADSVC) - The specified service is unknown. An entry for a service does not exist in the Server Service svc3.db database file. However, StreetTalk has a record of this service. The svc3.db database file may be corrupted by a system failure. Stop and restart the Server Service. If the error persists, call the appropriate support personnel.
5003 (SSBADCOMM) - The Server Service used an invalid command, resulting in a severe problem. Install the VINES software on the server again.
5004 (SSNOMEM) - The server does not have sufficient memory to process a server service request, such as a request from an administrator to add a service. Try again later.
5005 (SSNOPROG) - The specified program is not available. This error occurs for two reasons:
![]() |
The pgms3.db database file is corrupt. This file contains entries for all the legal service types. If the file was corrupted due to a system failure, entries for some program types may be incomplete or may not exist at all. Stop and restart the server service. If the error persists, the pgms3.db database file may be corrupt. In this case, install the VINES software again. |
![]() |
The option associated with a service type is not enabled. Enable the option. |
5006 (SSFIELDS) - Too many parameters are supplied. MSERVICE passed the Server Service too many initialization parameters for the service being created. The administrator does not have to correct this error.
5007 (SSETERNAL) - An administrator tried to add a service, and the service creation script that the Server Service uses to create the service failed. This error indicates that the service creation script may not be functioning properly. Try to add the service again. If the error persists, install VINES software on the server again.
5008 (SSETERNAL) - An attempt was made to stop or delete the Server Service, StreetTalk Service, or VINES Security Service. These services cannot be stopped or deleted manually.
5009 (SSNOTSTOPD) - You tried to delete a service that is running. Stop the service before deleting it.
5010 (SSSVCEXISTS) - You tried to add a service with a StreetTalk name that already exists. Specify a unique StreetTalk name for the service.
5011 (SSSVCRUNNING) - You attempted to start a service that is already running. Only stopped services can be started.
5012 (SSCNTEXC) - The maximum number of services of this type are running. No more services of this type can be started. Stop a service of this type before starting a new one.
5013 (SSNONAME) - The naming service is temporarily unavailable. StreetTalk is not running on the server. If the StreetTalk Service does not automatically start, try starting the service manually.
5014 (SSINVPARM) - An unauthorized or incorrect request was made. The Server Service cannot call StreetTalk successfully. Any StreetTalk error other than "STK1017 - Invalid Session Handle" causes SER1014 to appear. Check the StreetTalk log files for more information.
5015 (SSNOTIMP) - The specified function is not implemented yet. A program such as a client issues a function that is not fully supported yet to Server Service. The administrator does not have to correct this problem.
5016 (SSDESTROYERR) - An administrator tried to delete a service, and the script that the Server Service uses to delete the service failed. Try to delete the service again.
5017 (SSNORIGHT) - You are not authorized to perform this operation. You must be a member of the appropriate AdminList to perform this operation.
5018 (SSINUSE) - The specified device is currently in use. Someone tried to start a print service that is configured to use the same printer port as an already running print service. Two print services that run concurrently cannot use the same printer port.
5019 (SSINITING) - The server is initializing and temporarily cannot honor your request. Servers cannot process many types of requests while they initialize in the network. The servers process requests once they initialize, when the services on them are running. The administrator does not have to correct this problem.
5020 (SSINCONSIST) - The Server Service cannot find a name of a service in the StreetTalk database. This error results from an inconsistency between the Server Service and StreetTalk databases. Either the service does not exist in the network or the StreetTalk Service on this server cannot find this service due to network failures or other problems.
5021 (SSREADFAIL) - The Server Service could not read information from a file that is installed as part of a patch. Install the patch again.
5022 (SSWRITEFAIL) - The Server Service could not write information to a file that was installed as part of a patch. Install the patch again.
5023 (SSEXECFAIL) - A UNIX shell command failed to execute. Programs such as VINES logging programs that run from MSERVICE and OPERATE use a Server Service call to implement such commands. If this error occurs while you are performing a function through a program such as MSERVICE or OPERATE, try again. If the error persists, contact the appropriate support personnel.
5024 (SSATRNOFILE) - The service attributes database file, /disk1/banyan/ss/SvcAttrs, is missing. This file contains information about the logging mask for each service. Possible causes of this error are:
![]() |
The file was deleted due to a serious system error. |
![]() |
Someone accidentally deleted the file after accessing System Maintenance. |
5025 (SSATRNOFIND) - Service entry is missing in the attribute database. Every service requires an entry in the service attributes database file, /disk1/banyan/ss/SvcAttrs. This entry includes the StreetTalk name of the service and its logging mask, which can be set through MSERVICE or OPERATE. Possible causes of this error are:
![]() |
The entry was deleted due to a serious system error that corrupted SvcAttrs. |
![]() |
Someone accessed UNIX on the server and accidentally deleted the entry when editing the file. |
5026 (SSATRNOUPDAT) - The Server Service cannot update the service attributes database file, /disk1/banyan/ss/SvcAttrs. The file could be corrupt or the Server Service may not be able to write to the file.
5027 (SSATRNOTFOUND) - The attribute cannot be found. An entry in the service attributes database file, /disk1/banyan/ss/SvcAttrs, contains attribute information such as the logging mask for the service. Error 5027 appears when the Server Service cannot find this information. Possible causes of this error are:
![]() |
The entry was deleted due to a serious system error that corrupted SvcAttrs. |
![]() |
Someone accessed UNIX on the server and accidentally deleted the entry when editing the file. |
5028 (SSCREATEEXC) - The maximum number of services of this type are created. No more services of this type can be added. For example, this error occurs when you try to create more than one mail service on a server. Delete a service of this type before adding a new one.
5029 (SSXLATNOTAVAIL) - The location code is not supported on this server. A client program asks the Server Service to translate an error message in the language for which the workstation running the client is configured. However, the server running this server service does not support the workstation's language on VINES Files (drive Z). A location code identifies the files on drive Z that support a given language. For example, the code USA identifies the files that support American English. Use SETDRIVE at the workstation to access VINES Files on a server that supports the workstation's language.
5030 (SSUSRUNK) - The user ID or user name supplied is unknown. A mapping between a user ID and the corresponding user name was requested. However, Server Service cannot perform the mapping. Either the user was deleted or the supplied information is incorrect.
VINES Network System Management
The following VNSM return codes are common to many VNSM functions:
5504 () - There is a mismatch between the timestamp specified by the function and the time at which data was collected. Issue the function again with a timestamp of 0.
5901 (E_BADREV) - You specified an incorrect value for the revision parameter.
5904 (E_BUFSHORT) - The value for a buffer length is insufficient.
5905 (E_BADINFO) - The value specified in pStkInfo.info or pStkInfo.info_2 is not supported.
5906 (E_BADSTAT) - The type of statistic specified in Svrstat.stat is insufficient.
5907 (E_NOTSUPPORTED) - The called server cannot service the request.
5908 (E_BADSVCNAME) - The called server runs VINES 4.0 and the server is in the process of computing the requested data. This error can also occur if an invalid StreetTalk name is specified.
5909 (E_BADSVR) - The server being referenced does not support the required functionality.
5910 (E_INITIALIZING) - The called server runs VINES 4.0 and the server is in the process of computing the requested data.
5911 (E_NOMEM) - There is insufficient free memory available.
5912 (E_BADSLOT) - An invalid slot number is specified.
5913 (E_BADLINE) - An invalid line number is specified.
5914 (E_NOSVCSUPPORT) - A service cannot return SVC_CURRENTSESS or SVC_CURRENTUSERS statistics.
5915 (E_NOPARAM) - The number of data items/parameters passed with an alert does not match the number expected from the alert definition.
5916 (E_BUFOVERFLOW) - You tried to send too much data with an alert report. This overflows the alert data buffer.
5917 (E_BADALERTLEN) - An error occurred when decoding an alert while trying to unpack the alert data buffer.
5918 (E_NOTRANSLATE) - No mapping is found to translate the alert ID into a textual alert string while trying to decode an alert.
5919 (E_BADALERTACTION) - An invalid action code was specified when trying to register to receive alerts with VnsRegisterReceive.
5922 (E_MAXATTRIBIDS) - The number of attributes passed is greater than the maximum size of the lower-level attribute data buffer.
The following return codes are used by the EVS API:
7710 - This error can occur during a retrieve request using the Event Management Service (EVS) API. The error indicates that too many events match the specified filter criteria. EVS cannot return all the events. Re-issue the request, specifying a more selective filter criteria that limits the number of events retrieved at one time.
7711 - This error can occur during a retrieve request using the Event Management Service (EVS) API. The error indicates that no events in the database match the specified filter criteria.
7712 - This error can occur if the Event Management Service (EVS) cannot complete allocation of memory required to execute a request. Check for error conditions in the EVS service log and the server log of the server that maintains the EVS service.
7713 - This error might be the return value for a confirmed event. The error indicates that the Event Management Service (EVS) received an event with an old timestamp. The event is stored in the appropriate database file.
7714 - An unexpected failure condition occurred. Check for error conditions in the Event Management Service (EVS) service log and the server log of the server that maintains the EVS service.
7715 - This error might be the return value for a confirmed event. The error indicates that the Event Management Service (EVS) database file has reached the maximum size. As a result, the event was NOT stored in the database file.
7716 - This error might be the return value for a confirmed event. The error indicates that the Event Management Service (EVS) encountered an error writing to the database. A possible cause of this error may be that one of the fields in the event exceeded the size allowed.
7717 - This error can occur if the Event Management Service (EVS) is unable to translate an event to send a network message or mail message or is unable to translate strings during a retrieve request. A possible cause of this error may be that the translation file is missing from the necessary directory.
7718 - This error can occur if the Event Management Service (EVS) is unable to send a trap. A possible cause of this error may be that the .map file is missing from the necessary directory.
7719 - This error can occur if the Event Management Service (EVS) cannot execute a request. Verify that you have the required administrative privileges to issue the request. For example, to make a request to retrieve audit events, you must be on the audit list. The audit list is set through the EVS MIB. The default list is: auditor@audit@audit. This error can also indicate that the StreetTalk service is not accessible. Therefore, EVS can not verify your administrative privileges.
7740 - This error can occur during a request using the Event Management Service (EVS) API. The error indicates that the buffer specified in the API function is not large enough. Re-issue the function, using the buffer size indicated in the parameter returned with this error.
7760 - This condition can occur during a multi-pass retrieve request using the Event Management Service (EVS) API. The condition indicates that no more events in the database match the specified filter criteria. Thus, EVS has returned all the events requested.
The following return codes are used by HCS:
7801 (HCS_BUFFER_TOO_SMALL) - The user's return buffer specified in the API function is not large enough. Re-issue the function, using the buffer size HCS_BUFFER_SIZE.
7802 (HCS_UNPACK_FAILED) - HCS has encountered an OID with an HCSTLV type it does not recognize.
7803 (HCS_INVALID_TBLNAME) - The table name you specified is not found in the HCS configuration database. Verify that you specified a valid table name, and re-issue the request, if necessary. To obtain a list of valid table names, issue the VnsRetrieveTableList function.
7804 (HCS_BADREV) - You specified an invalid revision level when you issued a function. Verify the revision level you need to specify and re-issue the function.
7805 (HCS_INVALIDTIME) - This error can occur during a request using the VnsRetrieveHistory function of the History Collector Service (HCS) API. The error indicates that you specified an invalid time parameter when you issued the function. For example, this error occurs if you specify a start time that is greater than the end time. Check that the time parameter you specified is logical and re-issue the function.
7806 (HCS_NOMEMORY) - This error can occur if the History Collector Service (HCS) cannot complete allocation of memory required to execute a request. Check for error conditions in the HCS service log and the server log of the server that maintains the HCS service.
7807 (HCS_TABLENOTFOUND) - HCS cannot find the specified database file. Check for error conditions in the HCS service log and in the server log of the server that maintains the HCS service.
7808 (HCS_DBFAILURE) - HCS cannot perform a database operation on the specified database file. Check for error conditions in the HCS service log and in the server log of the server that maintains the HCS service.
7809 (HCS_NOMATCHFOUND) - No data in the database matches the specified request. A possible cause of this error may be that you specified a sample time for which no data exists in the database. Or, you may have specified an invalid OID value. Check that the sample time and the OIDs you specified are correct and re-issue the function.