This would be caused by a bug in adTempus, but it would be difficult to track down unless the problem returns in a way that demonstrates a pattern. If it occurs again, restarting the adTempus service should get adTempus running normally again; there is no need to restart the entire server.

I suggest you update to version 2.1, which is a free update from your version. It's possible that the underlying issue has been addressed there. If not, we are no longer making fixes for adTempus 2.x, so if the issue returns you would need to upgrade to version 3 or to the upcoming version 4.

Hi Bill,

thank you, we will consider upgrading the version at least to 2.1. We see there is a major upgrade for ver 3, but for ver2.1, can we just download and install it on current 2.0.4? Is there any preparation needed or roll-back function just in case something happened?

The other incident (at my other post) "connection between the server and console has broken" happened about 2 days before this Pure Virtual Function Call incident. In between this two incidents, we upgraded our server RAM  from 2Gb to 4Gb.

Other symptoms that we can see, in windows taskmgr, the page faults for adtempussvr.exe is very high. It can reach 3.8Gb when the pure virtual function call incident happened, which made us to restart the whole server.

Thanks,

Chandra Chen Weici

Hi,

The other thing that cross my mind is whether adtempus has different (so called enterprise edition) version to handle many jobs? Our current adtempus is handling around 120 jobs, is it too many for adtempus?

Thank you,

Chandra Chen Weici

You can just install version 2.1 over your current version. It is not a complicated update, but you can make a backup of your database if you want to be safe.

Page faults are not measured in GB. Are you looking at page faults or at memory usage? If you mean memory usage, then there is definitely a problem if adTempus is using that much memory. If it's page faults, then that number is only meaningful in comparison to how long adTempus has been running, and probably does not indicate a problem.

If you are still using the original Microsoft Access database for adTempus, you need to convert to SQL Server express, as discussed here.

adTempus can handle 120 jobs fine, though there have been many improvements and fixes since the version you are using.

Hi Bill,

thank you. We are now preparing the upgrade in our test environment.

For memory, the ADtempusSrv.exe still in the stable size. It uses around 40,000K in taskmgr. The thing that eats up memory is the sqlservr.exe. It takes in average 1,500,000K.

There is a repeated message in SQL logs ""This SQL Server has been optimized for 8 concurrent queries. This limit hasbeen exceeded by x queries and performance may be adversely affected." This message occurs even before our last week adtempus issue (lost connection issue).

We are using personal edition SQL which has above limitation. We will look into this after the upgrade to 2.1. But do you or any one have any comment before?