61 réponses à ce sujet

[S 3]

Same here. I have never tried to connect since started play (approx 2 Months ago). Just did and now getting this same "connection interupted or timed out" error message.

Tried many times... nothing.
Tried rebooting... nothing.
Tried disabling the auto-logon... nothing.

Any advice?

[Lynnux]

Btw., the same behaviour in Dragon Age: Origins now. So it simply looks like a server change, not the Reapers ;-)

[MoonlitChimera]

I have had the same problem already for over a week. I've now also disabled the auto login to my ea account and that seems to help.

However, I have been able to retrace the problem to the Player1.prf file. In my case, I got instantely the "error: Communication with the Mass Effect 2 server was interrupted or has timed out. Please try again later." - message, and when I pressed 'ok' my game just froze up completely. I've reinstalled the game and tried loads of other things suggested in previous threads about this error message popping up, but nothing seems to help. Thinking my Player1.prf file was corrupted I tried without it and it worked just fine (having to log in again). The moment I'd leave the game and try to get in it again, it would start all over again though (the game creating a new Player1.prf file).

No idea what the cause could be though. Like mentioned before disabling the auto login to Ea helps, but I'd like to know why this is happening. Since more people have this problem, something must have changed lately. Any ideas? I

[Belhawk]

maybe something got corrupted?
i renamed player1.prf file, in profile, in the folder that holds the save games. The game recreated that prf file, logged in and now i have no timeout/interrupt message.
ty moonltchimera for the heads up on curing the problem.

[34sucks]

Belhawk wrote...

maybe something got corrupted?
i renamed player1.prf file, in profile, in the folder that holds the save games. The game recreated that prf file, logged in and now i have no timeout/interrupt message.
ty moonltchimera for the heads up on curing the problem.

Renaming my player1.prf fixed my EA server connection issue.  However doing so cleared all my in-game achievements.

Make sure to backup/rename your profile instead of just deleting it [I know Belhawk renamed it].

On Windows 7 (possibly Vista), your profile should be located here:

C:\\Users\\USERNAME\\Documents\\BioWare\\Mass Effect 2\\BIOGame\\Profile

Edit: Apparently unchecking the option to automatically login to the EA network and restarting Mass Effect 2 allowed me to login and restore my EA network connection (w/ my original profile). I suggest trying this first.

Modifié par 34sucks, 17 avril 2011 - 09:36 .

[vykor]

Well, re-logging in solves the problem temporarily too. Does removing the prf file solve the problem permanently? Or does it return after quitting the game and waiting about 30 minutes or so?

Modifié par vykor, 17 avril 2011 - 08:25 .

[Asch Lavigne]

I've also been getting the "connection timed out" or whatnot every time I start up ME2. However, when I manually log in a second later it works just fine.

[Belhawk]

2nd time i played with the new prf, i got the error again. So, i think this file is more of a symtom than the problem itself. Maybe it is the server or it is confused by some of the characters created. I currently have 2 soldiers from the same me1 import.
i will probably just turn off auto login and just not login at all since it doesn't prevent 1 from playing the game with all DLCs.

[Valorefane Dragonwinter]

I'm having this issue also. Started about a week or ten days ago. It says "can't connect to the server" or whatever, and then I click OK. I log in manually and have no problems after that.

[MoonlitChimera]

@ Belhawk: Yeah, I've tried the same thing. Deleting the Player1.prf file (or renaming for that matter) doesn't help, as it will create a new one the next time you log in and the problems start all over again... and you've lost all your achievements It just seems the problem is located there somehow but what to do about it or even why is a mystery to me atm.

I logged out for a short while about a week ago, logged back in, and suddenly the error started popping up. I didn't change anything or downloaded/installed something new so it really seems a very random problem. Only solution atm seems to be to turn off outo login and log in manually.

Modifié par MoonlitChimera, 18 avril 2011 - 12:25 .

[Hirdas]

hmm funny i have it also, but i have to log in every time i want to play dragonage as well. Just wondering about something else, why can't i see my characters from me 2 anyone know?

[cluelessnewbie]

I have this problem but it only began after I reinstalled my OS and game a few days ago. Very annoying.

[didymos1120]

OK, this seems to have worked for me: disable auto-login (may want to quit and restart just to be on the safe side). Manually login, then re-enable auto-login. Quit and restart. It should login without error. I've tested it three times, and it succeeded every time.

That, or they've fixed some server-side thing.

ETA: tested again after a couple hours, and it was erroring out again. But I repeated the above procedure, and it went back to working properly again too.   So, temporary fix at best.

Modifié par didymos1120, 18 avril 2011 - 11:55 .

[JourneyMan_Steve]

Same stuff here exactly. Very recently got this failure. It was logging in fine before. I think the did something to the DLC server. Do any of you all also have a second EA account? I do have a second one and accessed it about the same time as this PITA problem reared its head.

Modifié par JourneyMan_Steve, 18 avril 2011 - 10:58 .

[JourneyMan_Steve]

Also, seemed to have begun after I played with a (re-)imported ME2 character in resume mode. I had never done that. I've had the game for well over a year, played it thru a few times, and rebuilt the OS at least once during all that time. I'm asking for anyone with similar use cases... or is it just a new server problem? This is a very new thread and I don't like the unhappy coincidence of the dates.

[JediNg]

didymos1120 wrote...

OK, this seems to have worked for me: disable auto-login (may want to quit and restart just to be on the safe side). Manually login, then re-enable auto-login. Quit and restart. It should login without error. I've tested it three times, and it succeeded every time.

That, or they've fixed some server-side thing.

I tried this and it worked for me.

[didymos1120]

JediNg wrote...

I tried this and it worked for me.

I made an edit to that post: doesn't seem to last.  You can repeat the process, and it'll go back to behaving itself, but eventually it's going to start throwing the error again.  What's triggering it, I've no clue.

[JB23]

i recently installed 'overlord pack'...worked fine a few days ago then tried logging in tonight and get 'unable to authorize the listed dlc. please log in to cerberus network with the account used to purchase the dlc.  lair of the shadow broker, blood dragon armor'....after logging in, i can't play anything b/c get error saying can't load b/c content missing - lair of shadow broker.

does it matter if load older dlc after playing newer one?

Modifié par JB23, 19 avril 2011 - 02:37 .

[asfaltowy]

same here

[JediNg]

didymos1120 wrote...

JediNg wrote...

I tried this and it worked for me.

I made an edit to that post: doesn't seem to last.  You can repeat the process, and it'll go back to behaving itself, but eventually it's going to start throwing the error again.  What's triggering it, I've no clue.

Yeah same.  Didn't last.  I think it's because we quit and logged back in too quick lol.

[MokonaNL]

You don't need to disable auto login to gain the temporary effect you describe. It seems that auto login works if you restart the game within short period of time after closing it. If the time between the restart grows the error occurs again.
Manually logging in is probably the best course of action at this time.

[didymos1120]

MokonaNL wrote...

You don't need to disable auto login to gain the temporary effect you describe. It seems that auto login works if you restart the game within short period of time after closing it.

Yeah, I've noticed that too, but it doesn't seem to work consistently.  The disable/login/re-enable does.  Of course, it's still ultimately useless, so...moot point.

Modifié par didymos1120, 19 avril 2011 - 12:22 .

[Belhawk]

i will just not log in since it doesn't shut down any of the DLCs.
I wonder if some of MSs security patches broke auto-login.

[Belhawk]

nothing fixes the problem for me, so i am leaving auto-login off.

Modifié par Belhawk, 21 avril 2011 - 12:09 .

[jd641]

There's been no official word as to why this is happening? :/