SQL Server 2000 connection problems

[Dirk]

I have recently installed syslog2odbc, and have high hopes for it, but can't seem to get it to run. I receive the following info:

SysLog2ODBC [Debug] - [01000] [Microsoft][ODBC SQL Server Driver][SQL Server]Cha
nged database context to 'Syslog'. (5701)

SysLog2ODBC [Debug] - [01000] [Microsoft][ODBC SQL Server Driver][SQL Server]Cha
nged language setting to us_english. (5703)

SysLog2ODBC [Critical] - bind() error [WSAGetLastError(): 10048]

SysLog2ODBC [Emergency] - CRITICAL ERROR! s2o_InitSysLog2ODBC()

Any ideas on this?

Thanks

[Pier Carlo CHIODI]

Hi,

as you say SysLog2ODBC reports the Windows Sockets Error 10048 during the bind() call.

This error (constant name = WSAEADDRINUSE) means that another server is already listening on the UDP port you type in the syslog2odbc.ini file (by default: 514).

I think you have other syslog server running, listening on port 514, so SysLog2ODBC can't have the control over this UDP Port, then exits.

I suggest you to stop other syslog server then run SysLog2ODBC again.

Please let me know if you can solve this problem!

Bye

[Dirk]

You were right about the port being in use, there was a syslog service running that I thought I had killed. I can get it to run now in console mode, but not as a service. Do I need to put the ini file somewhere specific like the system32 directory?
It gives me this error:

SysLog2ODBC [Critical] - s2o_ODBC_Connect

SysLog2ODBC [Emergency] - CRITICAL ERROR! s2o_InitSysLog2ODBC()

[Pier Carlo CHIODI]

The INI file should be in the same directory of SysLog2ODBC.

The error you get is about a problem in the connection to the ODBC data source; you should set the MinSeverity parameter (in the INI file) to debug

MinSeverity=7

then send me again the full error log that SysLog2ODBC writes.

[Dirk]

Here's the log printout:

2004-04-19 10:23:45 [Debug] - Using following configuration:
    Verbosity level: 7 [Debug]
    Bind to IP: 0.0.0.0
    UDP Port: 514
    Default values
        facility: 0 [Kernel]
        severity: 4 [Warning]
    ODBC Conn. string: DSN=SysLog2ODBC
    Wait on error: 2
    Max retry count: 5
    SQL Statement: INSERT INTO SysLogData( Sender_IP, Msg, raw_msg, Priority, Severity, Severity_Desc, Facility, Facility_Desc ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ? )
2004-04-19 10:23:45 [Critical] - [28000] [Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user 'TORCOM\EMAILER$'. (18456)
2004-04-19 10:23:45 [Critical] - s2o_ODBC_Connect
2004-04-19 10:23:45 [Emergency] - CRITICAL ERROR! s2o_InitSysLog2ODBC()

It would seem the error is with the login, which works fine if I run it under console mode. The name of the login should be torcom\emailer (without the $) so I'm not sure if that is the issue or what.

[Pier Carlo CHIODI]

Is the DSN based on Windows Authentication or SQL Server authentication?

What account is the SysLog2ODBC service running on?

Can you try to put the login password in the ODBC connection string parameter?

ConnectionString=DSN=SysLog2ODBC;UID=login;PWD=password