Jump to content
TrinityCore
Sign in to follow this  
AMDIvailo

Error #112

Recommended Posts

Hello i compiled the latest version of TC 6.x, updated the database to TDB_full_6.02_2015_07_14 and created account with bnet account create ***** *****,

but when i try to login the client gives me this error : Battle.net error #112 Unable to validate game version.

My game version is 6.2.0(20201)(64x Release)(Patched).

Why is that?

The last database says that it supports 6.2.0

Edited by AMDIvailo

Share this post


Link to post
Share on other sites

 Retail Version 6.2.0 build 20216 and you can connect to a starter account on retail to get get a copy of the client.

​Ok now i got error #114...Do you know how to fix it?

Share this post


Link to post
Share on other sites

Did you change  portal from "US" or "EU" to "localhost" ?

​Yep!

​By the way when i patch the client i got this output:

Creating patched binary...
Win32 client...
patching Portal
Found offset 11671340
patching redirect RSA Modulus
Found offset 10608752
patching BNet
Found offset 7933815
patching Signature
Found offset 7901388
Patching done.
EX: basic_string::_S_construct null not valid
An error occurred. Press ENTER to continue...

 

I see there is an error but it still creates a patched wow.exe

maybe the problem is caused by this error?

Share this post


Link to post
Share on other sites

Did you change  portal from "US" or "EU" to "localhost" ?

​Yep!

​By the way when i patch the client i got this output:

Creating patched binary...
Win32 client...
patching Portal
Found offset 11671340
patching redirect RSA Modulus
Found offset 10608752
patching BNet
Found offset 7933815
patching Signature
Found offset 7901388
Patching done.
EX: basic_string::_S_construct null not valid
An error occurred. Press ENTER to continue...

 

I see there is an error but it still creates a patched wow.exe

maybe the problem is caused by this error?

​the error is linux related...for some strange reason the connection patcher for the linux build gives this error. you will need to build the connection patcher on a windows machine and patch it there.

Share this post


Link to post
Share on other sites

hi,

i am getting the same error too.. :"Current version supported: live (20253) (all versions since 5ab88b993e8)"

What should I do ?

thx

Share this post


Link to post
Share on other sites

For AND ONLY FOR GNU/Linux users :

To get connection_patcher (linux version obviously...) working, you need to change bnet modules default path in the connection patcher source code. On Linux, bnet modules are located in /home/larry/.wine/drive_c/users/Public/Application Data/Blizzard Entertainment/Battle.net/Cache/

edit tools/connection_patcher/Program.cpp

case Constants::BinaryTypes::Pe32:
                std::cout << "Win32 client...\n";

                boost::algorithm::replace_all(renamed_binary_path, ".exe", "_Patched.exe");
                do_patches<Patches::Windows::x86, Patterns::Windows::x86>
                    (&patcher, renamed_binary_path, patchVersionPath, wowBuild);

                do_module<Patches::Windows::x86, Patterns::Windows::x86>
                    ( "8f52906a2c85b416a595702251570f96d3522f39237603115f2f1ab24962043c.auth"
                    , std::wstring(L"/home/larry/.wine/drive_c/users/Public/Application Data/Blizzard Entertainment/Battle.net/Cache/")
                    );

                break;
            case Constants::BinaryTypes::Pe64:
                std::cout << "Win64 client...\n";

                boost::algorithm::replace_all(renamed_binary_path, ".exe", "_Patched.exe");
                do_patches<Patches::Windows::x64, Patterns::Windows::x64>
                    (&patcher, renamed_binary_path, patchVersionPath, wowBuild);

                do_module<Patches::Windows::x64, Patterns::Windows::x64>
                    ( "0a3afee2cade3a0e8b458c4b4660104cac7fc50e2ca9bef0d708942e77f15c1d.auth"
                    , std::wstring(L"/home/larry/.wine/drive_c/users/Public/Application Data/Blizzard Entertainment/Battle.net/Cache/")
                    );

                break;

replace larry with your session username.

Edited by Elckerlijc

Share this post


Link to post
Share on other sites

I'm having the exact same issue.

So far I tried with two different versions, both with the same result.

version 20338 (most recent version from bnet):

