/
Failed Order: Customer could not be found

Failed Order: Customer could not be found

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

Customer could not be found: Customer IP Code: 12345678

Cause/Fix

Cause

Fix

Typically this error indicates the Aspenware ContactID is associated with a merged customer record in RTP. Aspenware’s merged contact check process usually prevents this error but there are situat5ions where it can still occur.

  1. Locate the merged customer's AlternateIDProfile in RTP and re-name. For example, if RTP has, ‘UNITY-AW-1234’ in the AlternateIDProfile table for a merged customer, update the data to be, ‘UNITY-AW-1234_merged’ so that Aspenware does not find this record associated with an inactive RTP IPCode when processing the order.

  2. Attempt to reprocess the order and email Aspenware support if the error persists.

 

Related content

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
More like this
Failed Order: The IP Code is not active or does not exist
Failed Order: The IP Code is not active or does not exist
More like this
Failed Order: A connection attempt failed
Failed Order: A connection attempt failed
More like this
Failed Order: Object reference not set to an instance of an object - CreateCustomerId
Failed Order: Object reference not set to an instance of an object - CreateCustomerId
More like this
Failed Order: Cannot connect to central database
Failed Order: Cannot connect to central database
More like this
Failed Order: An exception occurred while reading a database value for property GetAxessSerialNumberResult.SerialNumber
Failed Order: An exception occurred while reading a database value for property GetAxessSerialNumberResult.SerialNumber
More like this