Search the Aria Knowledgebase for
User Documentation, APIs, SDKs, and more!

 

Home > Aria Crescendo API List > Aria Crescendo API Error Messages > create_acct_complete_m

create_acct_complete_m

Table of contents
This article applies to:Aria Crescendo

Overview

The following error messages can be generated by create_acct_complete_m.

Error Code

Error Message

Associated Inputs

Additional Comments

1001

unexpected error

   

1004

authentication error

auth_key

 

1010

missing required parameters

all required inputs

 

1012

invalid or previously used receipt ID

client_receipt_id

This value must be unique for a client and must be alphanumeric. A previously used client_receipt_id can be reused if all those previous calls has failed (with an error_code other than 0/OK), if the client parameter NEVER_ALLOW_USED_RECEIPT_ID = FALSE.

1016

invalid input

 

 

1017

invalid password

acct_row.password

The password does not meet the parameters set by the client.

1023

userid is missing or invalid

acct_row.user_id

You must enter a user_id if the client is not enabledto automatically generate them.

1024

invalid date format

acct_start_date, alt_start_date, retroactive_start_date, override_bill_thru_date, acct contact birth_date, payment_method.birth_date, billing_group.stmt_contact.birth_date

All date inputs must be in yyyy-mm-dd format.

1031

can not pass in an alternate starting date AND alternate billing day

 alt_bill_day, alt_start_date

 

1033

a parameter that represents a true or false value contains invalid input

do_write, invoice_approval_required, consumer_acct_ind, create_session, master_plan_instance.usage_pooling, supp_plan_instance.usage_pooling, contract_plans_details.cascade_action

 

1046

invalid tax exemption level code

acct_row.tax_exemption_level

Note that tax_exemption_level is only used with Aria's internal tax engine.

1049

Billing or plan changes not allowed due to the account status

N/A

This message indicates a processing problem.

1053

invalid notification template group id

billing_group.notify_template_group

 

1058

Too many accounts. Please reduce the number of accounts to be under <limit>.

api level

 

1065

account cannot be created because inputs related to account or plan structure were not specified.

acct_row

The API input is missing acct rows.

1066

Locale name does not exist in the system.

acct_row.locale_name

 

1067

Locale no does not exist in the system.

acct_row.locale_no

 

1068

Combine invoices must be either 1-Long Cycle or 2-Short Cycle or 3-Consider Client Param.

acct_row.combine_invoices

 

1069

Long cycle (Combine invoice) is not available, since plan instance has plan rollover or contract rollover or future plan changes in the middle of the cycle or while generating a pending invoice.

N/A

 

3003

could not create invoice

N/A

 

3008

pending invoice was created, but auto accept failed

N/A

 

3010

skus must have have units greater than zero

nso_order_data.item_units

 

3017

pro-ration period cannot be greater than plan billing interval

N/A

 

3098

Negative Charge Line Items are not allowed.

N/A

 

3100

Future invoice cannot be created as there is an existing contract changes or plan unit instance fulfilment going to happen in the period.

N/A

 

4006

invalid pay method

payment_method.payment_method_type

 

4008

invalid expiration date

payment_method.cc_expiry_mm, cc_expiry_yyyy

 

4009

invalid cc number

payment_method.cc_number

 

4010

invalid bank draft info

payment_method.bank_acct_no, bank_routing_no

1. The client param BANK_DRAFT_INDICATOR must be enabled.
2. bank_acct_no and bank_routing_no are required.
3. valid bank_routing_no from aria's aba lookup in case of US address.
4. bank_routing_no must be numeric.
5. For US, bank_routing_no should be 9 digits in length (left padded with zeros).
6. bank_routing_no should pass checksum validation.

4011

cc authorization failed

Processing, related to payment_method.

$1 auth has failed.

4017

duplicate payment method client defined id.

payment_method.client_payment_method_id

This value must be unique at client level.

4022

invalid cc id

payment_method.cc_id

 

4032

cc_id is required.

payment_method.cc_id

 

5001

duplicate entry

 

This error can occur when the acct_no or userid of the new account is already in use.

5003

invalid notify method

billing_group.notify_method_no

 

5004

invalid responsibility level cd

master_plan_instance.resp_level_cd

Note that resp_level_cd=4 is not supported in Aria Crescendo.

5005

invalid parent account no

acct_row.senior_acct_no

 

5007

