EA_Shepard
Community Manager
Community ManagerRe: EA App Error Code EC:104
@ibra44123 Your connection only determines upload and download speeds. Your network is what can cause issues. Are you still having issues?
Forum Discussion
8 Replies
@EA_Shepard unfortunately i still have the same problem,
i checked the time and the date in my pc its fine,
i've cleared the cache and reinstalled the app,
and reinstalled the c++ files and i have put the background services in automatic and then start it
after all that i still have this errors , this is the first time i goes through that kind of errors.i send two photos of the error messages i've received .
it worked after repairing all VC Runtime 2012+ installations, setting compatibility of EABackgroundService.exe to Windows 7 and setting EABackgroundService startup type to Automatic (Delayed).
- EA_Shepard
I am glad to see that these steps are working for yall now! 👍
For anyone struggling with this problem, the following may help:
Open command prompt in administrator mode
Run net stop winnat and then start the game again, it should help (maybe the problem will arise again after restarting the computer), I didn’t find out the reason, but it helped me.yeah, this solves the issue for some reason. Thanks!
- @4jn8ilmiypku It solves the issue for me. Thank you
- @4jn8ilmiypku Thanks, this is a working if temporary fix for me, with the predominant error in my EADesktop.log being "Connect failed: <some numbers> "description":"socket is null".
The other logs in C:\Users\<ID>\AppData\Local\Electronic Arts\EA Desktop\Logs also contain the same error. Guessing it can't find a port because of this or some other conflicting issue. I'm sure the root of all this is the rancid telemetry in this app. Yes, I agree, it's definitely the telemetry service in the app that is causing all these problems. Apparently, it sends its data to IP addresses typically blocked by anti-spyware and ad-blocking DNS servers, like dnsforge.de which I was using. As soon as I switched to a vanilla unblocked DNS server, the app started working again.
@EA:
Please tone down your telemetry efforts, add proper error handling to your app and most importantly, make it work respecting your users' privacy also with regards to their DNS server choices.
Featured Places
