extend 9 AcuXDBC (64-bit) 9.1.0: No entry in xvision.slc file error

[Migrated content. Thread originally posted on 03 November 2011]

After installing extend 9 AcuXDBC (64-bit) 9.1.0 on Linux server and the corresponding extend 9 AcuXDBC (64-bit) client on a Windows Server 2008 R2, I created a "System" DSN for the data on the client using the 64-bit driver. Then, the when trying to create a linked server on SQL Server 2008 R2 (64-bit) using the 64-bit DSN; I get the following error:

OLE DB provider "MSDASQL" for linked server "(null)" returned message "[TOD][ODBC Driver][acuxdbc03:user/passwd/xvision:pamsdata001.cfg@20223:10.5.1.171!acuxdbc04]VISION: No entry for product 'AcuXDBCS' in file '/opt/acucorp/812/bin/xvision.slc'"

Notice the version in the path to the license file. For some reason it's looking at the wrong license file; it needs to look at '/opt/acucorp/910/bin/xvision.slc'. Is there some enviroment variable or config file setting that tells the xdbc server which license file to use?

Also, just to try and get it to work, I copied the xvision.slc file from /opt/acucorp/910/bin to /opt/acucorp/812/bin; but I still get the same error.

[Migrated content. Thread originally posted on 03 November 2011]

After installing extend 9 AcuXDBC (64-bit) 9.1.0 on Linux server and the corresponding extend 9 AcuXDBC (64-bit) client on a Windows Server 2008 R2, I created a "System" DSN for the data on the client using the 64-bit driver. Then, the when trying to create a linked server on SQL Server 2008 R2 (64-bit) using the 64-bit DSN; I get the following error:

OLE DB provider "MSDASQL" for linked server "(null)" returned message "[TOD][ODBC Driver][acuxdbc03:user/passwd/xvision:pamsdata001.cfg@20223:10.5.1.171!acuxdbc04]VISION: No entry for product 'AcuXDBCS' in file '/opt/acucorp/812/bin/xvision.slc'"

Notice the version in the path to the license file. For some reason it's looking at the wrong license file; it needs to look at '/opt/acucorp/910/bin/xvision.slc'. Is there some enviroment variable or config file setting that tells the xdbc server which license file to use?

Working through this, step by step. Now I'm getting the following error when creating the linked server:

Cannot initialize the data source object of OLE DB provider "MSDASQL" for linked server "PAMSDATA001".
OLE DB provider "MSDASQL" for linked server "PAMSDATA001" returned message "[Microsoft][ODBC Driver Manager] Driver's SQLSetConnectAttr failed".
OLE DB provider "MSDASQL" for linked server "PAMSDATA001" returned message "[TOD][ODBC Driver]DLLLOAD: xvision, /opt/acucorp/910/bin/xvision.so: undefined symbol: ShowLicenseError". (Microsoft SQL Server, Error: 7303)

[Migrated content. Thread originally posted on 03 November 2011]

After installing extend 9 AcuXDBC (64-bit) 9.1.0 on Linux server and the corresponding extend 9 AcuXDBC (64-bit) client on a Windows Server 2008 R2, I created a "System" DSN for the data on the client using the 64-bit driver. Then, the when trying to create a linked server on SQL Server 2008 R2 (64-bit) using the 64-bit DSN; I get the following error:

OLE DB provider "MSDASQL" for linked server "(null)" returned message "[TOD][ODBC Driver][acuxdbc03:user/passwd/xvision:pamsdata001.cfg@20223:10.5.1.171!acuxdbc04]VISION: No entry for product 'AcuXDBCS' in file '/opt/acucorp/812/bin/xvision.slc'"

Notice the version in the path to the license file. For some reason it's looking at the wrong license file; it needs to look at '/opt/acucorp/910/bin/xvision.slc'. Is there some enviroment variable or config file setting that tells the xdbc server which license file to use?

Is the 810 AcuXDBC Server still running or has it been killed? If it is stil running, you should configure them to run on different ports. Please post the contents of your xvision.slc license and / or contact Customer Care.

