Dotnetpanel Forums

I have noticed that recurring invoices due to be raised will only be raised if someone logs on to the control panel. This shouldn't be necessary, as there may be days when nobody logs in to the CP (for smaller ISPs) in which case invoices won't actually get sent out.

How many clients do you have? Does your DNP is used all the time (does DNP Enterprise app pool is running always)?

Currently only 60 - although I have several hundred in Helm and Hosting Controller logins. I haven't transferred them in yet because DNP cannot correctly handle the other issues I've raised in this forum (see my other postings from the same day).

Hi Malcolm!

According to your description of the issue I might suspect there is something wrong with Enterprise Server component... From this point I can infer the following issue: ES application pool might consume a lot of RAM and thus would be recycled, afterwards when someone logs in into the panel - Web Portal bothers ES instance and it has to start, so does Task Scheduler module.

Let me know if you can see any clues in Windows Event Log supporting my guesses.

Thanks.

Hi Pavel,

Nothing to indicate that, but perhaps the ES Billing component should be installed as a windows service rather than be IIS dependant.

Thanks

Malcolm

Paul:

According to your description of the issue I might suspect there is something wrong with Enterprise Server component

In my opinion there is nothing wring with Enterprise Server module. Having 60 clients which are probably using panel not so often makes possibility that Enterprise Server app pool in IIS is just killed by IIS itself because inactivity. Adjust Enterprise Server recycling time app pool setting and check if this has fixed your problem.

So what you're saying is if you're a smaller host don't use the billing component because it will be unreliable unless (a) you set session timeouts to be days rather than hours or minutes, or (b) you make sure you log in every day.

Alternatively, DNP could rewrite the billing component to not be dependant on IIS at all - as a Windows service, the same as Hosting Controller and previously Helm.

MalcolmW:

So what you're saying is if you're a smaller host don't use the billing component because it will be unreliable unless (a) you set session timeouts to be days rather than hours or minutes, or (b) you make sure you log in every day.

Alternatively, DNP could rewrite the billing component to not be dependant on IIS at all - as a Windows service, the same as Hosting Controller and previously Helm.

That's right. DNP Enterprise Server must be up and runing all the time (actually this is only problem at the beggining of being hosting company). I'm telling how it is now. How it could be / should be thats different case :). For sure this should be considered when writing DNP 3.x with new billing system.

On the other hand what problem for you is running DNP Enterprise application pool all the time?

MalcolmW:

So what you're saying is if you're a smaller host don't use the billing component because it will be unreliable unless (a) you set session timeouts to be days rather than hours or minutes, or (b) you make sure you log in every day.

It affects not only Ecommerce but Scheduled Task module as well. Naturally, all of Ecommerce (billing) routines must be running on a schedule basis, so do they.

Scheduled Tasks is a good technology to rely on but with some limitations though and no doubts, of course, mentioned tweaks with ES app pool recycling settings should be noted in red in the KB.

Paul:

Scheduled Tasks is a good technology to rely on but with some limitations though and no doubts, of course, mentioned tweaks with ES app pool recycling settings should be noted in red in the KB.

I agree, Scheduled Tasks should be Windows Service.

prostoemailee:

I agree, Scheduled Tasks should be Windows Service.

Absolutely. I'll do my best to put the highest priority to this task.