Home / Middleware

31 MCS-38601 to MCS-57840

MCS-38601: The diagnostics application encountered an internal error while processing the request.

Cause: Diagnostic Application Internal Error

Action: See the corresponding error message in the server logs for the root cause.

Level: 1

Type: SEVERE

Impact: Other

MCS-38602: Invalid value for request parameter ''{0}'': {1}

Cause: Invalid request parameter

Action: Retry the request with valid parameter values.

Level: 1

Type: SEVERE

Impact: Other

MCS-38610: The custom code container agent is not running, or cannot be reached (host: {0}, port: {1})

Cause: The custom code container agent is not running or cannot be reached

Action: Start the custom code container agent, or verify the system configuration

Level: 1

Type: WARNING

Impact: Other

MCS-15200: Invalid request URI: {0}. Relative URI must be of the form /<api>/<apiVersion>/<resource>.

Cause: The provided request URI is invalid.

Action: Relative URI must be of the form /api/apiVersion/resource.

Level: 1

Type: SEVERE

Impact: Other

MCS-15201: Could not retrieve metadata for the given API name and version.

Cause: Metadata could not be retrieved for the provided API name and version.

Action: Verify that the provided Backend, API and Resource information is correct.

Level: 1

Type: SEVERE

Impact: Other

MCS-15202: An IO exception occurred writing to ResponseContext out stream {0}.

Cause: An IO exception occurred writing to ResponseContext out stream.

Action: Check server diagnostics log for details.

Level: 1

Type: SEVERE

Impact: Other

MCS-15203: Processing of request URI {0} was aborted due to an exception occurring while attempting to access the HttpServletResponse output stream.

Cause: The HttpServletRequest output stream cound not be accessed.

Action: Check server diagnostics log for details.

Level: 1

Type: SEVERE

Impact: Other

MCS-15204: Could not create a request context for URI {0} as an unexpected exception has occurred.

Cause: An exception occurred while attempting to create a RequestContext.

Action: Check server diagnostics log for details.

Level: 1

Type: SEVERE

Impact: Other

MCS-15205: A timeout occured waiting on a response for the request context for URI {0}.

Cause: A timeout occurred waiting on a response from the RequestContext.

Action: Check server diagnostics log for details.

Level: 1

Type: SEVERE

Impact: Other

MCS-15206: Requested URI {0} references an internal API. Internal APIs are only accessable from within the domain.

Cause: An internal API request was made from outside the domain.

Action: Check server diagnostics log for details.

Level: 1

Type: SEVERE

Impact: Other

MCS-15207: 404 - Not Found

Cause:

Action:

Level: 1

Type: SEVERE

Impact: Other

MCS-15208: An authentication failure occurred while processing request URI {0}. An Authorization header with valid credentials is required.

Cause: An authentication failure occurred.

Action: Check server diagnostics log for details.

Level: 1

Type: SEVERE

Impact: Other

MCS-15209: 401 - Unauthorized

Cause:

Action:

Level: 1

Type: SEVERE

Impact: Other

MCS-15240: The RAML parser was unable to parse the supplied RAML for API {0}, version {1}. Error: {2}

Cause: The mobile API testing service was unable to parse the provided RAML

Action: Ensure the RAML provided to the API is correct.

Level: 1

Type: SEVERE

Impact: Other

MCS-15241: The API testing service received a poorly formatted Accept header in the request: {0}

Cause: The mobile API testing service received a poorly formatted Accept header

Action: Ensure the Accept header in the request is correctly formatted.

Level: 1

Type: WARNING

Impact: Other

MCS-15242: The API testing service received an Accept header for which it has no matching results. Available types are : {0}

Cause: The mobile API testing service received an Accept header it could not fulfil

Action: Ensure the Accept header in the request is of a type available in the RAML.

Level: 1

Type: WARNING

Impact: Other

MCS-15280: Service lifecycle listener {0} failed during startup with error: {1}

