Overview

This guide helps diagnose issues where tour planning cannot be completed.
Typical symptoms include:

• The planning process finishes without results
• Vehicles are not assigned to tours
• The planning run produces no output

These issues typically indicate availability, configuration, or background‑service problems.

Initial Checks

Review “Info Last Planning” Message

Check the message displayed under Info last planning.
It often provides direct insight into why planning did not complete.

Verify Vehicle Availability

Ensure that all vehicles intended for planning are marked as available.
If vehicles are unavailable or parameters are misconfigured, tour planning cannot continue.

Check Import and Export History

The Import/Export History in PTV Route Optimiser offers important diagnostic information.

Look for:

• Error messages
• Newly created entries
• Unusual patterns or gaps in activity

If no new entries appear, continue with the steps below.

Background Service Verification

Check Whether the Background Service Is Running

If the import/export history shows no new entries:

1. Confirm that the background service responsible for planning and data processing is running.
2. Restart the background service.

If entries still do not appear after restart, the upstream system may not be providing new order data.

Verify the Source of the Error Message

Ensure the displayed error message actually originates from PTV Route Optimiser.

• If the message comes from another internal system, the issue should be investigated by your internal IT team or the responsible system owner before continuing.

Confirm All Required System Services Are Running

Tour planning depends on several system services. Ensure the following are operational:

• Telematics services
• Notification services
• xServer services
• Background services for import and export

If possible, check the log files for these services for warnings or errors.

Review Application Logs

If the issue persists, check the PTV Route Optimiser application log for:

• Error messages
• Warnings
• Unusual system messages

These logs can help identify underlying causes such as failed imports, missing configuration, or system‑level failures.