invalid currency cd

acct_row.currency_cd

 

5008

invalid userid length

acct_row.user_id

This error is based on client parameters MIN_USERID_LENGTH and MAX_USERID_LENGTH.

5009

userid contains illegal characters

acct_row.user_id

Only alphanumeric chars are allowed.

5010

userid is reserved

acct_row.user_id

You must select another user ID

5011

userid is taken

acct_row.user_id

You must select another user ID

5012

password is too short

acct_row.password

This is based on the client parameter MIN_PASSWD_LENGTH.

5013

password is too long

acct_row.password

This is based on the client parameter MAX_PASSWD_LENGTH.

5014

password contains invalid characters

acct_row.password

 

5016

password not strong

acct_row.password

The password  must be at least eight characters in length and must contain at least one alphabetic and one numeric char.

5017

invalid iso country code

acct contact.country, payment_method.country, payment_method.bank_country_cd, billing_group.stmt_contact.country

 

5019

error recording balance forward

master_plan_instance.balance_forward

This indicates an error in the balance forward transaction creation.

5020

alternate billing day must be between 1 and 31

acct_row.alt_bill_day

 

5021

invalid test acct indicator

acct_row.test_acct_ind

 

5023

number of supp field values does not meet required minimum number of values

acct_row.supp_field.supp_field_value

Number of values given for a given field should meet the min values criteria set at configuration.

5024

number of supp field values exceeds maximum number of allowed values

acct_row.supp_field.supp_field_value

Number of values given for a given field should meet the max values criteria set at configuration.

5026

supp field value already exists

acct_row.supp_field.supp_field_name

This error occurs when the same name is provided more than once with the same value.

5029

invalid item or sku

master_plan_instance.master_plan_nso_list.client_sku, supp_plan_instance.supp_plan_nso_list.client_sku

 

5030

Child account's Currency is not matching with Parent account's Currency

acct_row.currency_cd

 

5031

Child account of this account cannot be set as its parent.

acct_row.senior_acct_no

The given senior_acct_no must not be a child account.

5033

Invalid parent account user id.

acct_row.senior_acct_user_id

 

5034

Invalid parent client account id.

acct_row.senior_client_acct_id

 

5036

Client Account ID is already assigned to other account

acct_row.client_acct_id

This validation happens only when the client parameter CHECK_CLIENT_ACCT_ID_ALREADY_TAKEN is enabled for the client.

5039

Invalid RevRec profile ID.

acct_row.revrec_profile_id

 

5040

Invalid RevRec client-defined ID.

acct_row.revrec_client_defined_id

 

5041

Invalid invoicing option provided

acct_row.invoicing_option

 

5048

Missing senior account number/identifier

acct_row.senior_acct_no and master_plan_instance.resp_level_cd

Senior account number is mandatory when master_plan_instance.resp_level_cd <> 1

5051

the responsible master plan instance number/identifier is not associated with the senior account number

master_plan_instance.resp_master_plan_inst_no

The resp mpi_no must be from the senior/parent account.

5052

Invalid product field

master_plan_instance.plan_instance_fields_info.field_name, supp_plan_instance.plan_instance_fields_info.field_name

The field is not mapped to the plan.

5054

The Account Contact name, Billing Contact name, and Statement Contact name must be the same for consumer accounts.

 

The first name, middle initial and last name of account contact, billing contact and statement contact must be the same when consumer_acct_ind = 1.

5059

Invalid Product Field Value.

master_plan_instance.plan_instance_fields_info.field_value, supp_plan_instance.plan_instance_fields_info.field_value

Value must be from the configured allowed values.

5061

Number of Product Field value exceeds maximum number of allowed values.

master_plan_instance.plan_instance_fields_info.field_value, supp_plan_instance.plan_instance_fields_info.field_value

Value must meet the configured min values.

5062

Number of Product Field values does not meet required minimum number of values.

master_plan_instance.plan_instance_fields_info.field_value, supp_plan_instance.plan_instance_fields_info.field_value

Value must meet the configured max values.

5070

Invalid Legal Entity no

acct_row.legal_entity_no

 

5071

Invalid Client Legal Entity ID

acct_row.client_legal_entity_id

 

5072

Either legal_entity_no or client_legal_entity_id is required

acct_row.legal_entity_no, acct_row.client_legal_entity_id