Cause: A setup or programming error has occurred for the indicated service lifecycle listener that prevented it from starting up correctly.

Action: Look for failures during invocation of this service instance

Level: 1

Type: WARNING

Impact: Other

MCS-15281: Service lifecycle listener {0} failed during shutdown with error: {2}

Cause: A setup or programming error has occurred for the indicated service lifecycle listener that prevented it from shutting down correctly.

Action: Error: Message CAUSE specified without a matching ACTION. Fix me.

Level: 1

Type: INFO

Impact: Other

MCS-15282: McsCore instance already set and cannot be reset

Cause:

Action:

Level: 1

Type: WARNING

Impact: Other

MCS-15283: Cannot get large/Reader Body content as a String

Cause: An attempt was made to read a message body as a String when the body had content that did not allow this

Action: Error: Message CAUSE specified without a matching ACTION. Fix me.

Level: 1

Type: WARNING

Impact: Other

MCS-15284: Cannot get large/stream Body content as a byte[]

Cause: An attempt was made to read a message body as a byte[] when the body had content that did not allow this

Action: Error: Message CAUSE specified without a matching ACTION. Fix me.

Level: 1

Type: WARNING

Impact: Other

MCS-15285: Cannot get binary content as a Reader/String (character data)

Cause: An attempt was made to read a message body as a Reader when the body had binary content. This is not allowed.

Action: Error: Message CAUSE specified without a matching ACTION. Fix me.

Level: 1

Type: WARNING

Impact: Other

MCS-15286: Body content already consumed. Cannot consume again.

Cause: An attempt was made to read a message body that had already been read, where the body is large and cannot be read multiple times.

Action: Error: Message CAUSE specified without a matching ACTION. Fix me.

Level: 1

Type: WARNING

Impact: Other

MCS-15287: Cannot find binary content from given types of content

Cause: An attempt to identify binary content for a message body (given current available content types) failed.

Action: Error: Message CAUSE specified without a matching ACTION. Fix me.

Level: 1

Type: WARNING

Impact: Other

MCS-15288: Cannot find character content from given types of content

Cause: An attempt to identify character content for a message body (given current available content types) failed.

Action: Error: Message CAUSE specified without a matching ACTION. Fix me.

Level: 1

Type: WARNING

Impact: Other

MCS-15289: Error draining stream into internal byte[] content

Cause: An attempt to drain a message body stream into an internal byte[] for processing has failed.

Action: Error: Message CAUSE specified without a matching ACTION. Fix me.

Level: 1

Type: WARNING

Impact: Other

MCS-15290: Error draining Reader into internal String content

Cause: An attempt to drain a message body Reader into an internal String for processing has failed.

Action: Error: Message CAUSE specified without a matching ACTION. Fix me.

Level: 1

Type: WARNING

Impact: Other

MCS-15291: Unsupported XML parsed/node type: {0}

Cause: An attempt was made to create an XML message body using an unsupported/unknown XML node/object type.

Action: Error: Message CAUSE specified without a matching ACTION. Fix me.

Level: 1

Type: WARNING

Impact: Other

MCS-15292: Service was interrupted by an unchecked Error: {0}

Cause:

Action:

Level: 1

Type: WARNING

Impact: Other

MCS-15293: Service was interrupted by an unchecked Exception: {0}

Cause:

Action:

Level: 1

Type: WARNING

Impact: Other

MCS-15360: Unhandled exception was caught and returned via onException()

Cause:

Action:

Level: 1

Type: INFO

Impact: Other

MCS-15361: Unhandled error was caught and callback notified via onError()

Cause:

Action:

Level: 1

Type: INFO

Impact: Other

MCS-15362: A second response has been recieved for the request. It has been ignored. {0}

Cause: Multiple responses have been received for a request.

Action: No action required. Only the first response has been returned.

Level: 1

Type: SEVERE

Impact: Other

MCS-15363: Ignoring response because an exception or error has already been returned. {0}

Cause:

Action:

Level: 1

