Old AMS system (AREV) (AREV Specific)
At 13 SEP 2002 04:33:19PM Jon Stevens wrote:
I have recently loaded the revelation service onto a new Windows 2000 server at our company. They are still using a very old version of AMS (AREV). They use 1 pc as a background processor for printing from AMS. After about five minutes of printing it locks up and they receive this error on the screen:
RTP32 Line 1
ERRMSG(B114)
ERRMSGD4 1 RTP18
!
Then we need to logout of AMS, log back in as TCL and start the background processor(Bg). Any advice would be greatly appreciated. My email address is : jon.laser@snet.net
At 13 SEP 2002 05:12PM Richard Hunt wrote:
Oh gosh… hmmm…
Well the "RTP32" error message is an RBASIC "FIELDSTORE" statement. Probably one of the arguments in the "FIELDSTORE" statement is undefined.
The "B114" is a message that basically is saying "it" is not found. I am not sure what "it" is.
The "RTP18" is the TCL command processor.
I ran into something like this with one customer. They seem to keep loosing network connection. I checked that the server and workstation did not go into "hibernate" or "stand by" modes. Also I verified that the network card did not ummmm… "go to sleep". Because once AREV decides that it can not connect (or looses connection) to a network drive, it (AREV) does not try again. And the connection is lost until you logoff and login again.
Well that is all I can say about your problem. Hope it helps ya.
At 13 SEP 2002 07:49PM [url=http://www.sprezzatura.com]The Sprezzatura Group[/url] wrote:
What version of AREV? Sounds like a problem we have seen with Windows 2000 and AREV 1.12.
World Leaders in all things RevSoft
At 16 SEP 2002 03:09PM S Botes wrote:
Saw a similiar problem with a Novell server and the NLM. A workstation that had made no requests to the NLM would have the connection dropped by the NLM. And even though the AREV app was open but idle, no indexing either, the connection with the NLM was dropped. The Novell workstation connection was fine. This was solved by increasing a parameter similiar to an idle disconnect in the revparam file… sorry don't remember exactly what it was.