[PC] There is a problem connecting to the server. ME1 authorization issue.
I installed Mass Effect 1 on Friday afternoon, on Windows 7 64 bit (Home Premium, Service Pack 1), using an install disk that uses the 5 authorizations style DRM. Due to personal preference, I'm not ...
We made some changes in order to try to fix this issue, but you didn't give us enough time to test it for all the games. 😉
Glad to hear it's working for you with Need for Speed Undercover! If anyone tries other games, please let us know how it goes!
Thanks, -Mai
Anonymous
8 years ago
Current situation: The problem seems to be on EA's end. They are aware of the issue, and a fix is hopefully in the works. I will update this post when I hear more news.
-
A work-around has been discovered thanks to @beerxced79000's posts on the Sims 3 thread. For more detail, refer to the posts here and here, and @puzzlezaddict's post here. If you're experiencing problems specifically with Sims 3, please follow puzzlezaddict's post for a potential solution. It was thanks to these posts that I managed to get Mass Effect to authorize, and it now works fine. However, due to the nature of the work-around, it may not be viable for everyone. Thanks to @beerxced79000's follow up information, I'm going to try explain the process here in a step-by-step format.
Warning: Before proceeding, this is going to involve swapping some game files around. If you're not comfortable with that, and you're sure you're experiencing the same problem, then the best thing to do is wait for an official fix from EA. With luck, you just have to be patient and wait for news 🙂 Please check your internet connection (information about how to do that here) to be sure that isn't causing the issue. I cannot guarantee this fix will work for you, and am not responsible if you accidently delete or break your game files. I am using Windows 7 64 bit, and may not be able to help if you're on another operating system.
-
Step 1: Determine if your game files have the 'paul.dll' file.
This should be located under your game's install directory, under either a 'binaries' or 'bin' folder. A 'winui.dll' should be in the same folder too. Example screenshot, credit to @beerxced79000
If your game does not have the 'paul.dll' file: As far as I know, this work around won't work for you, and you'll have to wait on a fix from EA.
If your game does have the 'paul.dll' file: Proceed to step 2.
Step 2: Replacing the 'paul.dll' file with another version of the file that will work.
For this, you're going to need to have another EA game which uses this .dll. I personally used Sims 3 files (following puzzlezaddict's post), and beerxced79000 seems to have used the files from Medal of Honor 2010. If you don't have either of these games, check this list for other possible games to look at. If you have any of these games, navigate to their install directory, and check under their 'binary' or 'bin' files to see if they have the 'paul.dll' too. If you don't have any other games with the 'paul.dll', this fix won't work for you, and you'll have to wait for a fix from EA.
If you've found another game with the 'paul.dll', proceed to step 3.
Step 3: Check what versions of 'paul.dll' you have avaliable.
To do this, right click on the 'paul.dll' file, and select properties. On the window that appears, click on the 'details' tab.
The highlighted numbers are what you're looking for. As far as we know, 'paul.dll' versions 4.1.1.13 and 4.1.1.14 are not working. If you only have these versions of the 'paul.dll', then this fix won't work for you. I can personally confirm that version 4.1.1.18 works, and if you have any other versions that aren't mentioned here, then it's worth continuing to try this fix. If you've found a potentially viable version of the 'paul.dll', proceed to step 4.
Step 4: !!BACK UP YOUR FILES!!
Again, I can't guarantee that this work-around will work for you, so make sure you have your files backed up before you change anything. Navigate back to the game that won't start's binary files. Create a new folder, name it whatever you want, then move 'paul.dll' and 'winui.dll' into this new folder for safekeeping. Do this either by dragging and dropping them into the new folder, or by cut and pasting them into it.
With your original game files safe, proceed to step 5 🙂
Step 5:Copy and paste (do not cut and paste like before) the newer versions of 'paul.dll' and 'winui.dll' from the other game files. These files work together, so make sure you get them from the same game, from the same folder. Place them in the 'binary' folder that you just moved the old version of 'paul.dll' and 'winui.dll' out of, so they're in the same place as the game's .exe file.
And that's it! Your game should now connect to EA's authorization servers, and start normally 🙂 If you still get the "There is a problem connecting to the server." message, then please check your version of the 'paul.dll', and let us know if it's not one of the versions mentioned here, so we know how many versions are effected by this issue. If this work-around doesn't work for you, make sure you return the old 'paul.dll' and 'winui.dll' files back to their original folder, so everything is back to its original state while you wait on a proper fix from EA.
OK, @EA_Mai and I figured out why there is a difference in the installation files.
It is because I use the Origin Access primer version of Mirror's edge (2009).
The "normal" purchased digital version still contains the "paul.dll" files while the Origin Access primer version is based on the Origin standard "Activation.dll" files.
In this process we also determinated that the Origin version with the "paul.dll" files woks flawless "out of the box".
So any problem whit the activation process of Mirror's edge (2009), regardless of the version, is not on EAs side, at least not in the moment.
no indeed! but I will not go into detail on the subject because EA may end up asking questions lol
there is a specific proxy for the activation of the Origin games and another very specific for the activation of the securom games at EA!
securom is content to start the game to look for a license on the user's computer in a file called "securom-v7-01.dat" in a hidden folder (user / username / AppData / Roaming / SECUROM / userdata)
if it found it, securom allows the program to start otherwise it uses paul.dll to recover a valid license! During this operation if there is any problem, the license server will generate a 4-digit GL code and securom will call winui.dll to display the message window on the user's screen with the corresponding message to the GL code! his messages are in a file called gl.ini next to paul.dll and winui.dll! you can open it by curiosity with the notepad windows😉
The logic would have wanted from the beginning to do things well, to replace the file gl.ini too, but as in any way the activation process is supposed to happen without problems, we do not care a bit: )
Origin stock the licenses in "programdata / Electronic Arts / EAservices / licenses" which has nothing to do with securom
here for today's lesson! An interview next Monday and good review
😉
About Mass Effect Franchise Discussion
The fate of the galaxy lies in your hands. Join the Mass Effect community forums and tell us how you'll fight for it.19,235 PostsLatest Activity: 6 hours ago