When the LEGAL_ENTITY_MASTER client parameter is enabled and client has a legal entity defined, then this is mandatory.

6003

could not validate billing information

backend, related to payment_method.*

There is an error during $1 auth attempt.

6004

validation not supported for this payment method

backend, related to payment_method.*

 

6005

invalid supplemental field

acct_row.supp_field.supp_field_name

Unknown field name.

6007

CVV Declined

backend, related to payment_method.*

$1 authorization has failed due to CVV.

6008

Address verification declined

backend, related to payment_method.*

$1 authorization has failed due to billing address.

6009

CVV timeout - retry

backend, related to payment_method.*

$1 auth has failed due to cvv check timeout.

6010

Address verification timeout - retry

backend, related to payment_method.*

$1 authorization has failed due to billing address check timeout.

6021

Invalid state_prov entered

acct contact.state_prov, payment_method.state_prov, payment_method.bank_country_cd, billing_group.stmt_contact.state_prov

 

6022

invalid supp field value

acct_row.supp_field.supp_field_value

Value is empty or not from the configured allowed values.

6027

IBAN is alphanumeric and is 16 to 34 characters in length

payment_method.iban

 

6029

Bank swift code is alphanumeric and is 8 or 11 characters in length

payment_method.bank_swift_cd

 

6031

BBAN is numeric and up to 16 digits

payment_method.bank_acct_no

 

6033

Bank branch code is numeric and up to 10 digits

payment_method.bank_branch_cd

 

6034

Basic bank account number or IBAN is required for Direct Debit

payment_method.iban and bank_acct_no

 

6045

Account can have only one active NETS payment method.

payment_method.payment_method_type

 

7027

master plan instance cannot be created without billing group

master_plan_instance.billing_group_idx/cdid

billing_group is mandatory when master_plan_instance.resp_level_cd = 1.

7028

duplicate billing group client defined id.

billing_group.client_billing_group_id

This value must be unique at the client level.

7029

duplicate dunning group client defined id.

dunning_group.client_dunning_group_id

This value must be unique at the client level.

7030

master plan instance cannot be created without dunning group

master_plan_instance.dunning_group_idx/cdid

dunning_group is mandatory when master_plan_instance.resp_level_cd = 1

7031

Invalid Dunning Process

dunning_group.dunning_process_no

 

7032

Single order billing not allowed because plan instance status prevents it

master_plans_detail_row.plan_instance_status

This error occurs in the following situations:

  1. When the plan instance status code allows billability and the invoice option is "NONE".
  2. If the plan instance status does not allow billability.

7033

Invalid client defined dunning process id

dunning_group_row.client_dunning_group_id

 

12001

Account group does not exist

client_seq_func_group_id

This error occurs if an invalid seq_function group_id is entered.

12005

Account belongs to collections based group using same payment method

collection_acct_group_row.collections_acct_group_no

This error occurs if two collection groups that have processors that share a pay method

12010

Client account group does not exist

collection_acct_group_row.collections_acct_group_no

 

14001

invalid master plan no

master_plans_detail_row.plan_no

 

14002

invalid supplemental plan no

supp_plan.plan_no

 

14005

invalid plan service combination

master_plans_detail_row.plan_no And MASTER_PLAN_SERVICES.SERVICE_NO

This error check the given plan number and service number combination for master and supplemental plans.

14006

invalid rate schedule no

acct_rate_schedule_no, mpi_rate_schedule_no
master_plans_detail.alt_rate_schedule_no
supp_plan.alt_rate_schedule_no

 

14012

Alternate rate schedule's currency does not match the account's currency.

alt_rate_schedule_no

The alt_rate_schedule currency does not match the  account currency

14013

New plan does not have a rate schedule with a currency matching the account's currency.

master_plans_detail.alt_rate_schedule_no
supp_plan.alt_rate_schedule_no along with acct_currency

if the given rate schedule doesn’t match with currency

14014

invalid rate tier structure

custom_rates.custom_rate_to_unit,
custom_rates.custom_rate_seq_no

While entering custom rates, the rate schedule must have the same number of units in each tier, and the same number of tiers, as the schedule on which it is based.

14015

custom from and to units not supported for given service_no

custom_rates.custom_rate_from_unit
custom_rates.custom_rate_to_unit

For the custom rate sequence, if you enter a "from" unit in one tier that is not immediately after the end unit in the previous tier, this error occurs.

14019

