Hooray! another work around that works. Thanks for sharing!
1 Like
After being seemingly fixed for me yesterday, though Agent still asked for my password (it’s never done that before this) Bnet successfully updated and I was able to log on. Twice. Then when I went to log on this morning the same s#$% happened. When I try to open the game directly from the game folder it gives me a list of errors as long as my arm so that’s not an option and I’m not all that computer savvy so I don’t want to go poking around in the game folders incase I f@$# up something completely so that’s also not really an option. FFS Blizz, get your s#$% together and get this fixed already, It’s now been over a week since it started and the last time we had a blue post was on Saturday, they could atleast give us an update on what is going on but instead its radio silence. I’ve been playing since vanilla and have put a lot of time AND money into this game, this is unacceptable.
5 Likes
Hey everyone,
I wanted to check in and let everyone know we’re still tracking this bug. The lack of updates on the thread is frankly cause we have none. As was mentioned elsewhere in the thread, there was some work done, yet the root cause still needs to be addressed. This is very much on the developers radar. We’ll post any updates as we have them to this thread.
Thanks again and we appreciate the reports and continued patience while this is sorted out.
1 Like
My App appears to be broken as well. It was stuck in the update loop until this morning, but I could still play the game. Now it errors out every time it tries to run the update, and it even errors out on scan and repair. I’ve done and checked on everything, except reinstall the game, which I see still hasn’t helped anyone. I’m on a Mac, Big Sur operating system.
2 Likes
Absolutely none of the solutions I’ve read in these threads has worked for my machine - an iMac (late 2015) running macOS Monterey Version 12.0.1
I’m trying to play WoW- retail. Haven’t played Classic or Hearthstone in over 2 years.
Launching currently generates a complaint window stating:
"The CAS system was unable to initialize: ClientHandler: initialization error: failed to create storage component
ClientHandler: initialization error: failed to create storage component
ClientHandler: initialization error: failed to create storage component
tact::ClientHandler::Create failed: E_STORAGE_INIT
[20211117T13:30:16] {196223} ERR: failed to bind shared memory file ‘/Applications/World of Warcraft/Data/data//shmem’: SHMEM_ACCESS_DENIED
[20211117T13:30:16] {196223} WRN: failed to open shared memory file ‘/Applications/World of Warcraft/Data/data//shmem’, error 13 (Permission denied)
[20211117T13:30:16] {196223} ERR: failed to bind shared memory file ‘/Applications/World of Warcraft/Data/data//shmem’: SHMEM_ACCESS_DENIED
[20211117T13:30:16] {196223} WRN: failed to open shared memory file ‘/Applications/World of Warcraft/Data/data//shmem’, error 13 (Permission denied)
[20211117T13:30:16] {196223} ERR: failed to bind shared memory file ‘/Applications/World of Warcraft/Data/data//shmem’: SHMEM_ACCESS_DENIED
[20211117T13:30:16] {196223} ERR: failed to bind Container index at ‘…/Data/data’: 7 (CCE_SHARED_MEMORY_BIND_FAILURE)
[20211117T13:30:16] {196223} ERR: failed to create data storage for base path ‘…/Data/data’: E_FAILURE
[20211117T13:30:16] {196223} ERR: failed to create storage handler: E_STORAGE_INIT
[20211117T13:30:16] {196283} INF: adding network address 8.253.153.40:443 for server https://level3.ssl.blizzard.com/
[20211117T13:30:16] {196283} INF: adding network address 8.251.12.20:443 for server https://level3.ssl.blizzard.com/
[20211117T13:30:16] {196283} INF: adding network address 67.26.250.30:443 for server https://level3.ssl.blizzard.com/
[20211117T13:30:16] {196283} INF: adding network address 8.251.31.254:80 for server http://level3.blizzard.com/
[20211117T13:30:16] {196283} INF: adding network address 8.252.57.126:80 for server http://level3.blizzard.com/
[20211117T13:30:16] {196283} INF: adding network address 8.249.47.254:80 for server http://level3.blizzard.com/
[20211117T13:30:16] {196283} INF: adding network address 8.252.66.254:80 for server http://level3.blizzard.com/
[20211117T13:30:16] {196283} INF: adding network address 8.253.153.249:80 for server http://level3.blizzard.com/
[20211117T13:30:16] {196283} INF: adding network address 137.221.64.8:443 for server https://us.cdn.blizzard.com/
[20211117T13:30:16] {196283} INF: adding network address 137.221.64.5:443 for server https://us.cdn.blizzard.com/
[20211117T13:30:16] {196283} INF: adding network address 137.221.64.4:443 for server https://us.cdn.blizzard.com/
[20211117T13:30:16] {196283} INF: adding network address 137.221.64.6:443 for server https://us.cdn.blizzard.com/
[20211117T13:30:16] {196283} INF: adding network address 137.221.64.7:443 for server https://us.cdn.blizzard.com/
[20211117T13:30:16] {196283} INF: adding network address 137.221.64.1:443 for server https://us.cdn.blizzard.com/
[20211117T13:30:16] {196283} INF: adding network address 137.221.64.2:443 for server https://us.cdn.blizzard.com/
[20211117T13:30:16] {196283} INF: adding network address 137.221.64.3:443 for server https://us.cdn.blizzard.com/
[20211117T13:30:16] {196283} INF: adding network address 137.221.64.8:80 for server http://us.cdn.blizzard.com/
[20211117T13:30:16] {196283} INF: adding network address 137.221.64.5:80 for server http://us.cdn.blizzard.com/
[20211117T13:30:16] {196283} INF: adding network address 137.221.64.4:80 for server http://us.cdn.blizzard.com/
[20211117T13:30:16] {196283} INF: adding network address 137.221.64.6:80 for server http://us.cdn.blizzard.com/
[20211117T13:30:16] {196283} INF: adding network address 137.221.64.7:80 for server http://us.cdn.blizzard.com/
[20211117T13:30:16] {196283} INF: adding network address 137.221.64.1:80 for server http://us.cdn.blizzard.com/
[20211117T13:30:16] {196283} INF: adding network address 137.221.64.2:80 for server http://us.cdn.blizzard.com/
[20211117T13:30:16] {196283} INF: adding network address 137.221.64.3:80 for server http://us.cdn.blizzard.com/
[20211117T13:30:16] {196283} INF: adding network address 23.45.112.65:443 for server https://blzddist1-a.akamaihd.net/
[20211117T13:30:16] {196283} INF: adding network address 23.45.112.64:443 for server https://blzddist1-a.akamaihd.net/
[20211117T13:30:16] {196283} INF: NameResolutionComplete numServers 5 numHosts 26
ClientHandler: initialization error: failed to create storage component
ClientHandler: initialization error: failed to create storage component
ClientHandler: initialization error: failed to create storage component
tact::ClientHandler::Create failed: E_STORAGE_INIT
[20211117T13:30:24] {196437} INF: adding network address 137.221.64.5:80 for server //us.cdn.blizzard.com
[20211117T13:30:24] {196437} INF: adding network address 137.221.64.4:80 for server //us.cdn.blizzard.com
[20211117T13:30:24] {196437} INF: adding network address 137.221.64.6:80 for server //us.cdn.blizzard.com
[20211117T13:30:24] {196437} INF: adding network address 137.221.64.7:80 for server //us.cdn.blizzard.com
[20211117T13:30:24] {196437} INF: adding network address 137.221.64.1:80 for server //us.cdn.blizzard.com
[20211117T13:30:24] {196437} INF: adding network address 137.221.64.2:80 for server //us.cdn.blizzard.com
[20211117T13:30:24] {196437} INF: adding network address 137.221.64.3:80 for server //us.cdn.blizzard.com
[20211117T13:30:24] {196437} INF: adding network address 8.251.31.254:80 for server //level3.blizzard.com
[20211117T13:30:24] {196437} INF: adding network address 8.252.57.126:80 for server //level3.blizzard.com
[20211117T13:30:24] {196437} INF: adding network address 8.249.47.254:80 for server //level3.blizzard.com
[20211117T13:30:24] {196437} INF: adding network address 8.252.66.254:80 for server //level3.blizzard.com
[20211117T13:30:24] {196437} INF: adding network address 8.253.153.249:80 for server //level3.blizzard.com
[20211117T13:30:24] {196437} INF: NameResolutionComplete numServers 2 numHosts 13
[20211117T13:30:24] {196223} INF: NGDP initialization - (archive: true, cache: true, Async: true)
[20211117T13:30:24] {196223} WRN: failed to open shared memory file ‘/Applications/World of Warcraft/Data/data//shmem’, error 13 (Permission denied)
[20211117T13:30:24] {196223} ERR: failed to bind shared memory file ‘/Applications/World of Warcraft/Data/data//shmem’: SHMEM_ACCESS_DENIED
[20211117T13:30:24] {196223} WRN: failed to open shared memory file ‘/Applications/World of Warcraft/Data/data//shmem’, error 13 (Permission denied)
[20211117T13:30:24] {196223} ERR: failed to bind shared memory file ‘/Applications/World of Warcraft/Data/data//shmem’: SHMEM_ACCESS_DENIED
[20211117T13:30:24] {196223} WRN: failed to open shared memory file ‘/Applications/World of Warcraft/Data/data//shmem’, error 13 (Permission denied)
[20211117T13:30:24] {196223} ERR: failed to bind shared memory file ‘/Applications/World of Warcraft/Data/data//shmem’: SHMEM_ACCESS_DENIED
[20211117T13:30:24] {196223} ERR: failed to bind Container index at ‘…/Data/data’: 7 (CCE_SHARED_MEMORY_BIND_FAILURE)
[20211117T13:30:24] {196223} ERR: failed to create data storage for base path ‘…/Data/data’: E_FAILURE
[20211117T13:30:24] {196223} ERR: failed to create storage handler: E_STORAGE_INIT
[20211117T13:30:24] {196446} INF: adding network address 8.251.31.254:80 for server //level3.blizzard.com
[20211117T13:30:24] {196446} INF: adding network address 8.252.57.126:80 for server //level3.blizzard.com
[20211117T13:30:24] {196446} INF: adding network address 8.249.47.254:80 for server //level3.blizzard.com
[20211117T13:30:24] {196446} INF: adding network address 8.252.66.254:80 for server //level3.blizzard.com
[20211117T13:30:24] {196446} INF: adding network address 8.253.153.249:80 for server //level3.blizzard.com
[20211117T13:30:24] {196446} INF: adding network address 137.221.64.8:80 for server //us.cdn.blizzard.com
[20211117T13:30:24] {196446} INF: adding network address 137.221.64.5:80 for server //us.cdn.blizzard.com
[20211117T13:30:24] {196446} INF: adding network address 137.221.64.4:80 for server //us.cdn.blizzard.com
[20211117T13:30:24] {196446} INF: adding network address 137.221.64.6:80 for server //us.cdn.blizzard.com
[20211117T13:30:24] {196446} INF: adding network address 137.221.64.7:80 for server //us.cdn.blizzard.com
[20211117T13:30:24] {196446} INF: adding network address 137.221.64.1:80 for server //us.cdn.blizzard.com
[20211117T13:30:24] {196446} INF: adding network address 137.221.64.2:80 for server //us.cdn.blizzard.com
[20211117T13:30:24] {196446} INF: adding network address 137.221.64.3:80 for server //us.cdn.blizzard.com
[20211117T13:30:24] {196446} INF: NameResolutionComplete numServers 2 numHosts 13"
I am a gamer, not a techie. I would really like to get back to raiding with my guild rather than trying unsuccessfully ideas proposed on these forums: I’ve already missed a week of raiding. Please, Blizzard, help.
3 Likes
Thank you for the honest update. I think many players who have not found this forum might appreciate a message on the launch page so they don’t assume it’s a problem on their end. There was one earlier, but it was removed. Anyway, just my 2 cents.
1 Like
I’m having this same error. I’ve deleted all addons and restarted the computer etc… I’m now going to update my OS, maybe that’s the problem. Anyone else find a fix?
I’ve been able to get into game (not using battle.net) Here is what I did.
I got an answer from a tech that told me to:
- Open Terminal, located in /Applications/Utilities.
- Type or copy and paste the following command into Terminal window:
sudo chmod 0754 ~/Library/Application\ Support/Battle.net
Then I went to my Applications/World of Warcraft folder
Selected the folder, unlocked that folder, changed/assigned read & write permissions to everything for admin. (some folders inside others had custom permissions) Then I launched World of Warcraft from inside that folder - I did NOT launch through Battle.net (afraid it would mess up)
** I had posted this in another thread that was/is being tracked too. Thought it may help you all that can’t do the agent thing. It will let you play but you can’t update until Bliz gets Battle.net fixed
So my concerns are for the time we have lost trying to play without being able to. Are we gonna get time added to our game time to supplement the time lost dealing with this bug? Cause for me the only way I can currently get into the game is to do a complete reinstall of the game. I dont want to do this often because Im afraid of the damage it can cause to my ssd since its almost 80 gigs of space thats being rewritten over and over and over. Or will blizzard just screw us that way also?
4 Likes
2018 MacBook Pro - Big Sur 11.6
1 Like
MacOS High Sierra (10.13.8). Was able to play fine this morning but now cannot update – Battle.net says something went wrong (though Hearthstone updated just fine) and launching WoW from the Finder directly returns the same long error as Descant had above.
i am concerned they are going to release 9.2 before fixing this issue, so blizzard halt on ANY 9.2 releases until you fix this because we will not be able to access 9.2 if the game won’t update via bnet app duh…i say this because there is already an article on wowhead saying possibly or there will be 9.2 on the PTR later this week and if so that is completely stupid since some people maybe still cant get the most updated version of the PTR due to this updating issue going on
1 Like
It seems it has gone on for an awful amount of time. This is seriously hurting our gameplay and we are falling behind.
1 Like
Is crazy that we will have to do this to play for a game that we are paying and investing our time. Thanks but no thanks.
1 Like
I demand a refund for at least a week of playing time… Just started playing again after 10 years off and immediatly have to deal with this BS…
Thank you. That worked for me.
Thanks; that seems to have worked for me as well. I was forgetting that a few Battle.net files existed outside the WoW folder when I made my permissions changes…
This worked for me and it appears to hold up.
it’s Thursday morning, and it’s been just about a full week and I still cannot get into the game, I get the admin password prompt, then initializing phase gets stuck until ultimately fails.
Mac OS Monterey 12.0.1
1 Like
Can confirm, this works