In case of an SQL error the message "transaction not connected"or "communication error" is issued, followed by other SQL error messages or program errors.
Possible cause: network failure, faulty cable, interfering influences, faulty drivers, network overloaded etc.
Usually, Beas tries to reconnect and to continue work. If the error message appears only once, it can be ignored. If, however, due to interference no connection is possible, the network must be checked by an expert. In this case, please contact your administrator.
This error can occur sporadically, as in background regularly the following statement is executed
select isnull(max(eventnumber),0) from Beas_event where touser=...
select ifnull(max("EVENTNUMBER",0) from "BEAS_EVENT" where "TOUSER"=...
More on this statement see Standstill