I’m having some problems running 3.01 Application Server. Basically, when it hits an Error in the code, it stops. Well, the actual service is still running, but it stops processing as it should, even though I have it in a loop (using the ntimer) which should have it processing forever. I’m under the understand that if Navision hits an error message, it should somehow keep going? I’m not quite sure how, but somehow keep going (either restarts from the top of codeunit 99 - not quite sure). But this doesnt. (I’m talking about an ordinary ERROR message, not a Dialog error. The way I’m using it is this: - I have function 99 in codeunit 1 firing up a single instance codeunit. - This single instance codeunit has the ntimer automation in it (set with events), which I am using run some processing periodically. This works fine so long as I hit no errors (It will run over and over and over). Any clues? Thanks.
I’ve been doing some further playing around with this, so I have some more information: The errors which are causing the Application Server to stop are somewhere within the CountDown trigger of my codeunit I’m using for App Server. If I make an error somewhere before this trigger is called, it acts the way I expect it to. (Restarts the application server after 30 seconds). Is this just the way it is? Does the nTimer.CountDown thing just plain old stop the Application Server from restarting? Do I have to do some tricky programming to stop the errors happening there?
I think I might have worked it out (to a degree)… It seems that any error that happens within the nTimer CountDown trigger breaks it from the trigger, and allows it to continue on. In my case, this is to the end of function 99 in codeunit 1. I’ve added an error message to the end of function 99 in codeunit 1. It now stops and restarts when it hits this, but doesnt give any information on why it stopped now…
Another update, I wasnt actually using the Navision Timer, I was using the cTimer automation. I tried using the Navision Timer, and that is working perfectly. So I guess problem solved…
You might consider moving up to version 3.70 on Your executables. There’s been done a lot of improvments in NAS since 3.01