xtConnect 3.9.1 "Proper Database Drivers have not been installed"

mike.howell 2019-08-05 16:26:44 UTC #1

xtConnect Batch Manager 3.9.1 (pre-production)
Windows Server 2008R2, 2016
PG9.6 (different server)
xtuple 5 RC client (pre-production)

After unpacking the zip on Windows Server 2008R2, or Server 2016, I run BatchManager.exe and use known-good administrator credentials / known good connection information and get message:

A connection could not be established with the specified Database as the Proper Database Drivers have not been installed. Contact your Systems Administrator.

Tried same BatchManager on the same Windows Servers with the same results. Running the xTuple.exe 5 RC client executable on these same servers against the same PG database works fine, so I'm not sure what "proper database drivers" this error refers to. Online docs on installing xtc are kinda thin. Any suggestions / guidance appreciated. Thanks.
~~Mike Howell

invena 2019-08-05 22:21:04 UTC #2

Jim McCluskey knows how to solve this problem.

Jim_McCluskey 2019-08-06 14:04:37 UTC #3

If you copy the batchmanager.exe file into the same folder as your 5.0 client and launch batch manager from there, the system should be able to find the appropriate drivers.

mike.howell 2019-08-06 17:58:39 UTC #4

Hi guys, thanks for the info Jim. I think I have a bead on this--I'm getting good results. Here is what I learned.

1) I copied BatchManager.exe into the xTuple 5.0 RC folder, and running it gives the error:

The application was unable to start correctly (0xc000007b). Click OK to close...

2) Getting clever, I thought to try copying BatchManager.exe to our production xTuple 4.11.1 environment. This one does seem to work! At least I get to the configuration screen now.

Do you know what files BatchManager needs to see to run? I would like to try to get it running standalone.

Thanks ~~Mike

mike.howell 2019-08-19 20:36:52 UTC #5

I did a little experimenting and discovered the exact files I needed to copy from our 4.11 client into the batch manager folder to make it work against our test environment. They are:

libpq.dll
ssleay32.dll
libea32.dll
libintl-8.dll
libconf-2.dll

At a point in the future, that PG9.6 will be upgraded to 10+ and I imagine this problem will go away. This issue can be closed. Thanks!