Detailed explanation of status messages sent in DataBridge email notification
Overview
When a problem is detected in DataBridge import or export processing for one or more lines a email notification is sent to the email address that is provided in the notification setup.
In the email a short description is given of the problem. In this article we will give you more detailed information on how to prevent or solve these kinds of errors.
Solution
In all cases go to the specific import or export Profile. Click the Jobs button and find the job that mentions the Failure. The job runs are sorted by date. Click on View to go into the detail of the job run. A how-to article is available here.
Investigate the log file for the failures and check below what you could do to repair and rerun the job. Note that the View Log file will not show all information with large log files. It is better to download the log file and open it in an editor like notepad
| Status | Error | Solution | |
|---|---|---|---|
| Success | N.A. | N.A. | |
| Completed with errors | Import | This line has failed with the message 'PriceList cannot be null' | Into your import file into the mentioned line, the PriceList field is empty. As it is a mandatory field this field needs to have a value. When the import file is corrected rerun the job. |
| Completed with errors | Import | WCF Method failed | For some lines, this error is given. The connection was temporarily lost with SuperOffice. Rerun the job to add the missing records. |
| Failure | Import | WCF Method failed | The connection is lost or there was no connection possible with SuperOffice. Rerun the job. |
| Failure | Import | File is empty | The import file is empty and contains no records to process. There could be a problem in the external delivery to fill this file e.g. your ERP system that has a hiccup. Check if you have records in your import file, then rerun the job. |
| Failure | Import | Timeout expired. The timeout period elapsed prior to obtaining a connection from the pool. This may have occurred because all pooled connections were in use and max pool size was reached. | SuperOffice could not make a new connection to their database due to maximum database connections reached. Rerun the job. |
| Failure | Import | We were unable to connect to your SuperOffice environment with the system user. Please try again later. If the problem persists contact support: support@superoffice.com. | Rerun the job. If the problem persists contact support: support@superoffice.com. |
| Failure | Import | Unable to initalize TimeZoneData | See KnowledgeBase article. When checked rerun the job. |
| Failure | Import | The content type text/html; charset=utf-8 of the response message does not match the content type of the binding (text/xml; charset=utf-8). If using a custom encoder, be sure that the IsContentTypeSupported method is implemented properly. The first 1024 bytes of the response were: "example: part of your text" | Check your input file for correct data. Rerun the job. |
| Failure | Import | Authentication failed! | Log in into the SuperOffice environment failed. Check the SuperOffice login status in DataBridge. Rerun the job. |
| Failure | Export | Error:"invalid_grant", Description:"Bad Request", Uri:"" | Log in to the shared Google Drive has failed. Go into your profile and reconnect the shared drive. Rerun the job. |