> For the complete documentation index, see [llms.txt](https://docs.solutioo.de/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.solutioo.de/dhl-connector/dhlconnector_en_us/troubleshooting-and-support/haufige-probleme-und-losungen.md).

# Troubleshooting

<details>

<summary><strong>Not All Functions of the DHL Connector Are Displayed, or the Assisted Setup Produces an Error Message.</strong></summary>

Your administrator controls which **permissions and views** you have access to.\
If you are missing functions you need, contact your **Business Central administrator** and request **additional permissions** specifically for the **DHL Connector**.

</details>

<details>

<summary><strong>An Error Message Appears When Uploading to DHL (Recipient Address Issue)</strong></summary>

If you have correctly filled in the **Package Code**, **Weight UOM**, and **Weight** fields in a sales order, but clicking **“Upload Packages”** causes an error — while other orders work fine — this is due to **DHL’s automatic address validation**.

When uploading, DHL checks whether the sender and recipient addresses are valid — for example, whether the **house number exists**.\
The same validation happens when manually creating a shipment in the DHL Business Customer Portal.

Please verify the following:

* The **house number** is separated from the **street name** by a **space**.
* The **postal code** matches the **city**.
* The **customer address** entered during checkout contains **no typos**, especially in the street name.

</details>

<details>

<summary><strong>An Error Occurs During Upload to DHL That Is Not Related to the Address</strong></summary>

There can be several possible causes. Please make sure that

* The **connection test** was **successful**. See [Basic settings](https://docs.solutioo.de/dhl-connector/dhlconnector_en_us/configuration/grundlegende-einstellungen.md)
* The **country code** stored in the customer record matches DHL’s requirements.\
  DHL expects a **two-letter country code**, while Business Central typically uses a **three-letter code** by default.
* The **package type** you are trying to use is **included in your DHL contract**.\
  Example: If your contract does **not include “Go Green”**, attempting to send a package with that service from Business Central will result in an error.
* If you receive the message **“Token could not be generated”**, the connection to DHL failed.\
  Check whether the option **“Allow HTTP Client Requests”** is enabled in the **Extension Management** section of the DHL Connector.\
  Then verify that the **connection test** completes successfully.

</details>

<details>

<summary><strong>The Assisted Setup for DHL Boxes Does Not Work</strong></summary>

As an alternative to the guided setup, you can use the **Business Central search** and enter **“DHL”**, then select **“DHL Packages.”**\
Here, you can create a new package manually — just as you would via the assisted setup.

If this page is not available to you, ask your **Business Central administrator** whether the appropriate **permissions** have been assigned to your user.

</details>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.solutioo.de/dhl-connector/dhlconnector_en_us/troubleshooting-and-support/haufige-probleme-und-losungen.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