[Migrated content. Thread originally posted on 03 November 2011]

After installing extend 9 AcuXDBC (64-bit) 9.1.0 on Linux server and the corresponding extend 9 AcuXDBC (64-bit) client on a Windows Server 2008 R2, I created a "System" DSN for the data on the client using the 64-bit driver. Then, the when trying to create a linked server on SQL Server 2008 R2 (64-bit) using the 64-bit DSN; I get the following error:

OLE DB provider "MSDASQL" for linked server "(null)" returned message "[TOD][ODBC Driver][acuxdbc03:user/passwd/xvision:pamsdata001.cfg@20223:10.5.1.171!acuxdbc04]VISION: No entry for product 'AcuXDBCS' in file '/opt/acucorp/812/bin/xvision.slc'"

Notice the version in the path to the license file. For some reason it's looking at the wrong license file; it needs to look at '/opt/acucorp/910/bin/xvision.slc'. Is there some enviroment variable or config file setting that tells the xdbc server which license file to use?

Hi Chris,

The 812 path in the error message tells me the environment was not set up correctly when AcuXDBC Server was started. You should kill AcuXDBC Server then make sure the following are set:

GENESIS_HOME=/opt/acucorp/910
LD_LIBRARY_PATH=/opt/acucorp/910/lib:/opt/acucorp/910/bin:
PATH=/opt/acucorp/910/bin;

Then start AcuXDBC Server.

Regards,
Doug

[Migrated content. Thread originally posted on 03 November 2011]

After installing extend 9 AcuXDBC (64-bit) 9.1.0 on Linux server and the corresponding extend 9 AcuXDBC (64-bit) client on a Windows Server 2008 R2, I created a "System" DSN for the data on the client using the 64-bit driver. Then, the when trying to create a linked server on SQL Server 2008 R2 (64-bit) using the 64-bit DSN; I get the following error:

OLE DB provider "MSDASQL" for linked server "(null)" returned message "[TOD][ODBC Driver][acuxdbc03:user/passwd/xvision:pamsdata001.cfg@20223:10.5.1.171!acuxdbc04]VISION: No entry for product 'AcuXDBCS' in file '/opt/acucorp/812/bin/xvision.slc'"

Notice the version in the path to the license file. For some reason it's looking at the wrong license file; it needs to look at '/opt/acucorp/910/bin/xvision.slc'. Is there some enviroment variable or config file setting that tells the xdbc server which license file to use?

Is is possible for 812 and 910 to co-exist? If not, then will 32-bit appplications connecting from client machines using either 812 32-bit and/or 910 32-bit will work with just 910 64-bit on the server?

[Migrated content. Thread originally posted on 03 November 2011]

After installing extend 9 AcuXDBC (64-bit) 9.1.0 on Linux server and the corresponding extend 9 AcuXDBC (64-bit) client on a Windows Server 2008 R2, I created a "System" DSN for the data on the client using the 64-bit driver. Then, the when trying to create a linked server on SQL Server 2008 R2 (64-bit) using the 64-bit DSN; I get the following error:

OLE DB provider "MSDASQL" for linked server "(null)" returned message "[TOD][ODBC Driver][acuxdbc03:user/passwd/xvision:pamsdata001.cfg@20223:10.5.1.171!acuxdbc04]VISION: No entry for product 'AcuXDBCS' in file '/opt/acucorp/812/bin/xvision.slc'"

Notice the version in the path to the license file. For some reason it's looking at the wrong license file; it needs to look at '/opt/acucorp/910/bin/xvision.slc'. Is there some enviroment variable or config file setting that tells the xdbc server which license file to use?

Both 812 and 910 can coexist and be used on the same server. You must make sure each is running in its own environment. To simplify that, use scripts to set the environment and then launch the application.

[Migrated content. Thread originally posted on 03 November 2011]

