MonitorWare Knowledge Base

**sorry posted this in the wrong area before, this is where it belongs**

Hello,
I've been trying to setup Winsyslog to write to an database file called syslog.mdb. The software is running on Windows 2000 Server, it is version 3.7. I can successfully write to a file, but i don't see anthing in the .mdb file. I've configure the ODBC portion with all the appropriate data and have setup the DSN. Although I don't know what username and passwords to use, i've tried the local admin user account and password to no avail. Also, I set up the Rules for an ODBC with the correct DSN name. HELP!!

Thanks.

Lester

Dear Lester,

many thanks for your mail. I suggest that you have a look at the Windows Application Event Log, if not already done so. Any problems encountered by WinSyslog are logged there (well, with 3.7, I need to say they "should" be logged there ... as far as I remember, not everything was logged by that release). Most often, the messages there are very descriptive.

Regarding the userid and password: in a default setup, there is no need to use them with an Access/JET MDB file. You only need to provide them if you have activated password protection within Access.

Please let us know if, and if so, what, messages are logged.

Looking forward to your reply.

Best regards,
Rainer Gerhards
Adiscon

Can't bind to socket - ERRORCODE: 10048

This error mostly occurs if another process is listening on the configured port. For example, if you have configured the same port for the WinSyslog Client and Service and the Realtime Logging of the WinSyslog Client is running.


Lester

After consulting the Event Logs, I realized that the Syslog Service and the Syslog Real-Time logging were competing for the same port. Thus, I turned off the Real Time logging and the service immediately started to write to the ODBC logging method, or to the MDB file.

Thanks for your help.

Lester

I am glad it works now - and many thanks for letting us know!

Rainer