Hello,

I am trying to test the 64 bit version of AcuXDBC and am having some issues when trying to use the ODBC connection in applications like Microsoft's Power BI.  When I try to access my ODBC connection I get the following errors:

We encountered an error while trying to connect.

Details: "ODBC: ERROR [S1000] [TOD][ODBC Driver]DLLLOAD: acuxdbc04, The specified module could not be found.

ERROR [01000] [Microsoft][ODBC Driver Manager] The driver doesn't support the version of ODBC behavior that the application requested (see SQLSetEnvAttr)."

Now if I use ASQL.bat that Microfocus supplies, I am able to connect to my data source and query data from it.

I also have the 32 bit version of XDBC installed on my computer, so I am not sure if that is causing any conflicts or not. 

I currently have the GENISIS_HOME set to my 64 bit install ACUGT directory.  I have my ACUGT\\bin folder in my Path.  When I check my registry for my data source, it all appears to be pointing to the correct locations.  For this set of data, my data files are Vision version 3 format.

Does anybody have any suggestions as to what to check next?

Our applications are all 32 bit applications, but we have some clients who want to use 64 bit tools like Power BI, so we are trying to see if we can get the 64 bit AcuXDBC to work so they can use these tools.

Thanks!

Scott

I would suggest getting a procmon trace to see exactly what DLLs are being found and loaded to make sure it's finding the AcuXDBC DLLs from the bin directory. 

I started the process monitor right before I clicked on the connect button and this is what I got.  Not really sure what I am looking at.

Hello,

I am trying to test the 64 bit version of AcuXDBC and am having some issues when trying to use the ODBC connection in applications like Microsoft's Power BI.  When I try to access my ODBC connection I get the following errors:

We encountered an error while trying to connect.

Details: "ODBC: ERROR [S1000] [TOD][ODBC Driver]DLLLOAD: acuxdbc04, The specified module could not be found.

ERROR [01000] [Microsoft][ODBC Driver Manager] The driver doesn't support the version of ODBC behavior that the application requested (see SQLSetEnvAttr)."

Now if I use ASQL.bat that Microfocus supplies, I am able to connect to my data source and query data from it.

I also have the 32 bit version of XDBC installed on my computer, so I am not sure if that is causing any conflicts or not. 

I currently have the GENISIS_HOME set to my 64 bit install ACUGT directory.  I have my ACUGT\\bin folder in my Path.  When I check my registry for my data source, it all appears to be pointing to the correct locations.  For this set of data, my data files are Vision version 3 format.

Does anybody have any suggestions as to what to check next?

Our applications are all 32 bit applications, but we have some clients who want to use 64 bit tools like Power BI, so we are trying to see if we can get the 64 bit AcuXDBC to work so they can use these tools.

Thanks!

Scott

We have found that some applications  expect a ODBC V 3 driver. Contact Customer Care and we can provide 10.3 64 bit V3 acuxdbc.dll.

This forum https://community.microfocus.com/t5/Extend-and-AcuCOBOL-Forum/Windows-10-ODBC-driver-libreoffice-acuxdbc03/td-p/2835290/page/2 post contains V3.zip which has the V3 acuxdbc.dll driver.

I copied in the updated acuxdbc.dll and copied all of the dll's from the Bin folder to the Windows\\system32 directory.

Now when I try to connect to my database I am getting the following errors.

Details: "ODBC: ERROR [HY000] [TOD][ODBC Driver]DLLLOAD: xvision, The specified module could not be found

ERROR [HY000] [TOD][ODBC Driver]DLLLOAD: xvision, The specified module could not be found.

I have attached the latest process monitor.

Scott

I apologize, as,  I do not know the exact list of DLLs that are required by the AcuXDBC driver; so, this type of non-standard deployment will require some amount of trial and error.

With that in mind, according to this latest failure messaging, you will also need to copy the "xvision.dll" library from the product installation into "C:\\Windows\\System32".

**As a note; it likely that you will need to resolve further dependencies, so, you will need to copy over any additional libraries that are referenced in future error reporting.

I copied all of the dll's from the bin folder into the windows/system32 directory.  I made sure that the xvision.dll was in there, and it is along with all the other dll's.

Thanks for the additional information, and, since both your statement, and the Process Monitor log, confirm that the libraries are present in "System32", then, this might indicate that it is the Visual C redistributables that are now inaccessible by the Power BI UWP application.

If that is the case, then, attached to this post is a zip archive, which, contains the VC libraries.  And, these DLLs will also need to be placed in the "C:\\Windows\\System32" directory.

If this doesn't work, then, it might be necessary to switch to a non-UWP version of Power BI, if that is at all possible.  Standard Windows programs will not have the same restrictions in regards to loading external libraries.  However, I am not sure if a standard Windows version of Power BI exists, or, if it is available to you under your licensing agreement.

As Steve says UWP apps are very locked down and don't pick up directories on the PATH so you have to move DLLs around, I've downloaded Power BI from Microsoft website (non UWP version) and tested it with AcuXDBC 10.2.1, 10.3.0 and 10.3.1 using the demo sample and it works with that version of Power BI.