Invoicing for recurring payments

[maiainternet]

Hi all,

 

Here's the thing:

 

Since upgrading last year all my monthly recurring customers haven't had a new invoice. All their payments since then have been added to the last invoice since the update.

 

I'm thinking it was an upgrade from v5 to v6 (august '15?)

 

I'm getting the payments fine and they've been added to the old invoice as a credit. No major issue as the money is coming in, but when a customer asks for 12 (a year's) invoices there's just one with only 1 month's time frame on it. Not good for their accountants!

 

I'm currently using v6.3.1 on Centos 5 and directadmin 1.50.1

 

any suggestions welcomed - I've fiddled with the settings through out and nothing seems to fix it.

 

Cheers

 

Dave

[brian!]

Dave,

 

is the cron running? anything in the activity log to indicate where the issue might be ??

[maiainternet]

Hi Brian,

 

as far as i can tell the cron is running and there doesn't seem to be any errors. Although there is no mention of the cron running or not running.

 

However, /var/log/cron has the entry:

 

Oct 30 09:00:01 mia crond[5217]: (maia) CMD (php -q /home/maia/domains/maia-internet.com/public_html/invoicing/crons/cron.php)

 

I've just looked in the cron.php file and I found some added code from a corrupt wordpress install a few months ago. I've cleaned it up and will run cron.php manually in a minute.

 

Thanks for the pointer and making me check again - I'll report back with the results.

 

Cheers,

 

Dave

[WHMCS ChrisD]

Hi Dave,

 

 

Invoice generation, payment reminders and account suspension/termination are some of the tasks handled by the daily cron job in accordance with your Automation Settings. Begin by reviewing Utilities > Logs > Activity Log and ensure you see a number of entries beginning "Cron Job" each day. The final entry every day should be "Cron Job: Completed".

 

 

* If you see no Cron Job entries at-all this means you have not configured your automation cron correctly, you must do this per our installation instructions. The relevant documentation can be found at http://docs.whmcs.com/Crons

 

 

* If you see some Cron Job entries but none after "Cron Job: Running Usage Stats Update" your cron is getting stuck at the Usage Stats Update stage. The most likely cause of this error is that you have an old server in Setup > Servers that is no longer available.

To resolve this, you should update or remove any inactive or offline servers from Setup > Servers so that they can all be connected to successfully. Or alternatively Update Usage Statistics can be disabled under Setup > Automation Settings.

 

 

* Finally, if you see some Cron Job entries but no "Cron Job: Completed" entry this suggests the cron is being terminated prematurely by your server. Please increase the memory_limit setting in your server's php.ini to 64M or 128MB which should easily be sufficient. Then see if things improve and you start getting the cron job report again over the next few days.

 

 

If the cron still doesn't complete with the increased memory limit please ensure display_errors is enabled in the server's PHP configuration and enable the Setup > General Settings > Other tab > Display Errors option, then run the cron manually by visiting the cron.php file in your browser. You should now see an error output to the screen. We have collected some of the most most common errors and their causes, refer to the appropriate page in the following sections:

 

 

*http://docs.whmcs.com/Server_Modules

*http://docs.whmcs.com/Domain_Registrars

*http://docs.whmcs.com/Common_Troubleshooting_Tips#Server_Errors

[maiainternet]

Thanks for the tips, looks like I may have fixed the cron running.

 

I tried to run it manually and it gave me an error I hadn't seen before:

 

Unable to communicate with the WHMCS installation.

Please verify the path configured within the crons directory config.php file.

For more information, please see http://docs.whmcs.com/Custom_Crons_Directory

 

On checking config.php the path to the root directory was relative '../'

 

Changing it to absolute seems to have fixed it - at least the cron job ran fully!

 

Weird, but let's see if that does the job - I might even upgrade to 7.0 now that I've updated my PHP to 5.6

 

thanks again all,

 

Dave

[WHMCS ChrisD]

Glad to hear it's sorted Dave!

Please feel free to reach out if you have any other questions.

[marc198710]

payolee offers recurring billing software