7/29 13:47:41.526  Login program=WoW platform=Win locale=enUS
7/29 13:47:41.615  Component WoW.Win.20338
7/29 13:47:41.671  Component WoW.base.20182
7/29 13:47:41.837  Battle.net is Component Bnet.Win.37165
7/29 13:47:41.908  LOGIN: state: LOGIN_STATE_CONNECTING result: LOGIN_OK 
7/29 13:47:41.947  Connecting to 127.0.0.1:1119
7/29 13:47:42.019  LOGIN: state: LOGIN_STATE_FAILED result: LOGIN_BADVERSION 
7/29 13:47:42.056  Disconnected from 127.0.0.1
7/29 13:47:42.143  Client initiated Disconnect from 127.0.0.1
7/29 13:47:42.206  LOGIN: state: LOGIN_STATE_FAILED result: LOGIN_BADVERSION 
7/29 13:47:42.306  Login program=WoW platform=Win locale=enUS
7/29 13:47:42.377  Component WoW.Win.20338
7/29 13:47:42.407  Component WoW.base.20182
7/29 13:47:42.436  Battle.net is Component Bnet.Win.37165

version 20182 (same version as server):

7/29 13:57:16.016  Login program=WoW platform=Win locale=enUS
7/29 13:57:16.050  Component WoW.Win.20182
7/29 13:57:16.081  Component WoW.base.20182
7/29 13:57:16.142  Battle.net is Component Bnet.Win.37165
7/29 13:57:16.170  LOGIN: state: LOGIN_STATE_CONNECTING result: LOGIN_OK 
7/29 13:57:16.196  Connecting to 127.0.0.1:1119
7/29 13:57:16.240  LOGIN: state: LOGIN_STATE_FAILED result: LOGIN_BADVERSION 
7/29 13:57:16.261  Disconnected from 127.0.0.1
7/29 13:57:16.293  Client initiated Disconnect from 127.0.0.1
7/29 13:57:16.319  LOGIN: state: LOGIN_STATE_FAILED result: LOGIN_BADVERSION 
7/29 13:57:16.348  Login program=WoW platform=Win locale=enUS
7/29 13:57:16.372  Component WoW.Win.20182
7/29 13:57:16.403  Component WoW.base.20182
7/29 13:57:16.429  Battle.net is Component Bnet.Win.37165

 

I have even tried 32 and 64 bit versions for both the client and server... nothing!

Share this post


Link to post
Share on other sites

It would seem that i am also having the same problem with the 122 error. I also have the latest patch which is version 20338. I have downloaded the latest trinity source code and compiled it all over again with only receiving the same error.

Edited by abdo

Share this post


Link to post
Share on other sites

Hello,

you have to have the same build of client which we support (currently 20338). Download it from blizzard launcher and then you have to use connection_patcher. This patch your client and you will get rid of that error. It will create new file Wow_patched.exe (Wow-64_patched.exe) and with that new file you can connect on your local server. Of course you have to change portal in WTF folder and Config.wtf file. Change it from EU (or possibly US) to IP of server where you are trying to connect (possibly localhost)

