Then a few minutes later when I started trinity and the WoW Client again(with the old patched wow-64.exe and " -uid wow-dede") and then out of nothing the error #112 showed up.įinally I tried the current new connection-patcher.exe on the wow-64.exe but still #112 error. I did not update the WoW Client it is still version 6.9. Trinity update went all fine no errors and for the first test I started the wow client with the old patched wow-64.exe from the old trinity version(2015.12.15.).Īll went fine I played for several hours and then did a normal logout and a normal trintiy server shutdown strg+c. Today I updated trinity to the current version(core.zip download date ). I never updated the wow client after the initial setup of the trintiy server it is still version 6.9. I used for over 3 months a trinity server(core.zip download date ) and always started the client wow-64.exe with " -uid wow-dede" command and never had a problem. I tried the before mentioned "Wow_Patched.exe -uid plsnopatch -noautolaunch64bit" but no success, still error #112. WoW - WARNING Issue with new NVIDIA drivers. I think I ran into similar problem here, at wow loginscreen getting -error #112 -> it says it couldn't check the game version. The World of Warcraft Mosaic is Complete Thanks to the combined effort of Warcraft players. sorry I could not be better assistance but I thought maybe if I supplied what didn't work it might save you time trying to come up with solution. So far thats all i have tried to come up with a work around. World of Warcraft could not resolve the address of the network data source. nope still calls update but fails because distro server is going to 127.0.0.1 lolĤ. Change all of blizzards server addresses to 127.0.0.1 in host file. Changing to exe to read only Nope didnt work update still triggered.ģ. Blocking exe via firewall doesnt even work via a closed network using 127.0.0.1 for server address It still tries to update.Ģ. I haven't found solution but i can list what wont work to save you timeġ. Right now I believe anyone running 6.2.3 is shot in foot so you are not alone. I have not checked this yet as im just now getting online since the update. but im sure the Offy Blizz server sends the packet to update Or client checks a hash list to see if it is the correct client to be running. Contents 1 Patch 3.3: Fall of the Lich King 2 Patch 3. set time day month year Sets the time and date. not to mention they did a change on their back-end supposedly to optimize the memory between bnet and client imho I believe it is more to control how client is used and also to control the client hashes IE: /6.2.2a /6.2.3/ 6.2.4/. Installation tips Torrent info Related Patches Patches category For the NPC in Icecrown, see 'Patches'. Cisco WAAS Troubleshooting Guide for Release 4.1.3 and Later. I.m not exactly sure when the client started doing this. The issue is that the build type is checked via ( i think bnet.dll) every time it is started
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |