Release Date Check
#76
Posté 07 mars 2012 - 04:12
#77
Posté 07 mars 2012 - 04:16
Doc-Boom wrote...
This may or may not help, as I was having a similar issue with the release date check. I'm running Win7 x64. Here's my process:
1. Open the release date checker.
2. Go to Task Manager -> Processes
3. Right-click the Mass Effect 3 release date checker process (I've forgotten the name)
4. Click the Open File Location option (Mine was in C:UsersUSERNAMEAppDataLocalTempmtka_tmp) and copy the path to the file
5. Go to Windows Firewall settings, click Allow a program...
6. Add the program (not MassEffect3.exe, but the release date checker program in the temp folder)
7. Click the "GO" button for the release date checker (or whatever it says... Next... OK... etc.)
8. TAKE EARTH BACK!
I need help finding the exact location at #4, I have to have the "Release Date Checker" running just so this shows up and when I Open the file location there are several files...
#78
Posté 07 mars 2012 - 04:31
I'm POSITIVE it's the damned Release Date Checker that is the problem, I just need to get past that.
#79
Posté 07 mars 2012 - 04:37
82JiminyCricket wrote...
Damn, my Release Date Checker still keeps bugging out (the *DING DING* shut down, then the same old "MASS EFFECT 3 has stopped working").
I'm POSITIVE it's the damned Release Date Checker that is the problem, I just need to get past that.
Well, I didn't get any error messages, but the name of the file is something like MassEffect3-activation or something like that. Same as the name of the process you right-clicked to get to the folder location. Unfortunately, after you first run it, it disappears, so I can't go back and look.
#80
Posté 07 mars 2012 - 05:54
It's probably not a firewall issue, but when in doubt it's always a great idea to just turn the damn thing off for a few minutes during the release date check. Remember it (should) only authenticate once and this (should) only take a moment. Once you see the game launch you can go ahead and flip the firewall back on (assuming it isnt interfering with EA's in game server communication and causing DLC issues, but that's a horse of a different color). If you want to be extra thorough and save screwing around with settings, disable the firewall and bypass your router if you're running one (as they often contain a hardware firewall or port forwarding settings). This issue being attributed to router or firewall issues is extremely unlikely but not impossible (I don't run Windows firewall, so if the previous fix mentioned resolves it for you, awesome)
Make sure you're running the LATEST version of Origin. EA Has confirmed issues with Mass Effect and old Origin clients, there's a help file on their site detailing this. Much of the time the client is not set to auto update like other digital distribution platforms *CoughSteamCough* and must be manually updated. If this update fails (It did for me) you will have to uninstall the existing copy of Origin completely, and possibly have to edit the registry to remove all pre-existing entries if you're still unable to install the newest version after this.
Once this is done and the game is giving you the activation attempts followed by a progress bar flash and a *ding* noise you can try either:
Origin may not be running with Administrator privledges. If it's already running on startup, right click the quickstart icon in the bottom right (down near the clock) and exit Origin. Then try modifying the program's compatibility settings by right clicking the shortcut on your desktop and forcing it to "Run as Administrator" - This fixed it on the Win 7 x64 box despite the fact that the user was only utilizing the Administrator account on the PC already (there were no other users) and had run a command line script to take ownership of the folder and all files within it and manually assigning them to the active user. The activation check failed until the "Run as Administrator" option was checked, so give it a try. After this, this box was able to run the game just fine. Troubleshooting this issue would have been MUCH easier had EA properly given an error code or stop error when the updater fails... but I've long since given up on them programming anything properly and having them suggest "Contacting the game vendor for a refund" didn't exactly help alleviate the issue.
Another user utilized the FlyVPN client that was already mentioned by someone else in this thread. This is done by visiting their website and downloading their client, then using their free trial code to connect, then selecting the "Asia" tab at the top of the available servers list and then selecting "Hong Kong" - This worked for the other machine and it was able to pass the release date check, after which we disconnected and uninstalled the VPN and play proceeded normally.
Modifié par Khaldara, 07 mars 2012 - 06:01 .
#81
Posté 07 mars 2012 - 06:42
edit: Also, thank you to the previous poster. I am trying those suggestions out now.
Modifié par SLZ117, 07 mars 2012 - 06:43 .
#82
Posté 07 mars 2012 - 08:44
#83
Posté 08 mars 2012 - 07:11





Retour en haut






