# Issue running batch file from Gateway Script again

**URL:** <https://forum.inductiveautomation.com/t/issue-running-batch-file-from-gateway-script-again/24976>\
**Category:** Ignition\
**Tags:** ignition79\
**Created:** [May 14, 2019, 2:45pm UTC](https://forum.inductiveautomation.com/t/issue-running-batch-file-from-gateway-script-again/24976 "2019-05-14T14:45:56Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![bkarabinchak.psi](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/bkarabinchak.psi/32/83567_2.png) [@bkarabinchak.psi](https://forum.inductiveautomation.com/u/bkarabinchak.psi)\
**Post date:** [May 14, 2019, 2:45pm UTC](https://forum.inductiveautomation.com/t/issue-running-batch-file-from-gateway-script-again/24976/1 "2019-05-14T14:45:56Z")

</div>

Two months ago I asked this question [Gateway Event Script not triggering batch file](http://forum.inductiveautomation.com/t/gateway-event-script-not-triggering-batch-file/22643) 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

```auto
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?