Hello all,

We are using AREV 3.12 on a Netware 5.1 system (NLM 5.0) most of our stations have win98 with nwclient 3.3

A few of our clients get this error message (System ID could not found….etc)at launch also the System ID in the "who" is blank. I checked for the MAC at station level and at the novell console they both reported it fine. The really strange part is that after spending a few minutes searching the discussions on this topic I was asked to recreate this error and it would not re create. The only thing that had been done was a shut down and restart. I can except that the shut down somehow fixed the problem, however that is the first thing i did to the affected station with no results. When a second station came up with the same error I shutdown/restarted it and got no repeat of the error.

I saw a few threads from '97 on this but no resolution. Any thoughts?

TIA

Kevin

Kevin,

When I get that FS187 message, it is always due to the fact that the networked drive that AREV is on did not connect (or map) correctly. And with AREV not being on a networked drive, AREV will not give or get a STATION.ID or LOCK items.

Although, when the networked drive does not connect (or map), normally the AREV on the networked drive will not boot up at all. So, not sure this would help you at all.

Kevin,

The last few times I 've run across people who were not getting uniques station ID's in Arev, it was due to a corrupt Arevpid.dat. This is located in the main Arev directory. Once you delete it, it will be recreated when you lauch Arev again. Why it is occuring intermittently or at all I cannot say. I certainly would re-check and make sure that the NLM is up and running properly. I would also check to see if anything else drops the connection to the server.

Hope it helps.

Kevin

Is BINDERY compatibility registered in the 3.3 client setup?

Also disable any write-behind caching in the client, and enable True Commit.

The Sprezzatura Group

World Leaders in all things RevSoft

Actually you hit on something I noticed a month or so ago. A user would report a "lockup" in AREV which is not unusual. However when I happened to check our netware console and noticed that even though the app window remained open the users login would show no files open. It was as if some network snafu had caused the NLM to close open files. Kinda like the user had logged off. I can't help but think these two issues are symptoms of a larger issue. Thanks for your response

Kevin

I have noticed some strange things happening, vis a vis: Novell showing no arev files open even though user had app window open (the app window appeared frozen but still functioned at the DOS level). Do you think this could be NWclient related? I've suggested unifying our client deployment to one version such as NWclient 3.31 i hope this will at least help in trouble shooting. Thanks for your response

Kevin

I'm going to confirm those things are implemented,

Thanks to you and all those at Sprezzatura for your continued support

Kevin

View this thread on the forum...