System busy, please try again later

rieihdius

Ok I know that this may have been asked before but honestly after a search on forum, I did not get an exact results.
Also the only google search that does have the same message goes to a dead link (maybe from the old forum)

Now to the question:
Some times when I login to the game I get pop up window that say: ''System, busy, please try again later''

here is a capture of the Message:


when i get this message I just close the game and reopen it and usually that solve the problem.

So the question is: Anyone know why I get this message?
Is just lag or some corrupt file?

So far i got this error on 2 diferent computers, a friend also got it. Here are the basic specs
An Old Samsung R480 laptop where I almost never run the game.
- Intel core i3 330
- 3GB of Ram (yeah I know is old )
- Video Nvidia GeForce GT 330 1GB
- OS Windows 7 Pro 32 bits


An old Desktop Computer.
-AMD Athlon II X3 455 3.10 Ghz
-8GB Of RAM
-Video Sapphire Radeon 5570
- OS Windows 10 Pro 64 bits (used to be 7 pro 64 and also got the error)

Last one is a friend PC and he got error 2 times so far
- i7-4790 3.6 GHz
- 16GB of Ram
- Windows 7 64
- Video NVIDIA GeForce GTX960 (not complete sure about the video)

Now as I say before the error is something not so common and not so anoying as the ''server error''
But still it would be nice to know.

Thanks for any reply in advance.

sylenthunder

It's similar. It would be better to get a traceroute taken when you are having the issue. Most likely it's from a high ping or dropped packets causing the client to not get the response it is expecting from the server. Your PC's are both plenty fine for running the client.​​

rieihdius

sylenthunder said:

It's similar. It would be better to get a traceroute taken when you are having the issue. Most likely it's from a high ping or dropped packets causing the client to not get the response it is expecting from the server. Your PC's are both plenty fine for running the client.​​

Thanks for Your reply, I had guess that it could be lag related. I honeslty forgot to do a traceroute but one of the few times I got this problem, the in game ping metter was dispaying a ping of more than 1000 ms.
Still I will make a traceroute if I get the error again.

Also my ISP is lately being bashed a lot by enraged costumers about network related problems.

Here is tracert taken at the moment of this post, I dont think it will show too much problems since Im not laging now but still can give you an Idea of how mi Client connects to the server

The first hop is my Modem/router and is configured to not reply so thats why it show a time out.


C:\>tracert pwiwest4.perfectworld.com Traza a la dirección pwiwest4.perfectworld.com [66.151.133.73] sobre un máximo de 30 saltos: 1 * * * Tiempo de espera agotado para esta solicitud. 2 15 ms 13 ms 11 ms 192.168.241.146 3 10 ms 10 ms 10 ms 192.168.241.49 4 31 ms 19 ms 11 ms 192.168.22.242 5 36 ms 13 ms 21 ms te4-2.ar3.SCL1.gblx.net [208.48.250.61] 6 118 ms 125 ms 119 ms po3-20G.ar2.MIA2.gblx.net [67.16.139.18] 7 127 ms 163 ms 125 ms xe-0-0-0-10.r05.miamfl02.us.bb.gin.ntt.net [129.250.9.117] 8 142 ms 120 ms 126 ms ae-4.r21.miamfl02.us.bb.gin.ntt.net [129.250.3.172] 9 150 ms 150 ms 148 ms ae-4.r22.dllstx09.us.bb.gin.ntt.net [129.250.2.219] 10 170 ms 150 ms 150 ms ae-3.r23.dllstx09.us.bb.gin.ntt.net [129.250.5.21] 11 181 ms 180 ms 162 ms ae-8.r23.snjsca04.us.bb.gin.ntt.net [129.250.4.154] 12 160 ms 204 ms 163 ms ae-45.r01.snjsca04.us.bb.gin.ntt.net [129.250.3.175] 13 161 ms 163 ms 162 ms ae-0.internap.snjsca04.us.bb.gin.ntt.net [157.238.64.138] 14 161 ms 171 ms 160 ms border2.t7-1-bbnet1.sje004.pnap.net [66.151.144.20] 15 187 ms 163 ms 165 ms perfectworld-10.border2.sje004.pnap.net [64.95.143.190] 16 164 ms 161 ms 162 ms 66.151.133.73 Traza completa.

sylenthunder

The first hop shouldn't be timing out unless you've disabled ping requests on that device. (Which is entirely possible, I configure mine that way sometimes.) The numbers after it do not indicate any serious issue though.

It appears as if you are going through a few internal routers before you get to an outside connection at hop 5, then hop 6 is a huge change. Hop 6 is a node in Kansas that has been giving me a LOT of grief lately. They've been dropping a fair number of packets over the past week or so.
After that, everything looks as I would expect. If Hop 6 weren't having the issues it's having, you'd probably have a ping under 75ms.​​