After installing extend 9 AcuXDBC (64-bit) 9.1.0 on Linux server and the corresponding extend 9 AcuXDBC (64-bit) client on a Windows Server 2008 R2, I created a "System" DSN for the data on the client using the 64-bit driver. Then, the when trying to create a linked server on SQL Server 2008 R2 (64-bit) using the 64-bit DSN; I get the following error:

OLE DB provider "MSDASQL" for linked server "(null)" returned message "[TOD][ODBC Driver][acuxdbc03:user/passwd/xvision:pamsdata001.cfg@20223:10.5.1.171!acuxdbc04]VISION: No entry for product 'AcuXDBCS' in file '/opt/acucorp/812/bin/xvision.slc'"

Notice the version in the path to the license file. For some reason it's looking at the wrong license file; it needs to look at '/opt/acucorp/910/bin/xvision.slc'. Is there some enviroment variable or config file setting that tells the xdbc server which license file to use?

I should add that if you are running AcuXDBC Server in both versions you must run them on different ports.

[Migrated content. Thread originally posted on 03 November 2011]

After installing extend 9 AcuXDBC (64-bit) 9.1.0 on Linux server and the corresponding extend 9 AcuXDBC (64-bit) client on a Windows Server 2008 R2, I created a "System" DSN for the data on the client using the 64-bit driver. Then, the when trying to create a linked server on SQL Server 2008 R2 (64-bit) using the 64-bit DSN; I get the following error:

OLE DB provider "MSDASQL" for linked server "(null)" returned message "[TOD][ODBC Driver][acuxdbc03:user/passwd/xvision:pamsdata001.cfg@20223:10.5.1.171!acuxdbc04]VISION: No entry for product 'AcuXDBCS' in file '/opt/acucorp/812/bin/xvision.slc'"

Notice the version in the path to the license file. For some reason it's looking at the wrong license file; it needs to look at '/opt/acucorp/910/bin/xvision.slc'. Is there some enviroment variable or config file setting that tells the xdbc server which license file to use?

I created a custom shell to start the 910 xdbcsrvr with the proper environment. When I attempt to create a linked server using 64-bit SQL Server, I get the same error from SQL Server:

Cannot initialize the data source object of OLE DB provider "MSDASQL" for linked server "PAMSDATA001".
OLE DB provider "MSDASQL" for linked server "PAMSDATA001" returned message "[Microsoft][ODBC Driver Manager] Driver's SQLSetConnectAttr failed".
OLE DB provider "MSDASQL" for linked server "PAMSDATA001" returned message "[TOD][ODBC Driver]DLLLOAD: xvision, /opt/acucorp/910/bin/xvision.so: undefined symbol: ShowLicenseError". (Microsoft SQL Server, Error: 7303)

Here is the xdbc log file from the linux server:

Thu Nov 3 17:02:32 2011 - Version 4.0.0.12.
Thu Nov 3 17:02:32 2011 - Starting vtxnetd (pid: 24121).
Thu Nov 3 17:02:32 2011 - Server port 20223
Thu Nov 3 17:02:32 2011 - Setting up signal handler
Thu Nov 3 17:02:32 2011 - Creating 'listen' queue (max: 10)
Thu Nov 3 17:02:32 2011 - Setup done. Going into 'accept' loop
Thu Nov 3 17:03:05 2011 - Got a connection request (fd: 5)
Thu Nov 3 17:03:05 2011 - child (pid: 24150) exec 'acuxdbc04'

[Migrated content. Thread originally posted on 03 November 2011]

After installing extend 9 AcuXDBC (64-bit) 9.1.0 on Linux server and the corresponding extend 9 AcuXDBC (64-bit) client on a Windows Server 2008 R2, I created a "System" DSN for the data on the client using the 64-bit driver. Then, the when trying to create a linked server on SQL Server 2008 R2 (64-bit) using the 64-bit DSN; I get the following error:

OLE DB provider "MSDASQL" for linked server "(null)" returned message "[TOD][ODBC Driver][acuxdbc03:user/passwd/xvision:pamsdata001.cfg@20223:10.5.1.171!acuxdbc04]VISION: No entry for product 'AcuXDBCS' in file '/opt/acucorp/812/bin/xvision.slc'"

