The cp_id: xxx for which you are receiving the mails from cron are not exist into your MB(seems to be deleted) but this cp_id i.e xxx is still remain into your MB database and hence you are receiving emails from cron.

Login to your phpMyAdmin and delete the logs which you want from the suspend_log file.

you will have to edit your database and run the following command on your ModernBill database:

DELETE FROM suspend_log WHERE suspend_id = xyz

§ register_globals = On
§ register_argc_argv = On
§ open_basedir = no value
§ short_open_tag = On
§ safe_mode = Off
§ error_reporting = 2039
§ memory_limit = 32M
Please make sure you have to restart your web server after you modify the php.ini file.

Please make sure you have set the following PHP variable to ON into your PHP.ini file on server.

register_globals = ON   ON

Remember to restart your web server after you modify the php.ini file and try to login to your MB.

Go to System config >> order setting >> Order Groups >> Edit the default order group >> set the Enable One Time Billing Mode (B): Yes in Order Integration Configuration and save the setting and check on order form.

 

Enable One Time Billing Mode: Set to YES to place ALL packages in this Vortech engine in non-recurring/one time billing mode. Enabling this setting will cause Vortech to ignore cycles above. Packages in this Vortech Type should be setup with only ONE price.

Try one of two :-

1) Delete all the .htaccess files from your Modernbill installation directories.

2) It is possible that suexec is activated in your PHP configuration. Deactivate suexec    and restart your webserver.

Login to your merchant account and see following settings are correct.

Navigate to: Helpful Links/Look and Feel > Settings

Direct Return: YES

Approved URL:  https://your_install_url/include/misc/mod_2checkout/2checkout_return.inc.php

Secret Word: your secret word from mod_2checkout

Cron is a program on Linux servers which allows you to schedule jobs to run at specific intervals. This is very useful for automating repetitive tasks.

The /etc/crontab file is defined to automatically execute cron jobs at certain intervals based upon the directories below.

/etc/cron.hourly
/etc/cron.daily
/etc/cron.weekly
/etc/cron.monthly

The purpose of the cron wizard is to allow you to easily configure the following in Modernbill:

1. Invoice Generation
2. Credit Card Batching
3. API Queue Batching
4. Auto-Suspend Timing
5. Auto-Enable Timing

Warning: mysql_fetch_array(): supplied argument is not a valid MySQL result resource in /home/user/public_html/billing/
include/misc/heart/db_functions.inc.php on line 1102

In order to get this issue solved, first you need to delete the current files and then upload db_functions.inc.php file in forced BINARY format and that should fixed your issue.

Cheers

1. Authorize.net
==========

If the authorize.net is set as payment module and if tested in the VT then we get 68 codes which shows that it is working fine and connecting Authorize from MB perfectly.

——————————————————————————————

2. BluePay
=======

If the Bluepay is set as payment module and if tested in the VT then we get 40 codes which shows that it is working fine and connecting Bluepay from MB perfectly.
————————————————————————————–

3. Echo
====

If the Echo Inc is set as payment module and if tested in the VT then we get 9 codes which shows that it is working fine and connecting Echo from MB perfectly.
————————————————————————————————–

4. eWAY
=====

If the eWAY is set as payment module and if tested in the VT then we get 5 codes which shows that it is working fine and connecting eWAY from MB perfectly.
————————————————————————————————–

5. FirePay
======

If the FirePay is set as payment module and if tested in the VT then we get 9 codes which shows that it is working fine and connecting FirePay from MB perfectly.
———————————————————————————————–

6.LinkPoint
=======

If the Linkpoint is set as payment module then turn on the debug mode and test it in VT,

In debug mode if you are looking for the following:
return_dump: r_csp:
r_time:
r_ref:
r_error: SGS-020003: Invalid XML.
r_ordernum:
r_message:
r_code:
r_tdate:
r_score:
r_authresponse:
r_approved:
r_avs:
AUTH CODE:
AVS CODE:
TRANS ID:

This means it’s good to go with the Linpoint Module and the connection is successful from MB.
————————————————————————————————

7. PSIGate
=======

If the PSIGate is set as payment module and if tested in the VT then we get 49 codes which shows that it is working fine and connecting PSIGate from MB perfectly.
————————————————————————————————

8. Cybersource
==========

Your order cannot be processed at this time. Your credit card was not accepted. Please try again later.
(102)

* Code1: reasonCode: 102
* Code2: invalidField_: billTo_email
* Code3: decision: REJECT
* Code4: invalidField_0: billTo_email
* Code5: invalidField_1: item_0_unitPrice
* Code6: requestID: 1388991845120169622803
* Code7: StatusDetail: REJECT -
——————————————————————————

When we create a package in MB for the Plesk server then there is no need to create a package in Plesk. We use the package attirubtbes in Modernbill and pass those via API.  If you want to match the attibutes then no you either have to do it in the way described above or have to do it in your own way w/o using Modernbill.
There is no need to setup a package in Modernbill and a package in plesk, you can setup a package in Modernbill and that is the only place that there needs to be a package. There does not need to be the same package setup as a template in Plesk.