You cannot login until the character boost process you recently initiated is complete

Support Bug Report
1

Returned to the game on Saturday, July 15th.

Immediately upon logging in, performed the gear update on my three mains, on Realm Ysera - US, in the following order;

Priest, Mage, Paladin

Did not allow one to complete before the other.

Since then, no character has been accessible, and the message I receive upon logging in is; "you cannot login until the character boost process you recently initiated is complete.

EDIT:

Additional Information; I have an unused level 60 boost on the account. Attempting to use it against all three of the characters results in a single message box that says ā€˜Internal Errorā€™. This was attempted around 7:38est on July 18th, if you wanna check your Log4Net logs, or whatever framework you guys are using over there :slight_smile:

EDIT2:

While grepping through random log files, I found something that (at least to my eyes), describes the behavior of logging into my Mage; Lampix;

7/18 19:37:37.259  Loading Screen Enable (1) : 2222 - 1
7/18 19:37:39.064  Client Object Manager Initialized: 2222
7/18 19:37:39.490  Succesfully Registered Nameplate
7/18 19:37:39.490  Loading Screen : Loading : Files Read 2739 : Bytes Read 1245066007 : Elapsed MS 2233 : MBytes Per Sec 531.745
7/18 19:37:39.490  Loading Screen : XML Loaded 0%
7/18 19:37:41.948  Client : Load Map Begin : 2222
7/18 19:37:41.963  Loading Screen : Loading : Files Read 257 : Bytes Read 74720634 : Elapsed MS 2472 : MBytes Per Sec 28.827
7/18 19:37:41.963  Loading Screen : XML Loaded 100%
7/18 19:37:44.001  Loading Screen : Loading : Files Read 2437 : Bytes Read 375252348 : Elapsed MS 2039 : MBytes Per Sec 175.512
7/18 19:37:44.001  Loading Screen : XML Loaded 100%
7/18 19:37:44.001  Loading Screen : World Loaded 61%
7/18 19:37:45.289  Client : Load Map End
7/18 19:37:45.289  Start waiting for active player
7/18 19:37:45.292  Character Login SEND
7/18 19:37:45.659  Stop waiting for active player
7/18 19:37:45.659  Client Object Manager Destroyed

I wanna say that, the message; ā€œWorld Loaded 61%ā€, is approximately how far the loading bar gets before kicking me back out to the character selection screen.

Peeking at more logs, be back shortly.

EDIT3:

There appears to be some fantastic function names hanging out in the ARM implementation on my M2;

7/18 19:38:47.284  M2DestroySkeletons()

Hereā€™s another log that appears to have been written during the login process;

7/18 19:37:28.707  Glue Start Login
7/18 19:37:28.707  BattleNet Attempt Logon
7/18 19:37:29.128  BattleNet Front Connected
7/18 19:37:29.228  BattleNet Logon Queue Update
7/18 19:37:29.411  BattleNet Logon Complete
7/18 19:37:29.528  BattleNet Game Account Name
7/18 19:37:29.594  BattleNet Web Credentials
7/18 19:37:29.594  BattleNet Attempt Complete Login
7/18 19:37:29.978  BattleNet Realm List Ticket
7/18 19:37:30.094  BattleNet Sub Region List
7/18 19:37:30.528  BattleNet Last Played Char
7/18 19:37:30.594  BattleNet Last Played Char
7/18 19:37:30.594  BattleNet Last Played Char
7/18 19:37:30.594  BattleNet Last Played Char
7/18 19:37:30.661  BattleNet Last Played Char
7/18 19:37:30.661  BattleNet Last Played Char
7/18 19:37:30.661  BattleNet Join Realm
7/18 19:37:30.944  BattleNet Realm Join
7/18 19:37:30.944  Change Connection
7/18 19:37:30.944  Connect
7/18 19:37:30.978  Handle Connect
7/18 19:37:32.566  Handle Auth Response: 0
7/18 19:37:32.566  Glue Authed To WoW: 0
7/18 19:37:33.017  BattleNet Connected To Realm
7/18 19:37:33.017  BattleNet Front Disconnecting
7/18 19:37:33.040  Handle Char Enum
7/18 19:37:33.057  Handle Char Enum
7/18 19:37:33.233  BattleNet Front Disconnected
7/18 19:37:45.644  Handle Character Login Failed: 10
7/18 19:37:46.114  Handle Char Enum
7/18 19:37:54.743  Handle Character Login Failed: 10
7/18 19:37:55.224  Handle Char Enum
7/18 19:38:02.277  Handle Character Login Failed: 10
7/18 19:38:02.796  Handle Char Enum
7/18 19:38:28.478  Handle Char Enum
7/18 19:38:44.254  Glue Script Disconnect From Server
7/18 19:38:44.254  BattleNet Defer Disconnect
7/18 19:38:44.254  Glue Cancel WoW Connection
7/18 19:38:44.254  Disconnect: 14
7/18 19:38:44.261  Handle Disconnect
7/18 19:38:44.390  Glue WoW Disconnect
7/18 19:38:44.390  BattleNet Defer Disconnect
7/18 19:38:47.344  Connection Destroy