Type: WARNING

Impact: Other

MCS-15364: Ignoring error because a response, exception or error has already been returned.

Cause:

Action:

Level: 1

Type: WARNING

Impact: Other

MCS-15365: Ignoring exception because a response, exception or error has already been returned.

Cause:

Action:

Level: 1

Type: WARNING

Impact: Other

MCS-15366: Ignoring exception raised when performing callback.

Cause:

Action:

Level: 1

Type: WARNING

Impact: Other

MCS-37000: Server does not support ECID

Cause: The server running MCS does not support ECID

Action: To use ECID deploy MCS to a server that supports ECID

Level: 1

Type: SEVERE

Impact: Other

MCS-37001: The metering event could not be emitted

Cause: The request information could not be interpreted.

Action: Review the reported exception for further details

Level: 1

Type: WARNING

Impact: Other

MCS-37002: Unable to register event listener {0}

Cause: The event listener is not installed properly and cannot be found from the classpath.

Action: Review the reported exception for further details

Level: 1

Type: WARNING

Impact: Other

MCS-37003: Unable to set request context

Cause: The request context cannot be set in the HttpServletRequest

Action: Review the reported exception for further details

Level: 1

Type: WARNING

Impact: Other

MCS-37004: Unable to set request attributes

Cause: The request attributes cannot be set in the HttpServletRequest

Action: Review the reported exception for further details

Level: 1

Type: WARNING

Impact: Other

MCS-37005: Meter Event Processor is interrupted

Cause: The Meter Event Processor is interrupted and cannot process further events

Action: Review the reported exception for further details

Level: 1

Type: WARNING

Impact: Other

MCS-38501: Failed to update derived noun {0}.

Cause: An exception prevented a derived noun from updating one or more of its metrics.

Action: Review the reported exception for further details

Level: 1

Type: WARNING

Impact: Other

MCS-38591: Start of API Invocation

Cause:

Action:

Level: 1

Type: INFO

Impact: Other

MCS-38592: End of API Invocation

Cause:

Action:

Level: 1

Type: INFO

Impact: Other

MCS-38593: Unserviceable request

Cause:

Action:

Level: 1

Type: INFO

Impact: Other

MCS-38594: Request Timeout

Cause:

Action:

Level: 1

Type: INFO

Impact: Other

MCS-82701: We can't find an object with key {0} in collection "{1}".

Cause:

Action:

Level: 1

Type: SEVERE

Impact: Other

MCS-82702: We can't find collection "{0}". Verify that {0} is included in your mobile backend.

Cause:

Action:

Level: 1

Type: SEVERE

Impact: Other

MCS-82703: You must specify the content-length HTTP request header (the size of the object in bytes).

Cause:

Action:

Level: 1

Type: SEVERE

Impact: Other

MCS-82704: SQL exception occurred.

Cause:

Action:

Level: 1

Type: INCIDENT_ERROR

Impact: Other

MCS-82705: {0} exceeds maximum object name length of {1} characters.

Cause:

Action:

Level: 1

Type: SEVERE

Impact: Other

MCS-82707: You must specify a device ID (using the {0} HTTP request header) to access a collection with device-level isolation.

Cause: A request was made against a device isolated collection without including the device id

Action: Enusre the M_DEVICE_ID header is specified on the request.

Level: 1

Type: SEVERE

Impact: Other

MCS-82708: We can't find your mobile backend. Verify the name and ID.

Cause: X-Backend-Token header was missing or a mobile backend with the corresponding token was not found

Action: Check that a valid X-Backend-Token header was provided on the request.

Level: 1

Type: SEVERE

Impact: Other

MCS-82709: Your object was last modified on {0}, and hasn't changed since the date specified in the If-Modified-Since HTTP request header: {1}

Cause:

Action:

Level: 1

Type: INFO

Impact: Other

MCS-82710: Your object was last modified on {0}, which is after the date specified in the If-Unmodified-Since HTTP request header: {1}

