This article from InSource shows one way how to deal with the Batch Manager crashing after migrating from a Physical to a Virtual Machine.
- Author: Rufus Handsome
- Published: 04/26/2017
- Applies to: InBatch v8.1
After migrating from a physical computer to a virtual machine, when starting up the VM, everything starts up fine. However, when going to the client to initialize a batch in batch manager, the service suddenly stops and you receive the message similar to "unexpected error, warm restart c461 - shutdown - disconnected from batch manager." With this situation, It would appear that the hidden .BatchWR directory is missing from the "C:\Program Files\FactorySuite\InBatch\cfg\config_A\" folder. To resolve the issue, open a dos window with cmd, then navigate to the directory "C:\Program Files\FactorySuite\InBatch\cfg\config_A", then use the "mkdir" command as follows: "mkdir .BatchWR", to re-create the hidden directory. Then in InBatch Scheduler, run a batch to test and verify.