Hyjal locking up for half the raid

#0 - April 2, 2008, 2:53 a.m.
Blizzard Post
Hi Blizzard,

Hyjal is locking up for half my raid tonight. Seems to be a random group of 15 people each time. On the Eldre'Thalas server, Guild is |Tempest|, raid ID of 2492197.

Anything you can tell us?

Thanks for your time,

Osullivan.
#3 - April 2, 2008, 3:17 a.m.
Blizzard Post
Checking this out, folks. Please continue to attempt to log in and let me know if you've any success with it.
#6 - April 2, 2008, 3:22 a.m.
Blizzard Post
Can anyone else verify this occurrence?
#11 - April 2, 2008, 3:25 a.m.
Blizzard Post
Sorry, Osullivan. Doing everything I can, but I understand if you guys have to call it.

Can any other groups verify that a warlock making soul shards correlates to their issues?
#16 - April 2, 2008, 3:30 a.m.
Blizzard Post
Are you making soul shards, Sindicate? This is rather an important piece of information.
#20 - April 2, 2008, 3:46 a.m.
Blizzard Post
Looking into this, guys. I'm truly sorry it's affected your raiding time.
#24 - April 2, 2008, 3:52 a.m.
Blizzard Post
Oh ho ho. Jibby jedi.
#26 - April 2, 2008, 3:55 a.m.
Blizzard Post
Q u o t e:
Has the problem of the disconnections been located yet? Can we get some information?


We're gathering the appropriate info now. I have no ETA on a resolution, only that it'll be ASAP.

And Osullivan, we're GMs here, not CMs. ;)
#32 - April 2, 2008, 4:37 a.m.
Blizzard Post
Q u o t e:
Additionally, the client doesn't just DC like normal, you have to actually ctrl-alt-del and kill the wow.exe process. It's more of a program crash. Once I was able to kill wow.exe and log back in, only to crash later and have my computer lock up completely. Not even ctrl-alt-del got me out of it that time. Just FYI.


Thank you for the info, Gilias. I don't have any workarounds to offer at the moment, but when I do, I'll share them.
#36 - April 2, 2008, 5:15 a.m.
Blizzard Post
Just wanted to let you guys know that QA is checking this out as well.
#39 - April 2, 2008, 5:47 a.m.
Blizzard Post
Anyone still attempting to get into the instance:

Please have your entire raid delete or rename your Interface folder and let me know here if you encounter the issue again.

The first group said that they ran without mods, but if what I think's happening is actually happening, even if one person has it, it can affect the raid.
#42 - April 2, 2008, 2:27 p.m.
Blizzard Post
Did your groups, by chance, happen to utilize a Rebirth or Soulstone Resurrection? This question applies to everyone herein :)
#45 - April 2, 2008, 3:41 p.m.
Blizzard Post
Q u o t e:
Can someone who DC’d last night and WASN’T using Omen2 report in ?

A member of my raid last night disabled the add-on in question completely and still experienced difficulties with multiple hardlocks :)

Thanks for the information, folks; I'll most certainly pass it on—in the meantime, though, I'd follow Belfaire's advice to heart and run with only minimal add-ons active
#79 - April 3, 2008, 4:44 a.m.
Blizzard Post
Q u o t e:
Tonight we updated everyone in raid to Omen r67732 (in game omen id itself as r67718). Killed three bosses in Black Temple and Rage Winterchill with no hard lockup issues or any connection issues beyond normal. I would suggest if you are still having issues make sure -everyone- in raid has updated.


Good news.

The Quality Assurance Team has the information on this issue thus far but I haven't received any news about it.