I'm migrating our 24X7 Scheduler over to Windows

Server 2003 and am having problems running our

scheduled jobs that use mapped drives. If I run the

jobs, either a direct .exe or a 24X7 script, via the

24X7 GUI they run fine. If I shut down the GUI and

start the 24X7 service the jobs complain about not

finding the local drive. All other jobs run OK except

ones that depend on mappings. The 24X7 service runs under

a domain based admin account that is part of the server

Local Admin group. I saw your thread on using explicit

UNC references for this but that still doesn't work.

Any suggestions here on what I may be missing?

BTW - the Windows native Scheduler can run these jobs

without a problem using the same account that our

24X7 Scheduler runs under.

Services cannot use mapped network shares. they can only access them directly if the service account has sufficient permissions. You should refer to networked files and folders using their UNC names, like \\share_name\path\file

:I'm migrating our 24X7 Scheduler over to Windows

: Server 2003 and am having problems running our

: scheduled jobs that use mapped drives. If I run the

: jobs, either a direct .exe or a 24X7 script, via the

: 24X7 GUI they run fine. If I shut down the GUI and

: start the 24X7 service the jobs complain about not

: finding the local drive. All other jobs run OK except

: ones that depend on mappings. The 24X7 service runs under

: a domain based admin account that is part of the server

: Local Admin group. I saw your thread on using explicit

: UNC references for this but that still doesn't work.

: Any suggestions here on what I may be missing?

: BTW - the Windows native Scheduler can run these jobs

: without a problem using the same account that our

: 24X7 Scheduler runs under.

: Services cannot use mapped network shares. they can only access them directly

: if the service account has sufficient permissions. You should refer to

: networked files and folders using their UNC names, like

: \\share_name\path\file

Thanks for the timely response. Like I said in my

original email I've already tried UNC names and it

still doesn't work. As far as permissions go the 24X7

service account that is being used has 'full

control' rights to the \\share\path on the remote

computer. Is there a local machine policy on the

remote server that has to be set here? If possible

please be specific when referring to "sufficient permissions"

for the 24X7 service account.

This is frustrating because all these 24X7 jobs

ran beautifully under MS Server 2000 and now they don't

under Server 2003. Thanks.

Rick Close

State of Calif

Franchise Tax Board

Let me restate the case. You have jobs that run fine on Windows 2000 server. Same jobs when ported to 2003 server run also fine when the scheduler is in GUI mode. When the scheduler is run in service mode they fail to run because they cannot access some network files. All files are accessed by their UNC names. Did I get this correctly?

If this is the case, then obviously service permissions are the root cause of the issue. Please check Security Event log on the computer hosting the network share if it registers failed attempts to access the files. If yes theis would indicate insufficient permissions. If no then it would indicate that referenced shares are not visible to the service. In the latest case please ty making and scheduling a simple DOS batch file that read / write something very simple from / to the share

NET VIEW \\computer_name /YES > C:\test.txt

Dir C:\*.* > \\computer_name\share\test.txt

Please let us know what you get

: Thanks for the timely response. Like I said in my

: original email I've already tried UNC names and it

: still doesn't work. As far as permissions go the 24X7

: service account that is being used has 'full

: control' rights to the \\share\path on the remote

: computer. Is there a local machine policy on the

: remote server that has to be set here? If possible

: please be specific when referring to "sufficient permissions"

: for the 24X7 service account.

: This is frustrating because all these 24X7 jobs

: ran beautifully under MS Server 2000 and now they don't

: under Server 2003. Thanks.

: Rick Close

: State of Calif

: Franchise Tax Board

: Let me restate the case. You have jobs that run fine on Windows 2000 server.

: Same jobs when ported to 2003 server run also fine when the scheduler is

: in GUI mode. When the scheduler is run in service mode they fail to run

: because they cannot access some network files. All files are accessed by

: their UNC names. Did I get this correctly?

: If this is the case, then obviously service permissions are the root cause of

: the issue. Please check Security Event log on the computer hosting the

