Scheduled task calls EXE file does not work.
On a Windows 2012 server, I create a Scheduled Task to run a EXE file.
The EXE file creates CSV files in a network share.
When I manually run the EXE, it works. But when I call it from the Scheduled Task and run the task, it just does not run and returns an error about access issue.
I am running the task as a domain admin who has right to that network share.
I do not know what else to check. I search the WEB and see a lot of people have similar issue. I have tried what have been suggested but still have no luck of getting it to work.
Anyone has any suggestion is appreciated.
Thanks in advance.
The EXE file creates CSV files in a network share.
When I manually run the EXE, it works. But when I call it from the Scheduled Task and run the task, it just does not run and returns an error about access issue.
I am running the task as a domain admin who has right to that network share.
I do not know what else to check. I search the WEB and see a lot of people have similar issue. I have tried what have been suggested but still have no luck of getting it to work.
Anyone has any suggestion is appreciated.
Thanks in advance.
NinjaStyle82
are you pointing to the network share by UNC path or drive letter?
Well, Scheduled Tasks run under a different account. Per default a local account without any network permissions. Even when you have used a different account, do you use a mapped drive? This is normally also not available under a different account.
So use an account with network permissions and access your file by using a UNC path.
So use an account with network permissions and access your file by using a UNC path.
ASKER
The EXE drops file to a UNC path. The account being used to run the task has R/W right to the UNC path.
Thanks.
Thanks.
Is the EXE located in a place where this account has permission as well? like not in a different user's profile on the server or anything, correct?
Sometimes explicit permission needs to be granted in Windows Server to profiles, even though inherently they should have permission.
Sometimes explicit permission needs to be granted in Windows Server to profiles, even though inherently they should have permission.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.