Cause:

Action:

Level: 1

Type: INFO

Impact: Other

MCS-82711: Method is not allowed.

Cause:

Action:

Level: 1

Type: SEVERE

Impact: Other

MCS-82712: The {0} query parameter must be an integer greater than or equal to 0. You specified: {1}.

Cause: Invalid value passed in for offset or limit query parameter

Action: Ensure the value of the offset and limit query parameters are valid integers.

Level: 1

Type: SEVERE

Impact: Other

MCS-82713: We can't fill your request for a subset of bytes in this range. Ensure that your range request does not exceed the size of the object in bytes.

Cause: Value provided in the Range header was not valid for this object.

Action: Update the value of the Range header. The range must be valid for the specified object.

Level: 1

Type: SEVERE

Impact: Other

MCS-82715: Object with eTag {0} did not match one of {1} that was specified in the If-Match HTTP request header.

Cause:

Action:

Level: 1

Type: INFO

Impact: Other

MCS-82716: Object with eTag {0} matched one of {1} that was specified on the If-None-Match HTTP request header.

Cause:

Action:

Level: 1

Type: INFO

Impact: Other

MCS-82717: We can't find an object with the GUID

Cause:

Action:

Level: 1

Type: SEVERE

Impact: Other

MCS-74500: Mobile client id is not specified

Cause: Mobile client id has not been specified.

Action: Ensure that an mobile client id is specified

Level: 1

Type: SEVERE

Impact: Other

MCS-74501: Platform is invalid (should be {0})

Cause: Platform is invalid.

Action: The error message indicates the correct platform

Level: 1

Type: SEVERE

Impact: Other

MCS-74502: Certificate is not specified

Cause: APNS certificate has not been specified.

Action: Ensure that an APNS certificate is specified

Level: 1

Type: SEVERE

Impact: Other

MCS-74503: Certificate is invalid: {0}

Cause: APNS certificate is invalid.

Action: Ensure that an APNS certificate is valid and encrypted correctly

Level: 1

Type: SEVERE

Impact: Other

MCS-74504: Certificate is empty

Cause: APNS certificate is empty.

Action: Ensure that an APNS certificate actually has a certificate

Level: 1

Type: SEVERE

Impact: Other

MCS-74505: API key is not specified

Cause: GCM API key has not been specified.

Action: Ensure that a GCM API key is specified

Level: 1

Type: SEVERE

Impact: Other

MCS-74506: Sender id is not specified

Cause: GCM sender id has not been specified It is required if using XMPP.

Action: Ensure that a GCM sender id is specified

Level: 1

Type: SEVERE

Impact: Other

MCS-74507: Method is not specified

Cause: GCM method has not been specified.

Action: Ensure that a GCM method is specified

Level: 1

Type: SEVERE

Impact: Other

MCS-74508: Service configuration for {0} ({1}) not found

Cause:

Action:

Level: 1

Type: INFO

Impact: Other

MCS-74509: One of message or payload must be specified

Cause: Neither messgae nor payload has been specified. We don't have a message to send.

Action: Specify either message or payload

Level: 1

Type: SEVERE

Impact: Other

MCS-74510: Backend id is not specified

Cause: Backend id has not been specified.

Action: Ensure that a backend id is specified

Level: 1

Type: SEVERE

Impact: Other

MCS-74511: Mobile client {0} not found

Cause: Mobile client was not found.

Action: Ensure that a mobile client has been registered

Level: 1

Type: SEVERE

Impact: Other

MCS-74512: The service configuration is invalid: {0}

Cause: The service configuration is invalid. The exception will be provide more exact details.

Action: Update the service configuration to correct the exception.

Level: 1

Type: SEVERE

Impact: Other

MCS-74513: Notification token is not specified

Cause: Notification token has not been specified.

Action: Ensure that a notification token is specified

Level: 1

Type: SEVERE

Impact: Other

MCS-74514: Platform is not specified

Cause: Platform has not been specified.

