Hey all,
Some updates on this topic:
ME:A
It is quite normal that ME:A players may often encounter error messages, primarily due to its dependence on peer-to-peer hosting. Our testing showed that we faced numerous failed attempts when we attempted to host or accept invitations on certain IPv6 addresses. However, we consistently succeeded when using a (static) IPv4 address. It's important to note that additional complications can arise from the use of Teredo tunnelling (used by some routers or ISPs) or VPNs. Unfortunately, these issues are likely to persist as there are no dedicated servers for the game.
However, we do have some potentially handy network troubleshooting steps that might help you in this situation. They can be found here.
ME:3
In the case of ME:3, some players experience problems with the game being correctly identified when launched from Steam up until late September or early October. The issue has internally been resolved by clearing the License folder. If any of you encounter an error stating that the game is not owned or installed, and you have not deleted the contents in the License folder and executed a game repair, we strongly recommend doing so.
*Especially the game repair (EA app) or verification of the game files (Steam).
In our testing, all boot issues were completely resolved after the deletion of the contents in the License folder, which is a step that does not occur automatically when the fix is installed.
How to delete the contents in the License folder
- Open Windows File Explorer and copy/paste this 'url' into the address bar: C:\ProgramData\Electronic Arts\EA Services\License.
- If you can't copy/paste this 'url', you can enable the "View hidden files and folders in Windows" option via these steps and navigate to the folder manually.
- In the "License" folder, where you should be if you've followed the above-shared steps, check if you can see any files.
- If there are any files, select them all and launch the game again & try to invite someone again or join an invitation. The game should now work.
If the problem persists, please report back to us in the thread.