Release 2 (9.0.2)
Part Number A95917-01
 Home |
 Solution Area |
 Contents |
 Index |
| Oracle9iAS Syndication Server User's and Administrator's Guide Release 2 (9.0.2) Part Number A95917-01 |
|
The following sections describe the error messages of Oracle9iAS Syndication Server.
The following messages are associated with Syndication Server.
SYND-200, OK
Cause: The operation completed successfully.
Action: No action need be taken.
SYND-201, Confirmed
Cause: The operation is confirmed.
Action: No action need be taken.
SYND-202, Package sequence state already current
Cause: A subscriber requested a package update but the subscriber is already in the current package sequence state, therefore there are no updates at the moment.
Action: No action need be taken.
SYND-300, Generic catastrophic payload error
Cause: A generic status code indicating an inability to comprehend the received payload.
Action: Check the request payload and resend it; if the problem persists, have your Syndication Server administrator check the status of the requester's account.
SYND-301, Payload incomplete or cannot parse
Cause: The payload sent is severely garbled and cannot be parsed possibly because it is not an XML payload. Expecting an XML payload and received a payload that was not XML.
Action: Resend the payload and be sure it is an XML payload.
SYND-302, Payload not well formed XML
Cause: The payload sent is recognizable as XML, but is not well formed per the definition of XML.
Action: Ask your Syndication Server administrator to fix the corresponding syndication operation module.
SYND-303, Payload validation failure
Cause: The payload failed validation according to the DTD.
Action: Check the request payload. It must conform to the specified request DTD provided by Syndication Server.
SYND-304, Temporary responder problem
Cause: The responder is either too busy, an update is in progress, and so forth. Eventually an identical retry request might succeed.
Action: Check the requester's local message system for any notification of system downtime, or try again later.
SYND-320, Incompatible version
Cause: The communication protocol used in the request is not supported.
Action: If you use the Syndication Server client library, check the list of protocol versions it supports and then contact Oracle Customer Support Services. If you do not use the Syndication Server client library, contact your local system administrator for help.
SYND-331, Failure fetching external data
Cause: The receiver could not follow an external reference (URL) given to it by the sender as an external entity reference. Syndication Server must not reply with this code.
Action: Double check the content offer reference link and all of its related access policies, such as certificates for an HTTP or HTTPS approach.
SYND-390, Payload temporary redirect
Cause: The payload is being redirected temporarily using the supplied new transport communication endpoint. In ICE/HTTP, this means a new URL is supplied.
Action: Contact Oracle Customer Support Services.
SYND-391, Payload permanent redirect
Cause: The payload is being redirected permanently using the supplied new transport endpoint. In ICE/HTTP, this means a new URL is supplied.
Action: Contact Oracle Customer Support Services.
SYND-400, Generic request error
Cause: A generic status code indicating an inability to comprehend the request.
Action: Check the request payload for errors and resend it.
SYND-401, Incomplete or cannot parse
Cause: The request sent is severely garbled and cannot be parsed.
Action: Check the request payload for errors and also make sure you close the communication channel only after the request is completely sent out.
SYND-402, Not well formed XML
Cause: The request sent is unrecognizable XML, but is not well formed per the definition of XML.
Action: Check the request payload for errors.
SYND-403, Validation failure
Cause: The request failed validation according to the DTD.
Action: Make sure the request payload conforms to the request DTD provided by Syndication Server.
SYND-405, Unrecognized sender
Cause: The sender does not have permission to access the current server.
Action: Contact your Syndication Server administrator to verify sender information.
SYND-406, Unrecognized subscription
Cause: Either the subscription ID is not correct, or the subscription is not in a consistent state.
Action: Contact your Syndication Server administrator to verify sender information.
SYND-407, Unrecognized operation
Cause: The request type is not supported at the server side.
Action: Make sure the operation you want to perform is supported for Syndication Server.
SYND-408 Unrecognized operation arguments
Cause: The request argument is not supported at the server side.
Action: Check the request payload against the request DTD provided by Syndication Server. If the error persists, contact Oracle Customer Support Services.
SYND-409, Not available under this subscription
Cause: The requester has referred to something not covered by the subscription referenced in the request.
Action: Resubscribe with additional conditions.
SYND-410, Not found
Cause: A generic error for being unable to find something.
Action: Check the error message for the detail description.
SYND-411, Unrecognized package sequence state
Cause: The package sequence identifier supplied by the sender is not understood by the receiver.
Action: Check the payload for errors. If the error persists, contact Oracle Customer Support Services.
SYND-412, Unauthorized
Cause: The subscriber does not have permission to access Syndication Server or a certain set of content providers.
Action: Contact your Syndication Server administrator.
SYND-413, Forbidden
Cause: Access violation according to the subscriber's profile.
Action: Contact your Syndication Server administrator.
SYND-414, Business term violation
Cause: The current operation or the content of the current request does not comply with the business terms between the subscriber and Syndication Server.
Action: Review the business terms for the subscriber account and adjust the request.
SYND-420, Constraint failure
Cause: A violation or inconsistency for the subscriber's request for content occurred from Syndication Server according to constraints specified in the subscriptions.
Action: Review the constraint for the subscription and adjust the subscriber's request payload.
SYND-422, Schedule violation, try again later
Cause: The request was made at an incorrect time.
Action: Issue the request for a package update within the agreed-upon timing window.
SYND-430, Not confirmed
Cause: A generic error indicating the operation is not confirmed.
Action: Check the subscriber's local system setting to send confirmation. If the error persists, contact Oracle Customer Support Services.
SYND-431, Error fetching external data
Cause: The receiver could not follow an external reference (URL) given to it by the sender.
Action: Check the subscriber's local system settings to enable such action.
SYND-440, Sorry
Cause: As part of the negotiation process, this response indicates the proposal is unacceptable for some reason.
Action: Review the subscription request and make necessary modifications; then resend the request.
SYND-441, Counter proposal
Cause: As part of the negotiation process, this response indicates an updated offer or a counter proposal.
Action: Review the counter offer subscription request and make necessary modifications, then send the response.
SYND-442, Renegotiation in progress
Cause: As part of the renegotiation process, this response indicates that renegotiation is in progress.
Action: Proceed to the renegotiation process.
SYND-443, Offer acknowledged but deferred
Cause: Used during parameter negotiation. The receiver of an offer cannot evaluate the offer without human intervention. The sender may try again later with the offered parameters and the same subscription ID. The receiver is expected to respond with a new offer (reflecting the result of the intervention) at some later time.
Action: After waiting for a reasonable period of time, if there is no response, contact your Syndication Server administrator to see if there was a network problem or system problem, which might explain why no response was received. If there were no obvious network or system problems, then the receiver may either contact the sender directly and come to some agreement, at which time the sender will send out a new offer, or the sender may resend the previous offer at a later time.
SYND-450, Range type invalid
Cause: Used during parameter negotiation. A protocol-specific RANGE of type numerical, lexical, time, or enumeration, has been incorrectly specified.
Action: Review the corresponding sections inside the request payload and make corrections.
SYND-451, Span selection out of range
Cause: Used during parameter negotiation. The value selected in a span is less than the minimum or greater than the maximum.
Action: Review the request payload and make the correction.
SYND-452, Selection error
Cause: Used during parameter negotiation. The number of items selected in an enumeration does not match the select attribute. For example, the select attribute may require one or more items to be selected but the number selected in the response was zero.
Action: Review the request payload and make the correction.
SYND-453, Enumeration selection empty or invalid
Cause: Used during parameter negotiation. The number of selectable ice-enum-item elements is not compatible with the select attribute. For example, the select attribute might indicate that at least one ice-enum-item must be selected, but the actual number of items available is less than the number of ice-enum-item elements in the enumeration.
Action: Review the request payload and make the correction.
SYND-454, Span invalid
Cause: Used during parameter negotiation. A span has values that violate its structure. For example, a span point must not have a value less than the span minimum nor larger than the span maximum.
Action: Review the request payload and make the correction.
SYND-456, Time formats incompatible for comparison
Cause: Used during parameter negotiation. Two time values to be compared during negotiation are in incompatible formats. For example, a duration is being compared with an ICE date or time.
Action: Review the request payload and make the correction.
SYND-500, Generic internal responder error
Cause: This is a catch-all response for general problems.
Action: Contact your Syndication Server administrator.
SYND-501, Temporary responder problem
Cause: The responder is too busy, an update is in progress, and so forth.
Action: Eventually, an identical retry request might succeed.
SYND-503, Not implemented
Cause: The service does not implement the requested operation.
Action: Make sure the operation you want to perform is supported by Syndication Server.
SYND-601, Unsolicited message must be processing now
Cause: The syndicator has unsolicited messages to send to the subscriber, and the subscriber has not yet requested them.
Action: Issue the request for pending packages to Syndication Server.
SYND-602, Excessive confirmations outstanding
Cause: The syndicator had requested confirmation of package delivery, and now refuses to perform any additional operations until the subscriber supplies the confirmations (positive or negative).
Action: Issue the confirmation for the requested package delivery.
SYND-603, No more confirmations to send
Cause: Syndication Server requests a package delivery confirmation that the subscriber believes has already been sent out.
Action: No action is needed.
SYND-604, No more unsolicited messages
Cause: The subscriber sent an ice-unsolicited-now message but the syndicator has no unsolicited messages to send.
Action: Check the subscriber's local system; if the inconsistencies still persist, contact Oracle Customer Support Services.
The following messages are associated with the Syndication Server implementation of the ICE Version 1.1 specification.
SYND-701, Failed to process subscription
Cause: This error happens while Syndication Server is processing the subscription request.
Action: Review the request payload and correct the errors.
SYND-702, Subscription already exists
Cause: The identical subscription to the current one already exists.
Action: Abandon the current request or regenerate the subscription request with different content, such as the ID.
SYND-703, Content provider already exists
Cause: The same content provider is already registered with Syndication Server. This is a Syndication Server administrator error message.
Action: Abandon the current transaction.
SYND-704, Content provider not found
Cause: Invalid content provider ID or the content provider has been removed. This is a Syndication Server administrator error message.
Action: Contact your Syndication Server administrator.
SYND-705, Content provider adaptor not found
Cause: Syndication Server could not locate the source to instantiate the adaptor.
Action: Contact your Syndication Server administrator to determine why there is an inconsistent state for the content provider.
SYND-706, Failed to load the Content Provider Adaptor class
Cause: The adaptor cannot be instantiated by Syndication Server.
Action: The content provider adaptor is corrupted. Contact your Syndication Server administrator.
SYND-707, I/O exception when trying to send a request
Cause: The transport manager failed to send out a payload due to protocol exceptions or because Syndication Server encountered an internal error. There may be a problem with your client library.
Action: Contact Oracle Customer Support Services.
SYND-708, HTTP response error
Cause: When using HTTP/S as the concrete network protocol, it indicated that some network errors happened. There may be a problem with your client library.
Action: Check and make sure the destination URL is correct; contact Oracle Customer Support Services.
SYND-709, Invalid content type for the response
Cause: When using HTTP/S as the concrete network protocol, the content type is not defined.
Action: Contact Oracle Customer Support Services.
SYND-710, Failed to spawn a scheduler
Cause: During the subscription process, if the subscriber asks for auto push delivery and Syndication Server cannot start up a scheduler to handle it, an exception will be returned.
Action: Contact your Syndication Server administrator.
SYND-711, Subscriber already exists
Cause: The subscriber account has already been created on Syndication Server. This is an administrator error message.
Action: Abandon the current registration process. Use the existing subscriber.
SYND-712, Subscriber not found
Cause: Cannot locate the subscriber by the given ID.
Action: Provide a valid subscriber ID.
SYND-713, There is no content provider associated with the current subscriber
Cause: The current subscriber has not been granted permission to access any content provider.
Action: Contact your Syndication Server administrator.
SYND-714, Subscription already expired
Cause: You tried to access content from an expired subscription.
Action: Resubscribe to the content offer.
SYND-715, Scheduler not found
Cause: Syndication Server internal error. The given scheduler has already been removed.
Action: Validate the scheduler ID by using the OSSAdmin utility.
SYND-716, The specified content provider is not accessible to the current subscriber
Cause: Permission is not granted to the subscriber to access the specified content provider.
Action: Verify the content provider ID is correct; if the problem persists, contact your Syndication Server administrator.
SYND-720, Event message exception: Invalid event message format; cannot be parsed
Cause: The event message format is not valid and cannot be parsed.
Action: Contact your Syndication Server administrator.
SYND-721, Event message exception: Failed to initialize the AQ/JMS topic
Cause: The AQ/JMS topic could not be initialized.
Action: Contact your Syndication Server administrator.
SYND-722, Event message exception: Failed to enqueue the message
Cause: The message could not be enqueued.
Action: Contact your Syndication Server administrator.
SYND-730, Cannot open the ZIP file specified by the given name
Cause: The registration (subscriber and content provider) package cannot be found by the given URL.
Action: Correct the URL; check the permission of the package in your local file system.
SYND-731, I/O Exception during the registration process
Cause: I/O error.
Action: Check the local environment or contact Oracle Customer Support Services.
SYND-732, Failed to get the descriptor file for the registration package
Cause: The MANIFEST file in the registration package is not pointing to the descriptor file.
Action: Check the registration package.
SYND-733, XMLException during the registration process
Cause: Failed to validate the descriptor file against the DTD. For example, if the registration process is for a subscriber, the descriptor file should conform to the Subscriber registration DTD.
Action: Check the descriptor file and its corresponding DTD.
SYND-734, Failed to load the specified resource (such as the .xsd file)
Cause: Cannot load the source from the environment (path, env, and so forth).
Action: Check the environment setting.
SYND-735, Gateway entry not found
Cause: Invalid gateway ID or the gateway entry has been removed.
Action: Verify the correctness of the gateway ID. If the problem persists, contact your Syndication Server administrator.
SYND-736, Gateway entry already exists
Cause: Internal administrator error. You tried to add a duplicate gateway entry.
Action: Stop the operation and use the existing one instead.
SYND-741, Failed to set cookie acceptance
Cause: The Oracle HTTP client library does not have the option of accepting an incoming cookie.
Action: Upgrade the Oracle HTTP client library.
SYND-742, Failed to build a valid SSO URL during the handling of redirection
Cause: The Syndication Server client library could not get the login server URL from the HTTP response of the login server.
Action: Check the version of the login server; the Syndication Server client supports only the Oracle9iAS V2 login server.
SYND-743, Internal Error: The Syndication Server client library failed to parse the response sent from the login server while it tried to authenticate the current connected Syndication Server client with the Syndication Server SSO module
Cause: The Syndication Server client library could not get the values of the required fields from the login page of the login server.
Action: Check the login page of the login server, the Syndication Server client supports only the Oracle9iAS V2 login server.
SYND-744, Oracle cookie module does not exist in the HTTP connection
Cause: The Oracle HTTP client library does not include the required cookie module.
Action: Update the Oracle HTTP client library.
SYND-745, Failed to enable the flag that indicates the current Syndication Server client is already successfully logged onto the Syndication Server system
Cause: Failed to set the cookie indicating that the current Syndication Server client is already authenticated.
Action: Update the Oracle HTTP client library.
SYND-750, Failed to send out email
Cause: The e-mail could not be sent.
Action: Check your e-mail server setting.
SYND-760, Client session expired
Cause: The Syndication Server client session expired.
Action: The Syndication Server client must log in again to refresh the session.
SYND-761, Requested handler not available
Cause: The Syndication Server client does not have the required handler.
Action: Check the request.
SYND-770, Failed to open HTTPS certifcates
Cause: The Syndication Server library could not find the required HTTPS certificates.
Action: Check your HTTPS cerficate path setting in the Syndication Server properties table.
SYND-771, Failed to deliver Ice-item-ref data
Cause: The Syndication Server library could not retrieve the content of ice-item-ref.
Action: Check the definition of the specified ice-item-ref.
SYND-772, Invalid proxy setting
Cause: Incorrect proxy setting.
Action: Check your proxy setting in the Syndication Server properties table.
|
 Copyright © 2002 Oracle Corporation. All Rights Reserved. |
|