/
Failed Order: Cannot connect to central database

Failed Order: Cannot connect to central database

Owned by Kevin Vogle
Feb 28, 2022
1 min read

To help troubleshoot failed orders in your order queue, please reference the details below. This should help you resolve the issue. If further assistance is required, please reach out to support@aspenware.com.

Full Error

Cannot connect to central database

Cause/Fix

Cause

Fix

Typically caused when RTPConnect cannot contact the RTP db's.

  1. Wait and resubmit the order.

  2. If problem persists, report to Aspenware support.

 

Related content

Failed Order: A connection attempt failed
Failed Order: A connection attempt failed
Aspenware Customer Hub
More like this
Failed Order: The time allotted to this operation may have been a portion of a longer timeout
Failed Order: The time allotted to this operation may have been a portion of a longer timeout
Aspenware Customer Hub
More like this
Failed Order: Execution Timeout Expired
Failed Order: Execution Timeout Expired
Aspenware Customer Hub
More like this
Failed Order: RTP|ONE Order, AW12345, already exists in the system
Failed Order: RTP|ONE Order, AW12345, already exists in the system
Aspenware Customer Hub
More like this
Failed Order: Customer is not defined / Error in RTP order line item; no customer given
Failed Order: Customer is not defined / Error in RTP order line item; no customer given
Aspenware Customer Hub
More like this
Failed Order: Customer could not be found
Failed Order: Customer could not be found
Aspenware Customer Hub
More like this