Close
Page 1 of 2 1 2 LastLast
Showing results 1 to 10 of 14
  1. #1

    Default error #132 (0x85100084) fatal exception

    Anyone else getting this when trying to log in to WoW today?
    Currently 5 Boxing 5 Protection Paladins on Whisperwind Alliance
    The Power of Five!!! ( short video )

  2. #2

    Default

    Nope I'm getting you have been disconnected. (BLZ51914003).

  3. #3

    Default

    Quote Originally Posted by Intrakit View Post
    Nope I'm getting you have been disconnected. (BLZ51914003).
    Im getting that if i log in via the launcher, the first one i i mentioned is when i bypass the launcher.. but a lot of people are right now I guess
    Currently 5 Boxing 5 Protection Paladins on Whisperwind Alliance
    The Power of Five!!! ( short video )

  4. #4

    Default

    To diagnose error #132 requires the full error log -- there are many different reasons that this general error code can be given
    Lax
    Author of ISBoxer
    Video: ISBoxer Quick Start

  5. #5

    Default

    Launcher worked fine, through InnerSpace I am getting the "You have been disconnected" message....

    There is a note about them being DDos'd again too.

  6. #6

    Default

    The Support site is hosed too...everyone must be killing the forums.

  7. #7

    Default

    i can confirm issues also.

    Bnet client (no wow update needed) -> play button = char select screen

    inner space launching 1 slot or my team = "You have been disconnected. (BLZ51914001)

  8. #8

    Default

    Seeing "BLZ51914003" as well

    From IRC (not sure if this person is on the forums)


    10:52 <aixenv> "You have been disconnected. (BLZ51914001)"
    10:53 <aixenv> no char select screen.. but with bnet client it works
    10:54 <@Svpernova> Dunno, could be related to the ddos they're under
    10:54 <aixenv> well i'd think that, except bnet client works everytime and isboxer/inner space never works
    10:55 <aixenv> i mean what would the odds be that would happen
    10:57 <@Svpernova> IS doesn't do anything with the connection from WoW to Blizzard servers.
    10:58 <aixenv> that's what i'd hope
    10:58 <aixenv> i was going to do a wireshark compare
    10:59 <aixenv> just tested again though.. IS doesnt work.. bnet client works
    11:00 <aixenv> interesting.. if i quit.. and go back to login screen it wont connect. so connecting via play on bnet client MUST do something dif or proxy/bypass something the login screen doesn't
    11:00 <aixenv> so yea must e related to the DDoS

    Sounds like it's not IS related.
    Last edited by Svpernova09 : 08-23-2016 at 12:01 PM

  9. #9

    Default

    confirmed this is Blizzard related (BLEH)

  10. #10

    Default

    I am in now...trying to hit more Invasions on my lock team!

    Did a scan and repair, not sure if it helped but...

Posting Rules

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •