LOGOUT
|
-1
|
Logout successful.
|
OK
|
0
|
Command successful.
|
LOGIN_FAILED
|
1
|
Login failed, session ID timed out. Invalid session ID
|
LOGIN_OK_DEFAULT_CALENDAR_NOT_FOUND
|
2
|
login.wcap was successful, but the default calendar for this
user was not found. A new default calendar set to the userid was created.
|
DELETE_EVENTS_BY_ID_FAILED
|
6
|
Command failed.
|
SETCALPROPS_FAILED
|
8
|
Command failed.
|
FETCH_EVENTS_BY_ID_FAILED
|
9
|
Command failed.
|
CREATECALENDAR_FAILED
|
10
|
Command failed.
|
DELETECALENDAR_FAILED
|
11
|
Command failed.
|
ADDLINK_FAILED
|
12
|
Command failed.
|
FETCHBYDATERANGE_FAILED
|
13
|
Command failed.
|
STOREEVENTS_FAILED
|
14
|
Command failed.
|
STORETODOS_FAILED
|
15
|
Command failed.
|
DELETE_TODOS_BY_ID_FAILED
|
16
|
Command failed.
|
FETCH_TODOS_BY_ID_FAILED
|
17
|
Command failed.
|
FETCHCOMPONENTS_FAILED_BAD_TZID
|
18
|
Command failed to find correct tzid. Applies to fetchcomponents_by_range, fetchevents_by_id, fetchtodos_by_id.
|
SEARCH_CALPROPS_FAILED
|
19
|
Command failed.
|
GET_CALPROPS_FAILED
|
20
|
Command failed.
|
DELETECOMPONENTS_BY_RANGE_FAILED
|
21
|
Command failed.
|
DELETEEVENTS_BY_RANGE_FAILED
|
22
|
Command failed.
|
DELETETODOS_BY_RANGE_FAILED
|
23
|
Command failed.
|
GET_ALL_TIMEZONES_FAILED
|
24
|
Command failed.
|
CREATECALENDAR_ALREADY_EXISTS_FAILED
|
25
|
The command createcalendar.wcap failed. A calendar with that
name already exists in the database.
|
SET_USERPREFS_FAILED
|
26
|
Command failed.
|
CHANGE_PASSWORD_FAILED
|
27
|
Command failed.
|
ACCESS_DENIED_TO_CALENDAR
|
28
|
Command failed. The user is denied access to a calendar.
|
CALENDAR_DOES_NOT_EXIST
|
29
|
Command failed. The requested calendar does not exist in the database.
|
ILLEGAL_CALID_NAME
|
30
|
createcalendar.wcap failed. Invalid calid passed
in.
|
CANNOT_MODIFY_LINKED_EVENTS
|
31
|
storeevents.wcap failed. The event to modify was a linked
event.
|
CANNOT_MODIFY_LINKED_TODOS
|
32
|
storetodos.wcap failed. The todo to modify was a linked todo.
|
CANNOT_SENT_EMAIL
|
33
|
Command failed. Email notification failed. Usually caused by the server not
being properly configured to send email. This can occur in storeevents, storetodos, deleteevents_by_id, deletetodos_by_id.
|
CALENDAR_DISABLED
|
34
|
Command failed. The calendar is disabled in the database.
|
WRITE_IMPORT_FAILED
|
35
|
Import failed when writing files to the server.
|
FETCH_BY_LAST_MODIFIED_FAILED
|
36
|
Command failed.
|
CAPI_NOT_SUPPORTED
|
37
|
Failed trying to read from unsupported format calendar data.
|
CALID_NOT_SPECIFIED
|
38
|
Calendar ID was not specified.
|
GET_FREEBUSY_FAILED
|
39
|
Command failed.
|
STORE_FAILED_DOUBLE_BOOKED
|
40
|
If double booking is not allowed in this calendar, storeevents fails
with this error when attempting to store an event in a time slot that was already
filled.
Double booking is not allowed under the following circumstances:
-
If theics.conf parameter is set to:user.allow.doublebook=”yes”, but the user’s LDAP calendar property is set to: doublebooking=0 (disallowed). The user’s LDAP calendar properties override the ics.conf setting.
-
If theics.conf parameter is set to: user.allow.doublebook=”no”, the user’s LDAP calendar properties
have no effect.
|
FETCH_BY_ALARM_RANGE_FAILED
|
41
|
Command failed.
|
FETCH_BY_ATTENDEE_ERROR_FAILED
|
42
|
Command failed.
|
ATTENDEE_GROUP_EXPANSION_CLIPPED
|
43
|
An LDAP group being expanded was too large and exceeded the maximum number allowed
in an expansion. The expansion stopped at the specified maximum limit. The maximum
limit defaults to 200. To change the maximum limit, set the server configuration preference calstore.group.attendee.maxsize.
|
USERPREFS_ACCESS_DENIED
|
44
|
Either the server does not allow this administrator access to get or modify
user preferences, or the requester is not an administrator.
|
NOT_ALLOWED_TO_REQUEST_PUBLISH
|
45
|
The requester was not an organizer of the event, and, therefore, is not allowed
to edit the component using the PUBLISH or REQUEST method.
|
INSUFFICIENT_PARAMETERS
|
46
|
The caller tried to invoke verifyevents_by_ids, or verifytodos_by_ids with insufficient arguments (mismatched number of uid's and rid's).
|
MUSTBEOWNER_OPERATION
|
47
|
The user needs to be an owner or co-owner of the calendar in questions to complete
this operation. (Probably related to private or confidential component.)
|
DWP_CONNECTION_FAILED
|
48
|
GSE scheduling engine failed to make connection to DWP.
|
DWP_MAX_CONNECTION_REACHED
|
49
|
Reached the maximum number of connections. When some of the connections are
freed, users can successfully connect. Same as error 11001.
|
DWP_CANNOT_RESOLVE_CALENDAR
|
50
|
Front end can’t resolve to a particular back end. Same as error11002.
|
DWP_BAD_DATA
|
51
|
Generic response. Check all DWP servers. One might be down. Same as error 11003.
|
BAD_COMMAND
|
52
|
The command sent in was not recognized. This is an internal only error code.
It should not appear in the error logs.
|
NOT_FOUND
|
53
|
Returned for all errors from a write to the Berkeley DB. This is an internal
only error code. It should not appear in the error logs.
|
WRITE_IMPORT_CANT_EXPAND_CALID
|
54
|
Can’t expand calid when importing file.
|
GETTIME_FAILED
|
55
|
Get server time failed.
|
FETCH_DELETEDCOMPONENTS_FAILED
|
56
|
fetch_deletedcomponents failed.
|
FETCH_DELETEDCOMPONENTS_PARTIAL_RESULT
|
57
|
Success but partial result.
|
WCAP_NO_SUCH_FORMAT
|
58
|
Returned in any of the commands when supplied fmt-out is
not a supported format.
|
COMPONENT_NOT_FOUND
|
59
|
Returned when a fetch or delete is attempted that does not exist.
|
BAD_ARGUMENTS
|
60
|
Currently used when attendee or organizer specified does not have a valid email
address.
|
GET_USERPREFS_FAILED
|
61
|
get_userprefs.wcap failed. The following error conditions
returns error code 61:
-
LDAP access denied
-
no results found
-
LDAP limit exceeded
-
LDAP connection failed
|
WCAP_MODIFY_NO_EVENT
|
62
|
storeevents.wcap issued with storeytype set
to 2 (WCAP_STORE_TYPE_MODIFY) and the event
doesn’t exist.
|
WCAP_CREATE_EXISTS
|
63
|
storeevents.wcap issued with storetype set
to 1 (WCAP_STORE_TYPE_CREATE) and the event
already exists.
|
WCAP_MODIFY_CANT_MAKE_COPY
|
64
|
storevents.wcap issued and copy of event failed during processing.
|
STORE_FAILED_RECUR_SKIP
|
65
|
One instance of a recurring event skips over another
|
STORE_FAILED_RECUR_SAMEDAY
|
66
|
Two instances of a recurring event can’t occur on the same day
|
BAD_ORG_ARGUMENTS
|
67
|
Bad organizer arguments. orgCalid or orgEmail must
be passed if any other org” parameter is sent. That is, orgUID can’t
be sent alone on a storeevents or a storetodos command
if it is trying about to "create" the event or task. Note, if no “org”
information is passed, the organizer defaults to the calid being
passed with the command.
|
STORE_FAILED_RECUR_PRIVACY
|
68
|
Error returned if you try to change the privacy or transparency of a single
instance in a recurring series.
|
LDAP_ERROR
|
69
|
For get_calprops, when there is an error is getting LDAP
derived token values (X-S1CS-CALPROPS-FB-INCLUDE, X-S1CS-CALPROPS-COMMON-NAME).
|
GET_INVITE_COUNT_FAILED
|
70
|
Error in getting invite count (for get_calprops.wcap and fetchcomponents_by_range.wcap commands)
|
LIST_FAILED
|
71
|
list.wcap failed
|
LIST_SUBSCRIBED_FAILED
|
72
|
list_subscribed.wcap failed
|
SUBSCRIBE_FAILED
|
73
|
subscribe.wcap failed
|
UNSUBSCRIBE_FAILED
|
74
|
unsubscribe.wcap failed
|
ANONYMOUS_NOT_ALLOWED
|
75
|
Command cannot be executed as anonymous. Used only for list.wcap, list_subscribed.wcap, subscribe.wcap, and unsubscribe.wcap commands.
|
ACCESS_DENIED
|
76
|
Generated if a non-administrator user tries to read or set the calendar-owned
list or the calendar-subscribed list of some other user, or if the option is not turned
on in the server
|
BAD_IMPORT_ARGUMENTS
|
77
|
Incorrect parameter received by import.wcap
|
READONLY_DATABASE
|
78
|
Database is in read-only mode. (returned for all attempts to write to the database)
|
ATTENDEE_NOT_ALLOWED_TO_REQUEST_ON_MODIFY
|
79
|
Attendee is not allowed to modify an event with method=request.
|
TRANSP_RESOURCE_NOT_ALLOWED
|
80
|
Resources do not permit the transparency parameter.
|
RECURRING_COMPONENT_NOT_FOUND
|
81
|
Recurring component not found. Only happens when recurring=1 is
passed in by fetch commands. This code is returned if part of the recurring series
(either the master or an exception) is missing.
|
CDWP_ERR_MAX_CONNECTION_REACHED
|
11000
|
Maximum connections to back-end database reached. As connections are freed up,
users can connect to the back-end.
|
CDWP_ERR_CANNOT_CONNECT
|
11001
|
Cannot connect to back-end server. Back-end machine might be down or DWP server
is not up and running.
|
CDWP_ERR_CANNOT_RESOLVE_CALENDAR
|
11002
|
Front-end can't resolve calendar to a particular back-end server.
|
CDWP_ERR_BAD_DATA
|
11003
|
Bad data received from DWP connection. This is a generic formatting error. Check
all DWP servers. One might be down.
|
CDWP_ERR_DWPHOST_CTX_DOES_NOT_EXIST
|
11004
|
For the back-end host, context doesn’t exist in the context table. Solution
is to add back-end host to ics.conf and restart front-end.
|
CDWP_ERR_HOSTNAME_NOT_RESOLVABLE
|
11005
|
DNS or NIS files, or hostname resolver is not set up properly or machine does
not exist.
|
CDWP_ERR_NO_DATA
|
11006
|
No data was received from reading the calendar properties from the DWP connection.
|
CDWP_ERR_AUTH_FAILED
|
11007
|
DWP authentication failed.
|
CDWP_ERR_CHECKVERSION_FAILED
|
11008
|
DWP version check failed.
|