Forum Discussion

Viejo99's avatar
Viejo99
Seasoned Rookie
9 years ago

Error syncing cloud storage data

For past two days, whenever launching into a BF4 game from battlelog, I get an origin popup stating "ERROR SYNCING CLOUD STORAGE DATA" (yes, the error message is in all-caps).

I can hit retry until I'm blue in the face, so have to choose "play anyway" to get into game.  At end of each game it always pops up similar message with only "retry" and "cancel" as options.

I posted about this in BF4 PC forum and many responded that are having same issue, and three people I regularly play with are all having the exact same problem.  

Is this a known problem?  

Is there a known solution?  

Is there a solution in progress?  

Is there an ETA?

Thanks.

battlefield 4

5 Replies

  • Indys2nd's avatar
    Indys2nd
    Hero (Retired)
    9 years ago

    Are you posting this also on the new Battlefield forum or the old Battlelog forum? It is bound to receive more views there and get forwarded to the right person. I have Origin set to not be on in game. I do not sync it with the Cloud. That's one option is to turn off Origin in game. But, if you prefer to keep it in the Cloud,  then it's something to bring to EA's attention. Game advisor: https://help.ea.com .  We are just a player helping player forum and can't really help you here. 

  • The_Patcher's avatar
    The_Patcher
    9 years ago
    @Indys2nd wrote:

    Are you posting this also on the new Battlefield forum or the old Battlelog forum? It is bound to receive more views there and get forwarded to the right person. I have Origin set to not be on in game. I do not sync it with the Cloud. That's one option is to turn off Origin in game. But, if you prefer to keep it in the Cloud,  then it's something to bring to EA's attention. Game advisor: https://help.ea.com .  We are just a player helping player forum and can't really help you here. 

    I reported it though support, but  at the end of submitting the new ticket I was forwarded to these forums.
    And I assume not only battlefield 4 is affected, the cause is in the origin client.

    Is there a way we can provide more information - e.g. by enabling some logs?

  • The_Patcher's avatar
    The_Patcher
    9 years ago

    I found this in the origin client log (C:\ProgramData\Origin\Logs\Client_Log.txt).

    **391 Mai 26 16:47:53.642 Warning Origin::Services::NetworkAccessManager::handleSslErrors 3992 Request to https://cloudsync.dm.origin.com/cloudsync/manifest/xxxxxxx failed with 2 unsuppressed SSL errors
    **392 Mai 26 16:47:53.642 Warning Origin::Services::NetworkAccessManager::handleSslErrors 3992 Certificate with common name(s) 'O=Electronic Arts, Inc. CN=cloudsync.dm.origin.com L=Redwood City OU=EA Online/Pogo.com C=US ST=California ', SHA-1 '9119793d5c677ba74e1c8a1d5cd66cde1cfa0308', expiry '2017-05-18T23:59:59Z' failed with error 'The issuer certificate of a locally looked up certificate could not be found'
    **393 Mai 26 16:47:53.642 Warning Origin::Services::NetworkAccessManager::handleSslErrors 3992 Certificate with common name(s) 'O=Electronic Arts, Inc. CN=cloudsync.dm.origin.com L=Redwood City OU=EA Online/Pogo.com C=US ST=California ', SHA-1 '9119793d5c677ba74e1c8a1d5cd66cde1cfa0308', expiry '2017-05-18T23:59:59Z' failed with error 'No certificates could be verified'
    **394 Mai 26 16:47:56.177 Error Origin::Services::OriginServiceResponse:😛rocessReply 3992 OriginServiceResponse QNetworkReply error code [203] error string : [Error downloading XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX - server replied: Not Found] HTTP status code [404] ...
    **395 Mai 26 16:47:56.177 Error Origin::Services::OriginServiceResponse::reportTelemetry 3992 Failed with REST error code -1 error string: Error downloading XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX - server replied: Not Found
    **

    Looks like there is a problem with SSL certificates.

  • The_Patcher's avatar
    The_Patcher
    9 years ago

    The log file started in April, but the "Origin::Services::NetworkAccessManager::handleSslErrors" messages started yesterday, May 25th.

Recent Discussions