Action: Ensure that a platform is specified

Level: 1

Type: SEVERE

Impact: Other

MCS-74515: Mobile client version is not specified

Cause: Moble client version has not been specified.

Action: Ensure that an mobile client version is specified

Level: 1

Type: SEVERE

Impact: Other

MCS-74516: Mobile client is not specified

Cause: Mobile client has not been specified.

Action: Ensure that a mobile client is specified

Level: 1

Type: SEVERE

Impact: Other

MCS-74517: Device is not specified

Cause: Device has not been specified.

Action: Ensure that a device is specified

Level: 1

Type: SEVERE

Impact: Other

MCS-74518: Problem formatting Date

Cause: The date send could not be parsed.

Action: Ensure that date specified are in the correct yyyy-MM-dd'T'HH:mm'Z' format

Level: 1

Type: SEVERE

Impact: Other

MCS-74519: Service configuration is not specified

Cause: Service configuration has not been specified.

Action: Ensure that a service configuration is specified

Level: 1

Type: SEVERE

Impact: Other

MCS-74520: Platform {0} does not match the service type {1}.

Cause: Service type in service configuration is not for the mobile client's platform.

Action: Ensure that the platform in the mobile client matches the service type

Level: 1

Type: SEVERE

Impact: Other

MCS-74530: Notification is not specified

Cause: Notification has not been specified.

Action: Ensure that a notification is specified

Level: 1

Type: SEVERE

Impact: Other

MCS-74531: Notification id not specified

Cause: Notification id has not been specified.

Action: Ensure that a notification id is specified

Level: 1

Type: SEVERE

Impact: Other

MCS-74532: Notification {0} not found

Cause: Notification was not found.

Action: Ensure that the correct notification id is specified.

Level: 1

Type: SEVERE

Impact: Other

MCS-74533: Notification has already been processed and cannot delete notification {0}

Cause: The notification has already been processed and cannot be deleted.

Action: No action required

Level: 1

Type: SEVERE

Impact: Other

MCS-74534: Unexpected exception occurred

Cause: Unexpected error has occurred

Action: The exception message should provide more details.

Level: 1

Type: SEVERE

Impact: Other

MCS-74535: Error uploading APNS certificate

Cause: There was an unexpected exception uploading the APNS certificate

Action: Take action based on the underlying exception

Level: 1

Type: SEVERE

Impact: Other

MCS-74536: Invalid devices have not been specified

Cause: Invalid devices have not been specified

Action: Ensure that the invalid devices have been specified

Level: 1

Type: SEVERE

Impact: Other

MCS-74537: The value {0} is not a valid integer

Cause: An invalid integer value has been specified

Action: Ensure that the value is an integer

Level: 1

Type: SEVERE

Impact: Other

MCS-74538: The value {0} is not in the correct date format (must be in the form "YYYY-MM-DD[Thh:mm]Z")

Cause: An invalid date format has been specified

Action: Ensure that the expected date format is used.

Level: 1

Type: SEVERE

Impact: Other

MCS-74539: The value {0} is not in the correct date format (must be in the form "YYYY-MM-DDThh:mm:ss.SSSZ")

Cause: An invalid date format has been specified

Action: Ensure that the expected date format is used.

Level: 1

Type: SEVERE

Impact: Other

MCS-74540: The value {0} is not valid for the {1} enumeration. Valid values are {2}

Cause: An invalid enum value has been specified

Action: Ensure that the value is valid for the enum

Level: 1

Type: SEVERE

Impact: Other

MCS-74541: A handler was NOT found for {0}.

Cause: A handler has not been found for the given URI. This shouldn't happen because Asset Catalog should not have forwarded the request if it is unsupported.

Action: Contact Oracle Support Services.

Level: 1

Type: SEVERE

Impact: Other

MCS-74542: The media type was wrong. Expected "{0}" but was "{1}"

Cause: The request has the wrong media type.

Action: Ensure that the request has the correct media type

Level: 1

