Oracle Calendar API Developer's Guide Release 2.5 Part Number B10097-01 |
|
| View PDF |
This chapter documents all CAPI_Status values that may be returned by CAPI functions, in alphabetical order. The functions CAPI_GetStatusString and CAPI_GetStatusLevels may be useful when interpreting CAPI_Status values.
API class status.
A bad parameter was passed.
There was a problem with a callback.
The callback returned an error, which is returned in bit field 5.
Bad flags were passed.
There was a problem with a handle.
The passed handle was corrupt.
The passed handle was not null.
The passed handle was null.
A null pointer was passed.
There was a problem with a session.
The passed session was corrupt.
The passed session was not null.
The passed session was null.
There was a problem with a stream.
The passed stream was corrupt.
The passed stream was not null.
The passed stream was null.
Data class status.
Information about the supplied cookie.
Information about a date.
The format of the date data is incorrect.
A specified date is invalid (e.g. Feb 30th)
A specified date is out of the range supported by this implementation.
The date range is incorrect.
Information about email.
No email address is set on the server for 1 or more users/resources.
Information about the encoding of supplied data.
Information about a hostname.
The format of the hostname string was wrong.
The hostname string could not be resolved to a host.
No server could be found on the specified host and port.
Information about iCalendar data.
An extra component was encountered. Either multiple specifications of a component which should only appear once, or a component which should not appear.
An expected or required component was missing.
There was a problem with a component name.
There was a problem with what a component contained.
There was a problem in the line folding.
A problem with this particular iCalendar implementation.
One of the iCal data lines was too long, breaching the iCalendar spec (RFC 2445).
The provided data was not iCalendar data.
There was an overflow when parsing the iCalendar data. This is caused by an internal limitation of the iCalendar library, and not not by a breach of the spec.
An extra parameter was encountered. Either multiple specifications of a parameter which should only appear once, or a parameter which should not appear.
An expected or required parameter was missing.
There was a problem with a parameter name.
There was a problem with a parameter value.
An extra property was encountered. Either multiple specifications of a property which should only appear once, or a property which should not appear.
An expected or required property was missing.
There was a problem with a property name.
There was a problem with a property value.
There was a problem with the recurrence specification. The rules laid out in the description of CAPI_StoreEvent were breached.
Information about MIME data.
There was a problem with a parameter name.
A comment could not be parsed.
The encoding specified in the MIME object is not supported.
There was a problem with a parameter name.
A header could not be parsed.
A restriction specific to this MIME implementation was breached.
The MIME object was nested too deeply.
One of the header lines was too long.
No MIME parts were found whose headers indicated that they contain iCalendar data.
No MIME data was found.
There was a problem with a parameter name.
Information about a UID.
The format of the UID string was wrong.
An event with the supplied UID could not be found.
The specified recurrence could not be found.
Information about a userid.
There was a problem with the Extended part of the UserId string.
Either userid AND X.400 were specified, or both a node and a calendar domain were specified.
The format of the extended string was bad.
There was a problem with the inifile.
Multiple users were identified by the string.
The specified node could not be found.
No users were identified by the string.
The format of the UserId string was wrong.
There was a problem with the Id part of the UserId string.
Library class status.
The feature is not fully implemented.
An internal error occured in the library.
Something completely unexpected happened internally.
There was a corruption of data in the library.
The function has expired in this library.
The library miscalled a function.
Some internal maximum was exceeded.
The library abused a protocol.
CAPI received an unknown C++ exception.
Failed to map an error code from a dependant library.
A limitation of or occurence on the server.
The server cannot service the request right now because it is busy.
The server does not provide support.
There is no support for the required character set.
There is no support for CAPI on this server.
There is no support for storing UIDs.
There is some problem with user data on the server.
Operation completed successfully. Value 0.
Security class status.
There was a security error on logon.
Logon authentication failed.
The specified account is locked.
Logon is locked for resources.
Logon is locked for Sysops.
There was a security error on read.
There was a security error reading alarm data.
There was a security error reading properties.
There was a security error in the server.
There was a licensing error on the server.
The server requires a SetIdentity call on the sysop logon to perform the operation.
There was a security error on write.
There was a security error writing to an agenda.
There was a security error writing to an event.
Service class status.
There was a problem caused by one of the ACE plugins.
Required ACE plugin could not be loaded.
Requested ACE option not supported.
There was a problem with system file services.
There was a problem closing a file.
There was a problem deleting a file.
There was a problem with the read or write mode for a file.
There was a problem opening a file.
There was a problem reading from a file.
There was a problem allocating a temporary file.
There was a problem writing to a file.
There was a problem with the standard library services.
There was a problem with system memory services.
Could not allocate memory.
There was a problem with network services.
Timeout while waiting for network services.
There was a problem with system thread services.
There was a problem with the standard time services.
GMTime could not be obtained.