Revmedia open error (AREV Specific)
At 03 APR 1998 10:58:05AM Mike O'Neal wrote:
Hello everyone:
A Novell 4.1 site of mine using the NLM crashed their server last night, all came back this morning except their AREV 3.1 app. Their error message is:
"Linear Hash IPX driver - Revmedia open error FS60417 unable to open boot media map"
Not sure what to do here, they get the same message whether logging into their app or SYSPROG. Do I need to re-install the NLM? Restore a REVBOOT or REVMEDIA?
TIA,
Mike O.
At 03 APR 1998 01:28PM Aaron Kaplan wrote:
Try restoring revmedia files.
See if you can get to it withough the NLM (REVBOOT.OLD contains the previous driver used)
Try turning off server only and letting it bypass if possible.
All this will really do is determine if it's a server problem or a file corruption problem.
At 19 JUL 1999 05:03PM Barbara Blackie wrote:
Would appreciate hearing from anyone who knows the exact meaning of this error message (FS60417), as we have a similar problem to solve.
At 19 JUL 1999 10:23PM Boston Blackie wrote:
It was a dark and stormy night and my system was throwing error messages at me like they were AOL disks, and yet, FS60417 is while unfamiliar to me, is strangely compelling, like Lauren Bacall teaching me how to whistle.
Boston Blackie
At 28 JUL 1999 01:48PM Whistle this wrote:
We asked for bread and they gave us stones.
An arcane reference to ancient media? Bother! I have pulled an old tire out of the cyber fishing hole! Phooey.
Real help and not mockery would be appreciated.
BB
At 28 JUL 1999 03:27PM [email protected] onmouseover=window.status=why not click here to send me email?;return(true)", [url=http://www.sprezzatura.com" onMouseOver=window.status=Why not click here to visit our web site?';return(true)]Sprezzatura Group[/url] wrote:
Well the only other person who reported this error (as reported by the stunningly useful search facility provided on this site) is here
World Leaders in all things RevSoft
At 09 AUG 2000 05:37PM CraigH wrote:
I encountered this error (FS60417). I found the problem to be a version conflict between the client (TSR) and the NLM. The client was 1.12 and the server was 1.5. Once I upgraded the client to 1.5, no more error!