You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We faced an issue, where the DHL Soap Server did not responded correctly or in time (I guess so), when a label was requested.
The error was logged, however, not visible in backend, which led to confusion:
What happened:
The first label creation was not successful due to a hard validation error. This was logged and is visible in backend.
The address was corrected and a label generation was manually requested again.
The Soap request was correct, as seen in logs and even a label was created in DHL business account.
However in Magento the creation was said to be failed, the logs say: dhlpaket.ERROR: Error Fetching http headers
The created label cannot be seen in Magento backend, nor is a shipment comment added that the manual creation failed nor a hint, that the creation might have been successful.
As a result, the packing employee created a (second) label manually within the DHL account, resulting in two valid labels.
The error was found on accident.
Images of Magento Backend
Log of the first failed attempt
logged correctly, error visible in backend, no label created
[2020-12-22 13:34:41] dhlpaket.ERROR: POST /services/production/soap HTTP/1.1
Host: cig.dhl.de
Connection: Keep-Alive
User-Agent: PHP-SOAP/7.3.24
Content-Type: text/xml; charset=utf-8
SOAPAction: "urn:createShipmentOrder"
Content-Length: 1855
Authorization: Basic [hidden]
<?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns1="http://dhl.de/webservice/cisbase" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:ns2="http://dhl.de/webservices/businesscustomershipping/3.0"><SOAP-ENV:Header><ns1:Authentification><ns1:user>[hidden]</ns1:user><ns1:signature>[hidden]</ns1:signature></ns1:Authentification></SOAP-ENV:Header><SOAP-ENV:Body><ns2:CreateShipmentOrderRequest><Version xsi:type="ns1:Version"><ns1:majorRelease>3</ns1:majorRelease><ns1:minorRelease>0</ns1:minorRelease></Version><ShipmentOrder><sequenceNumber>0</sequenceNumber><Shipment><ShipmentDetails><product>V53WPAK</product><ns1:accountNumber>[hidden]</ns1:accountNumber><customerReference>YY</customerReference><shipmentDate>2020-12-23</shipmentDate><ShipmentItem><weightInKG>0.36</weightInKG></ShipmentItem></ShipmentDetails><Shipper><Name><ns1:name1>xx</ns1:name1></Name><Address><ns1:streetName>xx</ns1:streetName><ns1:streetNumber>15</ns1:streetNumber><ns1:zip>06120</ns1:zip><ns1:city>Halle (Saale)</ns1:city><ns1:province>SAC</ns1:province><ns1:Origin><ns1:countryISOCode>DE</ns1:countryISOCode></ns1:Origin></Address><Communication/></Shipper><Receiver><ns1:name1>xx</ns1:name1><Address><ns1:name2></ns1:name2><ns1:streetName>52/xx</ns1:streetName><ns1:streetNumber></ns1:streetNumber><ns1:addressAddition></ns1:addressAddition><ns1:zip>eh530dn</ns1:zip><ns1:city>east calder</ns1:city><ns1:province></ns1:province><ns1:Origin><ns1:countryISOCode>GB</ns1:countryISOCode></ns1:Origin></Address><Communication/></Receiver></Shipment><PrintOnlyIfCodeable active="1"/></ShipmentOrder><labelResponseType>B64</labelResponseType></ns2:CreateShipmentOrderRequest></SOAP-ENV:Body></SOAP-ENV:Envelope>
[] []
[2020-12-22 13:34:41] dhlpaket.ERROR: HTTP/1.1 200 OK
Date: Tue, 22 Dec 2020 13:34:40 GMT
Server: WebServer
Strict-Transport-Security: max-age=63072000; includeSubdomains; preload
X-XSS-Protection: 1; mode=block
X-DNS-Prefetch-Control: off
X-Content-Type-Options: nosniff
X-Frame-Options: SAMEORIGIN
Content-Security-Policy: default-src 'none'; script-src 'none'; frame-src 'none'; object-src 'none'
Content-Type: text/xml;charset=utf-8
Content-Length: 1409
Keep-Alive: timeout=5, max=100
Connection: Keep-Alive
<soap:Envelope xmlns:bcs="http://dhl.de/webservices/businesscustomershipping/3.0" xmlns:cis="http://dhl.de/webservice/cisbase" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<soap:Header/>
<soap:Body>
<bcs:CreateShipmentOrderResponse>
<bcs:Version>
<majorRelease>3</majorRelease>
<minorRelease>0</minorRelease>
</bcs:Version>
<Status>
<statusCode>1101</statusCode>
<statusText>Hard validation error occured.</statusText>
</Status>
<CreationState>
<sequenceNumber>0</sequenceNumber>
<LabelData>
<Status>
<statusCode>1101</statusCode>
<statusText>Hard validation error occured.</statusText>
<statusMessage>Bitte geben Sie eine Hausnummer an.</statusMessage>
<statusMessage>Es handelt sich um eine ungültige Postleitzahl. Bitte verwenden Sie eine britisches Format: AA9A 9AA, A9A 9AA, A9 9AA, A99 9AA, AA9 9AA oder AA99 9AA. Es ist dennoch möglich, einen Versandschein zu drucken.</statusMessage>
<statusMessage>Bitte geben Sie eine Hausnummer an.</statusMessage>
</Status>
</LabelData>
</CreationState>
</bcs:CreateShipmentOrderResponse>
</soap:Body>
</soap:Envelope> [] []
[2020-12-22 13:34:41] dhlpaket.ERROR: Hard validation error occured. Bitte geben Sie eine Hausnummer an. Es handelt sich um eine ungültige Postleitzahl. Bitte verwenden Sie eine britisches Format: AA9A 9AA, A9A 9AA, A9 9AA, A99 9AA, AA9 9AA oder AA99 9AA. Es ist dennoch möglich, einen Versandschein zu drucken. [] []
Log of the second attempt
logged correctly, not visible in Magento backend (neither error message nor label), label created in DHL business account
At least a notice comment should be added on the shipment, that on this error a label might have been successfully created in DHL account, although it cannot be seen in Magento
The text was updated successfully, but these errors were encountered:
that is a tricky situation here. Most likely, the label creation succeeded in the DHL systems but the (positive) response was not received in time.
Based on such an empty response, we cannot make assumptions about the "actual" progress of shipment order processing in the remote systems. From the module perspective, anything but a positive response indicates a failure.
When the shipping label is created manually through the packaging popup, then no error comments are added because the admin user receives immediate feedback in the UI. When the shipping label is created automatically (cron or bulk), then a generic error is added to the order/shipment comments in such cases:
Label could not be created: Web service request failed.
Maybe this is sufficient to watch out for possibly affected shipment orders – if it is worth the effort.
yes, I see the issue. Maybe it would be a little improvement if in such cases the error messages are more specific, so that the non-technical packing worker knows what could have happened:
On bulk or cron processes: Comment to the shipment: "Web service request failed. A label might have been created, please go to DHL Business Portal. "
On manual processes: UI Message: "Web service request failed. A label might have been created, please go to DHL Business Portal. ", Additionally a note/comment to the shipment would also be of benefit for future reference.
@HenKun That does actually make sense. I've looked through some older support cases and found (after some digging) that this can indeed happen. We're going to change the error message and documentation accordingly.
We faced an issue, where the DHL Soap Server did not responded correctly or in time (I guess so), when a label was requested.
The error was logged, however, not visible in backend, which led to confusion:
What happened:
dhlpaket.ERROR: Error Fetching http headers
Images of Magento Backend
Log of the first failed attempt
Log of the second attempt
Proposed solution
The text was updated successfully, but these errors were encountered: