Billy

As you can see in the attached image, my search perimeter. This has been a problem for years, and would venture to say one of the main causes of questions getting repeated an awful lot.

Thanks for clearing that up for me.

Hello all, it's been awhile since I was last here. I went to pull 3.3.5a from the repository and noticed 3.3.5 & 3.3.5-auctionhouse. Both of these are full 3.3.5a servers? Only one has the auctionhouse bot in it I'm guessing? And if that is the case is 3.3.5-auctionhouse updated to match the 3.3.5 timestamp? I mean the last time 3.3.5-auctionhouse was updated according to Git was about 9 months ago, and 3.3.5 was updated today.

I always clear the 3 files before unzipping the new ones into the folder. The reason for not working for me was they were blocked by winblows due to coming from another computer, so the security "features" auto blocked it. But now I know what to look for.

I just got it working. Some how the file WSTC-64.exe and the key64.24461.wstc were blocked by my OS. To fix it I just right clicked on the properties of both files and unblocked them.

Thanks Aokromes. Guess I'll just have to keep digging.

Yes.

Been having problems with the sniffer that I get from here. I keep getting "WSTC-64.exe is not recognized as an internal or external command, operable program or batch file. Press any key to continue..." This has been going on for about 2 months now. I've asked the aurthor of the program if there are any dependencies or anything like that that I might not have installed yet, and was told it doesn't require any. The only other thing that I can think of that might be causing it to crash would be addons. So is there anybody out there using addons to the client and still able to sniff?

Just remember one thing. Seeing how as you are working with multiple servers, the server you need to have SQL's updated on, will need to have git set for that particular branch, or you'll get errors.

Use the Checkout Branch command in git.

If It were me, I would delete EVERYTHING, I do mean EVERYTHING, then goto the Wiki and follow it step by step. It sounds like you have something crossed up some where, some how.

Did you compile the latest extractors when you compiled the server?

Do you have a 7.2.0 client? If so patch it to 23911 and then do like Aokromes said, re-run the extractors. I ran into that problem yesterday. I was doing everything with the previous client 23875, that was the wrong thing to do. TC is updating the client as well. Not like 3.3.5a where it was the same client all the time.

'C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\bin\CL.exe' try using the VS 15 2017 Win64.

Thanks.

Hello all, after going through the core set up for Win, I noticed the wikki says I should have bnetserver.pdb and worldserver.pdb files in my build folder. I do not have those two files. I compiled using VS 2017. I also noticed that it says I need those two files for the 3.3.5 server as well, but I have never seen those 2 files in my 3.3.5 build folder before. Are those 2 files for OS's other than Winblows or did I miss something? I am currently trying to get the master branch up and running.

Does the CATA worldserver.conf have it's realm id set to 3 as well?

Are you trying to access WotLK with a CATA client?

Yes, but make sure both worldserver.confs point to the same auth database. You'll run 1 authserver and 2 worldservers.

In the CATA worldserver.conf, change: LoginDatabaseInfo = "192.168.1.3;3306;Trinity;********;cata-auth" to point to the WotLK auth database. LoginDatabaseInfo = "192.168.1.3;3306;Trinity;********;auth" and it should work then.

Are the ports open on the router?

Which client are you using? CATA or WotLK?

Restart authserver, then start up your worldservers.

In the auth database, go to realmlist. Add a new row for the second server, fill in the new row like the first one only use your second servers properties like port number, ip address, and change gamebuild to the client your second server uses. Once your database is done, you should be able to start authserver and both worldservers.