search

NETWAYS / icinga2-scom-connector

UNSUPPORTED - SCOM Alert connector for Icinga 2
GNU General Public License v2.0
2 stars 0 forks source link

Unicode data in a Unicode-only collation #9

Closed swizzly closed 5 years ago

swizzly commented 5 years ago

Hi by executing "scom_connector config" the following error is popping up:

DBD::Sybase::db selectall_hashref failed: Server message number=4004 severity=16 state=1 line=2 server=XXX\YYY text=Unicode data in a Unicode-only collation or ntext data cannot be sent to clients using DB-Library (such as ISQL) or ODBC version 3.7 or earlier. at ./scom_connector line 377. UNKNOWN - program ended unexcepted: error querying for entities: Server message number=4004 severity=16 state=1 line=2 server=XXX\YYY text=Unicode data in a Unicode-only collation or ntext data cannot be sent to clients using DB-Library (such as ISQL) or ODBC version 3.7 or earlier. at ./scom_connector line 377. I already changed the parameters: tds version = 8 and client charset = UTF-8 in the /etc/freetds.conf

In the freetds query a partly could avoid the "Unicode data in a Unicode-only collation..." Errors by using CAST in the queries e.g. SELECT CAST(TypeName AS TEXT) FROM ManagedType But since I am not a MSSQL guru, I didn't manage to apply the trick to all the MSSQL Queries in the script.

I'm trying to run the script on a RHEL7 (v7.6) Server with freetds-0.95.81-1.el7.x86_64. Cheers

swizzly commented 5 years ago

Sorry, my fault, I changed now the tds version = 8.0 from tds version = 8 which is appereantly false, and it is working now.