Notice the version in the path to the license file. For some reason it's looking at the wrong license file; it needs to look at '/opt/acucorp/910/bin/xvision.slc'. Is there some enviroment variable or config file setting that tells the xdbc server which license file to use?

To provide a little more info, here are the "acu" processes running on the linux server:

root 4700 1 0 03:08 ? 00:00:00 /opt/acucorp/800/bin/acushare -start
root 4706 1 0 03:08 ? 00:00:00 /opt/acucorp/800/bin/acurcl -start -c /etc/acurcl80.cfg -t7 -e /tmp/acurcl80.log
root 4732 1 0 03:08 ? 00:00:00 /opt/acucorp/810/bin/acurcl -start -c /etc/acurcl81.cfg -t7 -e /tmp/acurcl81.log
root 4743 1 0 03:08 ? 00:00:00 /opt/acucorp/812/bin/acurcl -start -c /etc/acurcl812.cfg -t7 -le /tmp/acurcl812.log
root 24121 1 0 17:02 pts/4 00:00:00 /opt/acucorp/910/bin/xdbcsrvr -z -p20223 log

[Migrated content. Thread originally posted on 03 November 2011]

After installing extend 9 AcuXDBC (64-bit) 9.1.0 on Linux server and the corresponding extend 9 AcuXDBC (64-bit) client on a Windows Server 2008 R2, I created a "System" DSN for the data on the client using the 64-bit driver. Then, the when trying to create a linked server on SQL Server 2008 R2 (64-bit) using the 64-bit DSN; I get the following error:

OLE DB provider "MSDASQL" for linked server "(null)" returned message "[TOD][ODBC Driver][acuxdbc03:user/passwd/xvision:pamsdata001.cfg@20223:10.5.1.171!acuxdbc04]VISION: No entry for product 'AcuXDBCS' in file '/opt/acucorp/812/bin/xvision.slc'"

Notice the version in the path to the license file. For some reason it's looking at the wrong license file; it needs to look at '/opt/acucorp/910/bin/xvision.slc'. Is there some enviroment variable or config file setting that tells the xdbc server which license file to use?

Here is the log file from the client:

Created: Fri Nov 04 11:35:27 2011


***** Calling DB *****

----------------------------- Send @0000000000716F10
FNC: CONFIG
OPT: 0 RBS: 0 CUR: 64 NRE: 0 AUX: 256 CMD: 0
PDL: 0 PDP: 0000000000000000
PBL: 0 PBP: 0000000000000000
SBL: 26 SBP: 000000000018A8D1
20223:10.5.1.171!acuxdbc04

***** Returning from DB *****

----------------------------- Receive @0000000000716F10
RET: 0 ARS: 4 NCO: 0 DEC: 0 NRA: 4194804
RBL: 0 RBP: 0000000000000000
MSL: 53 MBP:
@(T)$Id: zdb4.c,v 1.79 2007/08/01 20:22:04 niba Exp $
----------------------------- Misc @0000000000716F10
DID: 18 DBI: 0 DBC: 0 MBL: 384 MNC: 256 NAC: 64 NLC: 256 CIO: 0
time: 0.204187, total: 0.204187

***** Calling DB *****

----------------------------- Send @0000000000716F10
FNC: CONNECT
OPT: 0 RBS: 8192 CUR: 0 NRE: 384 AUX: 256 CMD: 0
PDL: 0 PDP: 0000000000000000
PBL: 0 PBP: 000007FEF36263B0
SBL: 38 SBP: 000000000018A8AA
system/manager/xvision:pamsdata001.cfg

***** Returning from DB *****

----------------------------- Receive @0000000000716F10
RET: 2 ARS: 0 NCO: 0 DEC: -1 NRA: 4194804
RBL: 0 RBP: 0000000000000000
MSL: 85 MBP:
DLLLOAD: xvision, /opt/acucorp/910/bin/xvision.so: undefined symbol: Sho
wLicenseError
----------------------------- Misc @0000000000716F10
DID: -1 DBI: 0 DBC: 0 MBL: 384 MNC: 256 NAC: 64 NLC: 256 CIO: 0
time: 0.047838, total: 0.252026

