-
Naturally, as soon as I posted this, I thought of something else to check - credentials for the service did not have rights to the database. Duh. Changed the credentials for the service and all is well.
2009-09-29 15:01:23 UTC by jcanaday
-
Trying to syslog an ASA 5510 to SQL Server. I have SysLog2ODBC running on a domain workstation. The configuration file is as follows:
[Server]
BindToIP=10.0.0.33
Port=514
[Logging]
LogToFile=1
LogFilePath=C:\Program Files\Syslog\syslog.log
MinSeverity=7
[ODBC]
ConnectionString=DSN=SysLogDatabase
SQLStatement=INSERT INTO SysLogEvents( Severity, Msg ) VALUES ( ?, ? ...
2009-09-29 14:54:08 UTC by jcanaday
-
SysLog2ODBC is crashing when the SysLog message is longer than 1024 bytes.
The following was posted by a user in the discussion forum. I've created the bug entry to have this fixed or to alert potential users of this issue if it isn't fixed:
User exjobb wrote:
I wanted to stress test syslog2ODBC so i downloaded Kiwi SyslogGen, a freeware tool to generate syslog messages and it has an...
2007-11-19 00:14:29 UTC by psychosmurf74
-
When SysLog2ODBC is installed as a service on Windows Server 2003; the service starts and then immediately stops logging an event ID 7016 "The SysLog2ODBC service has reported an invalid current state 0.". This prevents the software from being used on a Server 2003 system outside of the command line.
2007-11-17 05:57:04 UTC by psychosmurf74
-
Anonymous committed patchset 1 of module CVSROOT to the SysLog2ODBC CVS repository, changing 11 files.
2003-10-20 13:11:55 UTC by nobody
-
registered the SysLog2ODBC project.
2003-10-18 12:58:52 UTC by