Type: SEVERE

Impact: Other

MCS-74543: "{0}" is not a valid sort field format. It should be of the form "<field name>[:[asc|desc]]".

Cause: The specified sort is invalid.

Action: Ensure that the sort is in the valid form

Level: 1

Type: SEVERE

Impact: Other

MCS-74544: "{0}" is not a supported sort field. It should be one of {1}.

Cause: The specified sort is unsupported.

Action: Ensure that the sort is supported

Level: 1

Type: SEVERE

Impact: Other

MCS-74560: The device token is in an invalid format: {0}

Cause: The device token is in an invalid format

Action: Ensure that the device token is in a valid format (either a 64 character hex string or 32 byte binary equivalent).

Level: 1

Type: SEVERE

Impact: Other

MCS-74561: The device provider for {0} was not found

Cause: The driver provider for the specified service type was not found

Action: Ensure that the driver provider is registered with the driver registry.

Level: 1

Type: SEVERE

Impact: Other

MCS-74570: Notification sent via APNS using {0}

Cause:

Action:

Level: 1

Type: INFO

Impact: Other

MCS-74571: APNS returned a response packet: {0}

Cause: APNS sent a response packet

Action: Take action based on the reason.

Level: 1

Type: SEVERE

Impact: Other

MCS-74572: Unexpected exception thrown while sending via APNS

Cause: Exception thrown while sending an exception via APNS

Action: Take action based on the exception.

Level: 1

Type: SEVERE

Impact: Other

MCS-74573: Payload size ({0} bytes) exceeds limit ({1})

Cause: The payload is too large for APNS

Action: Ensure that the payload is less than the max size.

Level: 1

Type: SEVERE

Impact: Other

MCS-74574: Unexpected exception thrown while checking the feedback service

Cause: Exception thrown while checking the APNS Feedback Service

Action: Take action based on the reason it was rejected.

Level: 1

Type: SEVERE

Impact: Other

MCS-74580: Notification sent via GCM to {0} device(s)

Cause:

Action:

Level: 1

Type: INFO

Impact: Other

MCS-74581: Unexpected exception thrown while sending via GCM

Cause: Exception thrown while sending an exception via GCM

Action: Take action based on the exception.

Level: 1

Type: SEVERE

Impact: Other

MCS-74582: Notification was rejected by GCM. Status={0}. Response={1}

Cause: The request was rejected by GCM

Action: Take action based on the reason it was rejected.

Level: 1

Type: SEVERE

Impact: Other

MCS-74583: GCM returned an invalid number of responses (expected={0}; actual={1})

Cause: The response returned by GCM has an invalid no of results. It should equal the number of devices in the notification.

Action: Contact Oracle Support

Level: 1

Type: SEVERE

Impact: Other

MCS-74584: Driver not found for '{0}'

Cause: There is no driver for the specific service type.

Action: Contact Oracle Support

Level: 1

Type: SEVERE

Impact: Other

MCS-74585: Maximum retries exceeded for notification {0} ({1})

Cause:

Action:

Level: 1

Type: WARNING

Impact: Other

MCS-74590: Feedback service will next check for invalid tokens @ {0}

Cause:

Action:

Level: 1

Type: INFO

Impact: Other

MCS-74591: Error getting invalid notification tokens from APNS feedback service for {0}

Cause: An error occurred reading the invalid tokens from the APNS Feedback Service

Action: The exception message will provide more detail

Level: 1

Type: SEVERE

Impact: Other

MCS-74592: Unexpected status ({0}) when sending invalid tokens to environment {0}. Will be ignored.

Cause:

Action:

Level: 1

Type: WARNING

Impact: Other

MCS-74593: Checking APNS Feedback Service for invalid tokens

Cause:

Action:

Level: 1

Type: INFO

Impact: Other

MCS-74594: Unexpected exception thrown while gettign invalid notification tokens from APNS feedback service

Cause: Exception thrown while checking for invalid tokens from the APNS Feedback Service

