Error messages

If the received XML-messages are malformed, or something goes wrong during processing of the message, an error message will be returned by our integration service. This document covers the most common error messages. Unexpected faults might produce unknown exceptions which are not covered by this document.

Error messages are reported in one of two ways: as XML or as plain strings. Problems with file contents are generally reported as XML, while other problems, such as authentication and connectivity issues are reported as strings. Error messages are contained in the <UploadProductXmlResult>-tag.

Example of XML-reported error; trying to add a product that does not exist to a campaign:

<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
    <soap:Body>
        <UploadStoreInfoXmlResponse xmlns="http://www.mediablob.com/">
            <UploadStoreInfoXmlResult>?&lt;?xml version="1.0" encoding="utf-8"?&gt;&lt;storeInformation customerID="7" customerIDType="ShoppaID" xmlns="http://shoppa.com/storeInfoSchema"&gt;&lt;package id="C1" name="Campaign nr. 1" startDate="01/01/2019 00:00:00" stopDate="02/02/2019 00:00:00" countryCode="se"&gt;&lt;product id="000001" idType="code1" error="Product does not exist in Mediablob." /&gt;&lt;/package&gt;&lt;/storeInformation&gt;</UploadStoreInfoXmlResult>
        </UploadStoreInfoXmlResponse>
    </soap:Body>
</soap:Envelope>

Example of string-reported error; wrong password was used:

<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
    <soap:Body>
        <UploadStoreInfoXmlResponse xmlns="http://www.mediablob.com/">
            <UploadStoreInfoXmlResult>User is not authenticated.</UploadStoreInfoXmlResult>
        </UploadStoreInfoXmlResponse>
    </soap:Body>
</soap:Envelope>

XML-reported errors

The picture at '*' could not be retrieved.

The picture at the specified URL could not be retrieved. The reason is stated in the error text. Here are some example error texts:

• The picture at '*' could not be retrieved. Reason: The remote server returned an error: (404) Not Found.

• The picture at '*' could not be retrieved. Reason: Invalid URI: The format of the URI could not be determined.

• The picture at '*' could not be retrieved. Reason: Byte array for GUID must be exactly 16 bytes long.

• The picture at '*' could not be retrieved. Reason: Unable to read data from the transport connection: The connection was closed.

• The picture at '*' could not be retrieved. Reason: Exception has been thrown by the target of an invocation.

• The picture at '*' could not be retrieved. Reason: Lost connection to MySQL server during query

• The picture at '*' could not be retrieved. Reason: Lost connection to backend server.

• The picture at '*' could not be retrieved. Reason: Content-Disposition and Content-Type is missing and no file extension found in URI.

Recommended actions:

• The remote server returned an error: (404) Not Found.: Verify that the URL is working and is reachable by our service.

• Lost connection to MySQL server during query: Our service is not responding properly. Wait a few minutes and try again.

• Lost connection to backend server.: Our service is not responding properly. Wait a few minutes and try again.

• Content-Disposition and Content-Type is missing and no file extension found in URI.: Add missing meta-data to images, or add extensions to the URL.

Example XML excerpt:

<picture countryCode="xx" languageCode="xx" fieldName="productname" uri="http://example.com/img/product000001.jpg" error="The picture at 'http://example.com/img/product000001.jpg' could not be retrieved. Reason: The remote server returned an error: (404) Not Found.">http://example.com/img/product000001.jpg</picture>

The supplied picture hashcode does not match any known Mediablob picture

Error text: "The supplied picture hashcode (*) does not match any known Mediablob picture"

The hashcode doesn't match any picture in Mediablob.

Recommended action: Make sure the picture is uploaded before trying to assign it to a product.

Example XML excerpt:

<<picture fieldName="productName" hashCode="00000000-0000-0000-0000-000000000000" error="The supplied picture hashcode (00000000-0000-0000-0000-000000000000) does not match any known Mediablob picture.">00000000-0000-0000-0000-000000000000</picture>

Product does not exist in Mediablob

Error text: "Product does not exist in Mediablob"

You're trying to include a non-existing product in a campaign or price list.

Recommended action: Make sure the product is created before adding it to campaigns/price lists.

Example XML excerpt:

<product id="000001" idType="code1" error="Product does not exist in Mediablob.">
    <field name="price" value="299.00" />
</product>

Product does not exist

Error text: "Product does not exist"

You’re trying to delete a product that does not exist, or add a product that does not exist to a product group.

Recommended actions:

• Deleting a product: The product is already deleted, or never existed. If possible, revise your integration system to avoid deleting already deleted products.

• Adding to product group: Make sure the product is created before adding it to product groups.

Example XML excerpt (campaign/price list):

<product id="000001" idType="Code1" delete="true" error="Product does not exist.">true</product>

Example XML excerpt (product group):

<product id="000001" idType="Code1" error="Product does not exist">
    <group ref="22" />
</product>

Product is a duplicate

Error text: "Product is a duplicate"

The product appears twice in a campaign or price list.

Recommended action: If possible, revise your integration system to avoid sending the same product twice or more in the same context (same campaign, product import, etc.).

Example XML excerpt:

<product id="000001" idType="code1" error="Product is a duplicate.">
    <field name="price" value="299.00" />
</product>

Failed to Save the product

Error text: "Failed to Save the product"

The product could not be saved, probably because of something that happened serverside.

Recommended action: Wait a while and resend your data.

Example XML excerpt:

<product id="000001" idType="code1" error="Failed to Save the product" />

Found 2 products

Error text: "Found 2 products"

