The SharePoint server is busy with background tasks (maintenance, back-up, etc.). The SharePoint server is under too much load from other users. It is often due to a temporary issue and it generally happens for one of those reasons: This error occurs because the SharePoint server didn't respond to a request sent by Sharegate within the allowed time limit (5 minutes). If the routers have DNS entries, traceroute will list the names of the routers as well as their network affiliation and geographic location.Ĭheck for times between hops that are greater than 200 ms or that return asterisks *** which indicate that your request has timed out.Ĭopy and paste your results and send them along to us if you think there is something which we should investigate.SharePoint took too long to respond to a request. Traceroute will tell you how many routers your packets travel through, and how long it takes for them to travel between routers. More information on how to clear your DNS.įrom your hard-drive, open the Applications folder, and click to open the Utilities folder. 
Sometimes DNS caches (different than browser caches) can get corrupt and that command will flush the cache on Windows computers, but it will skip any DNS entries currently in use so all browsers windows/tabs must be closed. On Windows, another thing you could try is to close ALL browser windows (has to be ALL of them), then go to a command prompt and type. Tracert If there are more than 2-3 hops (host names and/or IP addresses) in the trace but it fails to reach the site then the network issue is upstream from you. If you are running Windows, you can see where the break is by going to a command shell and typing.
Here are some suggestions on how to resolve this: took too long to respond." This means there is a connection issue between your device and our website. You may have come across the following error in your browser: "The site can't be reached.
0 kommentar(er)
