Overview
This article helps diagnose issues where tours fail to export to a connected system.
Common symptoms include:
- Tours do not appear in the target system
- Tour data is not transferred
- The export process appears to stop or fail
Initial Checks
Confirm That Tours Have Been Released
Only released tours can be exported.
Ensure that the relevant tours are marked as released in PTV Route Optimiser.
Verify Export Type Configuration
Check which export type is configured.
Typical export types include:
- TransferDB (TDB)
- WebAPI
- SAP
- File-based formats
If TransferDB (TDB) is used
Verify that a functional database connection to the configured TransferDB system is available.
Check Import/Export History
The import/export history in PTV Route Optimiser provides valuable insights.
Check whether:
- Error messages are displayed
- New export entries are still being created
- The process shows delays, gaps, or repeated failures
If no new entries appear, continue with the steps below.
Background Service Verification
Ensure the Background Service Is Running
If export history is not updating:
- Check whether the background service responsible for import/export is running
- Restart the background service
If no entries appear after a restart, the issue may originate in the upstream system.
Verify the Source of the Error Message
Confirm whether the error message is generated by PTV Route Optimiser.
- If the message comes from another system (ERP, middleware, TMS, etc.), the issue must be investigated with internal IT or the system owner first.
- Resolving upstream system issues may restore normal export behaviour.
Check Required System Services
Multiple system services contribute to the export process. Ensure that all required services are running, including:
- Telematics services
- Notification services
- xServer services
- Background services for import/export
If possible, inspect the log files of these services for warnings or errors.
Review Application Logs
If the issue continues, review the PTV Route Optimiser application log for:
- Error entries
- Warning messages
- Unusual or repeated system messages
These logs often help pinpoint the root cause, such as connection failures, permission issues, or upstream system interruptions.