Page 1 of 1

Packaged Batch file Crashes when run from UNC path

Posted: Wed Mar 13, 2019 12:44 pm
by omcakr
Product, version and build: PrimalScript, 7.4.125
32 or 64 bit version of product: 64bit
Operating system: 64 bit OS: Windows 10, Windows 7, Windows Server 2016

*** Please add details and screenshots as needed below. ***

I converted a single line windows batch file to an executable using Deploy -> Build menu.
Script Engine Target: Microsoft Windows 32 and 64 bit
Script Engine: CMD
Output Settings: Generate .config file is selected
Other settings: Left default values

I copied the final executable package to a network location and users must call it using UNC path. When it is run from UNC path executable crashes with message ".... has stopped working. A problem caused the program to stop working correctly. Windows will close the program and notify you if a solution is available."

For testing purposes, I connected to the server where the file is hosted and run it directly. It runs fine. If I run it using UNC path it crashed with the same message.

Users has modify permission on parent folder an file.

Re: Packaged Batch file Crashes when run from UNC path

Posted: Wed Mar 13, 2019 1:39 pm
by Alexander Riedel
Thanks for letting us know. I'll forward it to QA for testing.

Re: Packaged Batch file Crashes when run from UNC path

Posted: Wed Mar 27, 2019 2:22 pm
by Alexander Riedel
We are not able to replicate this here. Could you provide more more information as to where the exe is located?
NAS? Windows Server? Etc.
I see you generate a 32 and a 64 bit version. Do both exhibit this behavior on your 64 bit machine or only one? If so, which one?
Additionally, a crash usually generates a system log entry. Could you check that and provide the enclosed information please?