Troubleshooting

Checks after setup and common issues during operation of the Klardaten DATEV Connector.

Basic checks after installation

After installation, at least the following checks should be completed:

  1. Check the Windows service: Make sure Klardaten DATEV Connector is installed, running, and configured for automatic startup.
  2. Check the logs: Review the application logs for warnings or errors. If installation failed, also check C:\klardaten_install_log.txt and the Windows Event Viewer.

Common issues

Backend connection does not work

If the connector cannot reach the backend, first verify connectivity to nats.klardaten.com:443.

Some firewalls expect HTTPS traffic on port 443 or perform Deep Packet Inspection (DPI). That causes problems here because the service uses NATS traffic over TLS and not HTTP.

If you use one of the following systems, apply the corresponding vendor recommendation:

  1. Sophos SG: Create a Transparenzmodus-Ausnahme for the DNS name nats.klardaten.com and the IP address 35.159.179.234.
  2. Kaspersky Webschutz: Add nats.klardaten.com to the whitelist.
  3. Securepoint Firewall: Create a rule for nats.klardaten.com and enable Disable DPI in the advanced settings.

Empty response or HTTP 500 on master-data endpoints

If requests to master-data endpoints return an empty response or a 500 error:

  1. Start Arbeitsplatz.exe once with the user klardaten.
  2. Restart the DATEVconnect Windows service.

No DMS access

Make sure the configured user is assigned to the correct DMS data environment.

Permission issues

Check that:

  • the installation was performed with administrator privileges, and
  • the configured user has the required permissions for the DATEV network drive and the data environment.

Incorrect or missing data

Make sure the user is assigned to the correct data environment (Datenumgebungen). DATEV provides additional information here:

https://apps.datev.de/help-center/documents/1007899

What to send to support

If an issue cannot be resolved directly, the following information helps with analysis:

  • relevant excerpts from the installer log or service log
  • the exact error message
  • a screenshot of the affected step
  • a short description of the environment and the affected step

Previous chapter

Configuration Reference

Next chapter

FAQ