Two months ago I asked this question Gateway Event Script not triggering batch file which resolved my issue on running a batch file that operates on mapped network drives, it’ s only purpose is to copy files to a back up hard drive. The solution then I needed was to map the network drive and it worked fine.
Recently, I had to add a few more commands to the batch file involving a new network drive which I mapped in the Ignition configuration file like so
wrapper.share.1.location=\\nas\Bay1
wrapper.share.1.target=M:
wrapper.share.1.type=DISK
wrapper.share.2.location=\\file3\F
wrapper.share.2.target=Z:
wrapper.share.2.type=DISK
wrapper.share.3.location=\\nas\Bay2
wrapper.share.3.target=N:
wrapper.share.3.type=DISK
wrapper.share.4.location=\\nas\Bay7
wrapper.share.4.target=S:
wrapper.share.4.type=DISK
wrapper.share.5.location=\\nas\Bay8
wrapper.share.5.target=T:
wrapper.share.5.type=DISK
Now, running the batch file on the gateway directly via double clicking works fine. Running a client on the gateway with a button that triggers the batch file works fine. But when my gateway triggers it, it does run, but it is not successful, and logs that it cannot find the N: drive. I’ve stopped and started Ignition in the services after changing the Ignition.conf file. I have no idea what else I can do. Any suggestions?