I recently changed 24x7 over to being a service. The scheduler executed tasks when the service was run as LocalSystem, however this violated some permissions in trying to open files that were part of a Unix Share (but could be accessed by their UNC).

I changed the account to be one that I knew was of sufficient privileges, but now nothing at all happens as far as I can tell.

What tidbit of information am I missing here?

Did the service start? If you setup the service to start under account A but after restarting the machine you logon as B the service does not start.

The same thing happens if you do not logon at all. Only LocalSystem and services under domain admin accounts get started.

: I recently changed 24x7 over to being a service. The scheduler executed tasks
: when the service was run as LocalSystem, however this violated some
: permissions in trying to open files that were part of a Unix Share (but
: could be accessed by their UNC).

: I changed the account to be one that I knew was of sufficient privileges, but
: now nothing at all happens as far as I can tell.

: What tidbit of information am I missing here?

I'm still stumped. The service does start. It uses account A. The system is also logged in under account A.

Maybe all my jobs interact with the desktop in some wacky way? I really don't think so, but how do you know?

Perhaps you can give me an example of a script that should work under all circumstances, because as far as I can tell, nothing at all happens when I run as a service under user A, even using 1 line test scripts.

: Did the service start? If you setup the service to start under account A but
: after restarting the machine you logon as B the service does not start.

: The same thing happens if you do not logon at all. Only LocalSystem and
: services under domain admin accounts get started.

Check schedule.log file. It should have "24x7 Scheduler [service] starting and then following by something else that should shed some light on the problem.

Now about the desktop, anything that is started from a service is run invisible. Actually it runs on the invisible Desktop created for services. That's why you cannot see your programs on the screen. You should rely on the job log to monitor running jobs. You can also use the Windows Task Manager to monitor currently running processes.

If you set the service to run under LocalSystem account you can tell Windows to allow the service to interact with Desktop so that Windows will set the 24x7 service Desktop to the user Desktop and this way you can see your scheduled programs. To allow service to interact with the Desktop use Control Panel's Services applet, go to 24x7 Scheduler service properties and check the "Allow service to interact with Desktop" checkbox.

If you have at least 2 licenses of 24x7 you can also use 24x7 Remote Control as a graphical console for connecting, managing and monitoring remote 24x7 Scheduler even if the Scheduler is running as a service.

: I'm still stumped. The service does start. It uses account A. The system is
: also logged in under account A.

: Maybe all my jobs interact with the desktop in some wacky way? I really don't
: think so, but how do you know?

: Perhaps you can give me an example of a script that should work under all
: circumstances, because as far as I can tell, nothing at all happens when I
: run as a service under user A, even using 1 line test scripts.

That's odd. Under Status in the Services screen, it says the scheduler is Started! (Log On As is set to DOMAIN\user)

However schedule.log shows none of this. I looked back over schedule.log and saw a few successful entries such as this one:

8/22/2002 11:03:47 0 0 24x7 Scheduler [24x7 service] 24x7 Scheduler starting...

But I bet that's when I was testing the service as LocalSystem. I must still be missing one really obvious piece of information. It's probably some permission thing, but who knows?

By the way, Windows Task Manager shows that both 24x7.exe and 24x7srv.exe are running. Also, I stopped the service, started 24x7 in standalone and tried to manually change the service to DOMAIN\user (under Tools/Options), but it won't stick.

: Check schedule.log file. It should have "24x7 Scheduler [service]
: starting and then following by something else that should shed some light
: on the problem.

Go to Windows Control Panel. In the Services applet specify proper user and password for the 24x7 service and try starting it manually.

: That's odd. Under Status in the Services screen, it says the scheduler is
: Started! (Log On As is set to DOMAIN\user)

: However schedule.log shows none of this. I looked back over schedule.log and
: saw a few successful entries such as this one: 8/22/2002 11:03:47 0 0 24x7
: Scheduler [24x7 service] 24x7 Scheduler starting...

: But I bet that's when I was testing the service as LocalSystem. I must still
: be missing one really obvious piece of information. It's probably some
: permission thing, but who knows?

: By the way, Windows Task Manager shows that both 24x7.exe and 24x7srv.exe are
: running. Also, I stopped the service, started 24x7 in standalone and tried
: to manually change the service to DOMAIN\user (under Tools/Options), but
: it won't stick.

Well it appears our sys admin got it to work. The username apparently needed administrator privileges to work. This isn't really what we had hoped for, but it works for now.

: Go to Windows Control Panel. In the Services applet specify proper user and
: password for the 24x7 service and try starting it manually.