Windows folder security setup for AX 2009 batch process

Windows folder/file security set up for AX 2009 batch processes

Microsoft Dynamics AX 2009 can work differently when accessing folders depending on whether the process is running on the client or on the server.

A simple folder path selected from a normal windows folder browser dialog will work if the process is running on the client. Example of such a path is C:\Temp

The same path will not work if the process is running on server as the server (AOS) generally remains on another physical machine than client and a local folder path from client will not be available/accessible for the server. The batch job generally becomes victim of this issue as the dialog where they are configured is run on client but they are run on a batch server.

To overcome this situation, few points needs to be taken care of

1. Try to provide the absolute paths / file names rather than local one. E.g. \\deepakgxp\DeepakTest\Source\TestFile.txt 
2. The process, which accesses the folder/file, should be given access. Server process might be running under a different network account then the person’s network account who configured the batch job. Please make sure both the network accounts have the access permission to the folder/file. Provide the permissions from the security tab of the shared folder. 

 

Also set the network permissions for the users.

 

On newer windows

 
(I have painted the screen shots blue/white in order not to show my client's setup here)

 3. The level of permission should match the type of work i.e. if a process is going to create, delete or modify a file; it should have relevant access permissions. 

Note - This setup is not an optimal one as it is asking you to do a bit more than what is needed. But it is worth  putting effort in setup rather than debugging what went wrong.