: network share if it registers failed attempts to access the files. If yes

: theis would indicate insufficient permissions. If no then it would

: indicate that referenced shares are not visible to the service. In the

: latest case please ty making and scheduling a simple DOS batch file that

: read / write something very simple from / to the share

: NET VIEW \\computer_name /YES > C:\test.txt

: Dir C:\*.* > \\computer_name\share\test.txt

: Please let us know what you get

STT Support,

Sorry for the tardy response, just getting back to this now.

Yes you are correct in your interpretation of the problem.

I tested the service just as you suggested and it worked fine

when run as a scheduled job under the 24X7 service. I then

added a third line to the same batch job that simulates what I'm

really attempting to do (run an .exe that resides on a

remote share): \\computer_name\share\test.exe .

When executed under the 24X7 service the first two lines

worked as expected but the .exe did not fire. Again when

running this same scheduled batch job with the 24X7 GUI open

the .exe fires off just fine.

Obviously there is some type of restriction here when

attempting to run a remote .exe under the 24X7 Scheduler

service under Windows Server 2003. Where do I go from here

or do I have to resort to running all these jobs under

the native MS Windows Scheduler? One option is to install all

the necessary run time files on each server that has the

24X7 Scheduler installed but that is not the preferred

solution. Any recommendations here?

Hi,

My guess is that the service is running under a different account with different permissions.

A Google search turned the following tip

Open your Add or Remove Programs from Control Panel.

Click on Add/Remove Windows Components.

Scroll down until you see the

"Internet Explorer Enhanced Security Configuration" checkbox.

By default it is checked on any Win 2k3 server.

Uncheck that and the dialog box will disappear when you run an exe off a network share.

Also take a look at the following article.

http://www.windowsecurity.com/articles/Security-Configuration-Wizard-Windows-Server-2003-SP1.html

This article describes how to enable and use the Security Configuration Wizard in Windows 2003. Using the Wizard you should be able to setup the security policy so that the service account has permissions to run EXEs from network shares.

: STT Support,

: Sorry for the tardy response, just getting back to this now.

: Yes you are correct in your interpretation of the problem.

: I tested the service just as you suggested and it worked fine

: when run as a scheduled job under the 24X7 service. I then

: added a third line to the same batch job that simulates what I'm

: really attempting to do (run an .exe that resides on a

: remote share): \\computer_name\share\test.exe .

: When executed under the 24X7 service the first two lines

: worked as expected but the .exe did not fire. Again when

: running this same scheduled batch job with the 24X7 GUI open

: the .exe fires off just fine.

: Obviously there is some type of restriction here when

: attempting to run a remote .exe under the 24X7 Scheduler

: service under Windows Server 2003. Where do I go from here

: or do I have to resort to running all these jobs under

: the native MS Windows Scheduler? One option is to install all

: the necessary run time files on each server that has the

: 24X7 Scheduler installed but that is not the preferred

: solution. Any recommendations here?

We have had some issues when running Exe's from 24X7 Scheduler where our anti-

virus was blocking the calls to the Exe's.

I guess something in the call signature matches a virus

definition.

Check your antivirus logs to see if that is blocking the call.

If you don't see anything there,

disable your antivirus and see if it works.

If it works with anti-virus diasabled,

then the antivirus is your culprit.

: Hi,

: My guess is that the service is running under a different account with

: different permissions.

: A Google search turned the following tip

: Open your Add or Remove Programs from Control Panel.

: Click on Add/Remove Windows Components.

: Scroll down until you see the

: "Internet Explorer Enhanced Security Configuration" checkbox.

: By default it is checked on any Win 2k3 server.

: Uncheck that and the dialog box will disappear when you run an exe off a

: network share.

: Also take a look at the following article.

:

: http://www.windowsecurity.com/articles/Security-Configuration-Wizard-Windows-Server-2003-SP1.html

: This article describes how to enable and use the Security Configuration

: Wizard in Windows 2003. Using the Wizard you should be able to setup the

: security policy so that the service account has permissions to run EXEs

: from network shares.