Calendar-WS: Common Errors Your Application May Encounter

This document describes some common errors that campus or departmental applications may encounter when accessing Calendar-WS, a Web Services interface to CalAgenda, the shared calendaring system on the University of California, Berkeley campus.

Errors when connecting

The following errors may occur when your application is attempting to connect to the CalAgenda service via the Calendar-WS interface:

CAPI_STAT_SERVICE_NET: <r:description>Connection to calendar server failed.</r:description> <r:oracle-calendar-error> <r:code>CAPI_STAT_SERVICE_NET</r:code> <r:explanation>There was a problem with network services.</r:explanation> </r:oracle-calendar-error>

The Calendar-WS Web Services interface cannot connect to the campus calendar server, CalAgenda. Either CalAgenda is down or otherwise not accepting new connections, or the network connection between the interface and CalAgenda is not working properly. If this occurs, you can try again later. You might also check the status of the CalAgenda service via news items on the CalAgenda website, the Check Server Status page on the CalAgenda website, or the IST System Status page.

Errors when authenticating

The following errors may occur when your application is attempting to authenticate to the calendar server:

CAPI_STAT_DATA_USERID_EXT_NONE: <r:oracle-calendar-error> <r:code>CAPI_STAT_DATA_USERID_EXT_NONE</r:code> <r:explanation>No users were identified by the string.</r:explanation> </r:oracle-calendar-error>

The CalNet UID or CalAgenda username provided, which your application is using to authenticate, does not match the name of a valid user account on the calendar server. This could mean that there is a typo in the UID or username, or that the user's UID hasn't yet been added to their directory information on the calendar server. (In the latter case, you can substitute the CalAgenda username instead.) If you are using a CalAgenda username, make sure that it has been entered exactly as it appears in the CalAgenda directory, including substituting a carat (^) for each space that occurs in the first, middle, or last names.
CAPI_STAT_SECUR_LOGON_AUTH: <r:oracle-calendar-error> <r:code>CAPI_STAT_SECUR_LOGON_AUTH</r:code> <r:explanation>Logon authentication failed.</r:explanation> </r:oracle-calendar-error>

The CalAgenda username and associated password that your application provided, when attempting to authenticate as a calendar user to the calendar server, is not valid. That calendar user account exists on the calendar server, but the password provided is incorrect.

Errors when acting as a designate for a calendar

The following errors may occur when your application is attempting to act as a designate for a calendar. These errors will typically have the error message Setting identity to user [...] failed in the description field within the error block of the results returned:

CAPI_STAT_DATA_USERID_EXT_NONE: <r:oracle-calendar-error> <r:code>CAPI_STAT_DATA_USERID_EXT_NONE</r:code> <r:explanation>No users were identified by the string.</r:explanation> </r:oracle-calendar-error>

The CalNet UID or CalAgenda username provided, for which your application is attempting to act as a designate, does not match the name of a valid user or resource account on the calendar server. This could mean that there is a typo in the UID or username, or that the user's UID hasn't yet been added to their directory information on the calendar server. (In the latter case, you can substitute their CalAgenda username instead.) If you are attempting to act as a designate for a resource, be sure you've added the prefix r: at the beginning of the resource name, and that you have not escaped or substituted for any space characters in the resource name; spaces are accepted "as is" in resource names.
CAPI_STAT_SECUR_INSUFFICIENTRIGHTS: <r:oracle-calendar-error> <r:code>CAPI_STAT_SECUR_INSUFFICIENTRIGHTS</r:code> <r:explanation>User doesn't have sufficient rights to perform the operation.</r:explanation> </r:oracle-calendar-error>

The user or resource calendar for which you are attempting to act as a designate is not currently configured to grant full rights to the CalAgenda user account that your application used to authenticate to the calendar server. You can use the Oracle Calendar client application to enable full designate and viewing rights for your application's CalAgenda user account in each of the user or resource accounts for which your application will be acting as a designate.
CAPI_STAT_SECUR_LOGON_AUTH: <r:oracle-calendar-error> <r:code>CAPI_STAT_SECUR_LOGON_AUTH</r:code> <r:explanation>Logon authentication failed.</r:explanation> </r:oracle-calendar-error>

The user or resource calendar for which you are attempting to act as a designate is not currently configured to grant full rights to the CalAgenda user account that your application used to authenticate to the calendar server. You can use the Oracle Calendar client application to enable full designate and viewing rights for your application's CalAgenda user account in each of the user or resource accounts for which your application will be acting as a designate.

Errors when getting events

The following errors may occur when your application is attempting to retrieve events:

Some events may be missing in the list returned by getEventsByRange()

When your application calls the getEventsByRange() remote procedure, under some circumstances, it may retrieve only a subset of the events on a calendar for the specified date range. When you view that calendar using the Oracle Calendar client application, you can see additional events that were not retrieved by that call.: This is due to a bug in the Oracle Calendar SDK, version 9.0.4.2, which we reported to the vendor in Fall 2004. Until this is fixed in a newer version of the SDK, you will need to enable full viewing rights, as well as full designate rights, to your application's calendar user account on any user or resource calendars for which your application will be acting as a designate. (Note: we have not yet verified whether this bug is fixed in SDK version 10.x, which is the version currently being used by the Calendar-WS interface.)

Errors when adding a new event

The following errors may occur when your application is attempting to add a new event. These errors will typically have the error message Storing events in the calendar failed in the description field within the error block of the results returned:

CAPI_STAT_DATA_ICAL_PROPEXTRA: <r:oracle-calendar-error> <r:code>CAPI_STAT_DATA_ICAL_PROPEXTRA</r:code> <r:explanation>An extra property was encountered. Either multiple specifications of a property which should only appear once, or a property which should not appear.</r:explanation> </r:oracle-calendar-error>

An unescaped comma (",") appears somewhere in the title, location, or details arguments in your call to the addEvent() remote procedure. This is confusing the Oracle Calendar SDK, which sees this as an attempt to add an iCalendar property following the comma. Be sure to escape all commas with backslashes ("\,"); e.g.

location = "2195 Hearst\, 200C Conference Room";
date of event does not match any of the expected date patterns: <r:description>... date of event ... does not match any of the expected date patterns.</r:description>

An invalid beginning or ending date for the event has been provided. The date either did not match the ISO 8601-based Date/Time String format for representing dates that is required by the interface, or is a non-existent calendar date (e.g. February 30).