Error Message Details
These messages may also be displayed in the audit log. Each message that is sent to the audit log is prefixed by "CommMgr."
This table describes the interactive messages generated by Mailbox Server.
| Message Number | Message | Description |
|---|---|---|
| 0 | success | The function was successful. |
| 1 | partial success | The function was successful overall, however some errors were encountered. This may happen if a message is sent where some recipients are unreachable. |
| 2 | invalid session | An invalid session ID was supplied to the function. This is usually the result of not calling Logon. |
| 3 | access denied | The function could not complete because either the caller or the Mailbox Service did not have permission to access a necessary resource. |
| 4 | database error | An ODBC error occurred during processing of the function. |
| 5 | database not available | The function could not complete because no database connections were available to service it. |
| 6 | invalid mailbox | An invalid mailbox ID, name, or email address was supplied to the function. |
| 7 | invalid list | An invalid list ID or name was supplied to the function. |
| 8 | invalid message | An invalid message ID was supplied to the function. |
| 9 | invalid recipient | The recipient ID supplied to the function was invalid (it was neither a mailbox id or a list ID). |
| 10 | invalid recipient type | An invalid recipient type was supplied to the function. |
| 11 | invalid attachment | An invalid attachment ID was supplied to the function. |
| 12 | error copying attachment | The function encountered an error while making a copy of an attachment. |
| 13 | invalid folder | An invalid folder ID was supplied to the function. |
| 14 | invalid sender | An invalid sender ID was supplied to the function. |
| 15 | invalid content type | An invalid content-type or sub-type was supplied to the function. |
| 16 | spooler delivering | A request was made for the spooler to start delivering, when in fact it was already delivering. |
| 17 | spooler not delivering | A request was made for the spooler to stop delivering, when in fact it was not delivering anyway. |
| 18 | spooler cannot deliver | The spooler was unable to start delivering messages. |
| 19 | message not ready | A request was made to send a message which is not ready to be sent (it may be missing recipients or have no sender ID). |
| 20 | no message recipients | A message could not be delivered because there were no recipients. |
| 21 | insufficient buffer | The function requires a larger buffer. |
| 22 | invalid acl | An invalid Access Control List was supplied to the function. |
| 23 | security descriptor error | Mailbox Server was unable to create or access a security descriptor. |
| 24 | no acl | No Access Control List is available. |
| 25 | impersonation error | Mailbox Server was unable to assume the identity of the calling application and consequently was unable to verify the caller’s access rights. |
| 26 | access check error | Mailbox Server encountered an error validating access rights. |
| 27 | network error | A network error was encountered while executing the function. This is usually the result of the Mailbox Server shutting down while a client which was connected is still running. |
| 28 | no connection | An attempt was made to call a function before a connection was successfully established to the Mailbox Server. |
| 29 | user cancel | The user cancelled the dialog. |
| 30 | connect failed | An error was encountered connecting to the Mailbox Server. This is usually because the server is not running. |
| 31 | menace not connected | A request was made to disconnect or setup notifications for a session with no associated Menace. |
| 32 | menace connect failed | The Mailbox Server was unable to connect to the requested Menace. |
| 33 | menace invalid mailbox | A request was made to cancel mailbox notifications for a session which has no Menace associated with that Mailbox. |
| 34 | invalid stream | An invalid stream ID was supplied to the function. |
| 35 | stream open failed | An error occurred opening a stream onto an attachment. |
| 36 | stream error | An error occurred while working with a stream. |
| 37 | attachment is shared | This error is obsolete. |
| 38 | gateway not loaded | The function attempted to invoke a gateway function on a gateway which failed to load when the Mailbox Server was started. |
| 39 | gateway not found | The function attempted to invoke a gateway function on a gateway mailbox which uses a gateway that failed to load when the Mailbox Server was started. |
| 41 | out of memory | The Mailbox Server was unable to allocate memory from the operating system. |
| 42 | thread token error | The Mailbox Server was unable to obtain necessary information about the thread. |
| 43 | thread model already set | An attempt was made to reinitialize the UI Library with a different threading model. |
| 44 | invalid thread model | An attempt was made to initialize the UI Library with an invalid threading model. |
| 45 | not supported | The requested function was not supported. |
| 46 | invalid clapi module | The CLAPI library was unable to connect to the CLAPI server interface using the supplied module handle. |
| 47 | invalid dynalink | An attempt was made to call a function in the CLAPI library which was not successfully connected to the CLAPI server interface. |
| 48 | invalid callback | A NULL callback function pointer was supplied. |
| 49 | use default properties | No properties were available. You should use reasonable defaults. |
| 50 | gateway property error | A gateway encountered an error retrieving its properties. |
| 51 | could not create timer | A system timer could not be created. This condition occurs on versions of Microsoft Windows prior to 4.0. |
| 52 | invalid gateway | An invalid gateway name was supplied. |
| 53 | file error | The Mailbox Server encountered a file system error. |
| 54 | sid error | The Mailbox Server encountered an error in a Security ID. |
| 55 | delivery agent not loaded | An attempt was made to call a function in a Delivery Agent which was not loaded when the Mailbox Server was started. |
| 56 | invalid delivery agent | An invalid delivery agent was supplied to the function. |
| 57 | invalid delivery rule | An invalid delivery rule was supplied to the function. |
| 58 | delivery agent handled message | The delivery agent handled the message fully, no more processing is required. |
| 59 | delivery agent param error | The delivery agent encountered an error in its parameters. This is usually caused by an incorrect command line in the delivery rule. |
| 60 | delivery agent error | The delivery agent encountered an error. |
| 71 | message store does not exist | The store directory containing mailbox configurations is missing. |
| 1000 | gateway error | The gateway encountered an error. |
| 1001 | mailbox not supported by gateway | The gateway was requested to perform a function using a mailbox which is not configured to use that gateway. |
| 1019 | The File System Gateway failed to initialize the collection process. | Verify all collection folders are valid and review the Microsoft Windows Application Event viewer for possible causes |