From ikorot01 at gmail.com Thu Jan 26 23:56:51 2017 From: ikorot01 at gmail.com (Igor Korot) Date: Thu, 26 Jan 2017 20:56:51 -0800 Subject: [freetds] Where is the Sybase ODBC driver Message-ID: Hi, I just installed Sybase ASE 16 Dev on my Linux box. Now I'm trying to set up a connection using native Sybase ODBC driver. However I have a hard time finding it. [code] igor at IgorReinCloud /opt $ find . -name *odbc* ./sap/DataAccess/bin/odbcversion ./sap/DataAccess/ODBC/samples/odbcbatch ./sap/DataAccess/ODBC/samples/odbcbatch/odbcbatch.cpp ./sap/DataAccess/ODBC/samples/odbcloblocator ./sap/DataAccess/ODBC/samples/odbcloblocator/odbcloblocator.cpp ./sap/DataAccess/ODBC/sp/odbc_mda_120.sql ./sap/DataAccess/ODBC/sp/odbc_mda_157.sql ./sap/DataAccess/ODBC/sp/odbc_mda_1251.sql ./sap/DataAccess/ODBC/sp/odbc_mda_1600000.sql ./sap/DataAccess/ODBC/sp/install_odbc_sprocs ./sap/DataAccess/ODBC/sp/odbc_mda_1570020.sql ./sap/DataAccess/ODBC/sp/odbc_mda_125.sql ./sap/DataAccess/ODBC/sp/odbc_mda_12503.sql ./sap/DataAccess/ODBC/sp/odbc_mda_150.sql ./sap/DataAccess/ODBC/sp/odbc_mda_1502.sql ./sap/DBISQL-16_0/lib/jodbc4.jar ./sap/DBISQL-16_0/bin/libdbodbc16_r.so.1 ./sap/DBISQL-16_0/bin/libdbodbc16_r.so ./sap/DBISQL-16_0/bin/libdbjodbc16.so.1 ./sap/DBISQL-16_0/bin/libdbjodbc16.so ./sap/ASE-16_0/lib/pca/libPCAodbc.so ./sap/ASE-16_0/symlib/pca/libPCAodbc.so ./sap/COCKPIT-4/bin/sa16/linux64/java/jodbc4.jar ./sap/COCKPIT-4/bin/sa16/linux64/lib64/libdbodbc16_r.so ./sap/COCKPIT-4/bin/sa16/linux64/lib64/libdbodbc16.so ./sap/COCKPIT-4/bin/sa16/linux64/lib64/libdbjodbc16.so ./sap/log/odbc.log ./sap/log/odbc.lst ./sap/DataAccess64/bin/odbcversion ./sap/DataAccess64/ODBC/dm/include/unixodbc.h ./sap/DataAccess64/ODBC/dm/include/odbc.h ./sap/DataAccess64/ODBC/dm/include/saodbc.h ./sap/DataAccess64/ODBC/dm/lib64/libodbc.so ./sap/DataAccess64/ODBC/samples/odbcbatch ./sap/DataAccess64/ODBC/samples/odbcbatch/odbcbatch.cpp ./sap/DataAccess64/ODBC/samples/odbcloblocator ./sap/DataAccess64/ODBC/samples/odbcloblocator/odbcloblocator.cpp ./sap/DataAccess64/ODBC/sp/odbc_mda_120.sql ./sap/DataAccess64/ODBC/sp/odbc_mda_157.sql ./sap/DataAccess64/ODBC/sp/odbc_mda_1251.sql ./sap/DataAccess64/ODBC/sp/odbc_mda_1600000.sql ./sap/DataAccess64/ODBC/sp/install_odbc_sprocs ./sap/DataAccess64/ODBC/sp/odbc_mda_1570020.sql ./sap/DataAccess64/ODBC/sp/odbc_mda_125.sql ./sap/DataAccess64/ODBC/sp/odbc_mda_12503.sql ./sap/DataAccess64/ODBC/sp/odbc_mda_150.sql ./sap/DataAccess64/ODBC/sp/odbc_mda_1502.sql [/code] Can anyone tell me which one is the Sybase ODBC driver? Thank you. From john at capps.com Fri Jan 27 00:42:13 2017 From: john at capps.com (John Kendall) Date: Fri, 27 Jan 2017 05:42:13 +0000 Subject: [freetds] Where is the Sybase ODBC driver In-Reply-To: References: Message-ID: <1F262A0D-9889-49D9-8037-CE285C48EEB3@capps.com> Igor, I think it's ./sap/DataAccess64/ODBC/lib/libsybdrvodb.so But for it to work, you'll need to set up the Sybase environment by sourcing ./sap/SYBASE.sh: . ./sap/SYBASE.sh Hope this helps, because I'm out of ideas. John > On Jan 26, 2017, at 8:56 PM, Igor Korot wrote: > > Hi, > I just installed Sybase ASE 16 Dev on my Linux box. > Now I'm trying to set up a connection using native Sybase ODBC > driver. However I have a hard time finding it. > > [code] > igor at IgorReinCloud /opt $ find . -name *odbc* > ./sap/DataAccess/bin/odbcversion > ./sap/DataAccess/ODBC/samples/odbcbatch > ./sap/DataAccess/ODBC/samples/odbcbatch/odbcbatch.cpp > ./sap/DataAccess/ODBC/samples/odbcloblocator > ./sap/DataAccess/ODBC/samples/odbcloblocator/odbcloblocator.cpp > ./sap/DataAccess/ODBC/sp/odbc_mda_120.sql > ./sap/DataAccess/ODBC/sp/odbc_mda_157.sql > ./sap/DataAccess/ODBC/sp/odbc_mda_1251.sql > ./sap/DataAccess/ODBC/sp/odbc_mda_1600000.sql > ./sap/DataAccess/ODBC/sp/install_odbc_sprocs > ./sap/DataAccess/ODBC/sp/odbc_mda_1570020.sql > ./sap/DataAccess/ODBC/sp/odbc_mda_125.sql > ./sap/DataAccess/ODBC/sp/odbc_mda_12503.sql > ./sap/DataAccess/ODBC/sp/odbc_mda_150.sql > ./sap/DataAccess/ODBC/sp/odbc_mda_1502.sql > ./sap/DBISQL-16_0/lib/jodbc4.jar > ./sap/DBISQL-16_0/bin/libdbodbc16_r.so.1 > ./sap/DBISQL-16_0/bin/libdbodbc16_r.so > ./sap/DBISQL-16_0/bin/libdbjodbc16.so.1 > ./sap/DBISQL-16_0/bin/libdbjodbc16.so > ./sap/ASE-16_0/lib/pca/libPCAodbc.so > ./sap/ASE-16_0/symlib/pca/libPCAodbc.so > ./sap/COCKPIT-4/bin/sa16/linux64/java/jodbc4.jar > ./sap/COCKPIT-4/bin/sa16/linux64/lib64/libdbodbc16_r.so > ./sap/COCKPIT-4/bin/sa16/linux64/lib64/libdbodbc16.so > ./sap/COCKPIT-4/bin/sa16/linux64/lib64/libdbjodbc16.so > ./sap/log/odbc.log > ./sap/log/odbc.lst > ./sap/DataAccess64/bin/odbcversion > ./sap/DataAccess64/ODBC/dm/include/unixodbc.h > ./sap/DataAccess64/ODBC/dm/include/odbc.h > ./sap/DataAccess64/ODBC/dm/include/saodbc.h > ./sap/DataAccess64/ODBC/dm/lib64/libodbc.so > ./sap/DataAccess64/ODBC/samples/odbcbatch > ./sap/DataAccess64/ODBC/samples/odbcbatch/odbcbatch.cpp > ./sap/DataAccess64/ODBC/samples/odbcloblocator > ./sap/DataAccess64/ODBC/samples/odbcloblocator/odbcloblocator.cpp > ./sap/DataAccess64/ODBC/sp/odbc_mda_120.sql > ./sap/DataAccess64/ODBC/sp/odbc_mda_157.sql > ./sap/DataAccess64/ODBC/sp/odbc_mda_1251.sql > ./sap/DataAccess64/ODBC/sp/odbc_mda_1600000.sql > ./sap/DataAccess64/ODBC/sp/install_odbc_sprocs > ./sap/DataAccess64/ODBC/sp/odbc_mda_1570020.sql > ./sap/DataAccess64/ODBC/sp/odbc_mda_125.sql > ./sap/DataAccess64/ODBC/sp/odbc_mda_12503.sql > ./sap/DataAccess64/ODBC/sp/odbc_mda_150.sql > ./sap/DataAccess64/ODBC/sp/odbc_mda_1502.sql > [/code] > > Can anyone tell me which one is the Sybase ODBC driver? > > Thank you. > _______________________________________________ > FreeTDS mailing list > FreeTDS at lists.ibiblio.org > https://url.serverdata.net/?ajZrMdQ0VsbeE8kMpqNYWHDt8NhXcTl0gExF9FI8Y1QGyylx0yNkuUl4kfJBSC8Cf02PCfXwjnNlwUAw6zdbO8Q~~ > From zhangjie at beijing101.com Fri Jan 27 00:08:06 2017 From: zhangjie at beijing101.com (zhangjie at beijing101.com) Date: Fri, 27 Jan 2017 13:08:06 +0800 Subject: [freetds] Auto-Re: Where is the Sybase ODBC driver Message-ID: <170127130806a2eb2f35c875778dc5f36b59ce7b18c1@beijing101.com> ??????????????????????????? ?? From ikorot01 at gmail.com Tue Jan 31 17:49:50 2017 From: ikorot01 at gmail.com (Igor Korot) Date: Tue, 31 Jan 2017 14:49:50 -0800 Subject: [freetds] Where is the Sybase ODBC driver In-Reply-To: <1F262A0D-9889-49D9-8037-CE285C48EEB3@capps.com> References: <1F262A0D-9889-49D9-8037-CE285C48EEB3@capps.com> Message-ID: Hi, John, On Thu, Jan 26, 2017 at 9:42 PM, John Kendall wrote: > Igor, > > I think it's > > ./sap/DataAccess64/ODBC/lib/libsybdrvodb.so I put this in and tried to connect. Here are my configuration files: igor at IgorReinCloud ~/wxWidgets/buildGTK $ cat /etc/unixODBC/odbcinst.ini [ODBC] Trace=yes TraceFile=/tmp/sql.log Pooling=No [Sybase] Description=Sybase 16 Native Driver Driver=/opt/sap/DataAccess64/ODBC/lib/libsybdrvodb.so UsageCount=1 igor at IgorReinCloud ~/wxWidgets/buildGTK $ cat /etc/unixODBC/odbc.ini [ODBC Data Sources] Sybase 16 test=Sybase 16 ODBC driver [Sybase 16 test] Description=Sybase 16 Driver Testing DSN Driver=Sybase Port=5000 Server=localhost User=root Password=wasqra Database=draft Option=3 Trying to connect I got: igor at IgorReinCloud ~/wxWidgets/buildGTK $ /usr/bin/isql "Sybase 16 test" [ISQL]ERROR: Could not SQLConnect Checking the log file I see: [quote] [ODBC][16867][1485764524.804129][/var/tmp/portage/dev-db/unixODBC-2.3.2-r1/work/unixODBC-2.3.2/DriverManager/__handles.c][460] Exit:[SQL_SUCCESS] Environment = 0x2253750 [ODBC][16867][1485764524.804240][/var/tmp/portage/dev-db/unixODBC-2.3.2-r1/work/unixODBC-2.3.2/DriverManager/SQLAllocHandle.c][375] Entry: Handle Type = 2 Input Handle = 0x2253750 [ODBC][16867][1485764524.804288][/var/tmp/portage/dev-db/unixODBC-2.3.2-r1/work/unixODBC-2.3.2/DriverManager/SQLAllocHandle.c][493] Exit:[SQL_SUCCESS] Output Handle = 0x2254050 [ODBC][16867][1485764524.804334][/var/tmp/portage/dev-db/unixODBC-2.3.2-r1/work/unixODBC-2.3.2/DriverManager/SQLConnect.c][3727] Entry: Connection = 0x2254050 Server Name = [Sybase 16 test][length = 14 (SQL_NTS)] User Name = [NULL] Authentication = [NULL] UNICODE Using encoding ASCII 'UTF8' and UNICODE 'UTF16LE' DIAG [HY000] [SAP][ASE ODBC Driver]There is no server listening at localhost:5000. DIAG [08001] [SAP][ASE ODBC Driver]Client unable to establish a connection ]/quote] But it is here and listening: [code] IgorReinCloud / # netstat -nptl Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name tcp 0 0 127.0.0.1:4900 0.0.0.0:* LISTEN 6014/jsagent tcp 0 0 127.0.0.1:5000 0.0.0.0:* LISTEN 5979/dataserver tcp 0 0 0.0.0.0:139 0.0.0.0:* LISTEN 3491/smbd tcp 0 0 0.0.0.0:445 0.0.0.0:* LISTEN 3491/smbd tcp6 0 0 :::139 :::* LISTEN 3491/smbd tcp6 0 0 :::445 :::* LISTEN 3491/smbd [/code] So what I did wrong? Thank you. > > But for it to work, you'll need to set up the Sybase environment by sourcing ./sap/SYBASE.sh: > > . ./sap/SYBASE.sh > > Hope this helps, because I'm out of ideas. > John > > > > >> On Jan 26, 2017, at 8:56 PM, Igor Korot wrote: >> >> Hi, >> I just installed Sybase ASE 16 Dev on my Linux box. >> Now I'm trying to set up a connection using native Sybase ODBC >> driver. However I have a hard time finding it. >> >> [code] >> igor at IgorReinCloud /opt $ find . -name *odbc* >> ./sap/DataAccess/bin/odbcversion >> ./sap/DataAccess/ODBC/samples/odbcbatch >> ./sap/DataAccess/ODBC/samples/odbcbatch/odbcbatch.cpp >> ./sap/DataAccess/ODBC/samples/odbcloblocator >> ./sap/DataAccess/ODBC/samples/odbcloblocator/odbcloblocator.cpp >> ./sap/DataAccess/ODBC/sp/odbc_mda_120.sql >> ./sap/DataAccess/ODBC/sp/odbc_mda_157.sql >> ./sap/DataAccess/ODBC/sp/odbc_mda_1251.sql >> ./sap/DataAccess/ODBC/sp/odbc_mda_1600000.sql >> ./sap/DataAccess/ODBC/sp/install_odbc_sprocs >> ./sap/DataAccess/ODBC/sp/odbc_mda_1570020.sql >> ./sap/DataAccess/ODBC/sp/odbc_mda_125.sql >> ./sap/DataAccess/ODBC/sp/odbc_mda_12503.sql >> ./sap/DataAccess/ODBC/sp/odbc_mda_150.sql >> ./sap/DataAccess/ODBC/sp/odbc_mda_1502.sql >> ./sap/DBISQL-16_0/lib/jodbc4.jar >> ./sap/DBISQL-16_0/bin/libdbodbc16_r.so.1 >> ./sap/DBISQL-16_0/bin/libdbodbc16_r.so >> ./sap/DBISQL-16_0/bin/libdbjodbc16.so.1 >> ./sap/DBISQL-16_0/bin/libdbjodbc16.so >> ./sap/ASE-16_0/lib/pca/libPCAodbc.so >> ./sap/ASE-16_0/symlib/pca/libPCAodbc.so >> ./sap/COCKPIT-4/bin/sa16/linux64/java/jodbc4.jar >> ./sap/COCKPIT-4/bin/sa16/linux64/lib64/libdbodbc16_r.so >> ./sap/COCKPIT-4/bin/sa16/linux64/lib64/libdbodbc16.so >> ./sap/COCKPIT-4/bin/sa16/linux64/lib64/libdbjodbc16.so >> ./sap/log/odbc.log >> ./sap/log/odbc.lst >> ./sap/DataAccess64/bin/odbcversion >> ./sap/DataAccess64/ODBC/dm/include/unixodbc.h >> ./sap/DataAccess64/ODBC/dm/include/odbc.h >> ./sap/DataAccess64/ODBC/dm/include/saodbc.h >> ./sap/DataAccess64/ODBC/dm/lib64/libodbc.so >> ./sap/DataAccess64/ODBC/samples/odbcbatch >> ./sap/DataAccess64/ODBC/samples/odbcbatch/odbcbatch.cpp >> ./sap/DataAccess64/ODBC/samples/odbcloblocator >> ./sap/DataAccess64/ODBC/samples/odbcloblocator/odbcloblocator.cpp >> ./sap/DataAccess64/ODBC/sp/odbc_mda_120.sql >> ./sap/DataAccess64/ODBC/sp/odbc_mda_157.sql >> ./sap/DataAccess64/ODBC/sp/odbc_mda_1251.sql >> ./sap/DataAccess64/ODBC/sp/odbc_mda_1600000.sql >> ./sap/DataAccess64/ODBC/sp/install_odbc_sprocs >> ./sap/DataAccess64/ODBC/sp/odbc_mda_1570020.sql >> ./sap/DataAccess64/ODBC/sp/odbc_mda_125.sql >> ./sap/DataAccess64/ODBC/sp/odbc_mda_12503.sql >> ./sap/DataAccess64/ODBC/sp/odbc_mda_150.sql >> ./sap/DataAccess64/ODBC/sp/odbc_mda_1502.sql >> [/code] >> >> Can anyone tell me which one is the Sybase ODBC driver? >> >> Thank you. >> _______________________________________________ >> FreeTDS mailing list >> FreeTDS at lists.ibiblio.org >> https://url.serverdata.net/?ajZrMdQ0VsbeE8kMpqNYWHDt8NhXcTl0gExF9FI8Y1QGyylx0yNkuUl4kfJBSC8Cf02PCfXwjnNlwUAw6zdbO8Q~~ >> > > _______________________________________________ > FreeTDS mailing list > FreeTDS at lists.ibiblio.org > http://lists.ibiblio.org/mailman/listinfo/freetds From john at capps.com Tue Jan 31 18:41:25 2017 From: john at capps.com (John Kendall) Date: Tue, 31 Jan 2017 23:41:25 +0000 Subject: [freetds] Where is the Sybase ODBC driver In-Reply-To: References: <1F262A0D-9889-49D9-8037-CE285C48EEB3@capps.com> Message-ID: <2AA578F2-916B-4FEC-96FA-76B3A53FD99C@capps.com> Igor, In you odbc.ini file you need: UserID=root not User=root (You could also put your username and password on the command line.) /usr/bin/isql -v "Sybase 16 test" root wasqra Other than that, all I can think of is make sure you source the SYBASE environment and use isql's -v option to get more information. source /opt/sap/SYBASE.sh /usr/bin/isql -v "Sybase 16 test" root wasqra That's all I know. Really! John On Jan 31, 2017, at 2:49 PM, Igor Korot wrote: > Hi, John, > > On Thu, Jan 26, 2017 at 9:42 PM, John Kendall wrote: >> Igor, >> >> I think it's >> >> ./sap/DataAccess64/ODBC/lib/libsybdrvodb.so > > I put this in and tried to connect. Here are my configuration files: > > igor at IgorReinCloud ~/wxWidgets/buildGTK $ cat /etc/unixODBC/odbcinst.ini > [ODBC] > Trace=yes > TraceFile=/tmp/sql.log > Pooling=No > > [Sybase] > Description=Sybase 16 Native Driver > Driver=/opt/sap/DataAccess64/ODBC/lib/libsybdrvodb.so > UsageCount=1 > > igor at IgorReinCloud ~/wxWidgets/buildGTK $ cat /etc/unixODBC/odbc.ini > [ODBC Data Sources] > Sybase 16 test=Sybase 16 ODBC driver > > [Sybase 16 test] > Description=Sybase 16 Driver Testing DSN > Driver=Sybase > Port=5000 > Server=localhost > User=root > Password=wasqra > Database=draft > Option=3 > > Trying to connect I got: > > igor at IgorReinCloud ~/wxWidgets/buildGTK $ /usr/bin/isql "Sybase 16 test" > [ISQL]ERROR: Could not SQLConnect > > Checking the log file I see: > > [quote] > [ODBC][16867][1485764524.804129][/var/tmp/portage/dev-db/unixODBC-2.3.2-r1/work/unixODBC-2.3.2/DriverManager/__handles.c][460] > Exit:[SQL_SUCCESS] > Environment = 0x2253750 > [ODBC][16867][1485764524.804240][/var/tmp/portage/dev-db/unixODBC-2.3.2-r1/work/unixODBC-2.3.2/DriverManager/SQLAllocHandle.c][375] > Entry: > Handle Type = 2 > Input Handle = 0x2253750 > [ODBC][16867][1485764524.804288][/var/tmp/portage/dev-db/unixODBC-2.3.2-r1/work/unixODBC-2.3.2/DriverManager/SQLAllocHandle.c][493] > Exit:[SQL_SUCCESS] > Output Handle = 0x2254050 > [ODBC][16867][1485764524.804334][/var/tmp/portage/dev-db/unixODBC-2.3.2-r1/work/unixODBC-2.3.2/DriverManager/SQLConnect.c][3727] > Entry: > Connection = 0x2254050 > Server Name = [Sybase 16 test][length = 14 (SQL_NTS)] > User Name = [NULL] > Authentication = [NULL] > UNICODE Using encoding ASCII 'UTF8' and UNICODE 'UTF16LE' > > DIAG [HY000] [SAP][ASE ODBC Driver]There is no server > listening at localhost:5000. > > DIAG [08001] [SAP][ASE ODBC Driver]Client unable to establish > a connection > ]/quote] > > But it is here and listening: > > [code] > IgorReinCloud / # netstat -nptl > Active Internet connections (only servers) > Proto Recv-Q Send-Q Local Address Foreign Address > State PID/Program name > tcp 0 0 127.0.0.1:4900 0.0.0.0:* > LISTEN 6014/jsagent > tcp 0 0 127.0.0.1:5000 0.0.0.0:* > LISTEN 5979/dataserver > tcp 0 0 0.0.0.0:139 0.0.0.0:* > LISTEN 3491/smbd > tcp 0 0 0.0.0.0:445 0.0.0.0:* > LISTEN 3491/smbd > tcp6 0 0 :::139 :::* > LISTEN 3491/smbd > tcp6 0 0 :::445 :::* > LISTEN 3491/smbd > [/code] > > So what I did wrong? > > Thank you. > >> >> But for it to work, you'll need to set up the Sybase environment by sourcing ./sap/SYBASE.sh: >> >> . ./sap/SYBASE.sh >> >> Hope this helps, because I'm out of ideas. >> John >> >> >> >> >>> On Jan 26, 2017, at 8:56 PM, Igor Korot wrote: >>> >>> Hi, >>> I just installed Sybase ASE 16 Dev on my Linux box. >>> Now I'm trying to set up a connection using native Sybase ODBC >>> driver. However I have a hard time finding it. >>> >>> [code] >>> igor at IgorReinCloud /opt $ find . -name *odbc* >>> ./sap/DataAccess/bin/odbcversion >>> ./sap/DataAccess/ODBC/samples/odbcbatch >>> ./sap/DataAccess/ODBC/samples/odbcbatch/odbcbatch.cpp >>> ./sap/DataAccess/ODBC/samples/odbcloblocator >>> ./sap/DataAccess/ODBC/samples/odbcloblocator/odbcloblocator.cpp >>> ./sap/DataAccess/ODBC/sp/odbc_mda_120.sql >>> ./sap/DataAccess/ODBC/sp/odbc_mda_157.sql >>> ./sap/DataAccess/ODBC/sp/odbc_mda_1251.sql >>> ./sap/DataAccess/ODBC/sp/odbc_mda_1600000.sql >>> ./sap/DataAccess/ODBC/sp/install_odbc_sprocs >>> ./sap/DataAccess/ODBC/sp/odbc_mda_1570020.sql >>> ./sap/DataAccess/ODBC/sp/odbc_mda_125.sql >>> ./sap/DataAccess/ODBC/sp/odbc_mda_12503.sql >>> ./sap/DataAccess/ODBC/sp/odbc_mda_150.sql >>> ./sap/DataAccess/ODBC/sp/odbc_mda_1502.sql >>> ./sap/DBISQL-16_0/lib/jodbc4.jar >>> ./sap/DBISQL-16_0/bin/libdbodbc16_r.so.1 >>> ./sap/DBISQL-16_0/bin/libdbodbc16_r.so >>> ./sap/DBISQL-16_0/bin/libdbjodbc16.so.1 >>> ./sap/DBISQL-16_0/bin/libdbjodbc16.so >>> ./sap/ASE-16_0/lib/pca/libPCAodbc.so >>> ./sap/ASE-16_0/symlib/pca/libPCAodbc.so >>> ./sap/COCKPIT-4/bin/sa16/linux64/java/jodbc4.jar >>> ./sap/COCKPIT-4/bin/sa16/linux64/lib64/libdbodbc16_r.so >>> ./sap/COCKPIT-4/bin/sa16/linux64/lib64/libdbodbc16.so >>> ./sap/COCKPIT-4/bin/sa16/linux64/lib64/libdbjodbc16.so >>> ./sap/log/odbc.log >>> ./sap/log/odbc.lst >>> ./sap/DataAccess64/bin/odbcversion >>> ./sap/DataAccess64/ODBC/dm/include/unixodbc.h >>> ./sap/DataAccess64/ODBC/dm/include/odbc.h >>> ./sap/DataAccess64/ODBC/dm/include/saodbc.h >>> ./sap/DataAccess64/ODBC/dm/lib64/libodbc.so >>> ./sap/DataAccess64/ODBC/samples/odbcbatch >>> ./sap/DataAccess64/ODBC/samples/odbcbatch/odbcbatch.cpp >>> ./sap/DataAccess64/ODBC/samples/odbcloblocator >>> ./sap/DataAccess64/ODBC/samples/odbcloblocator/odbcloblocator.cpp >>> ./sap/DataAccess64/ODBC/sp/odbc_mda_120.sql >>> ./sap/DataAccess64/ODBC/sp/odbc_mda_157.sql >>> ./sap/DataAccess64/ODBC/sp/odbc_mda_1251.sql >>> ./sap/DataAccess64/ODBC/sp/odbc_mda_1600000.sql >>> ./sap/DataAccess64/ODBC/sp/install_odbc_sprocs >>> ./sap/DataAccess64/ODBC/sp/odbc_mda_1570020.sql >>> ./sap/DataAccess64/ODBC/sp/odbc_mda_125.sql >>> ./sap/DataAccess64/ODBC/sp/odbc_mda_12503.sql >>> ./sap/DataAccess64/ODBC/sp/odbc_mda_150.sql >>> ./sap/DataAccess64/ODBC/sp/odbc_mda_1502.sql >>> [/code] >>> >>> Can anyone tell me which one is the Sybase ODBC driver? >>> >>> Thank you. >>> _______________________________________________ >>> FreeTDS mailing list >>> FreeTDS at lists.ibiblio.org >>> https://url.serverdata.net/?ajZrMdQ0VsbeE8kMpqNYWHDt8NhXcTl0gExF9FI8Y1QGyylx0yNkuUl4kfJBSC8Cf02PCfXwjnNlwUAw6zdbO8Q~~ >>> >> >> _______________________________________________ >> FreeTDS mailing list >> FreeTDS at lists.ibiblio.org >> https://url.serverdata.net/?ajZrMdQ0VsbeE8kMpqNYWHDt8NhXcTl0gExF9FI8Y1QGyylx0yNkuUl4kfJBSC8Cf02PCfXwjnNlwUAw6zdbO8Q~~ > _______________________________________________ > FreeTDS mailing list > FreeTDS at lists.ibiblio.org > https://url.serverdata.net/?ajZrMdQ0VsbeE8kMpqNYWHDt8NhXcTl0gExF9FI8Y1QGyylx0yNkuUl4kfJBSC8Cf02PCfXwjnNlwUAw6zdbO8Q~~ > From matthew.green at datamartcomputing.com Wed Feb 1 02:50:26 2017 From: matthew.green at datamartcomputing.com (matthew.green at datamartcomputing.com) Date: Wed, 01 Feb 2017 07:50:26 +0000 Subject: [freetds] Where is the Sybase ODBC driver In-Reply-To: <2AA578F2-916B-4FEC-96FA-76B3A53FD99C@capps.com> References: <2AA578F2-916B-4FEC-96FA-76B3A53FD99C@capps.com> <1F262A0D-9889-49D9-8037-CE285C48EEB3@capps.com> Message-ID: <76d72c9d125c5b572972c71bfaabc4ea@datamartcomputing.com> You've probably done this already but just in case.... have you checked using Sybases isql that you can connect? Have you double checked that the server really is listening on the right port? To be absolutely certain you could look in syslisteners. Sorry to go back to basics but sometimes these things get overlooked. Cheers, Matthew. February 1 2017 12:41 AM, "John Kendall" wrote: > Igor, > > In you odbc.ini file you need: > > UserID=root > > not > > User=root > > (You could also put your username and password on the command line.) > > /usr/bin/isql -v "Sybase 16 test" root wasqra > > Other than that, all I can think of is make sure you source the SYBASE environment and use isql's > -v option to get more information. > > source /opt/sap/SYBASE.sh > /usr/bin/isql -v "Sybase 16 test" root wasqra > > That's all I know. Really! > > John > > On Jan 31, 2017, at 2:49 PM, Igor Korot wrote: > >> Hi, John, >> >> On Thu, Jan 26, 2017 at 9:42 PM, John Kendall wrote: >>> Igor, >>> >>> I think it's >>> >>> ./sap/DataAccess64/ODBC/lib/libsybdrvodb.so >> >> I put this in and tried to connect. Here are my configuration files: >> >> igor at IgorReinCloud ~/wxWidgets/buildGTK $ cat /etc/unixODBC/odbcinst.ini >> [ODBC] >> Trace=yes >> TraceFile=/tmp/sql.log >> Pooling=No >> >> [Sybase] >> Description=Sybase 16 Native Driver >> Driver=/opt/sap/DataAccess64/ODBC/lib/libsybdrvodb.so >> UsageCount=1 >> >> igor at IgorReinCloud ~/wxWidgets/buildGTK $ cat /etc/unixODBC/odbc.ini >> [ODBC Data Sources] >> Sybase 16 test=Sybase 16 ODBC driver >> >> [Sybase 16 test] >> Description=Sybase 16 Driver Testing DSN >> Driver=Sybase >> Port=5000 >> Server=localhost >> User=root >> Password=wasqra >> Database=draft >> Option=3 >> >> Trying to connect I got: >> >> igor at IgorReinCloud ~/wxWidgets/buildGTK $ /usr/bin/isql "Sybase 16 test" >> [ISQL]ERROR: Could not SQLConnect >> >> Checking the log file I see: >> >> [quote] >> > [ODBC][16867][1485764524.804129][/var/tmp/portage/dev-db/unixODBC-2.3.2-r1/work/unixODBC-2.3.2/Drive >> Manager/__handles.c][460] >> Exit:[SQL_SUCCESS] >> Environment = 0x2253750 >> > [ODBC][16867][1485764524.804240][/var/tmp/portage/dev-db/unixODBC-2.3.2-r1/work/unixODBC-2.3.2/Drive >> Manager/SQLAllocHandle.c][375] >> Entry: >> Handle Type = 2 >> Input Handle = 0x2253750 >> > [ODBC][16867][1485764524.804288][/var/tmp/portage/dev-db/unixODBC-2.3.2-r1/work/unixODBC-2.3.2/Drive >> Manager/SQLAllocHandle.c][493] >> Exit:[SQL_SUCCESS] >> Output Handle = 0x2254050 >> > [ODBC][16867][1485764524.804334][/var/tmp/portage/dev-db/unixODBC-2.3.2-r1/work/unixODBC-2.3.2/Drive >> Manager/SQLConnect.c][3727] >> Entry: >> Connection = 0x2254050 >> Server Name = [Sybase 16 test][length = 14 (SQL_NTS)] >> User Name = [NULL] >> Authentication = [NULL] >> UNICODE Using encoding ASCII 'UTF8' and UNICODE 'UTF16LE' >> >> DIAG [HY000] [SAP][ASE ODBC Driver]There is no server >> listening at localhost:5000. >> >> DIAG [08001] [SAP][ASE ODBC Driver]Client unable to establish >> a connection >> ]/quote] >> >> But it is here and listening: >> >> [code] >> IgorReinCloud / # netstat -nptl >> Active Internet connections (only servers) >> Proto Recv-Q Send-Q Local Address Foreign Address >> State PID/Program name >> tcp 0 0 127.0.0.1:4900 0.0.0.0:* >> LISTEN 6014/jsagent >> tcp 0 0 127.0.0.1:5000 0.0.0.0:* >> LISTEN 5979/dataserver >> tcp 0 0 0.0.0.0:139 0.0.0.0:* >> LISTEN 3491/smbd >> tcp 0 0 0.0.0.0:445 0.0.0.0:* >> LISTEN 3491/smbd >> tcp6 0 0 :::139 :::* >> LISTEN 3491/smbd >> tcp6 0 0 :::445 :::* >> LISTEN 3491/smbd >> [/code] >> >> So what I did wrong? >> >> Thank you. >> >>> But for it to work, you'll need to set up the Sybase environment by sourcing ./sap/SYBASE.sh: >>> >>> . ./sap/SYBASE.sh >>> >>> Hope this helps, because I'm out of ideas. >>> John >>> >>>> On Jan 26, 2017, at 8:56 PM, Igor Korot wrote: >>>> >>>> Hi, >>>> I just installed Sybase ASE 16 Dev on my Linux box. >>>> Now I'm trying to set up a connection using native Sybase ODBC >>>> driver. However I have a hard time finding it. >>>> >>>> [code] >>>> igor at IgorReinCloud /opt $ find . -name *odbc* >>>> ./sap/DataAccess/bin/odbcversion >>>> ./sap/DataAccess/ODBC/samples/odbcbatch >>>> ./sap/DataAccess/ODBC/samples/odbcbatch/odbcbatch.cpp >>>> ./sap/DataAccess/ODBC/samples/odbcloblocator >>>> ./sap/DataAccess/ODBC/samples/odbcloblocator/odbcloblocator.cpp >>>> ./sap/DataAccess/ODBC/sp/odbc_mda_120.sql >>>> ./sap/DataAccess/ODBC/sp/odbc_mda_157.sql >>>> ./sap/DataAccess/ODBC/sp/odbc_mda_1251.sql >>>> ./sap/DataAccess/ODBC/sp/odbc_mda_1600000.sql >>>> ./sap/DataAccess/ODBC/sp/install_odbc_sprocs >>>> ./sap/DataAccess/ODBC/sp/odbc_mda_1570020.sql >>>> ./sap/DataAccess/ODBC/sp/odbc_mda_125.sql >>>> ./sap/DataAccess/ODBC/sp/odbc_mda_12503.sql >>>> ./sap/DataAccess/ODBC/sp/odbc_mda_150.sql >>>> ./sap/DataAccess/ODBC/sp/odbc_mda_1502.sql >>>> ./sap/DBISQL-16_0/lib/jodbc4.jar >>>> ./sap/DBISQL-16_0/bin/libdbodbc16_r.so.1 >>>> ./sap/DBISQL-16_0/bin/libdbodbc16_r.so >>>> ./sap/DBISQL-16_0/bin/libdbjodbc16.so.1 >>>> ./sap/DBISQL-16_0/bin/libdbjodbc16.so >>>> ./sap/ASE-16_0/lib/pca/libPCAodbc.so >>>> ./sap/ASE-16_0/symlib/pca/libPCAodbc.so >>>> ./sap/COCKPIT-4/bin/sa16/linux64/java/jodbc4.jar >>>> ./sap/COCKPIT-4/bin/sa16/linux64/lib64/libdbodbc16_r.so >>>> ./sap/COCKPIT-4/bin/sa16/linux64/lib64/libdbodbc16.so >>>> ./sap/COCKPIT-4/bin/sa16/linux64/lib64/libdbjodbc16.so >>>> ./sap/log/odbc.log >>>> ./sap/log/odbc.lst >>>> ./sap/DataAccess64/bin/odbcversion >>>> ./sap/DataAccess64/ODBC/dm/include/unixodbc.h >>>> ./sap/DataAccess64/ODBC/dm/include/odbc.h >>>> ./sap/DataAccess64/ODBC/dm/include/saodbc.h >>>> ./sap/DataAccess64/ODBC/dm/lib64/libodbc.so >>>> ./sap/DataAccess64/ODBC/samples/odbcbatch >>>> ./sap/DataAccess64/ODBC/samples/odbcbatch/odbcbatch.cpp >>>> ./sap/DataAccess64/ODBC/samples/odbcloblocator >>>> ./sap/DataAccess64/ODBC/samples/odbcloblocator/odbcloblocator.cpp >>>> ./sap/DataAccess64/ODBC/sp/odbc_mda_120.sql >>>> ./sap/DataAccess64/ODBC/sp/odbc_mda_157.sql >>>> ./sap/DataAccess64/ODBC/sp/odbc_mda_1251.sql >>>> ./sap/DataAccess64/ODBC/sp/odbc_mda_1600000.sql >>>> ./sap/DataAccess64/ODBC/sp/install_odbc_sprocs >>>> ./sap/DataAccess64/ODBC/sp/odbc_mda_1570020.sql >>>> ./sap/DataAccess64/ODBC/sp/odbc_mda_125.sql >>>> ./sap/DataAccess64/ODBC/sp/odbc_mda_12503.sql >>>> ./sap/DataAccess64/ODBC/sp/odbc_mda_150.sql >>>> ./sap/DataAccess64/ODBC/sp/odbc_mda_1502.sql >>>> [/code] >>>> >>>> Can anyone tell me which one is the Sybase ODBC driver? >>>> >>>> Thank you. >>>> _______________________________________________ >>>> FreeTDS mailing list >>>> FreeTDS at lists.ibiblio.org >>>> >>> >> > https://url.serverdata.net/?ajZrMdQ0VsbeE8kMpqNYWHDt8NhXcTl0gExF9FI8Y1QGyylx0yNkuUl4kfJBSC8Cf02PCfXw >>>> nNlwUAw6zdbO8Q~~ >>> >>> _______________________________________________ >>> FreeTDS mailing list >>> FreeTDS at lists.ibiblio.org >>> >> > https://url.serverdata.net/?ajZrMdQ0VsbeE8kMpqNYWHDt8NhXcTl0gExF9FI8Y1QGyylx0yNkuUl4kfJBSC8Cf02PCfXw >>> nNlwUAw6zdbO8Q~~ >> >> _______________________________________________ >> FreeTDS mailing list >> FreeTDS at lists.ibiblio.org >> > https://url.serverdata.net/?ajZrMdQ0VsbeE8kMpqNYWHDt8NhXcTl0gExF9FI8Y1QGyylx0yNkuUl4kfJBSC8Cf02PCfXw >> nNlwUAw6zdbO8Q~~ > > _______________________________________________ > FreeTDS mailing list > FreeTDS at lists.ibiblio.org > http://lists.ibiblio.org/mailman/listinfo/freetds From ikorot01 at gmail.com Wed Feb 1 18:57:33 2017 From: ikorot01 at gmail.com (Igor Korot) Date: Wed, 1 Feb 2017 18:57:33 -0500 Subject: [freetds] Where is the Sybase ODBC driver In-Reply-To: <76d72c9d125c5b572972c71bfaabc4ea@datamartcomputing.com> References: <1F262A0D-9889-49D9-8037-CE285C48EEB3@capps.com> <2AA578F2-916B-4FEC-96FA-76B3A53FD99C@capps.com> <76d72c9d125c5b572972c71bfaabc4ea@datamartcomputing.com> Message-ID: Hi, Matthew et al, On Wed, Feb 1, 2017 at 2:50 AM, wrote: > You've probably done this already but just in case.... have you checked using Sybases isql that you can connect? Have you double checked that the server really is listening on the right port? To be absolutely certain you could look in syslisteners. > > Sorry to go back to basics but sometimes these things get overlooked. Problem is solved. Apparently the culprit is line "Server=localhost". After setting it to the actual host name (Sybase by default set the server name to be the same as a host name) I moved further. Thank you. > > Cheers, > > Matthew. > > February 1 2017 12:41 AM, "John Kendall" wrote: >> Igor, >> >> In you odbc.ini file you need: >> >> UserID=root >> >> not >> >> User=root >> >> (You could also put your username and password on the command line.) >> >> /usr/bin/isql -v "Sybase 16 test" root wasqra >> >> Other than that, all I can think of is make sure you source the SYBASE environment and use isql's >> -v option to get more information. >> >> source /opt/sap/SYBASE.sh >> /usr/bin/isql -v "Sybase 16 test" root wasqra >> >> That's all I know. Really! >> >> John >> >> On Jan 31, 2017, at 2:49 PM, Igor Korot wrote: >> >>> Hi, John, >>> >>> On Thu, Jan 26, 2017 at 9:42 PM, John Kendall wrote: >>>> Igor, >>>> >>>> I think it's >>>> >>>> ./sap/DataAccess64/ODBC/lib/libsybdrvodb.so >>> >>> I put this in and tried to connect. Here are my configuration files: >>> >>> igor at IgorReinCloud ~/wxWidgets/buildGTK $ cat /etc/unixODBC/odbcinst.ini >>> [ODBC] >>> Trace=yes >>> TraceFile=/tmp/sql.log >>> Pooling=No >>> >>> [Sybase] >>> Description=Sybase 16 Native Driver >>> Driver=/opt/sap/DataAccess64/ODBC/lib/libsybdrvodb.so >>> UsageCount=1 >>> >>> igor at IgorReinCloud ~/wxWidgets/buildGTK $ cat /etc/unixODBC/odbc.ini >>> [ODBC Data Sources] >>> Sybase 16 test=Sybase 16 ODBC driver >>> >>> [Sybase 16 test] >>> Description=Sybase 16 Driver Testing DSN >>> Driver=Sybase >>> Port=5000 >>> Server=localhost >>> User=root >>> Password=wasqra >>> Database=draft >>> Option=3 >>> >>> Trying to connect I got: >>> >>> igor at IgorReinCloud ~/wxWidgets/buildGTK $ /usr/bin/isql "Sybase 16 test" >>> [ISQL]ERROR: Could not SQLConnect >>> >>> Checking the log file I see: >>> >>> [quote] >>> >> [ODBC][16867][1485764524.804129][/var/tmp/portage/dev-db/unixODBC-2.3.2-r1/work/unixODBC-2.3.2/Drive >>> Manager/__handles.c][460] >>> Exit:[SQL_SUCCESS] >>> Environment = 0x2253750 >>> >> [ODBC][16867][1485764524.804240][/var/tmp/portage/dev-db/unixODBC-2.3.2-r1/work/unixODBC-2.3.2/Drive >>> Manager/SQLAllocHandle.c][375] >>> Entry: >>> Handle Type = 2 >>> Input Handle = 0x2253750 >>> >> [ODBC][16867][1485764524.804288][/var/tmp/portage/dev-db/unixODBC-2.3.2-r1/work/unixODBC-2.3.2/Drive >>> Manager/SQLAllocHandle.c][493] >>> Exit:[SQL_SUCCESS] >>> Output Handle = 0x2254050 >>> >> [ODBC][16867][1485764524.804334][/var/tmp/portage/dev-db/unixODBC-2.3.2-r1/work/unixODBC-2.3.2/Drive >>> Manager/SQLConnect.c][3727] >>> Entry: >>> Connection = 0x2254050 >>> Server Name = [Sybase 16 test][length = 14 (SQL_NTS)] >>> User Name = [NULL] >>> Authentication = [NULL] >>> UNICODE Using encoding ASCII 'UTF8' and UNICODE 'UTF16LE' >>> >>> DIAG [HY000] [SAP][ASE ODBC Driver]There is no server >>> listening at localhost:5000. >>> >>> DIAG [08001] [SAP][ASE ODBC Driver]Client unable to establish >>> a connection >>> ]/quote] >>> >>> But it is here and listening: >>> >>> [code] >>> IgorReinCloud / # netstat -nptl >>> Active Internet connections (only servers) >>> Proto Recv-Q Send-Q Local Address Foreign Address >>> State PID/Program name >>> tcp 0 0 127.0.0.1:4900 0.0.0.0:* >>> LISTEN 6014/jsagent >>> tcp 0 0 127.0.0.1:5000 0.0.0.0:* >>> LISTEN 5979/dataserver >>> tcp 0 0 0.0.0.0:139 0.0.0.0:* >>> LISTEN 3491/smbd >>> tcp 0 0 0.0.0.0:445 0.0.0.0:* >>> LISTEN 3491/smbd >>> tcp6 0 0 :::139 :::* >>> LISTEN 3491/smbd >>> tcp6 0 0 :::445 :::* >>> LISTEN 3491/smbd >>> [/code] >>> >>> So what I did wrong? >>> >>> Thank you. >>> >>>> But for it to work, you'll need to set up the Sybase environment by sourcing ./sap/SYBASE.sh: >>>> >>>> . ./sap/SYBASE.sh >>>> >>>> Hope this helps, because I'm out of ideas. >>>> John >>>> >>>>> On Jan 26, 2017, at 8:56 PM, Igor Korot wrote: >>>>> >>>>> Hi, >>>>> I just installed Sybase ASE 16 Dev on my Linux box. >>>>> Now I'm trying to set up a connection using native Sybase ODBC >>>>> driver. However I have a hard time finding it. >>>>> >>>>> [code] >>>>> igor at IgorReinCloud /opt $ find . -name *odbc* >>>>> ./sap/DataAccess/bin/odbcversion >>>>> ./sap/DataAccess/ODBC/samples/odbcbatch >>>>> ./sap/DataAccess/ODBC/samples/odbcbatch/odbcbatch.cpp >>>>> ./sap/DataAccess/ODBC/samples/odbcloblocator >>>>> ./sap/DataAccess/ODBC/samples/odbcloblocator/odbcloblocator.cpp >>>>> ./sap/DataAccess/ODBC/sp/odbc_mda_120.sql >>>>> ./sap/DataAccess/ODBC/sp/odbc_mda_157.sql >>>>> ./sap/DataAccess/ODBC/sp/odbc_mda_1251.sql >>>>> ./sap/DataAccess/ODBC/sp/odbc_mda_1600000.sql >>>>> ./sap/DataAccess/ODBC/sp/install_odbc_sprocs >>>>> ./sap/DataAccess/ODBC/sp/odbc_mda_1570020.sql >>>>> ./sap/DataAccess/ODBC/sp/odbc_mda_125.sql >>>>> ./sap/DataAccess/ODBC/sp/odbc_mda_12503.sql >>>>> ./sap/DataAccess/ODBC/sp/odbc_mda_150.sql >>>>> ./sap/DataAccess/ODBC/sp/odbc_mda_1502.sql >>>>> ./sap/DBISQL-16_0/lib/jodbc4.jar >>>>> ./sap/DBISQL-16_0/bin/libdbodbc16_r.so.1 >>>>> ./sap/DBISQL-16_0/bin/libdbodbc16_r.so >>>>> ./sap/DBISQL-16_0/bin/libdbjodbc16.so.1 >>>>> ./sap/DBISQL-16_0/bin/libdbjodbc16.so >>>>> ./sap/ASE-16_0/lib/pca/libPCAodbc.so >>>>> ./sap/ASE-16_0/symlib/pca/libPCAodbc.so >>>>> ./sap/COCKPIT-4/bin/sa16/linux64/java/jodbc4.jar >>>>> ./sap/COCKPIT-4/bin/sa16/linux64/lib64/libdbodbc16_r.so >>>>> ./sap/COCKPIT-4/bin/sa16/linux64/lib64/libdbodbc16.so >>>>> ./sap/COCKPIT-4/bin/sa16/linux64/lib64/libdbjodbc16.so >>>>> ./sap/log/odbc.log >>>>> ./sap/log/odbc.lst >>>>> ./sap/DataAccess64/bin/odbcversion >>>>> ./sap/DataAccess64/ODBC/dm/include/unixodbc.h >>>>> ./sap/DataAccess64/ODBC/dm/include/odbc.h >>>>> ./sap/DataAccess64/ODBC/dm/include/saodbc.h >>>>> ./sap/DataAccess64/ODBC/dm/lib64/libodbc.so >>>>> ./sap/DataAccess64/ODBC/samples/odbcbatch >>>>> ./sap/DataAccess64/ODBC/samples/odbcbatch/odbcbatch.cpp >>>>> ./sap/DataAccess64/ODBC/samples/odbcloblocator >>>>> ./sap/DataAccess64/ODBC/samples/odbcloblocator/odbcloblocator.cpp >>>>> ./sap/DataAccess64/ODBC/sp/odbc_mda_120.sql >>>>> ./sap/DataAccess64/ODBC/sp/odbc_mda_157.sql >>>>> ./sap/DataAccess64/ODBC/sp/odbc_mda_1251.sql >>>>> ./sap/DataAccess64/ODBC/sp/odbc_mda_1600000.sql >>>>> ./sap/DataAccess64/ODBC/sp/install_odbc_sprocs >>>>> ./sap/DataAccess64/ODBC/sp/odbc_mda_1570020.sql >>>>> ./sap/DataAccess64/ODBC/sp/odbc_mda_125.sql >>>>> ./sap/DataAccess64/ODBC/sp/odbc_mda_12503.sql >>>>> ./sap/DataAccess64/ODBC/sp/odbc_mda_150.sql >>>>> ./sap/DataAccess64/ODBC/sp/odbc_mda_1502.sql >>>>> [/code] >>>>> >>>>> Can anyone tell me which one is the Sybase ODBC driver? >>>>> >>>>> Thank you. >>>>> _______________________________________________ >>>>> FreeTDS mailing list >>>>> FreeTDS at lists.ibiblio.org >>>>> >>>> >>> >> https://url.serverdata.net/?ajZrMdQ0VsbeE8kMpqNYWHDt8NhXcTl0gExF9FI8Y1QGyylx0yNkuUl4kfJBSC8Cf02PCfXw >>>>> nNlwUAw6zdbO8Q~~ >>>> >>>> _______________________________________________ >>>> FreeTDS mailing list >>>> FreeTDS at lists.ibiblio.org >>>> >>> >> https://url.serverdata.net/?ajZrMdQ0VsbeE8kMpqNYWHDt8NhXcTl0gExF9FI8Y1QGyylx0yNkuUl4kfJBSC8Cf02PCfXw >>>> nNlwUAw6zdbO8Q~~ >>> >>> _______________________________________________ >>> FreeTDS mailing list >>> FreeTDS at lists.ibiblio.org >>> >> https://url.serverdata.net/?ajZrMdQ0VsbeE8kMpqNYWHDt8NhXcTl0gExF9FI8Y1QGyylx0yNkuUl4kfJBSC8Cf02PCfXw >>> nNlwUAw6zdbO8Q~~ >> >> _______________________________________________ >> FreeTDS mailing list >> FreeTDS at lists.ibiblio.org >> http://lists.ibiblio.org/mailman/listinfo/freetds > _______________________________________________ > FreeTDS mailing list > FreeTDS at lists.ibiblio.org > http://lists.ibiblio.org/mailman/listinfo/freetds From lacak at zoznam.sk Mon Feb 6 02:34:00 2017 From: lacak at zoznam.sk (LacaK) Date: Mon, 6 Feb 2017 08:34:00 +0100 Subject: [freetds] Trusted authentication with TDS 7.3 fails Message-ID: <332004cf-b8bc-9ed7-1352-bfb27fbffb20@zoznam.sk> Hi, I am trying connect to MS SQL Server 2016 Express using FreeTDS db-lib. I have compiled db-lib myself from 1.00.11 sources with #define HAVE_SSPI 1 (I do NOT define HAVE_OPENSSL) I can successfuly connect using standard authentication (supplied user name and password). I can successfuly connect also using empty user name and password (Trusted authentication), but only if I set TDS version to 7.1 (freetds71.log). When I change TDS version to 7.3 I can not connect (with error message "Adaptive server connection failed") (freetds73a.log). When I use precompiled DLL from appveyor (which requires OpenSSL: ssleay32.dll and libeay32.dll) I also can NOT connect with TDS 7.3 (freetds73b.log). See please attached logs. Any idea why NTLM authentication with TDS 7.3 does not work ? (I have tried also adding "use ntlmv2 = yes" to FreeTDS.conf, but does not seems to help) Thanks -Laco. -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: freetds71.log URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: freetds73a.log URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: freetds73b.log URL: From freddy77 at gmail.com Mon Feb 6 03:57:49 2017 From: freddy77 at gmail.com (Frediano Ziglio) Date: Mon, 6 Feb 2017 08:57:49 +0000 Subject: [freetds] Trusted authentication with TDS 7.3 fails In-Reply-To: <332004cf-b8bc-9ed7-1352-bfb27fbffb20@zoznam.sk> References: <332004cf-b8bc-9ed7-1352-bfb27fbffb20@zoznam.sk> Message-ID: 2017-02-06 7:34 GMT+00:00 LacaK : > Hi, > > I am trying connect to MS SQL Server 2016 Express using FreeTDS db-lib. > > I have compiled db-lib myself from 1.00.11 sources with #define HAVE_SSPI 1 > (I do NOT define HAVE_OPENSSL) > > I can successfuly connect using standard authentication (supplied user name > and password). > > I can successfuly connect also using empty user name and password (Trusted > authentication), but only if I set TDS version to 7.1 (freetds71.log). > > When I change TDS version to 7.3 I can not connect (with error message > "Adaptive server connection failed") (freetds73a.log). > > When I use precompiled DLL from appveyor (which requires OpenSSL: > ssleay32.dll and libeay32.dll) I also can NOT connect with TDS 7.3 > (freetds73b.log). > > See please attached logs. > > Any idea why NTLM authentication with TDS 7.3 does not work ? > (I have tried also adding "use ntlmv2 = yes" to FreeTDS.conf, but does not > seems to help) > > Thanks > > -Laco. > In tds_sspi_handle_next there are these lines: if (len < 32) return TDS_FAIL; can you try to replace 32 with 16 ? I cannot find any place where this restriction apply and server is sendind 0x1d (29) bytes of data. Maybe this restriction was just for NTLM (make sense the same test in tds_ntlm_handle_next). Frediano From lacak at zoznam.sk Mon Feb 6 04:14:57 2017 From: lacak at zoznam.sk (LacaK) Date: Mon, 6 Feb 2017 10:14:57 +0100 Subject: [freetds] Trusted authentication with TDS 7.3 fails In-Reply-To: References: <332004cf-b8bc-9ed7-1352-bfb27fbffb20@zoznam.sk> Message-ID: <10299b33-5219-8712-e2fb-258bd197e267@zoznam.sk> >> I am trying connect to MS SQL Server 2016 Express using FreeTDS db-lib. >> >> I have compiled db-lib myself from 1.00.11 sources with #define HAVE_SSPI 1 >> (I do NOT define HAVE_OPENSSL) >> >> I can successfuly connect using standard authentication (supplied user name >> and password). >> >> I can successfuly connect also using empty user name and password (Trusted >> authentication), but only if I set TDS version to 7.1 (freetds71.log). >> >> When I change TDS version to 7.3 I can not connect (with error message >> "Adaptive server connection failed") (freetds73a.log). >> >> When I use precompiled DLL from appveyor (which requires OpenSSL: >> ssleay32.dll and libeay32.dll) I also can NOT connect with TDS 7.3 >> (freetds73b.log). >> >> See please attached logs. >> >> Any idea why NTLM authentication with TDS 7.3 does not work ? >> (I have tried also adding "use ntlmv2 = yes" to FreeTDS.conf, but does not >> seems to help) >> >> Thanks >> >> -Laco. >> > In tds_sspi_handle_next there are these lines: > > if (len < 32) > return TDS_FAIL; > > can you try to replace 32 with 16 ? Yes when I change 32 to 16 all works as expected ... :-) Thank you very much. May be, that you will commit it also to master branch ? -Laco. From freddy77 at gmail.com Mon Feb 6 09:30:39 2017 From: freddy77 at gmail.com (Frediano Ziglio) Date: Mon, 6 Feb 2017 14:30:39 +0000 Subject: [freetds] Trusted authentication with TDS 7.3 fails In-Reply-To: <10299b33-5219-8712-e2fb-258bd197e267@zoznam.sk> References: <332004cf-b8bc-9ed7-1352-bfb27fbffb20@zoznam.sk> <10299b33-5219-8712-e2fb-258bd197e267@zoznam.sk> Message-ID: 2017-02-06 9:14 GMT+00:00 LacaK : > >>> I am trying connect to MS SQL Server 2016 Express using FreeTDS db-lib. >>> >>> I have compiled db-lib myself from 1.00.11 sources with #define HAVE_SSPI >>> 1 >>> (I do NOT define HAVE_OPENSSL) >>> >>> I can successfuly connect using standard authentication (supplied user >>> name >>> and password). >>> >>> I can successfuly connect also using empty user name and password >>> (Trusted >>> authentication), but only if I set TDS version to 7.1 (freetds71.log). >>> >>> When I change TDS version to 7.3 I can not connect (with error message >>> "Adaptive server connection failed") (freetds73a.log). >>> >>> When I use precompiled DLL from appveyor (which requires OpenSSL: >>> ssleay32.dll and libeay32.dll) I also can NOT connect with TDS 7.3 >>> (freetds73b.log). >>> >>> See please attached logs. >>> >>> Any idea why NTLM authentication with TDS 7.3 does not work ? >>> (I have tried also adding "use ntlmv2 = yes" to FreeTDS.conf, but does >>> not >>> seems to help) >>> >>> Thanks >>> >>> -Laco. >>> >> In tds_sspi_handle_next there are these lines: >> >> if (len < 32) >> return TDS_FAIL; >> >> can you try to replace 32 with 16 ? > > Yes when I change 32 to 16 all works as expected ... :-) > Thank you very much. May be, that you will commit it also to master branch ? > -Laco. > Sure. Question is mainly if I should remove the check or which number to put. Maybe 1 ? I really think the check was just a copy&paste from NTLM. Frediano From lacak at zoznam.sk Tue Feb 7 02:52:57 2017 From: lacak at zoznam.sk (LacaK) Date: Tue, 7 Feb 2017 08:52:57 +0100 Subject: [freetds] Trusted authentication with TDS 7.3 fails In-Reply-To: References: <332004cf-b8bc-9ed7-1352-bfb27fbffb20@zoznam.sk> <10299b33-5219-8712-e2fb-258bd197e267@zoznam.sk> Message-ID: <86f5f7e0-adc4-635d-1684-af3d5db7eff2@zoznam.sk> D?a 6.2.2017 o 15:30 Frediano Ziglio nap?sal(a): >>>> I am trying connect to MS SQL Server 2016 Express using FreeTDS db-lib. >>>> >>>> I have compiled db-lib myself from 1.00.11 sources with #define HAVE_SSPI >>>> 1 >>>> (I do NOT define HAVE_OPENSSL) >>>> >>>> I can successfuly connect using standard authentication (supplied user >>>> name >>>> and password). >>>> >>>> I can successfuly connect also using empty user name and password >>>> (Trusted >>>> authentication), but only if I set TDS version to 7.1 (freetds71.log). >>>> >>>> When I change TDS version to 7.3 I can not connect (with error message >>>> "Adaptive server connection failed") (freetds73a.log). >>>> >>>> When I use precompiled DLL from appveyor (which requires OpenSSL: >>>> ssleay32.dll and libeay32.dll) I also can NOT connect with TDS 7.3 >>>> (freetds73b.log). >>>> >>>> See please attached logs. >>>> >>>> Any idea why NTLM authentication with TDS 7.3 does not work ? >>>> (I have tried also adding "use ntlmv2 = yes" to FreeTDS.conf, but does >>>> not >>>> seems to help) >>>> >>>> Thanks >>>> >>>> -Laco. >>>> >>> In tds_sspi_handle_next there are these lines: >>> >>> if (len < 32) >>> return TDS_FAIL; >>> >>> can you try to replace 32 with 16 ? >> Yes when I change 32 to 16 all works as expected ... :-) >> Thank you very much. May be, that you will commit it also to master branch ? >> -Laco. >> > > Sure. Question is mainly if I should remove the check or which number > to put. Maybe 1 ? Unfortunately I cannot advise, because my knowledge about SSPI is equal zero ;-) But I guess, that SSPI is generic API which can support various providers, so packet data structure/length depends on provider (authentification mechanism) used. I have no idea what can be minimal length, but 1 is for sure minimum ;-) Thank you for the commit ... -Laco. From sfhacker at hotmail.com Tue Feb 7 06:36:49 2017 From: sfhacker at hotmail.com (Sergio NNX) Date: Tue, 7 Feb 2017 11:36:49 +0000 Subject: [freetds] Trusted authentication with TDS 7.3 fails In-Reply-To: <86f5f7e0-adc4-635d-1684-af3d5db7eff2@zoznam.sk> References: <332004cf-b8bc-9ed7-1352-bfb27fbffb20@zoznam.sk> <10299b33-5219-8712-e2fb-258bd197e267@zoznam.sk> , <86f5f7e0-adc4-635d-1684-af3d5db7eff2@zoznam.sk> Message-ID: > But I guess, that SSPI is generic API which can support various > providers, so packet data structure/length depends on provider > (authentification mechanism) used. I haven't looked at the code, but ... is it the min value the code needs? Apparently, it should be 12 bytes for NTLMv1. > Question is mainly if I should remove the check or which number to put. Maybe 1 ? I do not know much about the internals of SSPI, but I wouldn't remove the check . From nikhil6018 at gmail.com Sat Feb 11 00:11:48 2017 From: nikhil6018 at gmail.com (nik mur) Date: Sat, 11 Feb 2017 05:11:48 +0000 Subject: [freetds] Unable to compile Freetds with OpenSSL 1.1.X Message-ID: This my first message to the list, very happy to do so. While compiling freetds with OpenSSL 1.1.0d I am receiving the following errors which I am unable to debug or make sense even after googling for hours Here is the error string (i am really sorry but the error string is very long) : tls.c: In function 'tds_pull_func_login': tls.c:83: error: dereferencing pointer to incomplete type tls.c: In function 'tds_push_func_login': tls.c:114: error: dereferencing pointer to incomplete type tls.c: In function 'tds_pull_func': tls.c:126: error: dereferencing pointer to incomplete type tls.c: In function 'tds_push_func': tls.c:149: error: dereferencing pointer to incomplete type tls.c: In function 'tds_ssl_ctrl_login': tls.c:551: error: dereferencing pointer to incomplete type --------------------------------------------------------------- tls.c:569: error: variable 'tds_method_login' has initializer but incomplete type tls.c:571: warning: excess elements in struct initializer tls.c:571: warning: (near initialization for 'tds_method_login') --------------------------------------------------------------- tls.c:580: warning: (near initialization for 'tds_method_login') tls.c:583: error: variable 'tds_method' has initializer but incomplete type ---------------------------------------------------------------- tls.c: In function 'tds_init_openssl': tls.c:611: warning: 'TLSv1_client_method' is deprecated (declared at /usr/local/apps/include/openssl/ssl.h:1598) tls.c: In function 'check_alt_names': tls.c:747: warning: 'ASN1_STRING_data' is deprecated (declared at /usr/local/apps/include/openssl/asn1.h:553) tls.c: In function 'tds_ssl_init': ---------------------------------------------------------------- tls.c:887: error: dereferencing pointer to incomplete type tls.c:887: error: 'SSL_ST_OK' undeclared (first use in this function) tls.c:887: error: (Each undeclared identifier is reported only once tls.c:887: error: for each function it appears in.) ---------------------------------------------------------------- In case if something is wrong with my configure command you can check it below : LDFLAGS="-L$PPS_PATH/lib" CPPFLAGS="-I$PPS_PATH/include" ./configure --prefix=$PPS_PATH \ --enable-shared \ --with-libiconv-prefix=$PPS_PATH \ --with-openssl=$PPS_PATH && make && make install >> $LOG 2>&1 Also you can check my openssl configure command below : LDFLAGS="-L$PPS_PATH/lib" CPPFLAGS="-I$PPS_PATH/include" ./config --prefix=$PPS_PATH \ --openssldir=$PPS_PATH/etc/openssl shared && make && make install >> $LOG 2>&1 From freddy77 at gmail.com Sat Feb 11 09:09:44 2017 From: freddy77 at gmail.com (Frediano Ziglio) Date: Sat, 11 Feb 2017 14:09:44 +0000 Subject: [freetds] Unable to compile Freetds with OpenSSL 1.1.X In-Reply-To: References: Message-ID: 2017-02-11 5:11 GMT+00:00 nik mur : > This my first message to the list, very happy to do so. > > While compiling freetds with OpenSSL 1.1.0d I am receiving the following > errors which I am unable to debug or make sense even after googling for > hours > > Here is the error string (i am really sorry but the error string is very > long) : > > tls.c: In function 'tds_pull_func_login': > tls.c:83: error: dereferencing pointer to incomplete type > tls.c: In function 'tds_push_func_login': > tls.c:114: error: dereferencing pointer to incomplete type > tls.c: In function 'tds_pull_func': > tls.c:126: error: dereferencing pointer to incomplete type > tls.c: In function 'tds_push_func': > tls.c:149: error: dereferencing pointer to incomplete type > tls.c: In function 'tds_ssl_ctrl_login': > tls.c:551: error: dereferencing pointer to incomplete type > --------------------------------------------------------------- > tls.c:569: error: variable 'tds_method_login' has initializer but > incomplete type > tls.c:571: warning: excess elements in struct initializer > tls.c:571: warning: (near initialization for 'tds_method_login') > --------------------------------------------------------------- > tls.c:580: warning: (near initialization for 'tds_method_login') > tls.c:583: error: variable 'tds_method' has initializer but incomplete type > ---------------------------------------------------------------- > tls.c: In function 'tds_init_openssl': > tls.c:611: warning: 'TLSv1_client_method' is deprecated (declared at > /usr/local/apps/include/openssl/ssl.h:1598) > tls.c: In function 'check_alt_names': > tls.c:747: warning: 'ASN1_STRING_data' is deprecated (declared at > /usr/local/apps/include/openssl/asn1.h:553) > tls.c: In function 'tds_ssl_init': > ---------------------------------------------------------------- > tls.c:887: error: dereferencing pointer to incomplete type > tls.c:887: error: 'SSL_ST_OK' undeclared (first use in this function) > tls.c:887: error: (Each undeclared identifier is reported only once > tls.c:887: error: for each function it appears in.) > ---------------------------------------------------------------- > > In case if something is wrong with my configure command you can check it > below : > > LDFLAGS="-L$PPS_PATH/lib" CPPFLAGS="-I$PPS_PATH/include" ./configure > --prefix=$PPS_PATH \ > --enable-shared \ > --with-libiconv-prefix=$PPS_PATH \ > --with-openssl=$PPS_PATH && make && make install >> $LOG 2>&1 > > Also you can check my openssl configure command below : > > LDFLAGS="-L$PPS_PATH/lib" CPPFLAGS="-I$PPS_PATH/include" ./config > --prefix=$PPS_PATH \ > --openssldir=$PPS_PATH/etc/openssl shared && make && make install >> $LOG > 2>&1 Looks like they decided to entirely break the ABI from 1.0 to 1.1... Not impossible to solve, just tedious and take some time. One reason I prefer GnuTLS. Patches are welcome! Frediano From nikhil6018 at gmail.com Mon Feb 13 02:53:36 2017 From: nikhil6018 at gmail.com (nik mur) Date: Mon, 13 Feb 2017 07:53:36 +0000 Subject: [freetds] Unable to compile Freetds with OpenSSL 1.1.X In-Reply-To: References: Message-ID: Seems like I will be stuck on OpenSSL 1.0.X for a while. On Sat, Feb 11, 2017 at 7:40 PM Frediano Ziglio wrote: > 2017-02-11 5:11 GMT+00:00 nik mur : > > This my first message to the list, very happy to do so. > > > > While compiling freetds with OpenSSL 1.1.0d I am receiving the following > > errors which I am unable to debug or make sense even after googling for > > hours > > > > Here is the error string (i am really sorry but the error string is very > > long) : > > > > tls.c: In function 'tds_pull_func_login': > > tls.c:83: error: dereferencing pointer to incomplete type > > tls.c: In function 'tds_push_func_login': > > tls.c:114: error: dereferencing pointer to incomplete type > > tls.c: In function 'tds_pull_func': > > tls.c:126: error: dereferencing pointer to incomplete type > > tls.c: In function 'tds_push_func': > > tls.c:149: error: dereferencing pointer to incomplete type > > tls.c: In function 'tds_ssl_ctrl_login': > > tls.c:551: error: dereferencing pointer to incomplete type > > --------------------------------------------------------------- > > tls.c:569: error: variable 'tds_method_login' has initializer but > > incomplete type > > tls.c:571: warning: excess elements in struct initializer > > tls.c:571: warning: (near initialization for 'tds_method_login') > > --------------------------------------------------------------- > > tls.c:580: warning: (near initialization for 'tds_method_login') > > tls.c:583: error: variable 'tds_method' has initializer but incomplete > type > > ---------------------------------------------------------------- > > tls.c: In function 'tds_init_openssl': > > tls.c:611: warning: 'TLSv1_client_method' is deprecated (declared at > > /usr/local/apps/include/openssl/ssl.h:1598) > > tls.c: In function 'check_alt_names': > > tls.c:747: warning: 'ASN1_STRING_data' is deprecated (declared at > > /usr/local/apps/include/openssl/asn1.h:553) > > tls.c: In function 'tds_ssl_init': > > ---------------------------------------------------------------- > > tls.c:887: error: dereferencing pointer to incomplete type > > tls.c:887: error: 'SSL_ST_OK' undeclared (first use in this function) > > tls.c:887: error: (Each undeclared identifier is reported only once > > tls.c:887: error: for each function it appears in.) > > ---------------------------------------------------------------- > > > > In case if something is wrong with my configure command you can check it > > below : > > > > LDFLAGS="-L$PPS_PATH/lib" CPPFLAGS="-I$PPS_PATH/include" ./configure > > --prefix=$PPS_PATH \ > > --enable-shared \ > > --with-libiconv-prefix=$PPS_PATH \ > > --with-openssl=$PPS_PATH && make && make install >> $LOG 2>&1 > > > > Also you can check my openssl configure command below : > > > > LDFLAGS="-L$PPS_PATH/lib" CPPFLAGS="-I$PPS_PATH/include" ./config > > --prefix=$PPS_PATH \ > > --openssldir=$PPS_PATH/etc/openssl shared && make && make install >> $LOG > > 2>&1 > > > Looks like they decided to entirely break the ABI from 1.0 to 1.1... > Not impossible to solve, just tedious and take some time. One reason I > prefer GnuTLS. > Patches are welcome! > > Frediano > _______________________________________________ > FreeTDS mailing list > FreeTDS at lists.ibiblio.org > http://lists.ibiblio.org/mailman/listinfo/freetds > From freddy77 at gmail.com Tue Feb 14 06:39:20 2017 From: freddy77 at gmail.com (Frediano Ziglio) Date: Tue, 14 Feb 2017 11:39:20 +0000 Subject: [freetds] Unable to compile Freetds with OpenSSL 1.1.X In-Reply-To: References: Message-ID: Fixed Frediano 2017-02-13 7:53 GMT+00:00 nik mur : > Seems like I will be stuck on OpenSSL 1.0.X for a while. > > On Sat, Feb 11, 2017 at 7:40 PM Frediano Ziglio wrote: > >> 2017-02-11 5:11 GMT+00:00 nik mur : >> > This my first message to the list, very happy to do so. >> > >> > While compiling freetds with OpenSSL 1.1.0d I am receiving the following >> > errors which I am unable to debug or make sense even after googling for >> > hours >> > >> > Here is the error string (i am really sorry but the error string is very >> > long) : >> > >> > tls.c: In function 'tds_pull_func_login': >> > tls.c:83: error: dereferencing pointer to incomplete type >> > tls.c: In function 'tds_push_func_login': >> > tls.c:114: error: dereferencing pointer to incomplete type >> > tls.c: In function 'tds_pull_func': >> > tls.c:126: error: dereferencing pointer to incomplete type >> > tls.c: In function 'tds_push_func': >> > tls.c:149: error: dereferencing pointer to incomplete type >> > tls.c: In function 'tds_ssl_ctrl_login': >> > tls.c:551: error: dereferencing pointer to incomplete type >> > --------------------------------------------------------------- >> > tls.c:569: error: variable 'tds_method_login' has initializer but >> > incomplete type >> > tls.c:571: warning: excess elements in struct initializer >> > tls.c:571: warning: (near initialization for 'tds_method_login') >> > --------------------------------------------------------------- >> > tls.c:580: warning: (near initialization for 'tds_method_login') >> > tls.c:583: error: variable 'tds_method' has initializer but incomplete >> type >> > ---------------------------------------------------------------- >> > tls.c: In function 'tds_init_openssl': >> > tls.c:611: warning: 'TLSv1_client_method' is deprecated (declared at >> > /usr/local/apps/include/openssl/ssl.h:1598) >> > tls.c: In function 'check_alt_names': >> > tls.c:747: warning: 'ASN1_STRING_data' is deprecated (declared at >> > /usr/local/apps/include/openssl/asn1.h:553) >> > tls.c: In function 'tds_ssl_init': >> > ---------------------------------------------------------------- >> > tls.c:887: error: dereferencing pointer to incomplete type >> > tls.c:887: error: 'SSL_ST_OK' undeclared (first use in this function) >> > tls.c:887: error: (Each undeclared identifier is reported only once >> > tls.c:887: error: for each function it appears in.) >> > ---------------------------------------------------------------- >> > >> > In case if something is wrong with my configure command you can check it >> > below : >> > >> > LDFLAGS="-L$PPS_PATH/lib" CPPFLAGS="-I$PPS_PATH/include" ./configure >> > --prefix=$PPS_PATH \ >> > --enable-shared \ >> > --with-libiconv-prefix=$PPS_PATH \ >> > --with-openssl=$PPS_PATH && make && make install >> $LOG 2>&1 >> > >> > Also you can check my openssl configure command below : >> > >> > LDFLAGS="-L$PPS_PATH/lib" CPPFLAGS="-I$PPS_PATH/include" ./config >> > --prefix=$PPS_PATH \ >> > --openssldir=$PPS_PATH/etc/openssl shared && make && make install >> $LOG >> > 2>&1 >> >> >> Looks like they decided to entirely break the ABI from 1.0 to 1.1... >> Not impossible to solve, just tedious and take some time. One reason I >> prefer GnuTLS. >> Patches are welcome! >> >> Frediano From nikhil6018 at gmail.com Tue Feb 14 08:07:46 2017 From: nikhil6018 at gmail.com (nik mur) Date: Tue, 14 Feb 2017 13:07:46 +0000 Subject: [freetds] Unable to compile Freetds with OpenSSL 1.1.X In-Reply-To: References: Message-ID: Thanks Frediano, will compile and check :) On Tue, Feb 14, 2017 at 5:09 PM Frediano Ziglio wrote: > Fixed > > Frediano > > > 2017-02-13 7:53 GMT+00:00 nik mur : > > Seems like I will be stuck on OpenSSL 1.0.X for a while. > > > > On Sat, Feb 11, 2017 at 7:40 PM Frediano Ziglio > wrote: > > > >> 2017-02-11 5:11 GMT+00:00 nik mur : > >> > This my first message to the list, very happy to do so. > >> > > >> > While compiling freetds with OpenSSL 1.1.0d I am receiving the > following > >> > errors which I am unable to debug or make sense even after googling > for > >> > hours > >> > > >> > Here is the error string (i am really sorry but the error string is > very > >> > long) : > >> > > >> > tls.c: In function 'tds_pull_func_login': > >> > tls.c:83: error: dereferencing pointer to incomplete type > >> > tls.c: In function 'tds_push_func_login': > >> > tls.c:114: error: dereferencing pointer to incomplete type > >> > tls.c: In function 'tds_pull_func': > >> > tls.c:126: error: dereferencing pointer to incomplete type > >> > tls.c: In function 'tds_push_func': > >> > tls.c:149: error: dereferencing pointer to incomplete type > >> > tls.c: In function 'tds_ssl_ctrl_login': > >> > tls.c:551: error: dereferencing pointer to incomplete type > >> > --------------------------------------------------------------- > >> > tls.c:569: error: variable 'tds_method_login' has initializer but > >> > incomplete type > >> > tls.c:571: warning: excess elements in struct initializer > >> > tls.c:571: warning: (near initialization for 'tds_method_login') > >> > --------------------------------------------------------------- > >> > tls.c:580: warning: (near initialization for 'tds_method_login') > >> > tls.c:583: error: variable 'tds_method' has initializer but incomplete > >> type > >> > ---------------------------------------------------------------- > >> > tls.c: In function 'tds_init_openssl': > >> > tls.c:611: warning: 'TLSv1_client_method' is deprecated (declared at > >> > /usr/local/apps/include/openssl/ssl.h:1598) > >> > tls.c: In function 'check_alt_names': > >> > tls.c:747: warning: 'ASN1_STRING_data' is deprecated (declared at > >> > /usr/local/apps/include/openssl/asn1.h:553) > >> > tls.c: In function 'tds_ssl_init': > >> > ---------------------------------------------------------------- > >> > tls.c:887: error: dereferencing pointer to incomplete type > >> > tls.c:887: error: 'SSL_ST_OK' undeclared (first use in this function) > >> > tls.c:887: error: (Each undeclared identifier is reported only once > >> > tls.c:887: error: for each function it appears in.) > >> > ---------------------------------------------------------------- > >> > > >> > In case if something is wrong with my configure command you can check > it > >> > below : > >> > > >> > LDFLAGS="-L$PPS_PATH/lib" CPPFLAGS="-I$PPS_PATH/include" ./configure > >> > --prefix=$PPS_PATH \ > >> > --enable-shared \ > >> > --with-libiconv-prefix=$PPS_PATH \ > >> > --with-openssl=$PPS_PATH && make && make install >> $LOG 2>&1 > >> > > >> > Also you can check my openssl configure command below : > >> > > >> > LDFLAGS="-L$PPS_PATH/lib" CPPFLAGS="-I$PPS_PATH/include" ./config > >> > --prefix=$PPS_PATH \ > >> > --openssldir=$PPS_PATH/etc/openssl shared && make && make install >> > $LOG > >> > 2>&1 > >> > >> > >> Looks like they decided to entirely break the ABI from 1.0 to 1.1... > >> Not impossible to solve, just tedious and take some time. One reason I > >> prefer GnuTLS. > >> Patches are welcome! > >> > >> Frediano > _______________________________________________ > FreeTDS mailing list > FreeTDS at lists.ibiblio.org > http://lists.ibiblio.org/mailman/listinfo/freetds > From freddy77 at gmail.com Wed Feb 15 10:11:35 2017 From: freddy77 at gmail.com (Frediano Ziglio) Date: Wed, 15 Feb 2017 15:11:35 +0000 Subject: [freetds] Subscription to the ML limited Message-ID: Hi, since a couple of months the ML is receiving some SPAM attacks. Subscribed users are not affected however some external scripts try to subscribe new users possibly posting new requests to the web (I suppose). I tried to contact the server administrator but after 3 mails and a months or so I didn't get any feedback. I was quite bored having to disable manually lot of users so yesterday I decided to disable the subscription using either e-mail and web and I put some notes on the information page asking to open issues in GitHub. Does somebody knows how to contact the server administrator? Can somebody suggest some Mailman configurations I can make to avoid such attempts? Regards, Frediano From no-reply at appveyor.com Fri Mar 10 10:42:27 2017 From: no-reply at appveyor.com (AppVeyor) Date: Fri, 10 Mar 2017 15:42:27 +0000 Subject: [freetds] Build failed: freetds 751 Message-ID: <20170310154218.92638.47686.39A0A3A6@appveyor.com> From no-reply at appveyor.com Fri Mar 10 12:47:08 2017 From: no-reply at appveyor.com (AppVeyor) Date: Fri, 10 Mar 2017 17:47:08 +0000 Subject: [freetds] Build completed: freetds 752 Message-ID: <20170310174707.91994.42527.996B5C29@appveyor.com> From vasanth.sengunthar at accenture.com Wed Mar 22 02:11:46 2017 From: vasanth.sengunthar at accenture.com (vasanth.sengunthar at accenture.com) Date: Wed, 22 Mar 2017 06:11:46 +0000 Subject: [freetds] Freebcp character conversion Issue Message-ID: Hi, Recently, I have been working with freebcp command of freetds driver, where I came across character conversion issue while trying to back up the table of MS SQL Server database. Please look into the below error and help to get rid of the same as soon as possible. We did try to declare client charset value with freetds.conf file but that is not useful either. Error: Some character(s) could not be converted into client's character set. Unconverted bytes were changed to question marks ('?')". Looking forward to your earliest response, Regards, Vasanth ________________________________ This message is for the designated recipient only and may contain privileged, proprietary, or otherwise confidential information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the e-mail by you is prohibited. Where allowed by local law, electronic communications with Accenture and its affiliates, including e-mail and instant messaging (including content), may be scanned by our systems for the purposes of information security and assessment of internal compliance with Accenture policy. ______________________________________________________________________________________ www.accenture.com From freddy77 at gmail.com Wed Mar 22 06:53:25 2017 From: freddy77 at gmail.com (Frediano Ziglio) Date: Wed, 22 Mar 2017 10:53:25 +0000 Subject: [freetds] Freebcp character conversion Issue In-Reply-To: References: Message-ID: Usually this is an indication of: - you are not uring libiconv; - the client charset is not able to handle some server character (try utf-8); - your database contains some garbage. Are you able to understand which data has the issue? Frediano 2017-03-22 6:11 GMT+00:00 : > Hi, > > Recently, I have been working with freebcp command of freetds driver, where I came across character conversion issue while trying to back up the table of MS SQL Server database. > Please look into the below error and help to get rid of the same as soon as possible. > > We did try to declare client charset value with freetds.conf file but that is not useful either. > > Error: > Some character(s) could not be converted into client's character set. Unconverted bytes were changed to question marks ('?')". > > > Looking forward to your earliest response, > > Regards, > Vasanth > From vasanth.sengunthar at accenture.com Wed Mar 22 07:40:10 2017 From: vasanth.sengunthar at accenture.com (vasanth.sengunthar at accenture.com) Date: Wed, 22 Mar 2017 11:40:10 +0000 Subject: [freetds] Freebcp character conversion Issue In-Reply-To: References: Message-ID: <717875b5cd17448fa09292e9ffc8b8b6@SN4PR4205MB0413.048d.mgd.msft.net> Hi, Thanks for immediate response Ferdino, however the table we are trying to backup is of login table with password column((sysname datatype), which is giving conversion issue due to cipher text. Please suggest if there is any alternate way to backup as we already applied utf-8 and failed with the fix. Regards, Vasanth -----Original Message----- From: FreeTDS [mailto:freetds-bounces at lists.ibiblio.org] On Behalf Of Frediano Ziglio Sent: Wednesday, March 22, 2017 4:23 PM To: FreeTDS Development Group Subject: Re: [freetds] Freebcp character conversion Issue Usually this is an indication of: - you are not uring libiconv; - the client charset is not able to handle some server character (try utf-8); - your database contains some garbage. Are you able to understand which data has the issue? Frediano 2017-03-22 6:11 GMT+00:00 : > Hi, > > Recently, I have been working with freebcp command of freetds driver, where I came across character conversion issue while trying to back up the table of MS SQL Server database. > Please look into the below error and help to get rid of the same as soon as possible. > > We did try to declare client charset value with freetds.conf file but that is not useful either. > > Error: > Some character(s) could not be converted into client's character set. Unconverted bytes were changed to question marks ('?')". > > > Looking forward to your earliest response, > > Regards, > Vasanth > _______________________________________________ FreeTDS mailing list FreeTDS at lists.ibiblio.org https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.ibiblio.org_mailman_listinfo_freetds&d=DwICAg&c=eIGjsITfXP_y-DLLX0uEHXJvU8nOHrUK8IrwNKOtkVU&r=vQqnb-FGv_1Cq8lIuKD95mRfUO0gBovRe0eqdms7a5s&m=9ohuXqX4RTRwoKFRR4Wnuo74pTeQQT046YqdTwZ71pc&s=WF2lSWQvV-WIiZX1t-TYi-SpxTAE2sjqgcx5No7MBb4&e= ________________________________ This message is for the designated recipient only and may contain privileged, proprietary, or otherwise confidential information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the e-mail by you is prohibited. Where allowed by local law, electronic communications with Accenture and its affiliates, including e-mail and instant messaging (including content), may be scanned by our systems for the purposes of information security and assessment of internal compliance with Accenture policy. ______________________________________________________________________________________ www.accenture.com From freddy77 at gmail.com Wed Mar 22 08:25:40 2017 From: freddy77 at gmail.com (Frediano Ziglio) Date: Wed, 22 Mar 2017 12:25:40 +0000 Subject: [freetds] Freebcp character conversion Issue In-Reply-To: <717875b5cd17448fa09292e9ffc8b8b6@SN4PR4205MB0413.048d.mgd.msft.net> References: <717875b5cd17448fa09292e9ffc8b8b6@SN4PR4205MB0413.048d.mgd.msft.net> Message-ID: Then the column contains garbage... cipher text means binary and binary should not be stored in a sysname column which, as Microsoft documented it, is like a nvarchar(128). The "workaround" would be to avoid any conversion and save as raw (so native format without conversions) which currently is not implemented. Or convert the column to a binary format (I would say varbinary(256)). Frediano 2017-03-22 11:40 GMT+00:00 : > Hi, > > Thanks for immediate response Ferdino, however the table we are trying to backup is of login table with password column((sysname datatype), which is giving conversion issue due to cipher text. > > Please suggest if there is any alternate way to backup as we already applied utf-8 and failed with the fix. > > Regards, > Vasanth > > -----Original Message----- > From: FreeTDS [mailto:freetds-bounces at lists.ibiblio.org] On Behalf Of Frediano Ziglio > Sent: Wednesday, March 22, 2017 4:23 PM > To: FreeTDS Development Group > Subject: Re: [freetds] Freebcp character conversion Issue > > Usually this is an indication of: > - you are not uring libiconv; > - the client charset is not able to handle some server character (try utf-8); > - your database contains some garbage. > > Are you able to understand which data has the issue? > > Frediano > > > 2017-03-22 6:11 GMT+00:00 : >> Hi, >> >> Recently, I have been working with freebcp command of freetds driver, where I came across character conversion issue while trying to back up the table of MS SQL Server database. >> Please look into the below error and help to get rid of the same as soon as possible. >> >> We did try to declare client charset value with freetds.conf file but that is not useful either. >> >> Error: >> Some character(s) could not be converted into client's character set. Unconverted bytes were changed to question marks ('?')". >> >> >> Looking forward to your earliest response, >> >> Regards, >> Vasanth >> > _______________________________________________ > FreeTDS mailing list > FreeTDS at lists.ibiblio.org > https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.ibiblio.org_mailman_listinfo_freetds&d=DwICAg&c=eIGjsITfXP_y-DLLX0uEHXJvU8nOHrUK8IrwNKOtkVU&r=vQqnb-FGv_1Cq8lIuKD95mRfUO0gBovRe0eqdms7a5s&m=9ohuXqX4RTRwoKFRR4Wnuo74pTeQQT046YqdTwZ71pc&s=WF2lSWQvV-WIiZX1t-TYi-SpxTAE2sjqgcx5No7MBb4&e= > > ________________________________ > > This message is for the designated recipient only and may contain privileged, proprietary, or otherwise confidential information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the e-mail by you is prohibited. Where allowed by local law, electronic communications with Accenture and its affiliates, including e-mail and instant messaging (including content), may be scanned by our systems for the purposes of information security and assessment of internal compliance with Accenture policy. > ______________________________________________________________________________________ > > www.accenture.com > _______________________________________________ > FreeTDS mailing list > FreeTDS at lists.ibiblio.org > http://lists.ibiblio.org/mailman/listinfo/freetds From vasanth.sengunthar at accenture.com Thu Mar 23 02:42:00 2017 From: vasanth.sengunthar at accenture.com (vasanth.sengunthar at accenture.com) Date: Thu, 23 Mar 2017 06:42:00 +0000 Subject: [freetds] Freebcp character conversion Issue In-Reply-To: References: <717875b5cd17448fa09292e9ffc8b8b6@SN4PR4205MB0413.048d.mgd.msft.net> Message-ID: Hi, Thanks for the suggestions Fredino, I created format file with SYBBINARY datatype for single issue column and it seems to work with freebcp command. Regards, Vasanth -----Original Message----- From: FreeTDS [mailto:freetds-bounces at lists.ibiblio.org] On Behalf Of Frediano Ziglio Sent: Wednesday, March 22, 2017 5:56 PM To: FreeTDS Development Group Subject: Re: [freetds] Freebcp character conversion Issue Then the column contains garbage... cipher text means binary and binary should not be stored in a sysname column which, as Microsoft documented it, is like a nvarchar(128). The "workaround" would be to avoid any conversion and save as raw (so native format without conversions) which currently is not implemented. Or convert the column to a binary format (I would say varbinary(256)). Frediano 2017-03-22 11:40 GMT+00:00 : > Hi, > > Thanks for immediate response Ferdino, however the table we are trying to backup is of login table with password column((sysname datatype), which is giving conversion issue due to cipher text. > > Please suggest if there is any alternate way to backup as we already applied utf-8 and failed with the fix. > > Regards, > Vasanth > > -----Original Message----- > From: FreeTDS [mailto:freetds-bounces at lists.ibiblio.org] On Behalf Of > Frediano Ziglio > Sent: Wednesday, March 22, 2017 4:23 PM > To: FreeTDS Development Group > Subject: Re: [freetds] Freebcp character conversion Issue > > Usually this is an indication of: > - you are not uring libiconv; > - the client charset is not able to handle some server character (try > utf-8); > - your database contains some garbage. > > Are you able to understand which data has the issue? > > Frediano > > > 2017-03-22 6:11 GMT+00:00 : >> Hi, >> >> Recently, I have been working with freebcp command of freetds driver, where I came across character conversion issue while trying to back up the table of MS SQL Server database. >> Please look into the below error and help to get rid of the same as soon as possible. >> >> We did try to declare client charset value with freetds.conf file but that is not useful either. >> >> Error: >> Some character(s) could not be converted into client's character set. Unconverted bytes were changed to question marks ('?')". >> >> >> Looking forward to your earliest response, >> >> Regards, >> Vasanth >> > _______________________________________________ > FreeTDS mailing list > FreeTDS at lists.ibiblio.org > https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.ibiblio.org_ > mailman_listinfo_freetds&d=DwICAg&c=eIGjsITfXP_y-DLLX0uEHXJvU8nOHrUK8I > rwNKOtkVU&r=vQqnb-FGv_1Cq8lIuKD95mRfUO0gBovRe0eqdms7a5s&m=9ohuXqX4RTRw > oKFRR4Wnuo74pTeQQT046YqdTwZ71pc&s=WF2lSWQvV-WIiZX1t-TYi-SpxTAE2sjqgcx5 > No7MBb4&e= > > ________________________________ > > This message is for the designated recipient only and may contain privileged, proprietary, or otherwise confidential information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the e-mail by you is prohibited. Where allowed by local law, electronic communications with Accenture and its affiliates, including e-mail and instant messaging (including content), may be scanned by our systems for the purposes of information security and assessment of internal compliance with Accenture policy. > ______________________________________________________________________ > ________________ > > www.accenture.com > _______________________________________________ > FreeTDS mailing list > FreeTDS at lists.ibiblio.org > https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.ibiblio.org_ > mailman_listinfo_freetds&d=DwICAg&c=eIGjsITfXP_y-DLLX0uEHXJvU8nOHrUK8I > rwNKOtkVU&r=vQqnb-FGv_1Cq8lIuKD95mRfUO0gBovRe0eqdms7a5s&m=cQ0czvjOoYiR > y2uDriiW3AHyVK7qye-hubApPYjVgXg&s=F5PTctaQhsDTLn2SuCnqQi1LAEuaQlaMoBxr > mcfxhkE&e= _______________________________________________ FreeTDS mailing list FreeTDS at lists.ibiblio.org https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.ibiblio.org_mailman_listinfo_freetds&d=DwICAg&c=eIGjsITfXP_y-DLLX0uEHXJvU8nOHrUK8IrwNKOtkVU&r=vQqnb-FGv_1Cq8lIuKD95mRfUO0gBovRe0eqdms7a5s&m=cQ0czvjOoYiRy2uDriiW3AHyVK7qye-hubApPYjVgXg&s=F5PTctaQhsDTLn2SuCnqQi1LAEuaQlaMoBxrmcfxhkE&e=