Do you have the same errors when users are connecting from HQ?

If yes, then this is a major problem in your Sage installation and, as a minimum full folder validation must be executed.

If no, then this is very odd case, nevertheless there can be some network lags and issues related to this. How to determine? Open VPN connection from remote office to HQ and run ping command to Sage server or whatever resource located in HQ. If there are a lot of packet loss or respond time have big numbers your network connection is very poor and needed to be fixed in prior to Sage connection issue.

Hi. no we don't get any errors when connecting from HQ. i tried pinging our SAGE server from our remote site and i got 17ms and 16ms in reply time. here is an image.

Dummy question, are you using the same user when you'r connecting from HQ and remote site?

What version of Sage X3 you'r using?

Yes. I use the same user. and i don't know which version but the product update shows me 9. where can i see the version of my sage x3?

Do you have this connection problem always or just sometimes?

Version can be found under Administrator-> About, the first line will show it.

somethimes. Web server version 9.3.102-0.

What exactly this particular user is doing when getting this error? Can this user repeat the same actions in HQ network?

This is very important to catch-up, 'cause there was some connection-related issues in 9.3 version. 

The user can be doing anything. Trying to view a sales order or trying to view a purchase request or trying to see a stock transaction, the error is the same. and yes the user can do all these things without error when he/she is at HQ. did you say connection related issues in this version? what kind of issues? can they be solved?

Have seen such behavior on this version when more then one browser with Sage opened was used on this version. As far as have updated version till 9.7 haven't seen such behavior anymore.

But still wan't to point you to the network related issue here, 'cause as you mentioned, when users are working in HQ there is no such behavior seen. And, to make clear, Sage web server is independent on network infrastructure you'r using to get connected to server. To make clear, run ping command from remote place to Sage server using, like PingPlotter for a long time, then you will see is you'r network connection stable and so on, 'cause running ping for a 4 replays is not enough to make sure that everything is fine in network infrastructure.

More, can you connect from remote location to Sage server (or any another computer located in HQ) via remote desktop and take a look is everything fine.

i connected to one of the servers in our HQ using remote desktop and i login to sage from a browser from that server and everything is fine. but when i try it from a browser in our remote site, it shows me that error. i think you might be right about the poor connection. but what i don't get is that i can get connected to any server in our HQ with remote desktop and use other applications or features easily and well. the problem arises when i use sage. 

You see, there is a huge difference in methods how remote desktop connection and Sage web server are working. To make clear, you need to use similar technology resources, 'cause remote desktop is quite "strong to avoid or hide network problems".

Only possibility to get something more clear is to run PingPlotter for a while from remote site to Sage server and then analyze the result.

Ok. Thanks for your response. I will try PingPlotter.