LinearHash errors using 2.1 Driver (Networking Products)
At 19 FEB 2010 10:29:09AM dave w bennett wrote:
Our account has been receiving the following message in the event log using 2003 SBS, they are using the 2.1 driver with REVPARAM containing serveronly=true in each folder.
Event Type: Error
Event Source: LinearHash
Event Category: None
Event ID: 30000
Date: 2/18/2010
Time: 5:21:50 PM
User: N/A
Computer: HOLLONMAIN
Description:
The "LHWriteRecord" call failed, returning LH error number 102, file number 1, group number 0. Error while writing data, the table is read-only.
Event Type: Error
Event Source: LinearHash
Event Category: None
Event ID: 30000
Date: 2/18/2010
Time: 9:01:10 AM
User: N/A
Computer: HOLLONMAIN
Description:
The "LHClearFile" call failed, returning LH error number 102, file number 1, group number 0. Error while writing data, the table is read-only.
Event Type: Error
Event Source: LinearHash
Event Category: None
Event ID: 30000
Date: 2/17/2010
Time: 10:55:15 AM
User: N/A
Computer: HOLLONMAIN
Description:
The "LHReadOnlyRecord" call failed, returning LH error number 1009, file number 2, group number 0. File open error.
At 20 FEB 2010 05:46PM Jared Bratu wrote:
In light of the previous question and this information I don't think you are getting proper usage of the Linear Hash service. This could be a symptom of clients opening files directly but the only way to determine that would be to looked at the server's Opened Files list to see if .LK or .OV files were being accessed directly by network users.
The error numbers correspond to the FS errors listed in the help file. I.e. FS1009, FS102.
Also, it could be an antivirus scanner, backup software, or some other monitoring software locking the files and preventing the LH service from reading them.
At 05 OCT 2010 05:10PM dave w bennett wrote:
It turned out that we only received messages at certain times of the day for 7 of the 500 files we had. I copied off the data and dictionaries and deleted the files and recreated them and copied the data and dictionaries back in.
Months later we are fine, I had to perform this at another account last month. It was another handfull of files, but different ones.
Dave