We are using web enabled 5.0 forms. We have hundreds of users
out in userland viewing the forms through Netscape 4.5 on NT.
Occasionaly, while using a form, the users get:
FRM-99999 Network error has occured. Client will be unable to
The form becomes unusable and none of the buttons work. The form
is dead. When I push details on the alert, I get information about
data stream and java sockets. So, I am guessing a broken java socket
has occured between the browser and the forms server. I read,
somehwere?, that a possible fix to this, is to catch the FRM-99999
error in an ON-ERROR trigger and issue a logon command to relogin to
the server. I have attempted to catch a FRM-99999 error but it seems
to be un-catchable. I dont think the ON-ERROR trigger fires during
an FRM-99999. I even tried an ON-MESSAGE trigger, no help. I have
also put a logon command within a button and tried pushing it when I
get a FRM-99999 network error to force a logon. This also did not
work. It seems as though once I get this error, the form is dead and
there is nothing I can do to restart the session within the form. To
restart a session, Netscape must be killed and restarted. Ofcourse,
killing netscape causes the non-responsive form to dissappear. All
work in the form is lost. My questions, that I hope someone with
experience will answer, are:
1) What exactly may be causing these network errors? Is it possible
the server has to many/limited socket connections? Can I change a
2) Will this logon on remedy above actually work after breaking a java
socket? Am I just approaching this logon imp the wrong way?
3) Anyone else experiencing FRM-99999 Network errors?
4) Is this possibly a Netscape 4.5 JVM problem? Will using a
different browser help?