Regards, Mitches

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Sign in to follow this  

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By Cantte
      Well ... today I was about to compile the trinity core version for WoW 4.3.4 of this repository "https://gitlab.com/trinitycore/TrinityCore_434". Download them and when you use the cmake, I generate the solution correctly. When I began to compile this went well until I got to the last step, when I was 90% practically.
      This was the error:
      Main.obj: error LNK2019: external symbol SSLeay_version unresolved referred to in the function "public: void __cdecl <lambda_4a2d53ce610f18dba0b4b4d6532c13a7> :: operator () (void) const" (?? R <lambda_4a2d53ce610f18dba0b4b4d6532c13a7> @@ QEBAXXZ)
      25> scripts.lib (cs_server.obj): error LNK2001: external symbol SSLeay_version unresolved
      25> gsoap.lib (stdsoap2.obj): error LNK2019: unresolved sk_num external symbol referenced in the tcp_connect function
      25> gsoap.lib (stdsoap2.obj): error LNK2019: unresolved sk_value external symbol referenced in the tcp_connect function
      25> gsoap.lib (stdsoap2.obj): error LNK2019: unresolved sk_pop_free external symbol referenced in the tcp_connect function
      25> gsoap.lib (stdsoap2.obj): error LNK2019: outer symbol OPENSSL_add_all_algorithms_noconf unresolved referenced in the soap_ssl_init function
      25> gsoap.lib (stdsoap2.obj): error LNK2019: external symbol SSL_load_error_strings unresolved referenced in the soap_ssl_init function
      25> gsoap.lib (stdsoap2.obj): error LNK2019: unresolved external SSLv23_method symbol referenced in the ssl_auth_init function
      25> gsoap.lib (stdsoap2.obj): error LNK2019: external symbol SSL_library_init unresolved referenced in the soap_ssl_init function
      25> gsoap.lib (stdsoap2.obj): error LNK2019: external symbol SSL_state unresolved referenced in the tcp_connect function
      25> common.lib (OpenSSLCrypto.obj): error LNK2019: external symbol CRYPTO_num_locks unresolved referred to in the function "void __cdecl OpenSSLCrypto :: threadsCleanup (void)" (? ThreadsCleanup @ OpenSSLCrypto @@ YAXXZ)
      25> common.lib (OpenSSLCrypto.obj): error LNK2019: external symbol CRYPTO_set_locking_callback unresolved referred to in the function "void __cdecl OpenSSLCrypto :: threadsCleanup (void)" (? ThreadsCleanup @ OpenSSLCrypto @@ YAXXZ)
      25> common.lib (OpenSSLCrypto.obj): error LNK2019: external symbol CRYPTO_THREADID_set_numeric unresolved referred to in the function "void __cdecl threadIdCallback (struct crypto_threadid_st *)" (? ThreadIdCallback @@ YAXPEAUcrypto_threadid_st @@@ Z)
      25> common.lib (OpenSSLCrypto.obj): error LNK2019: external symbol CRYPTO_THREADID_set_callback unresolved referenced in the function "void __cdecl OpenSSLCrypto :: threadsCleanup (void)" (? ThreadsCleanup @ OpenSSLCrypto @@ YAXXZ)
      25> common.lib (ARC4.obj): error LNK2019: external symbol EVP_CIPHER_CTX_init unresolved referred to in the function "public: __cdecl ARC4 :: ARC4 (unsigned int)" (?? 0ARC4 @@ QEAA @ I @ Z)
      25> common.lib (HmacHash.obj): error LNK2019: unresolved HMAC_CTX_init external symbol referenced in the "struct hmac_ctx_st * __cdecl HMAC_CTX_new (void)" function (? HMAC_CTX_new @@ YAPEAUhmac_ctx_st @@ XZ)
      25> common.lib (HmacHash.obj): error LNK2019: unresolved HMAC_CTX_cleanup external symbol referenced in the "void __cdecl HMAC_CTX_free (struct hmac_ctx_st *)" function (? HMAC_CTX_free @@ YAXPEAUhmac_ctx_st @@@ Z)
      25> E: \ Server-Wow \ TrinityCore_434-4.3.4 \ Build \ bin \ RelWithDebInfo \ worldserver.exe: fatal error LNK1120: 16 external unresolved
      25> Compilation of the "worldserver.vcxproj" project completed - ERROR.
      26> ------ Compile operation started: project: ALL_BUILD, configuration: RelWithDebInfo x64 ------
      26> Building Custom Rule E: /Server-Wow/TrinityCore_434-4.3.4/CMakeLists.txt
      26> CMake does not need to re-run because E: /Server-Wow/TrinityCore_434-4.3.4/Build/CMakeFiles/generate.stamp is up-to-date.
      ========== Compile: 23 correct, 3 incorrect, 0 updated, 0 omitted ==========
       
      And this is the original error in Spanish (since I use the compiler in Spanish)
       
      Main.obj : error LNK2019: símbolo externo SSLeay_version sin resolver al que se hace referencia en la función "public: void __cdecl <lambda_4a2d53ce610f18dba0b4b4d6532c13a7>::operator()(void)const " (??R<lambda_4a2d53ce610f18dba0b4b4d6532c13a7>@@QEBAXXZ)
      25>scripts.lib(cs_server.obj) : error LNK2001: símbolo externo SSLeay_version sin resolver
      25>gsoap.lib(stdsoap2.obj) : error LNK2019: símbolo externo sk_num sin resolver al que se hace referencia en la función tcp_connect
      25>gsoap.lib(stdsoap2.obj) : error LNK2019: símbolo externo sk_value sin resolver al que se hace referencia en la función tcp_connect
      25>gsoap.lib(stdsoap2.obj) : error LNK2019: símbolo externo sk_pop_free sin resolver al que se hace referencia en la función tcp_connect
      25>gsoap.lib(stdsoap2.obj) : error LNK2019: símbolo externo OPENSSL_add_all_algorithms_noconf sin resolver al que se hace referencia en la función soap_ssl_init
      25>gsoap.lib(stdsoap2.obj) : error LNK2019: símbolo externo SSL_load_error_strings sin resolver al que se hace referencia en la función soap_ssl_init
      25>gsoap.lib(stdsoap2.obj) : error LNK2019: símbolo externo SSLv23_method sin resolver al que se hace referencia en la función ssl_auth_init
      25>gsoap.lib(stdsoap2.obj) : error LNK2019: símbolo externo SSL_library_init sin resolver al que se hace referencia en la función soap_ssl_init
      25>gsoap.lib(stdsoap2.obj) : error LNK2019: símbolo externo SSL_state sin resolver al que se hace referencia en la función tcp_connect
      25>common.lib(OpenSSLCrypto.obj) : error LNK2019: símbolo externo CRYPTO_num_locks sin resolver al que se hace referencia en la función "void __cdecl OpenSSLCrypto::threadsCleanup(void)" ([email protected]@@YAXXZ)
      25>common.lib(OpenSSLCrypto.obj) : error LNK2019: símbolo externo CRYPTO_set_locking_callback sin resolver al que se hace referencia en la función "void __cdecl OpenSSLCrypto::threadsCleanup(void)" ([email protected]@@YAXXZ)
      25>common.lib(OpenSSLCrypto.obj) : error LNK2019: símbolo externo CRYPTO_THREADID_set_numeric sin resolver al que se hace referencia en la función "void __cdecl threadIdCallback(struct crypto_threadid_st *)" ([email protected]@[email protected]@@Z)
      25>common.lib(OpenSSLCrypto.obj) : error LNK2019: símbolo externo CRYPTO_THREADID_set_callback sin resolver al que se hace referencia en la función "void __cdecl OpenSSLCrypto::threadsCleanup(void)" ([email protected]@@YAXXZ)
      25>common.lib(ARC4.obj) : error LNK2019: símbolo externo EVP_CIPHER_CTX_init sin resolver al que se hace referencia en la función "public: __cdecl ARC4::ARC4(unsigned int)" ([email protected]@[email protected]@Z)
      25>common.lib(HmacHash.obj) : error LNK2019: símbolo externo HMAC_CTX_init sin resolver al que se hace referencia en la función "struct hmac_ctx_st * __cdecl HMAC_CTX_new(void)" ([email protected]@[email protected]@XZ)
      25>common.lib(HmacHash.obj) : error LNK2019: símbolo externo HMAC_CTX_cleanup sin resolver al que se hace referencia en la función "void __cdecl HMAC_CTX_free(struct hmac_ctx_st *)" ([email protected]@[email protected]@@Z)
      25>E:\Server-Wow\TrinityCore_434-4.3.4\Build\bin\RelWithDebInfo\worldserver.exe : fatal error LNK1120: 16 externos sin resolver
      25>Compilación del proyecto "worldserver.vcxproj" terminada -- ERROR.
      26>------ Operación Compilar iniciada: proyecto: ALL_BUILD, configuración: RelWithDebInfo x64 ------
      26>Building Custom Rule E:/Server-Wow/TrinityCore_434-4.3.4/CMakeLists.txt
      26>CMake does not need to re-run because E:/Server-Wow/TrinityCore_434-4.3.4/Build/CMakeFiles/generate.stamp is up-to-date.
      ========== Compilar: 23 correctos, 3 incorrectos, 0 actualizados, 0 omitidos ==========
       
       
      Thanks.
    • By Joy
      Edit By Aokromes:

      If you can't compile check that you meet requirements:

      https://trinitycore.atlassian.net/wiki/spaces/tc/pages/2130068/Requirements


      If you get SSE2 error use:

      -DCMAKE_C_FLAGS="-msse -msse2 -msse3"
      -DCMAKE_CXX_FLAGS="-msse -msse2 -msse3"

      If you get mysql libs error you miss MySQL development files
      These files are shipped with MySQL Server but to make it easier we packed the libs and include files for both 32 bits and 64 bits.
      Extract the files to a known location, e.g, C:/mysql_libs
      https://github.com/TrinityCore/TrinityCore/releases/download/TDB335.55/mysql_lib.zip
      If you get error 0xc000007b at start is that you are mixing 32 and 64 bits libraries.
    • By darki73
      So i guess it is pretty obvious about what am i going to ask =)
      Problem is, previousle we could just sha1 username and password separated by colon and here is the sha_pass_hash.
      The problem i am facing right now, is that according to https://github.com/TrinityCore/TrinityCore/blob/86b98686a95e23247ecb774fb23ecd5b8d94b97b/src/server/game/Accounts/BattlenetAccountMgr.cpp#L177 Trinity now uses SHA256, so the hashes do not match anymore. The thing is, password length in database is 40 symbols (exactly as many as in sha1 hash), but sha256 hash length is 64 characters long. I am confused...
      I've tried to recreate whole "Cryptography" thing on PHP but, guess what, failed.
      Can somebody explain me how the password is generated nowadays?
      Thank you for your attention. 
    • By HolyNitzan
      Hey Guys,
      I'm  using the last build of TrinityCore for WoD, currently using latest TDB release, I noticed that there are no spawns in Draenor, I would like to konw how could I solve it? is the TDB not populated with Draenor mobs/npc spawns?
    • By Shinzon
      I have searched all over the forums and can't find anything that exactly matches this. 
      I can connect fine to the server using my windows client, but when I try to connect using my mac client it immediately bounces back stating "You have been disconnected from the server". 
      I have the correct IP address in the config.wtf (And realmlist in the DB) but still can't connect. 
      I of course can't apply the connection patcher, because the EXE isn't mac compatible. 
      Is there something else I need to do to connect with mac?
      Here is my connection.log if it helps (NOTE that the ".logon.battle.net" I can't get rid of... there is no where config.wtf that has that).
       
      3/14 13:10:21.966  Login program=WoW platform=Mc64 locale=enUS 3/14 13:10:22.097  Component WoW.Mc64.20886 3/14 13:10:22.097  Component WoW.base.20726 3/14 13:10:22.099  Battle.net is Component Bnet.Mc64.37165 3/14 13:10:22.099  LOGIN: state: LOGIN_STATE_CONNECTING result: LOGIN_OK  3/14 13:10:22.145  Failed to resolve “108.26.241.19”.logon.battle.net 3/14 13:10:22.145  LOGIN: state: LOGIN_STATE_FAILED result: DISCONNECTED  3/14 13:10:22.145  Login program=WoW platform=Mc64 locale=enUS 3/14 13:10:22.145  Component WoW.Mc64.20886 3/14 13:10:22.145  Component WoW.base.20726 3/14 13:10:22.154  Battle.net is Component Bnet.Mc64.37165 3/14 13:10:23.298  Client Disconnect due to reason:8 3/14 13:12:54.053  LOGIN: state: LOGIN_STATE_CONNECTING result: LOGIN_OK  3/14 13:12:54.073  Failed to resolve “192.168.1.130”.logon.battle.net 3/14 13:12:54.151  LOGIN: state: LOGIN_STATE_FAILED result: DISCONNECTED  3/14 13:12:54.151  Login program=WoW platform=Mc64 locale=enUS 3/14 13:12:54.173  Component WoW.Mc64.20886 3/14 13:12:54.173  Component WoW.base.20726 3/14 13:12:54.308  Battle.net is Component Bnet.Mc64.37165 3/14 13:12:54.309  Client Disconnect due to reason:8  
       
       
×
×
  • Create New...