----------------------------------- Summary
Function Calls Errors Total time
---------- ----- ------ -----------
CONFIG 1 0 0.204187
CONNECT 1 1 0.047838
RELEASE 0 0 0.000000
COMMIT 0 0 0.000000
ROLLBACK 0 0 0.000000
CANCEL 0 0 0.000000
OPEN 0 0 0.000000
OPENFETCH 0 0 0.000000
FETCH 0 0 0.000000
FETCHNEXT 0 0 0.000000
CLOSE 0 0 0.000000
EXEC 0 0 0.000000
EXEC2 0 0 0.000000
DESCRIBE 0 0 0.000000
POPEN 0 0 0.000000
PEXEC 0 0 0.000000
COMMAND 0 0 0.000000
FREE 0 0 0.000000
EXIO 0 0 0.000000
EXIO2 0 0 0.000000
BLOB 0 0 0.000000
IPC 0 0 0.000000
FILE 0 0 0.000000
DESCPARMS 0 0 0.000000

[Migrated content. Thread originally posted on 03 November 2011]

After installing extend 9 AcuXDBC (64-bit) 9.1.0 on Linux server and the corresponding extend 9 AcuXDBC (64-bit) client on a Windows Server 2008 R2, I created a "System" DSN for the data on the client using the 64-bit driver. Then, the when trying to create a linked server on SQL Server 2008 R2 (64-bit) using the 64-bit DSN; I get the following error:

OLE DB provider "MSDASQL" for linked server "(null)" returned message "[TOD][ODBC Driver][acuxdbc03:user/passwd/xvision:pamsdata001.cfg@20223:10.5.1.171!acuxdbc04]VISION: No entry for product 'AcuXDBCS' in file '/opt/acucorp/812/bin/xvision.slc'"

Notice the version in the path to the license file. For some reason it's looking at the wrong license file; it needs to look at '/opt/acucorp/910/bin/xvision.slc'. Is there some enviroment variable or config file setting that tells the xdbc server which license file to use?

Okay, I think I'm onto something here... to me it looks like AcuXDBC uses Vortex drivers, which I think might be based on JDBC. I looked at the java runtime on that system and found two references to the /opt/acucorp/812 folder (see below).

My thinking here is that I need to modify the java runtime configuration, but I'm not sure exactly how/what changes to make.

-Dcom.sun.aas.ClassPathSuffix=/opt/acucorp/812/tools/CVM.jar
-Djava.library.path=/usr/local/webserver91/lib:/usr/local/webserver91/lib:/usr/local/webserver91/lib:/opt/acucorp/812/bin:/opt/acucorp/812/lib

[Migrated content. Thread originally posted on 03 November 2011]

After installing extend 9 AcuXDBC (64-bit) 9.1.0 on Linux server and the corresponding extend 9 AcuXDBC (64-bit) client on a Windows Server 2008 R2, I created a "System" DSN for the data on the client using the 64-bit driver. Then, the when trying to create a linked server on SQL Server 2008 R2 (64-bit) using the 64-bit DSN; I get the following error:

OLE DB provider "MSDASQL" for linked server "(null)" returned message "[TOD][ODBC Driver][acuxdbc03:user/passwd/xvision:pamsdata001.cfg@20223:10.5.1.171!acuxdbc04]VISION: No entry for product 'AcuXDBCS' in file '/opt/acucorp/812/bin/xvision.slc'"

Notice the version in the path to the license file. For some reason it's looking at the wrong license file; it needs to look at '/opt/acucorp/910/bin/xvision.slc'. Is there some enviroment variable or config file setting that tells the xdbc server which license file to use?

This turned out to be a defect in the AcuXDBC Server software. I have tested a patch, which seems to have resolved the problem.