Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

Why do I get SQL Timeouts when I use AuthBy SQL with Sybase ODBC libraries?

authby Libraries ODBC sql Sybase
0
Posted

Why do I get SQL Timeouts when I use AuthBy SQL with Sybase ODBC libraries?

0

The Sybase ODBC libraries (which are the ones you get if you use DBD-ODBC with Sybase) on Unix use ALRM signals, which breaks Radiator’s independent use of alarms to detect SQL timeouts. With versions of Radiator post 2.17.1, you can set Timeout to 0 in any SQL clause, which stops Radiator from implementing any alarms. It will then rely on the underlying SQL library to time out if there is an SQL problem. We recommend you do this for any Sybase ODBC connections. 99. I get an unknown socket error on Windows 2000 or NTOn Windows 2000 Server or NT, you might see an error like: Could not bind authentication socket: unknown error at ./radiusd line 336. This usually means that there is already a radius server running in that machine. It is likely to be the Microsoft IIS radius server that is enabled by default on Windows 2000 Server. In that case the solution is to edit the Services on that machine and set the ‘Internet Authentication’ service to ‘Manual’. This error is sometimes seen if any

Related Questions

What is your question?

*Sadly, we had to bring back ads too. Hopefully more targeted.

Experts123