invalid usage accumulation reset months value

usage_accumulation_reset_months

If the accumulation months is not given between 0 to 99, then we will raise the error

14022

supplemental plan violates plan exclusion group

supp_plan.plan_no

The passed supplemental plan is not matched with the master plan exclusion group

14027

The end units of final rate tier is not infinity

custom_rates.custom_rate_to_unit

The custom rates final unit must be infinity

14033

Invalid Promo Code

promo_cd

 

14035

Invalid client plan id

client_plan_id

 

14036

Invalid client service id

client_service_id

 

14038

Invalid client master plan id

client_resp_master_plan_inst_id

 

14039

Invalid client rate schedule id

client_alt_rate_schedule_id

 

14040

No Universal Place Holder rate schedule for this currency

acct_rate_schedule_no, mpi_rate_schedule_no
master_plans_detail.alt_rate_schedule_no
supp_plan.alt_rate_schedule_no

 

14043

Invalid plan instance rate_seq combination

custom_rates.custom_rate_from_unit
custom_rates.custom_rate_to_unit

If the from/to units are not specified, the given rate_seq_no mut be a valid rate_seq_no.

14051

Invalid plan status for the new plan

plan_instance_status

 

14055

Missing senior master plan instance number/identifier

resp_master_plan_inst_no and client_resp_master_plan_inst_id

if resp_level_cd is not 1 and you did not enter the responsible plan instance number or ID, then this error occurs.

14059

The senior master plan instance cannot be responsible for another plan instance because it is set to Parent Pay

resp_master_plan_inst_no and client_resp_master_plan_inst_id

If the responsible plan instance itself is a child pay then this error occurs.

14063

duplicate plan instance client defined id.

client_plan_instance_id

 

14071

Master Plan Instance information is missing

plan_no or client_plan_id

If these two fields are not entered, this error occurs.

14073

Invalid responsibility master plan instance index

master_plan_instance.resp_master_plan_inst_idx

The idx must be present in the master_plans array input.

14077

Account status not support plan provisioning.

acct_row.status_cd

The current status of the account does not allow provisioning.

14078

Master plan instance status not support plan provisioning.

master_plan_instance.status_cd

The current status of the master plan does not allow provisioning.

14079

Supp plan instance status not support plan provisioning.

supp_plan.status_cd

 

14084

Invalid rate schedule. Please verify start date and end date of provided rate schedule.

supp/master_plan_instance.alt_rate_schedule_no

 

14085

Mandatory child plans are not included in the input. Please correct this and try again.

backend

 

14086

Plan Units cannot be below the minimum required units for this child plan.

backend

 

14087

The maximum number of allowable units has been exceeded.

backend

 

14107

Invalid Service Number.

   

15001

invalid coupon code

acct_row.coupon_codes, master_plan_instance.coupon_codes

 

15002

coupon expired

acct_row.coupon_codes, master_plan_instance.coupon_codes

 

15006

Duplicate surcharge number in input

acct_row.acct_surcharges, master_plan_instance.mpi_surcharges

 

15008

Invalid surcharge rate schedule no

acct_row.acct_surcharges.rate_schedule_no, master_plan_instance.rate_schedule_no

 

15009

Invalid surcharge number

acct_row.acct_surcharges.surcharge_no, master_plan_instance.mpi_surcharges.surcharge_no

 

15011

The coupon code provided for this account or master plan does not match its specified Coupon Applicability Scope, which determines whether the coupon is available at the account level, the master plan instance level, or both.

acct_row.coupon_codes, master_plan_instance.coupon_codes

This error occurs based on coupon's configuration (account-only, MPI-only).

15012

Coupon code has already been applied and cannot be used again.

acct_row.coupon_codes, master_plan_instance.coupon_codes

 

15013

The surcharge provided for this Account or Master Plan does not match its specified Surcharge Applicability Scope, which determines whether the surcharge is available at the account level, master plan instance level or both.

acct_row.acct_surcharges, master_plan_instance.mpi_surcharges

This error occurs based on surcharge's configuration (account-only, MPI-only).

15014

Duplicate Surcharges found.

   

15015

Surcharge can't be assigned because its application scope is payment method

acct_row.acct_surcharges, master_plan_instance.mpi_surcharges

 

16011

This account is ineligible for new contract creation because it has a universal contract in effect.

backend

 

16013

Unsupported contract type

