Shop Closed on PC

Hey there,

Thank you again for providing these files and for working with us on this. We hope to have more info soon.

Edit:

1 Like

A week has passed and ā€¦ the shop is closed AGAIN. Eu Win7 64-bit.

3 Likes

I have the exact same error logs as the others.

{1578} ERR: Failed to obtain oauth. ResultCode=[0] StatusCode=[400] Body=[]

and

Job (HearthstoneCheckout.InitializeCheckoutClient(ID:288)) FAILED: [HearthstoneCheckout.InitializeCheckoutClient] Failed to initialize checkout client.

3 Likes

I didnā€™t have any shop issues last month when several other people were experiencing them. However, after the most recent Battle.Net update earlier this week, the in-game HS shop now shows as ā€œShop Closedā€ for me across all 3 servers (Americas, EU, Asia).

So to be clear, the problem didnā€™t start for me until the most recent Battle.Net update (client update, not HS patch). Iā€™m on a PC, Windows 8, 64-bit. I havenā€™t tried to access my HS account on any other device, so I donā€™t know if the issue is platform-specific for me.

I sent my HS jobs.log file to the TechInfo e-mail address, as requested. The log file had a similar error message to that of other posters here:

Job (HearthstoneCheckout.InitializeCheckoutClient(ID:288)) FAILED: [HearthstoneCheckout.InitializeCheckoutClient] Failed to initialize checkout client.

3 Likes

Store log

E 11:50:57.0632653 OnDiagMessage (BNL_Scene_Checkout) : [20200605T11:50:57] {1c7c} ERR: Failed to obtain oauth. ResultCode=[0] StatusCode=[400] Body=
E 11:50:58.4015512 OnDiagMessage (BNL_Scene_Checkout) : [20200605T11:50:58] {1c7c} ERR: Failed to obtain oauth. ResultCode=[0] StatusCode=[400] Body=
E 11:50:59.7724536 OnDiagMessage (BNL_Scene_Checkout) : [20200605T11:50:59] {1c7c} ERR: Failed to obtain oauth. ResultCode=[0] StatusCode=[400] Body=

Jobs log

E 11:50:59.7724536 Job (HearthstoneCheckout.InitializeCheckoutClient(ID:291)) FAILED: [HearthstoneCheckout.InitializeCheckoutClient] Failed to initialize checkout client.

3 Likes

Jobs.log:

E 10:43:57.3421421 Job (HearthstoneCheckout.CreateCheckoutClient(ID:425)) FAILED due to dependency failure: GenerateSSOToken
E 10:43:59.8098869 Job (HearthstoneCheckout.InitializeCheckoutClient(ID:289)) FAILED: [HearthstoneCheckout.InitializeCheckoutClient] Failed to initialize checkout client.

Store.log:

E 11:16:14.0898145 OnDiagMessage (BNL_Scene_Checkout) : [20200604T11:16:14] {2714} ERR: Failed to obtain oauth. ResultCode=[0] StatusCode=[400] Body=
E 11:16:15.3969193 OnDiagMessage (BNL_Scene_Checkout) : [20200604T11:16:15] {2714} ERR: Failed to obtain oauth. ResultCode=[0] StatusCode=[400] Body=
E 11:16:16.7020244 OnDiagMessage (BNL_Scene_Checkout) : [20200604T11:16:16] {2714} ERR: Failed to obtain oauth. ResultCode=[0] StatusCode=[400] Body=

Iā€™ve attached a Debugger to Hearthstone.exe, which also revealed:

Exception: System.ArgumentException
Message: An element with the same key (37.244.54.10:1119) already exists in the dictionary.

Not sure if itā€™s relevant, but if that IP address belongs to some sort of authentication server, it might be related to the oauth problems and shop closed issues.

3 Likes

New patch and the shop is STILL CLOSED.

5 Likes

Confirmed. Press/Media? Anyone looking into this?

4 Likes

New patch and shop still closed, but logs changed a bit.

job

Job (HearthstoneCheckout.InitializeCheckoutClient(ID:292)) FAILED: [HearthstoneCheckout.InitializeCheckoutClient] Failed to initialize checkout client.

store

{31c} ERR: Failed to obtain oauth. ResultCode=[0] StatusCode=[400] Body=[]

job

Job (HearthstoneCheckout.InitializeCheckoutClient(ID:292)) FAILED: [HearthstoneCheckout.InitializeCheckoutClient] Failed to initialize checkout client.

store

{ee0} ERR: Failed to obtain oauth. ResultCode=[0] StatusCode=[400] Body=[]

1 Like

Store log:

E 19:22:56.6774578 OnDiagMessage (BNL_Scene_Checkout) : [20200614T19:22:56] {1850} ERR: Failed to obtain oauth. ResultCode=[0] StatusCode=[400] Body=
E 19:23:00.8146945 OnDiagMessage (BNL_Scene_Checkout) : [20200614T19:23:00] {1850} ERR: Failed to obtain oauth. ResultCode=[0] StatusCode=[400] Body=
E 19:23:02.4837900 OnDiagMessage (BNL_Scene_Checkout) : [20200614T19:23:02] {1850} ERR: Failed to obtain oauth. ResultCode=[0] StatusCode=[400] Body=

I hope this issue is still being worked on. Itā€™s been over a month now, I have close to 2000 gold I canā€™t spend, and the last Outland packs I opened were the ones from ranked play at the beginning of the month.
I get that work is slower, COVID-19 is affecting us all, but Iā€™m starting to forget that Hearthstone is even a thing. Also, I managed to get Nemsy by logging from another device a while back, but Iā€™m sure others didnā€™t have that opportunity, and no word has come as to how youā€™ll handle that. Do you have any news for the people who are affected by this?

5 Likes

Do we need to send something? Or do something? How long we have to wait for the fix? At least, give us an update on the situation.

5 Likes

Windows 8 server EU close market

3 Likes

Here we see a clear example of how Blizzard treats paying customers like utter garbage.

Support closed my ticket without resolving the issue.

I am done spending a single dime on this game AND on this company.

6 Likes

Windows 8, Windows 7
Europe
Shop is closed.

3 Likes

Windows 8
Europe
Shop is closed.

3 Likes

Win 10 Pro, 64 bit. I solve problem on my end. Not sure if it helps, but gonna post here just in case it helps someone. Shop was blocked by Kaspersky (antivirus) ā€œalways check protected connectionsā€ feature. Normally (in 4 years of playing), it never blocked shop. I guess, its because they change many technical things in patch, that cause the problem in the first place. Oh, and never choose to ā€œcontrol all portsā€ feature, its gonna block acess to Hearthstone completly. Check everything related to traffic. VPN, ports, connections, etc. Hope it helps.

1 Like

What do you mean by Antivirus? Why do you blame Kaspersky? I will talk to them about this Issue. Thanks for your Feedback.

Btw: We do not run Kaspersky and the Error is still there.

2 Likes

I mean, i start Hearthstone with ā€œalways check protected connectionsā€ - shop closed. I disable it, start Hearthstone - shop is open. Its pretty obvious. And i dont blame anyone. But i still wanna report here, because normally (before that patch), it was working fine.

1 Like

Would you explain this?

1 Like

I donā€™t use Kaspersky either. I did consider this might be due to an Antivirus issue, but surely we shouldnā€™t be expected to disable our protection in order to make Hearthstone work.
Itā€™s been 21 days since the last update, 11 since I last posted here asking for some news. Does Blizzard still consider this to be an active issue?

2 Likes