sebster wrote:Yes it certainly does treat it as a transaction. Just losing the connection should be no problem at all for Servoy Server.
What do you mean servoy-admin did not answer:
1) did the connection succeed but did you not receive any data
2) the connection failed because servoy was no longer listening at that port (connection refused)
3) the connection failed because the port was no longer reachable (timeout on connection)
The server administration page was unreacheable (it didn't open at all); the client launch page was still available, but launching the client only made the client app start, but no solution was available for opening.
sebster wrote:Do you have any log of the incident? For example .log.txt in the root directory? (If you restarted Servoy this log is overwritten unfortunately). Do you have any specific error messages?
Unfortunately, I don't have any log (the problem occurred when I was far from my customer's location, so I didn't have the chance to save any log)
sebster wrote: Was the database server still reachable? Did it generate any error messages?
I don't know if Sybase was still reachable because the port of ASA is not open on customer's router (I normally don't need to access it directly, from WAN: I always access it using Servoy).
It didn't generate any error: the admin page didn't load and the solutions weren't available, but no error.
sebster wrote:I would like to resolve this issue for you, but I will need more information.
Thanks for your help: is greatly appreciated