acct_row.contracts.contract_type_no

 

16018

Universal contract cannot be created because all plan statuses on this account are Suspended, Pending Cancellation, Cancelled or Terminated.

backend

 

16019

Multi plan instance contract cannot be created because the given plan instance statuses on this account are Suspended, Pending Cancellation, Cancelled or Terminated.

acct_row.contracts.contract_plans.plan_instance_idx/cdid

 

16029

The contract start date must be on or after the effective date of the account (account creation date, account start date or retroactive start date) covered by the contract.

acct_row.contracts.contract_start_date

 

16030

The contract start date must be on or after the earliest effective date (plan assignment date or retroactive start date) of the plans covered by the contract.

acct_row.contracts.contract_start_date

 

18005

Invalid Template number

alt_msg_template_no, cn_alt_msg_template_no

 

18006

Invalid client template id

client_cn_alt_msg_template_id, client_alt_msg_template_id

 

18010

Invalid Credit Memo Template number

credit_memo_template

The credit memo template must be mapped to "CM" template class

18011

Invalid Rebill Template number

rebill_template

The rebill template mujst be mapped to "RB" template class

20026

agreement id OR credit card info is required

pay_method_type, bill_agreement_id, cc_num

If the pay_method_type is "13" and bill_agreement_id is null and cc_num is null then this error occurs.

20031

agreement id is mandatory for this payment method

pay_method_type, bill_agreement_id

If the pay_method_type is "29" and bill_agreement_id is null then this error occurs.

23013

Invalid usage threshold applicability

usage_threshold_applicability

if the usage_threshold_applicability is not in, "ut" or "up", then this error occurs.

25001

failed to calculate taxes

   

25003

Provided inventory item is not bundled with the plan definition

client_sku

You have entered an invalid inventory item.

25005

Inventory item units must be equal to or greater than the minimum quantity defined in the Product Catalog

item_units, plan_no, client_plan_id

 

25006

Total inventory item units must equal the number of plan units assigned

item_units, plan_no, client_plan_id

 

25007

Inventory item  units must be equal to or less than the maximum quantity specified in the Product Catalog

item_units, plan_no, client_plan_id

If the NSO type is individual and the item_units is less than the maximum quantity specified in the product catalog then this error occurs.

25010

One or more provided inventory items are Inactive.

client_sku

 

25020

Illegal characters entered

All character field inputs like firstname lastname

 

25023

Primary payment method is required.

pay_method_type, pay_method_name, client_pay_method_cdid,bill_agreement_id

 

25025

Backup pay method cannot be different than primary pay method

   

25026

Primary pay method cannot be different than backup pay method

   

25030

When override_bill_thru_date is specified, alt_bill_day cannot be used.

override_bill_thru_date, alt_bill_day  

25031

When override_bill_thru_date is specified, status_until_alt_start cannot be used (defaults to Inactive).

override_bill_thru_date, status_until_alt_start

If override_bill_thru_date is given, then the status_until_alt_start must be NULL or this error occurs.

25032

The override_bill_thru_date must be in the future, must be after the alt_start_date (if provided), and cannot exceed one recurring billing interval in the future.

override_bill_thru_date, alt_start_date

If override_bill_thru_date is less than alt_start_date then this error occurs.

25033

When override_bill_thru_date is specified, invoicing_option must be configured to be Perform Prorated Invoicing.

acct_data.override_bill_thru_date, invoicing_option

 

25043

Primary payment method does not support secondary pay method.

backend

If the primary_client_payment_method_id is not 1, 2, or 13) and teh backup_client_payment_method_id is not null then this error occurs.

25044

Secondary payment method type must match the primary.

backend

If the backup_client_payment_method_id is not 1, 2, or 13) then this error occurs.

26012

Invalid client-defined billing group ID.

client_billing_group_id

 

26014

Invalid client-defined dunning group ID.

client_dunning_group_id

 

26019

Provided primary payment method idx or primary payment method client defined id is invalid

primary_payment_method_idx, primary_client_payment_method_id

 

26020

Provided secondary payment method idx or secondary payment method client defined id is invalid

backup_client_payment_method_id, backup_payment_method_idx

 

26021

Invalid billing group idx

billing_group_idx

 

26022

Invalid dunning group idx

dunning_group_idx

 

26024

The account status provided is not supported when your client parameter Account_EOM_Enabled is set to True.

