Job Scheduler on Server

Remco · 2008-01-22

Hi,

I developed an interface using the Job Scheduler. I have a Navision client running on the Server. In this client the Job Scheduler is running. However this customer is rebooting this server every night. There for the Navision client gets down.
Does anybody has an idea how to solve this problem. Is is for instance possible to start the Navision client with the Job scheduler again with a script. Any other solutions are also welcome.

kriki · 2008-01-22

Why does the customer reboot the server every night?

BTW : did you ever think about the NAS?

Remco · 2008-01-23

They reboot their server because for better performance says their external system engineer.

We have a couple of options:
- Not reboot the server every night
- Using the NAS

About the NAS: It is a small customer and perhaps the NAS-solution is to heavy. Besides that we proposed the solution of the Job Scheduler to the customer. It is not very professional to come up with another solution now. We also have to sell the NAS to the customer again.

There for my questions if there are some other solutions.

DenSter · 2008-01-23

Every license comes with one instance of NAS. If they don't already use NAS for something (email logging, OL integration) then they should be able to use that one.

Rebooting the server every day does not increase performance, unless you have programs running that are known to not release system resources.

If your job scheduler is a form, then you could put a NAV shortcut into the Startup folder, and it should automatically open NAV. It will have to be Windows Authentication

Remco · 2008-01-23

Hi,

The customer has a 3.60 client. In their license there is no NAS.
Do you know if the license for a 3.60 client should also have a NAS in it.

ara3n · 2008-01-24

Nas was released in 2.6 and every client gets a 1 free NAS user.

bbrown · 2008-01-24

Sounds like they need to find a new "external system engineer"

There is no valid reason to be rebooting a database server on a regular basis. If there is a problem, fix it. Don't settle for band-aid solutions like rebooting a server.

If there is a bad behaving app, get them to move it to another server.

kriki · 2008-01-24

DenSter wrote:

Rebooting the server every day does not increase performance, unless you have programs running that are known to not release system resources.

It can also decrease performance, because the DBcache is cold after each restart.

fl · 2008-01-30

Yes, it's possible to do that. (I did this a few times on request of client)

Steps:
Make sure that server logon automatically after reboot (look on internet, is possible by a few changes in register).

Define Navision client as an application to start-up automatically after reboot. Use a navision client WITH windows login security for this reason, so that everything can be fixed in the startup-properties.

Change codeunit 1, so that in companyopen trigger, you check to see if the user that is login in matches the one of the application server, if yes start form of job scheduler. (in version < 4.00, this was a standard possibility with the startup form from the user-setup table).

Change form6094, so that field "Scheduler is Running" does NOT initially stop your scheduler.

After all these changes a reboot of the server, will cause auo-login, auto-start navision client, auto-start scheduler. \:D/

Job Scheduler on Server

Comments

Categories