I have a problem similar to one posted on 2/12/99 where I get the W611} error when I try to select any of my indexed tables. The problem only occurs on my Test/Development system, not on the production systems. This problem has existed for some time now, but has not affected any development or testing efforts until recently.
I have checked the !file and ! records in the index file, and they appear fine. I see the proper account name, but do not see a reference to any volume name. I have not changed my volume or account names, so there should be no problem. Nonetheless, I deleted the ! record and re-attached the table, but to no avail.
I am running AREV 3.12 on a Novell 4.10 server with the NLM version 1.12. On the client side, I am using a Win95 machine with the Novell Client for Windows 95/98 v 3.10, as well as an old DOS/Win31 machine with VLM drivers. The production sites have upgraded to Novell 4.12, but did not experience this problem prior to upgrading.
Are there any global indexing parameters or settings that I should check, since I am having this problem with all of my indexes?
Thank you for any assistance that can be provided.
As long as you know how the indexing is set on the file I would try deleting the !file. If you cannot do a DELETETABLE then edit the appropriate REVMEDIA file and delete the reference for it there. Then remove the indexing from the file. You may have to manually create a dummy !file for the datafile to do this or you can remove the SI.MFS reference in the REVMEDIA file and reattach. If you do this, though, you will have to manually remove the indexing information from the dictionary (see the appropriate tech bulletin).
The other thing to do is check your REVMEDIA files and see if a duplicate of the datafile is not getting attached somewhere along the line which could through SI.MFS off too.
this happened to me a while back but for the life of me i can't remember what i did to solve it. it was failry simple and i think it had to do with a corrupt dictionary (but it was for only one file not everyone). I think irestored the appropriate dcitionary from backup and everything was cool again. But like i said it was a while ago.
ed