status_cd

 

26025

Invalid billing group idx or client-defined billing group id. Each master plan being assigned must be associated with a billing group.

billing_group_idx, client_billing_group_id

 

26026

Invalid dunning group idx or client-defined dunning group id. Each master plan being assigned must be associated with a dunning group.

dunning_group_idx, client_dunning_group_id

 

26028

Duplicate plan instance index in input

plan_instance_idx

If the same plan_instance_idx is submitted twice, then this error occurs.

26031

Client payment terms id not found.

client_payment_term_id

 

26032

Payment terms is not available for the account .

payment_terms_no

The payment_terms_no must be mapped to the acct_group_no

26034

Payment terms not found.

payment_terms_no

 

26035

Invalid Payment option.

payment_option

If the payment_option is not "TERMS" or "METHODS" then this error occurs.

26036

Payment Terms Required.

payment_option, payment_terms_no, client_payment_term_id

If the payment_option is "TERMS" and the payment_terms_no or client_payment_term_id is not entered, then this error occurs.

26037

EAN GLN number and EAN GLN requisition numbers are required for EAN GLN Payment Terms.

payment_terms_no, ean_gln_num, ean_gln_requisition_num

if the payment_terms_no is valid and requires that ean_gln_num and ean_gln_requisition_num values are entered, and these values are not entered, then  this error occurs.

27004

invalid plan unit instance id

client_plan_unit_inst_id

 

27005

The service provided is not a fulfillment based service.

plan_unit_instance_services_row.service_no

The entered service_no must be a  a fulfillment based service.

27007

The fulfillment date should not be provided before account creation date

fulfillment_directive, service_fulfillment_date, acct.created

If the fulfillment_directive is immediate and service_fulfillment_date is before the acct.created date then this error occurs.

27015

Plan Unit Instances is not supported because your client parameter Enable Plan Unit Instances is set to False. Please contact Aria Customer Support with questions about the Enable Plan Unit Instances client parameter.

PLAN_UNIT_INSTANCES_ROW are given

if the PLAN_UNIT_INSTANCES_ROW is not null and the client parameter "ENABLE_PLAN_UNIT_INSTANCES" is false then this error occurs.

27016

Since this account does not have a retroactive start date, the service fulfillment date must be the same as the current date when fulfillment_directive = 1.

fulfillment_directive, service_fulfillment_date

When the fulfillment_directive is immediate (1) and the service_fulfillment_date is not the curent date, then this error occurs.

27017

Eligible service no/service id is required when Eligible fulfillment date/fulfillment directive is specified.

service_fulfillment_date, fulfillment_directive, client_service_id, service_no

If service_fulfillment_date and fulfillment_directive are passed and the client_service_id or service_no is not passed then this error occurs.

27018

Whenever fulfillment_directive = 1 is used, all service fulfillment dates provided for the fulfillment-based services associated with a given plan instance must be the same date.

service_fulfillment_date

The service_fulfillment_date must be the same for all unit instances.

27019

Invalid fulfillment directive as the account start date is in future.

fulfillment_directive (1), alt_start_date

If the fulfillment_directive is immediate (1) and alt_start_date is in the future then this error occurs

27022

Since this account has a retroactive start date, the service fulfillment date must be on or after the account's retroactive start date and on or before the current date when fulfillment_directive = 1.

fulfillment_directive, service_fulfillment_date, retroactive_start_date

If the fulfillment_directive is immediate (1) and service_fulfillment_date falls before the retroactive_start_date, then this error occurs.

29001

The service location provided is not valid.

svc_location_no,
item_svc_location_no

The given service location is not available for the client.

29002

The client service location id provided is not valid.

client_svc_location_id
client_item_svc_location_id

The given service location ID is not available for the client

29003

The service location provided has been disabled or deleted and cannot be associated with a plan instance.

svc_location_no,
item_svc_location_no

The given service location must be active.

29004

Provided contact idx is invalid.

contact_idx, bill_contact_idx, stmt_contact_idx, dest_contact_idx, item_dest_contact_idx

When there is no matching map index available for acct_contact_idx, contact_idx, bill_contact_idx, stmt_contact_idx, dest_contact_idx, item_dest_contact_id, this error occurs.

 

 

You must to post a comment.
Last modified
15:07, 21 Apr 2017

Tags

This page has no custom tags.

Classifications

This page has no classifications.