Error after submiting new multiplayer game version

I just tried to submit the latest version of my multiplayer game ( in beta ). Every time I try to connect to the server I get a "Unable to connect to server" error.

I dont seem to have any problem connecting to my older versions, however when I re-submit an older version I get the same server error. This leads me to believe that I havent introduced some kind of error into my code. I have been running everything fine locally.

Are there any known problems with the flash submission process, also is there any way to get more information then "Unable to connect to server"

My current plan of action is to just try to re-submit my game in a few hours.

Now I cannot even go to the version tab of my game, I get a Server Error:


We're sorry, but an error occurred while processing your page.

Please try again.


The version tab works fine on another game I have.

I tried using Firefox and Chrome to submit my game with the same results. I had first thought my firefox no script ad on could be causing a problem.

I was able to post a new version into a different game profile and everything went ok. Went I tried to submit another version there which used the same server dll I started to see the same problems again.

I am wondering if posting the same server DLL into a games profile is causing the errors.

I created yet another game profile, made sure I uploaded all the correct files, and everything works. So I am sure that my files are not the issue.

Right now it seems like uploading the same server DLL causes issues. It works the first time but then all of the other game instances get "Error connecting server" errors. There seems to be a limit of 1 server DLL per game profile. It would be nice to have clarification on this since one of my game profiles has gotten locked down.

We are aware of this issue and is working on it.

Any fix for this in sight? I'm having same issues.

Is it possible to get an idea of how long this fix may take? I want to release a game soon ( 2 months ) and this bug could cause some serious problems if I need to update it after release.

Hi,

This issue should be fixed now.

The reason it took so long, was that it was really hard to locate exactly what was the issue. We couldn't reproduce it in any of our development or staging environments.

It turned out to be a special value that was in our production memcached cluster, which caused erratic behavior in exactly this case for some users.

Please contact me directly if you have further issues