Visual LANSA Forum

Has anyone seen this error before and/or know how to fix it?

We are running Visual LANSA/LANSA Integrator V15 on Windows. When we interrogate our SOAP Server service, we are seeing these messages in x_err.log. We aren't attempting to access LX_F96 so suspecting the error is occurring in some LANSA internal functionality. SQL error code 18456 has to do with invalid credentials. We have no issues accessing the database using SQL Server Management Studio or using our LANSA code to read/write database tables.

Thanks.

Message : (0381) - Unable to allocate ODBC statement handle.
SQL Error Code : 18456
Routine : X_DBI_Prepare_Stmnt
Job Number: OS User : IUSR
DBII=LANSA_IRDPGMLIB DBUT=MSSQLS GUSR=QOTHPRDOWN LOGO=N BPQS=Y MODE=B QUET=Y PROC=KOFPRO08 FUNC=KOFFN11 PART=IRD LANG=ENG
ROOT=C:\LANSA_IRDPGMLIB\X_WIN95
==============================================================================
Tue Sep 20 20:10:49 2022
Version 15.0.0 Build 4403 Windows Server Server Standard (Full Installation) EditionMessage : (0183) - Fatal and unexpected SQL error when attempting to use the named SQL table.
SQL Table : LX_F96
SQL Error Code : 18456
Routine : c:\l4wbuild\v15\L4W15000\work\x_win95\x_lansa\src\x_fun5.c
Job Number: OS User : IUSR
==============================================================================
Tue Sep 20 20:10:49 2022
Version 15.0.0 Build 4403 Windows Server Server Standard (Full Installation) EditionMessage : (0183) - Fatal and unexpected SQL error when attempting to use the named SQL table.
SQL Table : LX_F96
SQL Error Code : -9997
Routine : c:\l4wbuild\Trunk\work\x_win95\x_lansa\src\x_xql8.c
Job Number: OS User : IUSR

Hi

SQL Management Studio uses the odbc connector which usually uses windows authentication or sql authentication.

LANSA Integrator uses java, so it is using a jdbc connector, which requires a connection string like

jdbc:sqlserver://127.0.0.1:57566;instanceName=LANSAINS;

that connection string may be using a port to connect to the database by tcp/ip address, which needs to be open using the SQL Server Manager usually available in

C:\Windows\SysWOW64\SQLServerManager15.msc

number could be different according to your version.... 14, 13, etc.

so, check the connection string in use, ip, port (dynamic port), user for that connection string authorized to the database, verify it is working correctly.

in more doubt, support may assist, create a case.

Thanks for responding, Dino.

It turned out to be the way IUSR was locked down on the server. It had no permission to access the database but it seemed LANSA was expecting it to have access. Once access was provided, the code ran successfully.

I did open a ticket with LANSA support also, as the customer wants to know the specific permissions IUSR should have.