Oracle® Calendar Reference Manual Release 2 (9.0.4) Part Number B10891-02 |
|
|
View PDF |
This appendix describes the most frequently encountered server errors generated by the Oracle Calendar server when running any Oracle Calendar client or utility. Each error code listing contains the error code ID, error name, an explanation of the probable causes, and a recommended action. If you do not find a specific error code in this list, or the information provided does not solve your problem, please use MetaLink, Oracle's web support service. Oracle MetaLink allows you to search a global repository of technical knowledge and query the bug database for known issues. In addition, if the information you need is not available, you can log, view, access and monitor TARs (Technical Assistance Requests) online.
Cause: unib2lendian
failed because the unison.dbd
file cannot be opened.
Action: Verify that the unison.dbd
file exists and that permissions are set correctly.
Cause: unib2lendian
failed because the indicated node-ID was not found in the [YOURNODEID]
section of the unison.ini
file.
Action: Verify that the [YOURNODEID]
section exists and is set correctly in the unison.ini
file.
Cause: An attempt to enable the logging system failed because it was already enabled.
Action: Disable the logging system by specifying [DXSCHED] errlog = FALSE
in the client-side unison.ini
file and restart the client.
Cause: The calendar server has shut down normally, having met no exceptions.
Action: No action required.
Cause: The utility failed because the indicated host name was either missing or invalid.
Action: Correct the syntax and retry the command.
Refer to the Oracle Calendar Reference Manual for instructions on the usage and syntax of all utilities shipped with the Oracle Calendar server.
Cause: The client or utility cannot connect to the indicated calendar server.
Action: Verify that the calendar server is running. If not, restart the calendar server.
Cause: The client or remote node server has been disconnected from the network, or some other network error has occurred.
Action: Restart your client, or wait for the remote node to reconnect automatically.
Cause: A client or remote node server has been disconnected from the network, or some other network error has occurred.
Action: Restart your client, or wait for the remote node to reconnect automatically.
Cause: The client or remote node server has been disconnected from the network, or some other network error has occurred.
Action: Restart your client, or wait for the remote node to reconnect automatically.
Cause: The client has encountered an unexpected situation during network transactions and is unable to continue.
Action: Restart your client.
Cause: A client or remote node server has encountered an undefined response code, or some other network error has occurred.
Action: Restart your client, or wait for the remote node to reconnect automatically.
Cause: The [AUTHENTICATION | COMPRESSION | ENCRYPTION] default
parameter value specified is not included in the [AUTHENTICATION | COMPRESSION | ENCRYPTION] supported
parameter.
Action: Verify that the [AUTHENTICATION | COMPRESSION | ENCRYPTION] default
parameter value specified is included in the [AUTHENTICATION | COMPRESSION | ENCRYPTION] supported
parameter in the unison.ini
file.
Refer to the Oracle Calendar Reference Manual for instructions on setting the parameters available to configure your calendar server.
Cause: The client or remote node server has been disconnected from the network, or some other network error has occurred.
Action: Restart your client, or wait for the remote node to reconnect automatically.
Cause: A client or remote node server has been disconnected from the network, or some other network error has occurred.
Action: Restart your client, or wait for the remote node to reconnect automatically.
Cause: The client or remote node server has been disconnected from the network, or some other network error has occurred.
Action: Restart your client, or wait for the remote node to reconnect automatically.
Cause: Token socket files remaining in the /users/unison/tmp
directory cause a conflict when the calendar server is subsequently restarted.
Action: Delete the .sck
files from the /users/unison/tmp
directory and restart the server.
Refer to the Oracle Calendar Reference Manual for instructions on the usage and syntax of all utilities shipped with the Oracle Calendar server.
Cause: A client or remote node server has been disconnected from the network, or some other network error has occurred.
Action: Restart your client, or wait for the remote node to reconnect automatically.
Cause: The Engine or Directory Access Server encountered a time out before receiving a response. Either the network or remote machine may be busy, or another network problem may have occurred.
Action: Restart your client, or wait for the remote node to reconnect automatically.
Cause: The [UTL] host
parameter value is missing or invalid.
Action: Set the [UTL] host
parameter correctly in the unison.ini
file and restart the server.
Refer to the Oracle Calendar Reference Manual for instructions on setting the parameters available to configure your calendar server.
Cause: uniaccessright
failed because the grantor is an event calendar.
Action: Correct the syntax and retry the command.
Refer to the Oracle Calendar Reference Manual for instructions on the usage and syntax of all utilities shipped with the Oracle Calendar server.
Cause: An attempt to attach an event calendar to a group failed.
Action: No action is required. A proper error message is now returned stating that an event calendar cannot be attached to a group.
Cause: The server encountered an unexpected situation and is unable to continue. Possible causes include:
Action: Depending on the cause:
unidbbackup
and unidbfix
Refer to the Oracle Calendar Reference Manual to calculate your kernel parameters.
WARNING:
Cause: The client contained a defect with the Work On-line/Work Off-line functionality.
Action: Upgrade to a later release of the client containing the resolution for this limitation.
Cause: The client or utility is attempting to connect to an incompatible or unsupported calendar server.
Action: Upgrade your version of the Oracle Calendar server. Refer to the Oracle Calendar client Release Notes for system requirements.
Cause: The specified item could not be found. Possible reasons include:
Action: Depending on the cause:
unidbfix
unidsdiff
and unidssync
to force synchronization between calendar server and directory serverRefer to the Oracle Calendar Reference Manual for instructions on the usage and syntax of all utilities shipped with the Oracle Calendar server.
Cause: The utility failed because the access control information (ACI) in the OID for the calendar server ADMIN group may be set improperly.
Action: Run unidsacisetup
to ensure the ACI for the ADMIN group is set correctly.
Refer to the Oracle Calendar Reference Manual for instructions on the usage and syntax of all utilities shipped with the Oracle Calendar server.
Cause: The client contains a defect with modifying the Off-line Agenda file location functionality.
Action: Upgrade to a later release of the client containing the resolution for this limitation.
Cause: The client contains a defect with the Address Book functionality.
Action: Upgrade to a later release of the client containing the resolution for this limitation.
Cause: The client contains a defect with the Off-line functionality.
Action: Upgrade to a later release of the client containing the resolution for this limitation.
Cause: The client's Off-line Agenda files may be corrupt.
Action: Delete the client-side unison.ini
file and Off-line Agenda files from your system.
Windows: Off-line Agenda files [xtmlocal.dat, xtmlocal.ndx, xtmparam.ini, xtmtzone.ini
]
Macintosh: Off-line Agenda files [CorporateTime Index, CorporateTime Data, CorporateTime Params, CorporateTime Timezones
]
Motif: Off-line Agenda files [OfflineData, OfflineIndex, OfflineParameters, OfflineTimezones
]
WARNING:
unison.ini file
contains configuration parameters. Deleting the unison.ini
file will result in the loss of certain user settings and preferences including your connection name.Cause: The client contains a defect with the copy/paste functionality in the Group Agenda View.
Action: Upgrade to a later release of the client containing the resolution for this limitation.
Cause: The client's Off-line Agenda files may be corrupt.
Action: Delete the Off-line Agenda files from your system.
Windows: Off-line Agenda files [xtmlocal.dat, xtmlocal.ndx, xtmparam.ini, xtmtzone.ini
]
Macintosh: Off-line Agenda files [CorporateTime Index, CorporateTime Data, CorporateTime Params, CorporateTime Timezones
]
Motif: Off-line Agenda files [OfflineData, OfflineIndex, OfflineParameters, OfflineTimezones
]
WARNING: Deleting the Off-line Agenda files will delete any unpublished Address Books. Publish all Address Books before deleting the Off-line Agenda files.
Cause: The unirmold -n
argument is missing or invalid.
Action: Correct the syntax and retry the command.
Refer to the Oracle Calendar Reference Manual for instructions on the usage and syntax of all utilities shipped with the Oracle Calendar server.
Cause: The client contains a defect with the date range specified for the import, export or print functionality.
Action: Upgrade to a later release of the client containing the resolution for this limitation.
Cause: The client contains a defect with the create and edit functionality of a recurring Meeting.
Action: Upgrade to a later release of the client containing the resolution for this limitation.
Cause: The client's Off-line Agenda files may be corrupt.
Action: Delete the Off-line Agenda files from your system.
Windows: Off-line Agenda files [xtmlocal.dat, xtmlocal.ndx, xtmparam.ini, xtmtzone.ini
]
Macintosh: Off-line Agenda files [CorporateTime Index, CorporateTime Data, CorporateTime Params, CorporateTime Timezones
]
Motif: Off-line Agenda files [OfflineData, OfflineIndex, OfflineParameters, OfflineTimezones
]
WARNING: Deleting the Off-line Agenda files will delete any unpublished Address Books. Publish all Address Books before deleting the Off-line Agenda files.
Cause: The client contains a defect with the sign-in functionality for resources.
Action: Upgrade to a later release of the client containing the resolution for this limitation.
Cause: The SNC daemon/service cannot start because a node has been stopped.
Action: Check that all nodes are up and restart the server.
Cause: The client contains a defect with the date range specified when attempting to create or edit a Task.
Action: Upgrade to a later release of the client containing the resolution for this limitation.
Cause: The Oracle Calendar server license has expired.
Action: Acquire a valid Oracle Calendar server license.
Cause: The client contains a defect with setting designate access rights for other users.
Action: Upgrade to a later release of the client containing the resolution for this limitation.
Cause: The client is not compatible with the version of the Oracle Calendar server that you are using.
Action: Upgrade your version of the Oracle Calendar server. Refer to the Oracle Calendar client Release Notes for system requirements.
Cause: The Engine or Synchronous Network Connection encountered an unexpected situation while connecting to a remote node.
Action: Use Oracle MetaLink to search for error code definitions or to log a Technical Assistance Request (TAR) online.
Cause: The Engine or Synchronous Network Connection did not respond before a configured time out. The machine or network may be busy, or another network error may have occurred.
Action: The calendar server should re-connect automatically. If this error occurs regularly, it may be necessary to increase the time out values specified in the unison.ini
file.
Refer to the Oracle Calendar Reference Manual for instructions on setting the parameters available to configure your calendar server.
Cause: The Directory Access Server cannot be reached because the unidasd
daemon/service is either down or improperly configured.
Action: Check that the unidasd
daemon/service is enabled [DAS] enable = TRUE
in the unison.ini
file. If it is enabled, check the snc.log
and das.log
files for further information.
Cause: The client or remote node server has been disconnected from the network, or some other network error has occurred.
Action: Restart your client, or wait for the remote node to reconnect automatically.
Cause: The client's Off-line Address Book may be corrupt.
Action: Delete the Off-line Agenda files from your system.
Windows: Off-line Agenda files [xtmlocal.dat, xtmlocal.ndx, xtmparam.ini, xtmtzone.ini
]
Macintosh: Off-line Agenda files [CorporateTime Index, CorporateTime Data, CorporateTime Params, CorporateTime Timezones
]
Motif: Off-line Agenda files [OfflineData, OfflineIndex, OfflineParameters, OfflineTimezones
]
WARNING: Deleting the Off-line Agenda files will delete any unpublished Address Books. Publish all Address Books before deleting the Off-line Agenda files.
Cause: The Directory Access Server daemon encountered an unexpected situation.
Action: Use Oracle MetaLink to search for error code definitions or to log a Technical Assistance Request (TAR) online if the problem persists.
Cause: The specified Directory ID could not be found. Possible reasons include:
Action: Depending on the cause:
unidbfix
unidsdiff
and unidssync
to force synchronization between calendar server and directory server.Refer to the Oracle Calendar Reference Manual for instructions on the usage and syntax of all utilities shipped with the Oracle Calendar server.
Cause: unidssearch failed because the Directory Access Service (DAS) is down, or the calendar server is configured to use its internal directory.
Action: Ensure that your calendar server is configured to connect to an LDAP directory server and that the unidasd
daemon/service is running.
Refer to the Oracle Calendar Reference Manual for instructions on the usage and syntax of all utilities shipped with the Oracle Calendar server.
Cause: The [ENG] utf8_autoconvert
parameter is set to FALSE
.
Action: Set the [ENG] utf8_autoconvert
parameter to TRUE
in the unison.ini
file.
Refer to the Oracle Calendar Reference Manual for instructions on setting the parameters available to configure your calendar server.
Cause: The value passed as a stream offset when saving certain values on the client was not initialized properly.
Action: This error is used internally. No action is required.
Cause: The [ENG] utf8_autoconvert
parameter is set to FALSE
.
Action: Set the [ENG] utf8_autoconvert
parameter to TRUE
in the unison.ini
file.
Refer to the Oracle Calendar Reference Manual for instructions on setting the parameters available to configure your calendar server.
Cause: The client contains a defect whereby the server name specified in the Connection Editor dialog exceeds the maximum defined length.
Action: No action required. Under most circumstances, the client or utility responds to this error with an appropriate message.
Cause: EventCalendar
encountered a problem because ItemAllocate()
received a NULL
(default item).
Action: This error is used internally. No action is required.
Cause: The client contains a defect with the sign-in functionality whereby the client attempts to sign-in before receiving the Kerberos Ticket for authentication. A possible cause may be software used on your network to synchronize time between the server and PC.
Action: Upgrade to a later release of the client containing the resolution for this limitation.
Cause: The client contains a defect whereby specifying the IP Address rather than the server name in the Connection Editor dialog fails.
Action: Upgrade to a later release of the client containing the resolution for this limitation.
Cause: The client contains a defect whereby the fixed length string buffer was not long enough to hold the resource name.
Action: Upgrade to a later release of the client containing the resolution for this limitation.
Cause: The client contains a defect whereby after installing the latest version of the client, you are unable to reinstall an older version. The Off-line Agenda files are not backward compatible.
Action: To resolve this issue, you will need to delete the client-side unison.ini
file as well as the Off-line Agenda files from your system.
WARNING:
unison.ini
file contains configuration parameters. Deleting the unison.ini
file will result in the loss of certain user settings and preferences including your connection name.Cause: The client contains a defect with the sign-in functionality when an invalid user name is specified.
Action: No action required. Under most circumstances, the client or utility responds to this error with an appropriate message.
Cause: The client contains a defect with the Search Agenda functionality.
Action: Upgrade to a later release of the client containing the resolution for this limitation.
Cause: Token socket files remaining in the /users/unison/tmp
directory cause a conflict when the calendar server is subsequently restarted.
Action: Delete the .sck
files from the /users/unison/tmp
directory and restart the server.
Refer to the Oracle Calendar Reference Manual for instructions on the usage and syntax of all utilities shipped with the Oracle Calendar server.
Cause: The [ENG] utf8_autoconvert
parameter is set to FALSE
.
Action: Set the [ENG] utf8_autoconvert
parameter to TRUE
in the unison.ini
file.
Refer to the Oracle Calendar Reference Manual for instructions on setting the parameters available to configure your calendar server.
Cause: The client contains a defect with the Find Entry functionality whereby references to some events were not managed properly. This means that the events you have in the In-tray are referenced in the shared data if you have that event referenced by having a view that has it referenced in the shared data. Some events might not be referenced properly if they are only in the In-tray.
Action: Upgrade to a later release of the client containing the resolution for this limitation.
Cause: The client contains a defect with the Modify Preferences functionality whereby opening the preferences page would cause a JavaScript error using Netscape Navigator and the page would not load using Microsoft Internet Explorer.
Action: Upgrade to a later release of the client containing the resolution for this limitation.
Cause: The client contains a defect with the Search Agenda functionality.
Action: Upgrade to a later release of the client containing the resolution for this limitation.
Cause: A variable was not initialized properly.
Action: This error is used internally. No action is required.
Cause: The client-side unison.ini
file may be corrupt.
Action: Delete the client-side unison.ini
file from your system.
WARNING: The client-side unison.ini
file contains configuration parameters. Deleting the unison.ini
file will result in the loss of certain user settings and preferences including your connection name.
Cause: unistart
failed because the unison.ini
file cannot be opened.
Action: Verify that the unison.ini
file exists and that permissions are set correctly.
Cause: A section is missing from the unison.ini
file.
Action: No action is required. Each parameter's stated default value is used if its section is omitted from the configuration file.
Refer to the Oracle Calendar Reference Manual for instructions on setting the parameters available to configure your calendar server.
Cause: unistart
failed because certain parameters are missing from the unison.ini
file.
Action: Verify that the unison.ini
file contains the necessary parameters.
Refer to the Oracle Calendar Reference Manual for instructions on setting the parameters available to configure your calendar server.
Cause: unistart
failed because a parameter value contains a negative sign although its accepted values are positive integers.
Action: Verify that the indicated parameter value is set correctly in the unison.ini
file and restart the server.
Refer to the Oracle Calendar Reference Manual for instructions on setting the parameters available to configure your calendar server.
Cause: unistart
failed because a parameter value contains alphanumeric characters although its accepted values are positive integers.
Action: Verify that the indicated parameter value is set correctly in the unison.ini
file and restart the server.
Refer to the Oracle Calendar Reference Manual for instructions on setting the parameters available to configure your calendar server.
Cause: unistart
failed because a parameter value exceeded the maximum value allowed.
Action: Set the parameters correctly in the unison.ini
file and restart the server.
Refer to the Oracle Calendar Reference Manual for instructions on setting the parameters available to configure your calendar server.
Cause: The [ENG] AutoAcceptResource
parameter value is missing or invalid.
Action: Set the [ENG] AutoAcceptResource
parameter correctly in the unison.ini
file and restart the server.
Refer to the Oracle Calendar Reference Manual for instructions on setting the parameters available to configure your calendar server.
Cause: unistart
failed because a parameter value is missing a quotation mark.
Action: Verify that the indicated parameter value is set correctly in the unison.ini
file and restart the server.
Refer to the Oracle Calendar Reference Manual for instructions on setting the parameters available to configure your calendar server.
Cause: unistart
failed because duplicate sections are specified in the unison.ini
file.
Action: Verify that each section in the unison.ini
file is specified only once.
Refer to the Oracle Calendar Reference Manual for instructions on setting the parameters available to configure your calendar server.
Cause: unistart
failed because duplicate parameters are specified within a given section in the unison.ini
file.
Action: Verify that each parameter within a given section in the unison.ini
file is specified only once.
Refer to the Oracle Calendar Reference Manual for instructions on setting the parameters available to configure your calendar server.
Cause: unitzinfo
failed because the begin1
and/or end1
parameters specified in the timezone.ini
file are missing or invalid.
Action: Ensure that the timezone.ini
file has not been modified. If this file is corrupted, client connections to the server will be refused and errors will be returned. This drastic measure is used to protect the database from being corrupted.
Cause: The [YOURNODEID] timezone
parameter value is invalid or missing.
Action: Set the [YOURNODEID] timezone
parameter correctly in the unison.ini
file.
Refer to the Oracle Calendar Reference Manual for instructions on setting the parameters available to configure your calendar server.
Cause: The client's Off-line Agenda files may be corrupt.
Action: Delete the Off-line Agenda files from your system.
Windows: Off-line Agenda files [xtmlocal.dat, xtmlocal.ndx, xtmparam.ini, xtmtzone.ini
]
Macintosh: Off-line Agenda files [CorporateTime Index, CorporateTime Data, CorporateTime Params, CorporateTime Timezones
]
Motif: Off-line Agenda files [OfflineData, OfflineIndex, OfflineParameters, OfflineTimezones
]
WARNING: Deleting the Off-line Agenda files will delete any unpublished Address Books. Publish all Address Books before deleting the Off-line Agenda files.
Cause: The client's Off-line Address Book may be corrupt.
Action: Delete the Off-line Agenda files from your system.
Windows: Off-line Agenda files [xtmlocal.dat, xtmlocal.ndx, xtmparam.ini, xtmtzone.ini
]
Macintosh: Off-line Agenda files [CorporateTime Index, CorporateTime Data, CorporateTime Params, CorporateTime Timezones
]
Motif: Off-line Agenda files [OfflineData, OfflineIndex, OfflineParameters, OfflineTimezones
]
WARNING: Deleting the Off-line Agenda files will delete any unpublished Address Books. Publish all Address Books before deleting the Off-line Agenda files.
Cause: The [SYS] sys_owner
and/or [SYS] sys_group
parameter value is invalid.
Action: Set the [SYS] sys_owner
and/or [SYS] sys_group
parameter correctly in the unison.ini
file.
Refer to the Oracle Calendar Reference Manual for instructions on setting the parameters available to configure your calendar server.
Cause: The [ENG] port
parameter is invalid or missing.
Action: Set the [ENG] port
parameter correctly in the unison.ini
file.
Refer to the Oracle Calendar Reference Manual for instructions on setting the parameters available to configure your calendar server.
Cause: unistart
failed because the indicated [LCK] lck_users
parameter is obsolete.
Action: Set the [ENG] maxsessions
parameter instead of the [LCK] lck_users
parameter in the unison.ini
file and restart the server.
Refer to the Oracle Calendar Reference Manual for instructions on setting the parameters available to configure your calendar server.
Cause: unistats
failed because the stats.log
file cannot be opened.
Action: Verify that the stats.log
file exists and that permissions are set correctly.
Refer to the Oracle Calendar Reference Manual for instructions on setting the parameters available to configure your calendar server.
Cause: unistats
failed because a character was specified after a wild card symbol (*). This is not allowed.
Action: Check that no characters are specified after a wild card symbol (*).
Refer to the Oracle Calendar Reference Manual for instructions on the usage and syntax of all utilities shipped with the Oracle Calendar server.
Cause: The unistats -client
argument is missing or invalid.
Action: Correct the syntax and retry the command.
Refer to the Oracle Calendar Reference Manual for instructions on the usage and syntax of all utilities shipped with the Oracle Calendar server.
Cause: A duplicate option was specified with the unistats
utility.
Action: Correct the syntax and retry the command.
Refer to the Oracle Calendar Reference Manual for instructions on the usage and syntax of all utilities shipped with the Oracle Calendar server.
Cause: unistats
failed because the stats.log
file is empty.
Action: Verify that the stats.log
file exists and is not empty.
Refer to the Oracle Calendar Reference Manual for instructions on setting the parameters available to configure your calendar server.
Cause: unistats
failed because the end time specified is earlier than the start time.
Action: Correct the syntax and retry the command.
Refer to the Oracle Calendar Reference Manual for instructions on the usage and syntax of all utilities shipped with the Oracle Calendar server.
Cause: The unistats -e
argument is missing or invalid.
Action: Correct the syntax and retry the command.
Refer to the Oracle Calendar Reference Manual for instructions on the usage and syntax of all utilities shipped with the Oracle Calendar server.
Cause: The unistats -res
argument is missing or invalid.
Action: Correct the syntax and retry the command.
Refer to the Oracle Calendar Reference Manual for instructions on the usage and syntax of all utilities shipped with the Oracle Calendar server.
Cause: The unistats -server
argument is missing or invalid.
Action: Correct the syntax and retry the command.
Refer to the Oracle Calendar Reference Manual for instructions on the usage and syntax of all utilities shipped with the Oracle Calendar server.
Cause: unistats
failed because the start time specified is later than the current system time.
Action: Correct the syntax and retry the command.
Refer to the Oracle Calendar Reference Manual for instructions on the usage and syntax of all utilities shipped with the Oracle Calendar server.
Cause: The unistats -s
argument is missing or invalid.
Action: Correct the syntax and retry the command.
Refer to the Oracle Calendar Reference Manual for instructions on the usage and syntax of all utilities shipped with the Oracle Calendar server.
Cause: An invalid option was specified with the unistats
utility.
Action: Correct the syntax and retry the command.
Refer to the Oracle Calendar Reference Manual for instructions on the usage and syntax of all utilities shipped with the Oracle Calendar server.
Cause: The unistats -user
argument is missing or invalid.
Action: Correct the syntax and retry the command.
Refer to the Oracle Calendar Reference Manual for instructions on the usage and syntax of all utilities shipped with the Oracle Calendar server.
Cause: unistats
failed because the mutually exclusive options -user
and -res
were specified at the same time.
Action: Correct the syntax and retry the command.
Refer to the Oracle Calendar Reference Manual for instructions on the usage and syntax of all utilities shipped with the Oracle Calendar server.
Cause: The unistats -n
argument is missing or invalid.
Action: Correct the syntax and retry the command.
Refer to the Oracle Calendar Reference Manual for instructions on the usage and syntax of all utilities shipped with the Oracle Calendar server.
Cause: Invalid or missing option specified with the unimvuser
utility.
Action: Correct the syntax and retry the command.
Refer to the Oracle Calendar Reference Manual for instructions on the usage and syntax of all utilities shipped with the Oracle Calendar server.
Cause: A string has exceeded the maximum defined length or does not meet the minimum assigned length.
Action: No action is required. Under most circumstances, the client or utility responds to this error with an appropriate message.
Cause: The Directory Access Server received a CTLDAP_CRITICAL_ERR
. Possible reasons include:
Action: Depending on the cause:
Cause: Invalid option specified with the unidsacisetup
utility.
Action: Correct the syntax and retry the command.
Refer to the Oracle Calendar Reference Manual for instructions on the usage and syntax of all utilities shipped with the Oracle Calendar server.
Cause: A user or resource in the directory server is registered as a calendar user but possesses no ctcalxitemid
attribute.
Action: Run the unidsdiff
and unidssync
utilities to force synchronization of the directory and calendar servers.
Refer to the Oracle Calendar Reference Manual for instructions on the usage and syntax of all utilities shipped with the Oracle Calendar server.
Cause: The calendar database is marked as read only. Possible reasons include:
Action: Wait and retry the operation later.
Cause: The client contains a defect with the automatic sign-in functionality when the user does not have a USERID or when the USERID is not unique.
Action: Upgrade to a later release of the client containing the resolution for this limitation.
Cause: The [LIMITS] maxrecur
and [ENG] maxinstances
parameters are missing or set inconsistently. Another cause may be that the parameters are set too low.
Action: Set the [LIMITS] maxrecur
parameter (client-side) and [ENG] maxinstances
parameter (server-side) in the unison.ini
file. It is recommended that you ensure these parameters always be set to the same value to ensure consistency between all clients. If this issue still persists, it may be because the parameters are set too low. To resolve this issue, you will need to increase the values specified for these parameters.
Refer to the Oracle Calendar Reference Manual for instructions on setting the parameters available to configure your calendar server.
Cause: The client contains a defect with the Event Editor when an attempt is made to create a duplicate instance of a recurring Meeting, Daily Note or Day Event. Validation to ensure that there are no duplicate times should be performed before continuing with creation of events.
Action: No action required. Under most circumstances, the client or utility responds to this error with an appropriate message.
Cause: The [LIMITS] resourceconflict
and [ENG] allowresourceconflict
parameters are missing or set inconsistently.
Action: Set the [LIMITS] resourceconflict
parameter (client-side) and [ENG] allowresourceconflict
parameter (server-side) in the unison.ini
file. These parameters should always be set to the same value.
Refer to the Oracle Calendar Reference Manual for instructions on setting the parameters available to configure your calendar server.
Cause: uniical
import failed due to invalid icalendar data attributes.
Action: Correct the icalendar data attribute syntax and retry the command.
Cause: An attempt to create a resource failed because it already exists in the Directory Server.
Action: Specify a different name for the resource you are attempting to create.
Cause: The client contains a defect whereby exception handling was missing when you attempt to add a user that you should not be able to invite to an instance of a recurring Meeting.
Action: Upgrade to a later release of the client containing the resolution for this limitation.
Cause: An attempt to add a node failed because it is already owned by another calendar server on the same host.
Action: Specify a different name for the node you are attempting to create.
Cause: The calendar server does not support the selected or configured character set.
Action: Select a character set from the list of supported character sets provided for the [LOCALE] charset
parameter.
Refer to the Oracle Calendar Reference Manual for instructions on setting the parameters available to configure your calendar server.
Cause: unimmimpsrv
failed because the file required to migrate data from Meeting Maker cannot be opened.
Action: Verify that the required file exists and that permissions are set correctly.
Cause: unirnsynch
failed because the node-ID of the node that is to have its remote node information updated is either missing or invalid.
Action: Correct the syntax and retry the command.
Refer to the Oracle Calendar Reference Manual for instructions on the usage and syntax of all utilities shipped with the Oracle Calendar server.
Cause: The client contains a defect with the Off-line Agenda conversion functionality whereby the shiva libraries were not being initialized properly thus failing to protect against multiple processes from accessing the same set of LST files.
Action: Upgrade to a later release of the client containing the resolution for this limitation.
Cause: The calendar server is unable to load the LDAP client libraries correctly.
Action: To resolve this issue, follow these steps:
Cause: The [ACE_PLUGINS_CLIENT] web_CAL_sharedkey
and/or [ACE_PLUGINS_SERVER] web_CAL_sharedkey
parameter value is invalid.
Action: Set the [ACE_PLUGINS_CLIENT] web_CAL_sharedkey
and/or [ACE_PLUGINS_SERVER] web_CAL_sharedkey
parameter correctly in the unison.ini
file.
Refer to the Oracle Calendar Reference Manual for instructions on setting the parameters available to configure your calendar server.
Cause: uniencrypt
failed because the encryption method specified is missing or invalid.
Action: Correct the syntax and retry the command.
Refer to the Oracle Calendar Reference Manual for instructions on the usage and syntax of all utilities shipped with the Oracle Calendar server.
Cause: An attempt to set an encrypted empty password failed.
Action: Specify a non-empty password to be encrypted.
Cause: The client contains a defect with the sign-in functionality whereby the ctsis.dll asks the operating system for the name of the current user. However, the operating system does not know the name of the current user.
Action: Upgrade to a later release of the client containing the resolution for this limitation.
Cause: The client contains a defect with the lookup functionality when an invalid server name is specified in the Connection Editor dialog.
Action: No action required. Under most circumstances, the client or utility responds to this error with an appropriate message.
Cause: The client contains a defect with the lookup functionality when no server name is specified in the Connection Editor dialog.
Action: No action required. Under most circumstances, the client or utility responds to this error with an appropriate message.
Cause: A client or remote node server has been disconnected from the network, or some other network error has occurred.
Action: Restart your client, or wait for the remote node to reconnect automatically.