Edit 4

grep -rni " error " has yielded more results which seems to reference the above ā€˜Glueingā€™ process. I also want to be clear that Iā€™m just dumping info here in hopes that it could be at all useful to someone.

"[GlueLogin] [F] Fatal error while logging inresult=\"( code=\" (325)\" localizedMessage=\"\" debugMessage=\"\")\""

Edit 5

Iā€™m leaning toward ā€˜probably unrelatedā€™, because I attempted to log back in with my Mage, and an additional ā€˜glueā€™ related message did not appear in the logs.

It appears the glue is working as intended. Glue away.

Edit 6

The mystery continues; When logging into my new fancy Dragonman, ā€œIshhā€ on the realm Blood Furnace from the WoW companion app, all good. When I log into my Mage on the Wow companion app? Errors out.

Iā€™m starting to think my Mage, who was the first character I ever created in this game, was actually a fever dream of the last 15 years? Does he actually exist?

Edit 7

My battle pets via the armory search for my mage appear to beā€¦cubes to me? Anyone else? Is my simulation collapsing?

P.S, Blizzard y u disable markdown links? :frowning:

Edit 8

Iā€™ve found this thread from a while ago in which a GM specifies that itā€™s happening to people with another character service available during a boost. Guessing that the boost feature acted like a standard boost, sans the leveling portion, this bug seems related. Eventually, a resolution was reached, but no direct reasoning or timing was provided. It seems like it might be a waiting game? Bummer, because Iā€™ve had DF for 5 days now, but I havenā€™t been able to play it at all.

4 Likes
2

Just relaying here what I posted in another thread - having the same issue, also since Saturday (7/15)

Was informed in a second response on my ticket that todayā€™s server restarts were intended to fix the issue, however that does not appear to have been the case

2 Likes
3

I also have this issue, went through the ticket process to get a poor response saying they donā€™t have a fix yet. Am now trying to get a refund as I am interested in playing without my other toons and wasting money on time that I canā€™t play.

I should also mention this is happening on almost all my characters, like 15+ of them.

3 Likes
4

I as well have the same issue. Finally picked up dragon flight bought the game Saturday night and still have not be able to log into my toon.

3 Likes
5

Can confirm the issue is not fixed as of yet here as well; I have 3 alts all locked by this, and they remain stuck in limbo as many are reporting.

Honestly, this looks like a failure of the character boost system: instead of copying, deleting, then replacing, the system just flagged the character and never finished the process. When any boost works, it makes a new copy of the character at the boosted level and replaces the old one; thatā€™s why the game mails your inventory back to your ā€œnewā€ character.

But here, itā€™s just getting stuck at some step on this chain; Blizzard may want to consider Restoring characters that are stuck like this at this point if itā€™s at all possible.

2 Likes
6

+1 here

20 chars

1 Like
7

Iā€™ve had the same issue as well. I havenā€™t been able to play my main on this account for almost five days now. I submitted a ticket a couple of days ago but havenā€™t received a direct response.

8

Reporting back that the issue has been resolved for my account! Thank you Dev team!