SAP B1 HANA: Error: -8031 Unable to retrieve OBSERVERDLL.dll from server - sapb1

When I use DI API: connect to SAP BUSINESS ONE HANA 9.3 PL13, I'm get error: -8031 Unable to retrieve OBSERVERDLL.dll from server.
Plz help me!

Related

Azure Logic Apps SQL Connector Error: Bad Request

I'm using the SQL Connector in Azure Logic Apps to connect to our Azure SQL Database to perform queries, update tables, and execute stored procedures. After several months of developing logic apps, I'm seeing the below error message when using the SQL Connector "Execute Stored Procedure (V2)". I'm only encountering this error with this specific connector. All the other connectors work just fine. Has anyone encountered this error before and had success troubleshooting?
Error:
Could not retrieve values. Error code: 'BadRequest', Message: 'The value's length for key 'application name' exceeds it's limit of '128'.
clientRequestId: 'XXXXX'. More diagnostic information: x-ms-client-request-id is 'XXXXX'.
Just had a call with Microsoft Support and got confirmation: this is the global issue in the SQL connector of LogicApp. They are working on this to fix, no ETA for now.
Update: should be fixed from around 29.03.2022 03:00 CET

SSAS tabular project connection issue - memSQL DB as data source

I am trying to create a SSAS tabular project where data source is memSQL DB. I am able to connect to the memSQL database from any SQL client tool using MySQL and/or MariaDb OBDC driver. But when I am using the same ODBC driver for a SSAS tabular project "using OLEDB provider for ODBC" then I am getting error like below:
Failed to retrieve data from DATE_DIM. Reason: ERROR [42000] [MySQL][ODBC 5.3(w) Driver][mysqld-5.5.58]You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '*
FROM [DATE_DIM]' at line 1
ERROR [42000] [ma-3.0.9][5.5.58]You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '*
FROM [DATE_DIM]' at line 1
I have used the connect string as "Provider=MSDASQL.1;Persist Security Info=False;DSN=memSQLDB". Test connection was successful, but when trying to preview any table's data it throws the above error to me.
Is it a compatibility issue between memSQL (5.5.58) version and MySQL ODBC driver (version-5.3) or MariaDB OBDC driver (version-3.0.9)?
Can anyone suggest if there is any compatible ODBC driver exists, which can work with SSAS ?
With this error message, it appears it's less about authenticating correctly and more about the SSAS tool issuing queries with syntax MemSQL doesn't understand. Can you grab the query(ies) and post them here? That'll help us migrate these to compatible syntax. Depending on how the tool works, you may not have control over changing these queries, and will need the tool vendor to patch the query syntax to be more compatible.

Neoload SQL ODBC database configuration

i have the task to connect NeoLoad to an ODBC oracle database for getting actual test data variables. My approach is to import a new variable type SQL and select Oracle as the driver and put in all the details i have.
When filling in the database configuration, i get the error
ORA-12505 TNS:listener does not currently know of SID given in connect descriptor
...which means, i miss the correct connection details. In this case, i only have a service name given and no SID.
connection_string_lt = "Driver={Microsoft ODBC for Oracle};CONNECTSTRING=(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=a.b.c.com)(PORT = 1521))(CONNECT_DATA=(SERVICE_NAME=d.world)));uid=user;pwd=pwd"
When trying to get around this by selecting a custom database configuration, NeoLoad wants me to put a driver class and an URL.
However, i had difficulties to find the correct connection URL as it does not match with the connection data i have as well as the driver class, which i don't know where to get from (should i ask the database administrator ?).
Could somebody support me with how the input should look like for this ?
Thanks in advance.
Neoload has its own "SQL Connection" action which helps to connect with database and execute queries. To connect with Oracle it requires connection URL which can be in below format.
jdbc:oracle:thin:#//Hostname:1521/servicename
Username and Password of the Schema you need to access needs to be provided in required space.
Screenshot for connection

Azure SQL Data warehouse ADO.Net Error Codes

I just want to ask the following questions below:
Are SQL error codes in Azure SQL database will also apply in Azure SQL Data Warehouse?
Can anyone point me the URL where I can find list of error codes that's specific only from Azure SQL data warehouse?
Cheers,
Jhessie
Yes, they are the same. Reference: MSDN Forum
To view all the error messages, you can execute this query on master:
select * from sys.messages;

Error using Sybase IQ proxy table

I have a use case that requires me to make a join on a table t1 from Sybase ASE and table t2 from Sybase IQ . I am trying to achieve this by creating a proxy_table on Sybase IQ as follows:
create server SYB1 class 'ASAODBC' using
Driver=libsyb64.so;Server=hostname;Port=portnum;PacketSize=16384;
EnableServerPacketSize=0'
(I even tried above with 'ASEODBC' and 'ODBC' classes)
create external login XYZ to SYB1 remote login 'SYBASEASEusername'
identified by SYBASEASEpwd'
create existing table 'proxy_table_name' at 'SYB1.dbname.owner.tablename'
On firing above sqls I get:
[Sybase][ODBC Driver][Sybase IQ] Unable to connect to 'SYB1': [Sybase][ODBC Driver]
[SQL Anywhere] Unable to connect ; server definition is circular
I have entry for the above mentioned Sybase ASE host in interfaces file and I tried to create the server by specifying the server name itself but it failed nevertheless.
Any help appreciated.
That error occurs when you attempt to connect to a remote server that maps to the local database. That's not possible in Sybase IQ. Check if the ODBC is pointing to the correct server (in your case should be the ASE server).
Your proxy server is using class 'ASAODBC' but since you're connecting to an ASE server, it should be 'ASEODBC'. As aF. said, you also need to make sure your connection string is pointing at the ASE server, not the IQ server.
Full disclosure: I work for SAP in SAP SQL Anywhere engineering. SQL Anywhere is the execution engine for SAP IQ (formerly Sybase IQ).