When trying to add a product to a product group, two products with the same code were found.

Recommended action: Resolve the conflict, or use a different code to add the product to the product group.

Example XML excerpt:

<product id="000001" idType="Code1" error="Found 2 products">
    <group ref="22" />
</product>

Product has duplicates in the Xml file. The first copy of the product is saved.

Error text: "Product has duplicates in the Xml file. The first copy of the product is saved."

The same product appears multiple times in a product import. Only the first appearance of the product is used, the other ones are discarded.

Recommended action: If possible, revise your integration system to avoid sending the same product twice or more in the same context (same campaign, product import, etc.).

Example XML excerpt:

<product id="000001" idType="Code1" error="Product has duplicates in the Xml file. The first copy of the product is saved.">Code1</product>

The product already belongs to another supplier.

Error text: "The product already belongs to another supplier."

You are trying to modify, or superimpose a value on, a code on a product that does not belong to the customer node you are integrating to. E.g. a store cannot change a code on a product that is owned by their HQ.

Recommended action: If possible, revise your integration system to not attempt to modify codes on lower levels in the customer hierarchy than the product is created on.

Example XML excerpt:

<product id="000001" idType="Code1" error="The product already belongs to another supplier.">Code1</product>

Found existing product in database using the same product code

Error text: Found existing product in database using the same product code: CodeType '*', Value '*'. Product codes must be unique.

You are trying to assign a code to a product, but the code is already used on another product in Mediablob.

Recommended action: If possible, revise your integration system to avoid this behaviour.

Example XML excerpt:

<product id="000001" idType="code1" error="Found existing product in database using the same product code: CodeType 'code1', Value '000001'. Product codes must be unique." />

Found duplicate code

Error text: Found duplicate code: CodeType '*', Value '*'. Product codes must be unique.

You are trying to assign the same code to multiple products within the same file.

Recommended action: If possible, revise your integration system to avoid this behaviour.

Example XML excerpt:

<product id="000001" idType="code1" error="Found duplicate code: CodeType 'code1', Value '000001'. Product codes must be unique." />

String-reported errors

User is not authenticated.

Error text: "User is not authenticated."

The authentication provided in the SOAP-object is not valid.

Recommended action: Verify that you are using the correct login information.

Either uri or keyword MUST be set on a product picture

Error text: "Either uri or keyword MUST be set on a product picture."

There is a picture tag that lacks 'uri', 'hashCode' and 'md5' attributes. One of them must be present to successfully reference a picture.

Recommended action: If possible, revise your integration system to avoid this behaviour.

Object reference not set to an instance of an object

Error text: "Object reference not set to an instance of an object."

The imported XML does not contain any information.

Example of imported XML:

<?xml version="1.0" encoding="utf-8"?>
<mediablob customerID="7" customerIDType="ShoppaID" createDate="2016-07-15T00:31:12.0043405+02:00" xmlns="http://shoppa.com/mediablobSchema">
</mediablob>

Recommended action: If possible, revise your integration system to avoid sending anything if there is no data to send.

Failed to save picture '*'

Error text: "Failed to save picture '*'. The picture might be corrupt, try uploading the picture again or use another picture."

Something went wrong when uploading one or more pictures. Several instances can be present in the same response.

Recommended action: Try uploading the picture again.

Example:

Failed to save picture '00000000-0000-0000-0000-000000000000'. The picture might be corrupt, try uploading the picture again or use another picture.
Failed to save picture '00000001-0001-0001-0001-000000000001'. The picture might be corrupt, try uploading the picture again or use another picture.

Syntax error

Error text: "*. Line *, position *."

There is a syntax error in the imported XML. This is typically caused by unescaped special characters: '&', '<' and '>'. See the encoding section for more details.

Recommended action: Make sure you are encoding special characters correctly: once to get them into the import XML and then once again to get them into the SOAP-object.

Example:

'<', hexadecimal value 0x3C, is an invalid attribute character. Line 3, position 57.

Guid *

Error text: "Guid *"

You have done too many revisions and the version number has gone out of bounds.

Recommended action: Contact Shoppa.

Example:

Guid 00000000-0000-0000-0000-000000000000

Validation error

Error text: "Line: *, Position: * "*""

The imported XML does not match the XML-schema.

Recommended action: Adjust the generation of the XML content according to the given reason.

Example:

Line: 11, Position: 27 "The 'productName' attribute is invalid - The value '' is invalid according to its datatype 'String' - The actual length is less than the MinLength value."

Deadlock found when trying to get lock

Error text: "Deadlock found when trying to get lock; try restarting transaction"

Something went wrong serverside.

Recommended action: Wait a while and resend your data.

Connection must be opened

Error text: "Connection must be opened."

Something went wrong serverside.

Recommended action: Wait a while and resend your data.

Lost connection to MySQL server during query

Error text: "Lost connection to MySQL server during query"

Something went wrong serverside.

Recommended action: Wait a while and resend your data.

Failed to create new session

Error text: "failed to create new session"

Something went wrong serverside.

Recommended action: Wait a while and resend your data.

Exception has been thrown by the target of an invocation

Error text: "Exception has been thrown by the target of an invocation."

Something went wrong serverside.

Recommended action: Wait a while and resend your data.

Lost connection to backend server

Error text: "Lost connection to backend server."

Something went wrong serverside.

Recommended action: Wait a while and resend your data.

An exception occured that could not be fully serialized

Error text: "An exception occured that could not be fully serialized: Exception has been thrown by the target of an invocation."

Something went wrong serverside.

Recommended action: Wait a while and resend your data.