Hi Guys!
I have a problem on WIN2003 server. After I configured all file replication/
synchronization jobs using 24*7 scheduler and switched it to Run as NT Service
mode using sufficient checkbox after reboot of the system it's seems that nothing
happens. I mean that system shows that service is running in the "Services" and
It's seems that no one of the jobs ran since "Run as NT service" is configured.
After I reset check box - service has been restarted and jobs started to run. But
actually I need to use 24*7 as a Service without logged in user. Probably I'm
doing something wrong. Can you help me with it?

thnx.

1. Check it is not running as LocalSystem. You need n account with suffcient network privileges. If you use domain admin account the service can then start with the computer before anybody logon to the system.
2. If you are doing Local Sync (share to share or similar) ensure you use only UNC file names. Drive mapping is not available to services.

: Hi Guys!
: I have a problem on WIN2003 server. After I configured all file replication/
: synchronization jobs using 24*7 scheduler and switched it to Run as NT
: Service
: mode using sufficient checkbox after reboot of the system it's seems that
: nothing
: happens. I mean that system shows that service is running in the
: "Services" and
: It's seems that no one of the jobs ran since "Run as NT service" is
: configured.
: After I reset check box - service has been restarted and jobs started to run.
: But
: actually I need to use 24*7 as a Service without logged in user. Probably I'm
: doing something wrong. Can you help me with it?

: thnx.

: 1. Check it is not running as LocalSystem. You need n account with suffcient
: network privileges. If you use domain admin account the service can then
: start with the computer before anybody logon to the system.
: 2. If you are doing Local Sync (share to share or similar) ensure you use
: only UNC file names. Drive mapping is not available to services.

Hi Again,
I checked 1. and 2. and actually everything is configured correctly - 1. My account
is a member of DomainAdmin group and has sufficient network permission. But
in the matter of fact, it's seems that problem is not related to permission -
jobs just couldn't start and there are no information in the job's log about it.
As I said in the "Services" system shows that 24*7 is running and account is correct.
Can you help me with it?
Thnx

: Hi Again,
: I checked 1. and 2. and actually everything is configured correctly - 1. My
: account
: is a member of DomainAdmin group and has sufficient network permission. But
: in the matter of fact, it's seems that problem is not related to permission -
: jobs just couldn't start and there are no information in the job's log about
: it.
: As I said in the "Services" system shows that 24*7 is running and
: account is correct.
: Can you help me with it?
: Thnx

I periodically having this problem as well. It seems like the service gets stuck executing scripts which execute just fine manually (and not via the "run now" function in 24x7). Even bouncing the server seemed to do nothing to resolve until I stopped the service started a new instance and then left the box locked as admin.

Well, bouncing the entire server is the same as stopping every service, restarting the machine and then having the service start automatically when nobody is logged on to the machine and no interactive network connection is available. Right? Only scripts and programs that are specifically designed for such environment can run.
When the service is restarted manually, at that time you are logged to the machine and you have a different network connection that can be used by any script or program and so they start running ok. Do you agree with that position?

: I periodically having this problem as well. It seems like the service gets
: stuck executing scripts which execute just fine manually (and not via the
: "run now" function in 24x7). Even bouncing the server seemed to
: do nothing to resolve until I stopped the service started a new instance
: and then left the box locked as admin.