#1 - 2012/12/11 08:47:00 PMI am trying to log into the game and i start getting Error 3007. I closed the game, attempted to log in and it said There is a new patch that needs to be downloaded blah blah. Then i closed it again, opened it, did a 10mb patch then attempted to log into the game again. The game said there is a new patch that needs to be downloaded again... I open the launcher and now apparently there is a 2.34gb patch? Does anyone else having this problem?
#19 - 2012/12/11 10:24:00 PMEdit: Hey all! We're still monitoring the issue from our end, so if those of you who are continuing to experience Error 3007 are willing, we've asked for some additional information over in this thread in Tech Support: http://us.battle.net/d3/en/forum/topic/7393109698
Thanks for the posts! Our engineers and QA team are currently investigating this error, and I'll report back to this thread once we have any additional info to share.
#57 - 2012/12/12 12:45:00 AMQuick update everyone currently receiving an Error 3007:
We've researched your reports quite thoroughly, and the issue appears to be occurring on the ISP side and not with our game or authentication servers, which means there's not much we can do to assist with this particular problem. It should be resolved once the ISP is able to get correct DNS propagating.
In the meantime, you can try to use different DNS servers, and Narull has provided an excellent workaround for that process here: http://us.battle.net/d3/en/forum/topic/7393109275?page=9#171
Thanks again for your reports! We really appreciate players bringing this issue to our attention so quickly. (And thanks for being patient while we investigated.)
#60 - 2012/12/12 12:51:00 AM
So you're saying there is something wrong on my end when i've done nothing?
How does that work?
Not your fault! But there are steps you can take to potentially workaround the issue until it can be resolved on the ISP's end (which are linked in my previous post).
#67 - 2012/12/12 01:28:00 AM
I am playing from California, trying to log into the North American servers. I could log on at about 1 AM PST just fine. The maintainence was supposed to end today at 1 PM PST right?
So you're saying that my ISP, which is Verizon FIOS, *just happened* to change their DNS settings or whatever at the exact same time of the maintainence and that is the reason I can't log in?
According to your posting history from today, it looks like you're experiencing a different issue (especially since it doesn't appear like you're receiving Error 3007). You've tried running the Repair Tool and it didn't resolve the issue, correct?
#69 - 2012/12/12 01:39:00 AM
Fixed the issue without resolving to changing my DNS servers like mentioned. for some reason my firewall was blocking D3 from updating, I let it through now and the launcher downloaded the 12MB update and I can now play. Thx and sorry
No worries! Glad you were able to find a fix. :)
#255 - 2012/12/13 12:48:00 AMHey all! We're still monitoring the issue from our end, so if those of you who are continuing to experience Error 3007 are willing, we've asked for some additional information over in this thread in Tech Support: http://us.battle.net/d3/en/forum/topic/7393109698
#257 - 2012/12/13 01:26:00 AM
12/12/2012 05:14 PMPosted by NevahDiehey lylirra how about any sort of update....your patch notes for your hotfix/fastpatch must have been lost somewhere, i only saw one thing that should not have taken 11 and a half hours.....i mean really....so whats the good word? any word of bashiok getting his job back? at least that kid was honest and straight up about rmah and ah controlling drop rates....they just dont make gms like they used to huh.
We posted the patch notes for 1.0.6a the Monday before we patched in the forums as a sticky, and on the day of the patch here. The only thing 1.0.6a included was a bug fix for an issue that could not be hotfixed (but was critical enough to address now rather than waiting for our next full patch cycle).
Please note that the downtime experienced on Tuesday occurred across all Blizzards games, not just Diablo III. This is because the downtime was due to database maintenance, and not the deployment of the patch.