Forum Discussion

EA_Shepard's avatar
EA_Shepard
Icon for Community Manager rankCommunity Manager
2 years ago

Re: (Old Report) Dragon Age Keep Error Oops, An Error Has Occurred

Hey Everyone,

If you have not already tried, you should be able to access the keep again. If not clear all browser history and cache and you should be able to log in after that.

17 Replies

  • Tekenou's avatar
    Tekenou
    2 years ago

    Thanks it works! miracles do still happen, happy dragon aging everyone.

  • Bah. Yeah, it worked...long enough for me to spend 30 minutes working up a new world state then crap out before I could save it. This thing blows chunks.

  • EpicSorcer's avatar
    EpicSorcer
    2 years ago
    @EA_Shepard... I enjoyed readying all of the replies to my post because when I got to these last couple of updates, it just made the world make sense again... Very happy, thanks for letting us know.
  • Zstiegz's avatar
    Zstiegz
    2 years ago

    Yeah so no the issue as of today is not solved.  

    I am able to log in, and I see my default world state from like...years ago.  But the moment I try to change anything, including choosing a different world state, it goes into loading mode, and will load until I get the "Oops, An Error has Occurred" try reloading.

    This isn't a connection issue or an account issue, what on earth is going on with this website???  (also since there is no analog way to import our saves) I literally can't play Inquisition without having a blank World State...


  • EA_Shepard's avatar
    EA_Shepard
    Icon for Community Manager rankCommunity Manager
    2 years ago

    @Zstiegz The world state itself isn't necessary to actually play, just cannot play with the decisions prior games had which is what we want. This issue was resolved. I attempted to log in on three browsers and three different connections and was able to get in.

    Can you please clear all browsing history and cache from all browsers that you use and then reset your EA password to something simple and then try again on different connections if you can?

    Since you can use any browser this can be on console, PC and mobile devices. This has nothing to do with your connection so we don't need to troubleshoot connection issues since it is a site issue. However, as the issue is resolved, it can be a cache issue or a bad login preventing you from logging in.

  • lizmeyerr's avatar
    lizmeyerr
    2 years ago

    This issue has been happening for me as well since August 2023. I've tried everything (clearing my cache, changing browsers, using a different device, using incognito mode, clearing my temp files, etc.) I also spoke with a live EA chat agent who said she would report it but didn't know when it would be fixed. Is this happening for anyone else recently or is it an issue with my account?

  • As potentially dumb as this solution may seem, it has been working for me the past week.

    All week I've been getting Internal error 500 whenever I attempt to "Sign In" on the Keep. I coincidentally logged into ea.com after one failed attempt, while searching the forums, then decided to try one more time. The Keep logged me in with no issue. Every time since, the Keep still gives me the 500 error, and then I go to the main ea.com, log in, and tab back over to the Keep; clicking Sign In sends me straight to the tapestry with no issue.

    If I were a betting man, it seems like the Keep's frontline log-in site has some serious issues attempting to connect to ea.com to initialize the username and password section of the login. If you instead open another tab and login on ea.com, tab back over to the Keep's site and hit Sign In, it bypasses the username/password splash and instead connects directly to ea.com to validate your account.

    This may not be a permanent fix, but it's working for me as of 13NOV23, and has been for the past week.

  • EA_Shepard's avatar
    EA_Shepard
    Icon for Community Manager rankCommunity Manager
    2 years ago

    @JCPhoenix83 wrote:

    As potentially dumb as this solution may seem, it has been working for me the past week.

    All week I've been getting Internal error 500 whenever I attempt to "Sign In" on the Keep. I coincidentally logged into ea.com after one failed attempt, while searching the forums, then decided to try one more time. The Keep logged me in with no issue. Every time since, the Keep still gives me the 500 error, and then I go to the main ea.com, log in, and tab back over to the Keep; clicking Sign In sends me straight to the tapestry with no issue.

    If I were a betting man, it seems like the Keep's frontline log-in site has some serious issues attempting to connect to ea.com to initialize the username and password section of the login. If you instead open another tab and login on ea.com, tab back over to the Keep's site and hit Sign In, it bypasses the username/password splash and instead connects directly to ea.com to validate your account.

    This may not be a permanent fix, but it's working for me as of 13NOV23, and has been for the past week.


    We appreciate the details on this. We can forward that over for review. They are still good steps to have especially if they work for you and you are able to get in.

    Cheers!

  • Just got the same issue just after finishing DA2 with mods and went to check my Dragon Age Keep just to find my profile picture in the login screen had changed to a question mark and got the pop up saying an error had occurred , I had tried every single solution given in the forum but to no avail. Decided to wait a week to see if it worked but it still didn’t so I asked a friend to share a world state with me but when he tried searching for my username in the friends list apparently my account didn’t even exist in Dragon Age Keep anymore. 

    Is it because I used mods on DA2 and it somehow corrupted the import to the keep? I remember watching a video and the person said that modding DA2 could corrupt your DAK..?

    idk hopefully it’ll fix itself sooner or later

  • lizmeyerr's avatar
    lizmeyerr
    2 years ago

    My profile picture has the question mark on the login screen as well (and it never had that before). I do wonder if it is a modding problem because I had started a new playthrough where I had mods in both Dragon Age Origins and Dragon Age 2 and that is when this issue started happening. I really hope this gets fixed soon seeing as how I've been waiting on something to change since August.

  • EA_Shepard's avatar
    EA_Shepard
    Icon for Community Manager rankCommunity Manager
    2 years ago

    @lizmeyerr The keep at this point has very little support so if it was a keep issue, it would not really be high on the list of priorities right now but can still be reported.

    If there are mods involved, I would do a manual edit with a new playthrough with no mod data to test it. Mods can be an issue for sure but wouldn't know unless you test it out in your keep.

  • can confirm that a fresh install, new playthrough and no mods does not solve the issue with the error loading on the keep

  • EA_Shepard's avatar
    EA_Shepard
    Icon for Community Manager rankCommunity Manager
    2 years ago

    This one is tougher because there is almost little to no support on the keep due to the age of it now. Can you try the following for me?

    1. Log out of any browser that you use on PC and mobile devices
    2. Clear all cache and browser history from PC and mobile
    3. Reset the password to your EA account to something simple for now
    4. Make sure that IF you use Chrome or Edge you are not logged into the browser with an account

    Then, go to the keep on each browser and log in with the new password but do this on the following connections

    1. WiFi
    2. Data
    3. Hot Spot (if you have one)

    The purpose of this is to get the site to sync your account as we are not able to here.

  • Hey there! I seem to be getting the exact same issue. I've tried for a few days now to get the keep to work.

    I am getting the same "Oops! an error occured".

    I have tried to clear the broswer cache on both edge, opera and firefox. and then proceeded to log in. All say the exact same error.

    I have also tried incognito mode on opera and firefox.