We are receiving inputs from some of our end-users saying that they receive this error message in smart client and can not use it. They have no firewall active.
Beside the firewall, which is not the case, what could be the cause of this error and how can be solved?
We are receiving inputs from some of our end-users saying that they receive this error message in smart client and can not use it. They have no firewall active.
Beside the firewall, which is not the case, what could be the cause of this error and how can be solved?
Greetings,
Bogdan.
We experienced this for the first time today too - OK on one PC and not on another - same LAN - connecting to the server over the web. Because we figured the system was well broken and Java reinstall did not fix it (and a system Restore did nothing) we ended up bringing forward a system upgrade for that PC to Win 7 - Now OK again. But it would be very useful to know the reason!!!
We don’t know why. But when we have this error (cannot find dataservice), we go into Java>Network Settings and set it to “Direct Connection”. Then it works fine
I’m waiting an answer from the users. I told them to try direct connection.
I have changed the tunnelConnectionMode to http&socket. Can Servoy automatically change the mode from socket to http in a proper manner in case it encounter problems with the network and fails the data transfer using sockets? Or it’s safe to let it on http only?
I have noticed that the TwoWaySocket setting exists also in client’s preferences. Is this the only one? What about the TunnelConnectionMode? If I changed it on the server will the clients be affected by the change or they will have the old setting?
In general, if I change preferences on server that also can be changed from the client, like NumberFormat, or this TwoWaySocket property, how can I force all clients to read them from the server and override their local settings?
will always be pushed, same for its TunnelConnectionMode
2 way socket is a client property because clients dont have to use that if they are in the same local lan of the server… But normally you dont want to set this at the clients to false if the server is true
You cant push this property to be changed if the client did set it them self.