Batch Initialization Error 31

Keywords: 	  Batch Initialization Error 31

---

Question:

I'm getting this error on a compiled EXE that I'm trying to kick off on particular server, but this same EXE runs fine on another machine.

I have two compiled WB EXE and the first large EXE launches fine, it then does a RunWait of the 2nd EXE. The 2nd EXE is getting the Batch Initialization error 31, and it gets the error regardless of whether it's run standalone or RunWaited from the 1st EXE.

I have two DLLs in the same directory as the EXEs: WBDBM32I.DLL and WBDBV32I.DLL.

Answer:

The error description for this error is:

General failure

"A device attached to the system is not functioning"

Kind of cryptic.

Your EXEs are created by two different versions of the compiler and the one EXE that's failing with this error message is trying to access a DLL that's become corrupted.

Rename all the Winbatch DLLs on that server to force the large EXEs to recreate their DLLs locally. Then once that's done and it's working again, mark those DLLs and EXEs read-only.

If that doesn't work, run DiskScan on the affected drive with a "thorough" setting to inspect the disk surface. Some kind of weird corruption maybe.

---

Article ID:   W14587

Filename:   Batch Initialization Error 31.txt