LHErrors & the Event Log

I'd like to see if you have some experience or perhaps better tools to assist in the business of tracking down LHERRORS and the useless information in NT Event logs.

We have a number of databases which number between 500K & 800K records, with 4 indexed fields at a couple of client sites.

At one site in particular, there's the ever present and unexplainable LHERRORS appearing in the event logs.

I've spent time enough in this bulletin board looking for an approach in making sense of the LHErrors and the details in the event log - and cannot locate anything which helps.

The errors are not reproducible on demand, so turning on OI Logging is not an option.

We've done the running of the Bull in a China Shop of spending a day at a time to LHverify the whole of their database - to turn up a clean bill of health

Yet, problems recur.

Personally we're of the opinion that these issues are network and infrastructure related, but we cannot talk away the event logs, and as always the customer is relying on the

event logs as their proof of fault.

What tools / methods / approaches exist to sorting these things out?

Is the UD4 any more useful in the details that it spins out to the event log? Currently the clients are on 3.x network drivers and the databases have been stable to yonks.

Do Revelation have some special (techo only) tools that you can use to check these databases for us - at cost? This is just beyond casual annoyance now and is killing customer confidence in the product, which is not good for me.

Thank you

We do not have special tools.

One customer pointed us to WireShark as a good tool. It is a packet sniffer with powerful filters. For instance you can monitor transactions between 2 ip addresses on a specific port.

I worked with someone else who kept getting server messages. As I recall it was FS3000. We used the lh log to determine the file number associated with each rev file number, then worked back from there to determine the rev file that was causing the errors.

- Bob

Yes but how do you know what file number is associated to what rev file.

Tells you at the beginning of the log file - open XYZ to 0, open ABC to 34 etc.

The Sprezzatura Group

World leaders in all things RevSoft

View this thread on the Works forum...