Hi

I have a clean install of Windows XP Pro SP3 with MS automatic updates turned on and with DrayTek syslog v4.2.1 installed on it. Syslog is picking up syslog messages from a Vigor 2820vn with firmware 3.3.3_232201

Very frequently syslog reports the error message below when new syslog messages arrive from the router:

OpenDB InsertDB_Top:Code = 80004005
Meaning = Unspecified Error
Source = Microsoft JET Database Engine
Description = Selected collating sequence not supported by operating system

I have looked on the MS website and the only thing it mentions is making sure the MS Jet Database is up to date, which it is. Is there a fix to this error?

Thanks

We had this problem - from microsoft it seems to be a language problem with the access database used to record logs.

http://support.microsoft.com/kb/202150

We had been running an older version of syslog before so there was an MDB already in existence:

You need to shut down any running copy and delete any MDB files in the directory you have chosen to record the logs or it will still give errors. I suspect this recreates the MDB in the general sort order.

For those who do not have 4.2.1 which just crashes with a C++ error in the above situation...

This is sorted by downloading the V4.2.1 router tools from draytek:

http://draytek.com/user/SupportDLUtility.php#

or just the syslog file (copy it over the top of the one in Program Files\Router Tools) from:

http://www.draytek.co.uk/support/download/Syslog_421_Win.zip

Don't forget to delete any old MDB as above

When it gives that error, afaik it doesn't crash, just shows that error and keeps going - it only really matters if you want to store the syslog as a database.
Draytek are apparently working on a fix for it though, which should be released soon.

timgilberts wrote: We had this problem - from microsoft it seems to be a language problem with the access database used to record logs.

http://support.microsoft.com/kb/202150

We had been running an older version of syslog before so there was an MDB already in existence:

You need to shut down any running copy and delete any MDB files in the directory you have chosen to record the logs or it will still give errors. I suspect this recreates the MDB in the general sort order.

That is brilliant, syslog is working fine now, many thanks!