# system.file.writeFile() and 'Unable to create path to file'

**URL:** <https://forum.inductiveautomation.com/t/system-file-writefile-and-unable-to-create-path-to-file/75656>\
**Category:** Ignition\
**Created:** [June 28, 2023, 3:34pm UTC](https://forum.inductiveautomation.com/t/system-file-writefile-and-unable-to-create-path-to-file/75656 "2023-06-28T15:34:30Z")\
**Posts on this page:** 1\
**Showing post:** 3

<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:** [June 28, 2023, 3:44pm UTC](https://forum.inductiveautomation.com/t/system-file-writefile-and-unable-to-create-path-to-file/75656/3 "2023-06-28T15:44:19Z")

</div>

Just regarding the .conf file methodology it tries to connect when the gateway starts up but if the connection is lost while the GW is running it will not retry and as far as I can tell (I asked if there was a way to retry programatically via a GW script) it does not seem like there is a way.

> [@How to force the Gateway to map drives when there is a failed attempt at restart](https://forum.inductiveautomation.com/t/how-to-force-the-gateway-to-map-drives-when-there-is-a-failed-attempt-at-restart/65929):
>
> This week-end the Ignition Gateway server rebooted after windows updates. At reboot, the gateway failed to map a drive to a remote server (maybe because it was rebooting too) Is there a way to force the gateway to try remap the drive manually without restarting the entire gateway ?

Highly recommend using one of the other options Phil listed instead of trying to make the .conf login method be more robust - doesn't seem possible.

---

_[View the full topic](https://forum.inductiveautomation.com/t/system-file-writefile-and-unable-to-create-path-to-file/75656)._