🛈 Announcement
Greetings! The Crew forums are now archived and accessible in read-only mode, please go to the new platform to discuss the game
  1. #171
    myx6's Avatar Junior Member
    Join Date
    Sep 2020
    Posts
    4
    Hi.
    The game works. THX. Holidays this year earlier. HEHE
    Share this post

  2. #172
    Just wanted to let folks know that The Crew magically started working for me today. Odd thing was the first time my NAT said moderate on the games screen, so I went into my Xbox settings and it was on double NAT strict!?
    I wanted to play the game for a while before trying to reset it. After a while I checked my router settings and got my Xbox back to Open NAT. Thought for sure as soon as I started the game it was going to boot me with the error again but much to my surprise it did not. Hope the rest of you had the same luck today.
    Share this post

  3. #173
    maarcis12's Avatar Junior Member
    Join Date
    Oct 2015
    Location
    Latvia
    Posts
    19
    Thank you very much, it took you long, but you finally fixed it.
    Share this post

  4. #174
    Ubi-Raziel's Avatar Ubisoft Support Staff
    Join Date
    Jan 2019
    Posts
    4,533
    Hello everyone!

    There were many threads regarding this thread so I have merged you all together.

    As many of you can see, we implemented a solution during yesterday's maintenance which seems to have resolved the issue.

    We are keeping an eye on it for the time being, so we're certain this fixed has worked for everyone.

    If you are still affected by error #3_7f0fbc84_142 please let us know.

    All the best to you!
     2 people found this helpful
    Share this post

  5. #175
    Hello. Here we go again... it's been a week since this error is happening again.
    Can someone please have a look at it?

    Thank you!
    Share this post

  6. #176
    Ubi-Orion's Avatar Ubisoft Support Staff
    Join Date
    Dec 2018
    Posts
    2,324
    Originally Posted by Stricken03 Go to original post
    Hello. Here we go again... it's been a week since this error is happening again.
    Can someone please have a look at it?

    Thank you!
    Hi there.

    If this issue is still present for you can you give our connectivity troubleshooting a try first of all please? If the issue persists after doing so please let me know.
    Share this post

  7. #177
    Originally Posted by Ubi-Orion Go to original post
    Hi there.

    If this issue is still present for you can you give our connectivity troubleshooting a try first of all please? If the issue persists after doing so please let me know.
    I don't know if you noticed it, but it's an all platform issue that has been keeping us from playing the game for nearly 2 weeks now. This kind of issue happens every 6 months and it always boils down to something being broken with the Wild Run expansion and someone who participated in the Summit (as evident by base game players not suffering from this re-occurring bug, and new players that have yet to compete in the summit)

    So no, that garbage of a connectivity troubleshooting will not help in this instance.... I'm surprised that no one in the studio hasn't made a knowledge base of their own, to speed up the fixing of the same issue in less than week's time.
    Share this post

  8. #178
    My game went down end of November.
    I have never competed in a Summit Race. I did get the base game to work but all addons crash the game with error #3_so on
    I have an xbox one x console on uplay connection. No Steam
    I was communicating with Ubisoft about this but they closed my case before it was solved. Just blew me off.
    But like I posted before, I got the base game to work by uninstalling Calling All Units and Wild Run.
    A lot of my vehicles are gone (drag cars, motorcycles, monster trucks, police cars and some hyper cars) but the game itself is playable for me.

    I haven't been on an xbox one in awhile (mine is an X) and I think its a little different but you can separate the base game with the addons to uninstall by unchecking them.

    Xbox One X
    Go to:
    My Games and Apps on home page
    then click Full Library
    select All Games Owned
    select The Crew game icon
    select second tab from bottom left ( Manage )
    Uncheck Calling All Units & Wild Run
    Save changes
    Will uninstall automatically
    Restart The Crew from home page

    Hope this helps. Good Luck!
    Share this post

  9. #179
    Originally Posted by Ubi-Orion Go to original post
    Hi there.

    If this issue is still present for you can you give our connectivity troubleshooting a try first of all please? If the issue persists after doing so please let me know.
    Stop please to kidding us!
    Its no problem in our Networks, Ports or anything else! The problem is in your game! Since two weeks now and its Friday again. Next weekend without The Crew....
    If the Team need more time or is not able to fix it.....Just say it and dont reach time with this troubleshooting trash!!
    Sorry for the hard words, but I'm very disapointed after this time.

    I think you need a Dev from Ivory to fix it and thats cost money. And UBI will not spent money in an old Game!

    Every little Company is able to fix a known issue in two weeks. ...if she want!
    And we talking here over Ubisoft, a big Player in the Game Industrie!

    Point of this to long post!
    Please tell us the True and dont reach time!
    Share this post

  10. #180
    Ubi-Raziel's Avatar Ubisoft Support Staff
    Join Date
    Jan 2019
    Posts
    4,533
    Hello everyone!

    Apologies for previously sending connectivity troubleshooting. This is standard practice if we receive a single report of an issue that we thought to be resolved.

    As you are all affected, it seems clear to be that this is something we will need to fix server-side.

    We are planning to release a fix for connectivity error #3_EA3A66D7_111 on Monday which also affects all platforms.

    Here you go: https://forums.ubisoft.com/showthread.php/2312213

    Please try playing the game once again after that update. If the issue persists, let us know and we'll ask our dev team to look into this further.

    Thank you!
    Share this post