Action: Take action based on the exception.

Level: 1

Type: SEVERE

Impact: Other

MCS-39500: The MetricFeederAPI cannot be initialized

Cause: The required resources for the MetricsFeederAPI such as JMS cannot be acquired

Action: Check JMS configurations corresponding to Analytics server.

Level: 1

Type: WARNING

Impact: Other

MCS-57800: Implementation file {0} ({1} byte(s)) was uploaded

Cause:

Action:

Level: 1

Type: INFO

Impact: Other

MCS-57801: RAML file validation failed

Cause:

Action:

Level: 1

Type: WARNING

Impact: Other

MCS-57802: Could not upload implementation; the file with implementation is empty or API not defined.

Cause:

Action:

Level: 1

Type: WARNING

Impact: Other

MCS-57803: Could not upload implementation; the content of the file with implementation is invalid.

Cause:

Action:

Level: 1

Type: WARNING

Impact: Other

MCS-57804: Could not upload implementation due to internal server error.

Cause:

Action:

Level: 1

Type: WARNING

Impact: Other

MCS-57805: Exception thrown in AssetCatalog REST API. Mapped to the REST error response.

Cause:

Action:

Level: 1

Type: WARNING

Impact: Other

MCS-57806: Attempted to rename asset ''{0}'' (type: ''{1}'') to ''{2}''. Asset renaming is not allowed

Cause: Asset renaming is not allowed

Action: Avoid renaming asset

Level: 1

Type: SEVERE

Impact: Other

MCS-57807: BindingPolicy can be assigned to Environment only. Got: ' for API ''{1}''.

Cause: BindingPolicy can be assigned to Environment only

Action: Avoid attaching BindingPolicy to other assets

Level: 1

Type: SEVERE

Impact: Other

MCS-57808: Preset metadata references a resource ''{0}'' that can not be found

Cause: Cannot find requested resource

Action: Verify that resource is available at the specified location

Level: 1

Type: SEVERE

Impact: Other

MCS-57809: Can not update read-only Asset (name: {0}, version: {1}, id: {2})

Cause: Read-only assets cannot be updated

Action: Clone read-only asset instead of updating it

Level: 1

Type: SEVERE

Impact: Other

