Article ID: 8410, created on Apr 8, 2010, last review on Jun 23, 2016

  • Applies to:
  • Odin Business Automation Standard 4.5


The periodic task "Recurring payment process along with Invoice and Statements creation procedure" fails and problem reports are being generated in the folder '/var/log/hpsc' during the task executing.

The task performs customer billing process, it creates and provisions renewal order, so the task is of very importance.

The article describes ways how to investigate problems with the task execution.


The general way of failed task troubleshooting is to open the problem report generated and try to find the reason of problem. You can search by words ERR, FATAL, WARN (in upper case) and Error.

E.g. in the examples below we can see practically all of these words, in all cases they mean that a real error occurred:

[2010/02/15 04:52:58] [FATAL] [15709] [Error::throw] Subscription has been deleted already at /usr/lib/perl5/site_perl/5.8.8/HSPC/MT/Billing/ line 1388.

Error-TEXT: 53:41] [FATAL] [11753] [Error::throw] [SiteBuilder] site_order_id invalid!

[2010/02/15 05:01:27] [FATAL] [20059] [Error::throw] Can't load plesk client cache for subscription id=256

Error-TEXT: 37:36] [FATAL] [32679] [Error::throw] Could not find Virtuozzo Container object by CTID = 2410

Log::Log4perl::Logger::__ANON\__(Log::Log4perl::Logger=HASH(0xe4bbefc), '[SiteBuilder] Error ERROR: Date::Manip unable to determine TimeZone. at /usr/lib/perl5/site_perl/5.8.8/Date/ line 3635

[2010/03/26 04:24:50] [WARN] [24091] [HSPC::MT::DM::DNSGate::switch_activity] Zone () not found. Nothing to do

Lets us now study some particular problems with the task "Recurring payment process along with Invoice and Statements creation procedure".

1. Error message "Cannot decrypt the payment method. The payment method has been deleted."

The error means what it says -- customer's payment method (credit card) was deleted from OBAS and thus cannot be decrypted. The problem could appear this way: customer had a credit card in his or her account in OBAS, the card was marked as default and was used to pay recurring payments. OBAS generated a renewal order, assigned that default credit card to the order and tried to pay it. At that time the payment could not be processed for some reason. Later the customer deleted the payment method from OBAS, however it is still assigned to the renewal order, so OBAS is trying to process the renewal order using a credit card which was deleted from the system.

Solution: detach the removed credit card from the renewal order which cannot be processed and pay it using another payment method.

To detach a deleted payment method from an order or an invoice go Top > Billing Director > Receivable > Documents, find the needed document, click the button 'Change Payment Method' and choose the option 'Unassign the Credit Card from the document'. After that try to pay an order or an invoice using another payment method of the customer.

2. Error message "Payment not allowed for card #352".

Again, the error message is self-explanatory, it means that the credit card is disabled and cannot be used for payments. Look at the properties of the credit card #352 in PCC under Top > Commerce Director > Online Payments > Credit Cards to check the actual status of the credit card. There is no universal solution in case the credit card is disabled, Provider needs to check such cards manually and decide what to do with them.

Search Words

Recurring payment process along with Invoice and Statements creation procedure

400e18f6ede9f8be5575a475d2d6b0a6 caea8340e2d186a540518d08602aa065 624ca542e40215e6f1d39170d8e7ec75 70a5401e8b9354cd1d64d0346f2c4a3e

Email subscription for changes to this article
Save as PDF