I am using Navision 3.01. Recently started using the Job Scheduler. The Navision service is stopped everynight for backup. The Job Scheduler appears to be running after the service restarts, but is really not. I would like it to autostart the Job Scheduler everytime the Navision service is restarted.Can I use NAS for this? Or is there another method?
You should be able to do it with a shortcut... .
Probably, you do it with a .bat (or .cmd) file to stop server/backup/start server?
well, extend this with calling a shortcut to NAV to your form. In your form, you could add some code in the trigger "OnHyperlink" or "OnOpenForm" to start immediately.
Hope this helps.
You are correct that it is done with a .bat file. I'm not exactly sure how to call the form from the .bat file- I did not write that code. Can you please provide some sample code?
First, you create a shortcut of your form.
In your .bat file, you open dat shortcut. E.g:
"C:\==WORKINGFOLDER\Temp\10000 The Cannon Group PLC waldo - Customer Card.url"
I just tested this on my testdb, and it works fine.
This would work great except for the known bug in 3.01 that does not allow access to the Job Scheduler log. I work for an end user and our license does not allow us to change the code for the Job Scheduler form.
Any other ideas?
Yes 3.01 is a very unstable version of the product. Do you have the ability to upgrade to a new version of the executables. Even going to 3.10 will make a huge difference.
You make me laugh! I have been pushing for an upgrade for 4 1/2 years to no avail. Do you have anything that might help me?
marybricco: You make me laugh! I have been pushing for an upgrade for 4 1/2 years to no avail. Do you have anything that might help me?
Where do you want help?
It is becoming quite difficult to help you because you can't do anything in the database... .
Well if you have a maintenance contract, then you can just upgrade the executables to at least 4.00sp3. Even without support, if memory serves me correctly, your license should work with 3.10 executables.
True, but keep in mind that the license has to be updated. This only takes 5 minutes and is free of charge (if you pay maintenance) ... but often forgotten.
waldo:True, but keep in mind that the license has to be updated. This only takes 5 minutes and is free of charge (if you pay maintenance) ... but often forgotten.
Thats what I was saying, if memory serves me correctly there was no EXE license change form 3.01 to 3.10, only granule differences, but I am not 100% sure. If you remember back, when 3.00 came out, they had the granule 3.xx License, and until they changed things in 3.60 I think that the licenses worked with all 3.xx versions.
I can make changes in the database; just not to the Job Scheduler form because of the known bug.
They don't pay maintenance and upgrading is not an option. I have tried going down that path and ended up stuck in the mud.The challenge is to find the work around to starting the Job Scheduler when the service is restarted.
Can't you ask your solution center to do this?
marybricco:I can make changes in the database; just not to the Job Scheduler form because of the known bug. They don't pay maintenance and upgrading is not an option. I have tried going down that path and ended up stuck in the mud.The challenge is to find the work around to starting the Job Scheduler when the service is restarted.
So what is the "known Bug"?