MCS-57810: Asset name (''{0}') is too long. Actual length: ''{1}''. Allowed length: ''{2}''.

Cause: Asset name length is limited

Action: Limit asset name to the suggested value

Level: 1

Type: SEVERE

Impact: Other

MCS-57811: Asset name (''{0}'') contains one of the reserved characters: ''{1}''

Cause: Asset name contains invalid characters

Action: Specify correct asset name

Level: 1

Type: SEVERE

Impact: Other

MCS-57812: Asset ''{0}'' has no version value provided.

Cause: Asset version is missing

Action: Provide version for the asset

Level: 1

Type: SEVERE

Impact: Other

MCS-57813: Asset ''{0}'' has version (''{1}'') in incorrect format. Supported version format is 'major.minor[.extra]+' with only '.'(dot) and digits allowed.

Cause: Asset version is incorrect

Action: Provide correct version for the asset

Level: 1

Type: SEVERE

Impact: Other

MCS-57814: Failed to convert {0} into {1}

Cause: Cannot find appropriate convertor

Action: Register appropriate convertor for required types

Level: 1

Type: SEVERE

Impact: Other

MCS-57815: Failed to merge {0} with {1}

Cause: Cannot find appropriate merger

Action: Register appropriate merger for required types

Level: 1

Type: SEVERE

Impact: Other

MCS-57816: Failed to patch {0} using {1}

Cause: Cannot find appropriate patcher

Action: Register appropriate patcher for required types

Level: 1

Type: SEVERE

Impact: Other

MCS-57817: Failed to load RAML content

Cause: Cannot load RAML content

Action: Verify RAML artifact details

Level: 1

Type: SEVERE

Impact: Other

MCS-57819: Cannot find default Environment

Cause: Cannot find default environment

Action: Create default environment

Level: 1

Type: SEVERE

Impact: Other

MCS-57820: Icon {0} not found

Cause: Cannot find requested icon

Action: Verify icon identifier

Level: 1

Type: SEVERE

Impact: Other

MCS-57821: Artifact {0} not found

Cause: Cannot find requested artifact

Action: Verify artifact identifier

Level: 1

Type: SEVERE

Impact: Other

MCS-57822: Unable to detect default user realm.

Cause: Cannot identify default user realm

Action: Verify that only user realm exist with default name

Level: 1

Type: SEVERE

Impact: Other

MCS-57823: Asset not found: {0}

Cause: Cannot find requested asset

Action: Verify that requested asset exists

Level: 1

Type: SEVERE

Impact: Other

MCS-57824: Policy Specification ''{0}'' does not exist

Cause: Specified policy specification does not exist

Action: Verify that policy specification name is correct, or create a new one

Level: 1

Type: SEVERE

Impact: Other

MCS-57825: Cannot delete missing entity: {0}

Cause: Specified entity does not exist

Action: Verify that correct entity identifier was specified

Level: 1

Type: SEVERE

Impact: Other

MCS-57826: Cannot update missing entity: {0}

Cause: Specified entity does not exist

Action: Verify that correct entity identifier was specified

Level: 1

Type: SEVERE

Impact: Other

MCS-57827: Incorrect token: ''{0}''. The appropriate Mobile Backend cannot be found

Cause: Specified mobile backend token is incorrect

Action: Verify mobile backend token

Level: 1

Type: SEVERE

Impact: Other

MCS-57828: ErrorCode must be a URI: {0}

Cause: Specified error code is incorrect

Action: Verify error code

Level: 1

Type: SEVERE

Impact: Other

MCS-57829: Cannot lookup specified EJB: {0}

Cause: Specified EJB is not found

Action: Verify EJB name

Level: 1

Type: SEVERE

Impact: Other

MCS-57830: Generic error

Cause: Generic error occured

Action: Verify logs

Level: 1

Type: SEVERE

Impact: Other

MCS-57832: No unique collection with a given name ''{0}'' is associated with the Mobile Backend identified by token ''{1}''

Cause: Incorrect collection name given

Action: Verify requested collection name

Level: 1

Type: SEVERE

Impact: Other

MCS-57833: Cannot clone missing entity: {0}

Cause: Specified entity does not exist

Action: Verify that correct entity identifier was specified

Level: 1

Type: SEVERE

Impact: Other

MCS-57834: Asset can not have empty name

Cause: Asset name is empty or not specified

Action: Set name to the asset

Level: 1

Type: SEVERE

Impact: Other

MCS-57835: Resource paths ''{0}'' and ''{1}'' can not be a part of one API, because one of them contains path parameter in place where another has a static value or they differ only by path parameter names or they are completely similar.

Cause: Incorrect API definition

Action: Verify API definition

Level: 1

Type: SEVERE

Impact: Other

MCS-57836: Client could not be published

Cause: Client couldn't be published

Action: Do not publish the Client

Level: 1

Type: SEVERE

Impact: Other

MCS-57837: Name is empty or is not specified in the package.json file

Cause: Name is empty or is not specified in the package.json file

Action: Set name to the implementation

Level: 1

Type: SEVERE

Impact: Other

MCS-57838: Version is empty or is not specified in the package.json file

Cause: Version is empty or is not specified in the package.json file

Action: Set version to the implementation

Level: 1

Type: SEVERE

Impact: Other

MCS-57839: Main entry is empty or is not specified in the package.json file

Cause: Main entry is empty or is not specified in the package.json file

Action: Set main entry to the implementation

Level: 1

Type: SEVERE

Impact: Other

MCS-57840: Keyword {0} not found

Cause: Cannot find requested keyword

Action: Verify keyword name

Level: 1

Type: SEVERE

Impact: Other