A client of mine is complaining that they frequently (though not always) find an AREV 3.12 process frozen when they arrive in the morning. The process is an LHVERIFY which kicks off at 5:00am on their DOS-based dedicated indexing machine when it wakes up after being logged out at 11:00pm for the backup. They can still access AREV on other workstations, but are locked out of whatever file the LHVERIFY has frozen on. Usually, because they are a small company with no in-house expertise, they simply restart their file server and everything is fine. Yesterday, they mentioned this issue to the person who looks after their network and he attempted to stop the Linear Hash Service, but was not able to do so…he also had to restart the file server. I have read about a patch to v2.1, but I'm not sure that the description of what it fixes applies to this particular problem. Would the new Universal Driver solve this? I will be at this client's site tomorrow, so any ideas or suggestions would be very much appreciated.

Thanks in advance,

Gray Cunningham

If you are using the service then why do you regularly run an LHVerify?

Doesn't make sense…

John

View this thread on the Works forum...