CASCHost icon indicating copy to clipboard operation
CASCHost copied to clipboard

Published 20 hours ago • verified publisher icon WowDevTools

WoW CAS system unable to initialize

Open Razinao opened this issue 7 years ago • 4 comments

This WoW error is caused by unexpected CDNS behaviour, where the client cannot pull the data and therefore errors, generating an error message alike the following: Error 1, Error 2

Steps to reproduce:

  1. Start CASCHost with a clean output folder, custom changes already present in the Data folder and entries in the root_entries table.
  2. Login to WoW with Client 1. Do not login with Client 2 (two separate WoW folders)
  3. Exit Wow from Client 1
  4. Make an update to the CASCHost - amend one of the files and rebuild
  5. Login to WoW with Client 1 and Client 2

Expected Behaviour:

  • Both Client 1 and Client 2 reach the login screen

Actual Behaviour:

  • Client 1 reaches the login screen. Client 2 experiences the errors above.

When Client 2 is attempting to connect, the CASCHost outputs a lot of inexplicable 404 errors. It seems that the Client 2 is unable to access files that are a part of the custom CDNS.

Razinao avatar May 27 '18 16:05 Razinao

Could you paste .build.info from both Client 1 and Client 2

justMaku avatar May 27 '18 16:05 justMaku

There is no .build.info for either clients.

Razinao avatar May 27 '18 16:05 Razinao

If Client 1 is functional and has all your custom changes then it sounds like Client 2 isn't connecting to the CDN or has picked up some dodgy configs.

Have you tried connecting with Client 2 after the first build? If it still doesn't work after the first build, I'd suggest deleting ./Data/config and ./Data/indicies and letting it rebuild the structure.

For the record, is this with TinyClient? If so, is this on live?

barncastle avatar May 27 '18 16:05 barncastle

Client 2 was connecting to the CDN as requests were being made and were visible in the CASCHost console.

Client 2 couldn't connect on any of the following rebuilds. It was only able to connect after the Output folder was cleaned out and CASCHost started anew (with changes from the last time this was done included). The Data folders were emptied out in an attempt to fix this initially but were not successfl.

This is with two full Battle.net clients downloaded from live and connecting into the CDN as described in the above steps.

Razinao avatar May 27 '18 17:05 Razinao