Anyone out there with RFS knowledge and/or Windows 2003 server knowledge? Having issues with master reboots,trans.log errors on systems with 10 to 41 terminals.
Limit the number of master terminals you have defined. By that I mean in environment variables and in ibercfg.bat make most of them master and server capable false. You only maybe want 10% of them to be master and server capable in that large of an environment. That will cut down on network traffic and help with performance. Also check your debouts, there is one for rfs on every terminal, see if you can see any fatal errors in there around the time the translog corrupts. And remember, not every version is perfect, you may find another is better. I hear the latest 6.2, 6.2.21 has the best rfs files yet.
have done all that. we are down to trying services signing on local account instead of .\Aloha. If this doesn't work, we will probably put server 2003 on master terminal and remove rfs. Somehow 6.2.20 broke it and 6.2.21 just cannot fix it.
We have no cure as of yet. All three sites are different as far as network topology, hardware and TS or QS. The commonality for failure we think is the version 6.2.20 upgrade. We upgraded to 6.2.21 which seemed to help one site, but not the other two. However, this site crashed again last week.
Email me directly for assistance. I am a former Aloha Reseller and probably can help you out. Have worked on large networks with RFS and such. My website is
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.