The message, “An error occurred during this operation” appears when you access Calendar from Communications Express.
This error can appear because of either one or more of the following reasons.
The Calendar Server configurations in uwc-deployed-path /WEB_INF/config/uwcconfig.properties are incorrect.
Both Communications Express and Calendar Server are not enabled for hosted domains.
Make sure either Communications Express and Calendar Server are both enabled for Virtual Domains or both disabled for Virtual Domains. Refer to Enabling Hosted Domain Configuration in Calendar for details on enabling Communications Express and Calendar Server for virtual domains.
Calendar Server is not started.
Calendar service is not enabled for this user.
The message, “Calendar Not Available. Could Not Display View. The selected calendar(s) was either deleted, or does not exist, or you do not have permissions to view it. Select another calendar(s)” appears when you access Calendar from Communications Express.
This error can occur when users are provisioned using commcli, which is used for Schema 2, in a non-hosted domain setup scenario. The error message is displayed because commcli incorrectly appends @domain to the value of icsCalendar attribute in the user’s LDAP entry.
To provision users using commcli in a non-hosted domain environment, use the -k legacy option in the commadmin command. For a Hosted domain environment, use -k hosted option. If the -k option is not specified a hosted domain setup is assumed.
./commadmin user create -D admin -w password -X siroe .varrius .com -n siroe.varrius.com -p 85 -d siroe.varrius.com-F test -L user2 -l user2 -Wuser2 -S mail,cal -k legacy ok
If the entry corresponding to an already provisioned user cannot be removed, manually remove the '@domain ' part from icsCalendar, icsSubscribed and icsOwned attributes.
The messages, “Calendars across the domain cannot be searched,” “Calendars across the domain cannot be invited,” “Calendars across the domain cannot be subscribed,” or “Check Availability for Calendars across the domain cannot be done,” appears when you search, invite, subscribe, or check the availability of Calendars across domains from Communications Express.
To search, invite, subscribe, or check the availability of calendars, Cross Domain search needs to be enabled. Refer to the section on “Enabling Cross Domain Searches” in Chapter 13 of the Calendar Server 6 2005Q1 Administration Guide.
Issues with Default Event Status Filter.
The Default Event Status Filter in the Options Calendar window specifies the events to be displayed in the day, week, and month calendar views. The options available are: Accepted, Tentative, Declined, No Response.
When the “Accepted” option is selected as the event status, only those invitations you have accepted are displayed in the day, week or month calendar views. However, all events created by you are always displayed in day, week, or month calendar views.
In the Options Calendar Window, by default only “Accepted” and “Tentative” are selected, which means as a user, you will not see events you have declined or to which you have not responded as yet.
To view all the events in the Day, Week, Month, and Year views, you should select all the options, that is, Accepted, Tentative, Declined, No Response in the Options Calendar window.
Communications Express displays "Server Error" while uploading files greater than 2 MB.
This error occurs while importing events and tasks to a calendar or importing contacts to an address book when the uploaded file size is greater than 2 MB.
By default Communications Express allows import of upto 2 MB file data. However, upload file size limit is configurable.
Configure a greater upload file size limit.
To configure a greater upload file size limit configure the following init parameters for the filter, MultipartFormServletFilter in web.xml:
fileSizeHardLimit . Specifies the maximum byte size of the uploaded file content before an error occurs and the request processing is stopped. For example, if a user uploads three files in one request, and if one or more of the files exceeds the fileSizeHardLimit limit, all files will be discarded and the filter will signal an error condition.
requestSizeLimit . Specifies the maximum byte size of the entire incoming request. If a request violates this limit, request processing will stop and the input stream will be discarded. The filter will then handle the violation as it would for a content size hard limit violation. This limit defaults to 4 MB
fileSizeLimit. Specifies the maximum byte size of uploaded file content. For example, if a user uploads three files in one request, each one of the files may not be larger than this limit. Note that this limit is a softlimit , meaning that if uploaded content exceeds this limit, the content will be discarded but the request will still proceed normally, allowing for handling of the size violation by the application. This limit defaults to 1 MB
failureRedirectURL .(Optional). Specifies the redirect URL the request is forwarded to, when an error occurs. The redirect URL can be configured via the failureRedirectURL init parameter. If no redirect URL has been specified, the filter will throw an exception to immediately end the request. This limit defaults to 2 MB.
For example, to increase the upload file size to 10MB, follow the configuration steps mentioned below:
Take a backup of the existing web.xml from uwc-deployed-path/WEB-INF/web.xml.
Edit the web.xml file at uwc-deployed-path /WEB-INF/web.xml.
Provide the configuration for MultipartFormServletFilter in web.xml as indicated in bold in code example 5-2.
<web-app\> .. .. <filter\> <filter-name\>MultipartFormServletFilter</filter-name\> <filter-class\>com.sun.uwc.calclient.MultipartFormServletFilter</filter-class\> .. .. <init-param\> <param-name\>fileSizeHardLimit</param-name\> <param-value\>10485760</param-value\> <description\>Ten mega bytes</description\> </init-param\> <init-param\> <param-name\>requestSizeLimit</param-name\> <param-value\>10485760</param-value\> <description\>Ten mega bytes</description\> </init-param\> <init-param\> <param-name\>fileSizeLimit</param-name\> <param-value\>10485760</param-value\> <description\>Ten mega bytes</description\> </init-param\> <init-param\> <param-name\>failureRedirectURL</param-name\> <param-value\>put your url here</param-value\> <description\>Request is redirected to this url when uploaded file size crosses fileSizeHardLimit value</description\> </init-param\> .. .. </filter\> .. .. .. .. </web-app\>
Restart web container to have the changes take effect.