We apologize for the inconvenience and are currently investigating and working to resolve the issue on our end. We will update this thread once we know more.
Modifié par Rob Bartel, 11 avril 2011 - 07:00 .
"Unauthorized DLC" error message
Débuté par
Rob Bartel
, avril 11 2011 06:58
#1
Posté 11 avril 2011 - 06:58
Rob Bartel
-
- BioWare Employees
-
- 444 messages
Over the April 9, 2011 weekend, some of our Dragon Age: Origins content servers experienced an as yet unidentified failure. As a result, users began to experience error messages when attempting to access their downloadable content, indicating that the DLC was unauthorized.
We apologize for the inconvenience and are currently investigating and working to resolve the issue on our end. We will update this thread once we know more.
We apologize for the inconvenience and are currently investigating and working to resolve the issue on our end. We will update this thread once we know more.
Retour en haut
#2
Posté 03 mai 2011 - 11:10
Rob Bartel
-
- BioWare Employees
-
- 444 messages
Sorry, everyone - I feel terrible for not updating this thread sooner. No excuse other than that life got busy and I forgot. Let the beatings commence.
The problem we experienced with our authentication servers was corrected on the April 13th and then we took them down during off-peak hours for a couple of 15-minute outages in the weeks that followed to perform some further tweaks and analysis. Throughout this time, our console users were largely unaffected.
The issue raised by Bleakwail is a separate issue and was resolved for him via the standard customer service channels.
Thank you for your understanding and patience and, once again, I apologize for not updating this thread in a more timely fashion.
The problem we experienced with our authentication servers was corrected on the April 13th and then we took them down during off-peak hours for a couple of 15-minute outages in the weeks that followed to perform some further tweaks and analysis. Throughout this time, our console users were largely unaffected.
The issue raised by Bleakwail is a separate issue and was resolved for him via the standard customer service channels.
Thank you for your understanding and patience and, once again, I apologize for not updating this thread in a more timely fashion.
