queryserv.exe stuck on "Connecting To Mysql"
 

Alrighty. Forgive me if this is a novice error, but I can't figure out what's causing the problem.

http://i.imgur.com/L5nPXx3.png

And here's a copy of my eqemu_config.xml
Here's a paste of all the files in my EQEmuServer folder:

As you can see, queryserv.exe is stuck on connecting to MySQL. It's been like that for 30 minutes, and no change.

The log files in EQEmuServer have nothing in them; they are literally 0 bytes.

No errors occur when launching world.exe on it's own.

Yes, the MySQL server is up. XAMPP says 'tis. I'm also able to connect via command prompt using the uroot login and password, as well as the second account to be used for the config file.

So, uh, any idea what the problem is?

Could be your start.bat file that's missing something. Although looking at it I'd say your server isn't connecting to your mysql either. You running Windows 7 ect? Couls also be a bad compile aswell. Just some thoughts for you. I'd post you start.bat file so we can see it

Edit: Aye, I'm using Windows 7 64bit, but compiled everything in 32 bit, as per the guide. Used Visual Studio Ultimate 2013.

Just for the record, I can access the peq database just fine through HeidiSQL, so it might not be a database problem?

*Mumble grumble* this forum needs support for [spoiler][/spoiler]

The start.bat is the one provided with the official guide.

I found that if I start the programs manually through command prompt, ucs.exe outputs another line.

Here's what I typed:

And yes, I literally typed "zone" after eqlaunch.exe. Is that a bad thing?

In the bat file, shared_memory.exe does not have a start command. I launched it by typing "start shared_memory.exe" which then outputted a couple lines such as "loading items...", and after a few seconds, it closed.

Just realized I can copy-paste the text in command prompt, so 'ere we go.

World.exe:


Queryserv.exe:


ucs.exe:


eqlaunch.exe:

Yes, eqlaunch.exe has no text displayed.

Now, since I started the programs through command prompt, I've also got a couple log files:

The world logs are the same, sans differing IP addresses. Here's the most recent log:

World_3452.log:


ucs_4856.log:


One peculiar thing that's happening, is that the server shows up in the server listing, but is listed as locked. I can join, but am greeted with just a black screen.

The client I'm using is the one provided with Steam, sans the updates (downloaded the client, but never launched it; moved the game folder and deleted the Everquest entry from Steam).

Ahh... when did you download the client from Steam?

Daybreak updated the Steam client from the supported RoF version to a new, unsupported TDS version in mid-June. The myriad undocumented changes haven't yet been reverse-engineered and added into the server code to get the latest version working.

Hello. I'm far from an expert of computer stuff. I just like to try and solve problems.

It seems like there may be an issue with zone. If zone were connecting, you would see in the world window something similar to "[World Server] New TCP connection from 127.0.0.1:1186" and several more listings than you have based on what you set in your `launcher` table in your database.

I also noticed there are lines in your config file which are uncommented and vary from the default file. I'm not sure if this would affect anything.

I didn't see it mentioned whether this was a fresh install. I assume it is.

Just downloaded it around three days ago.

And bah, I even just finished re-downloading, making sure to stop Steam from updating it.

From what I've read, the reason we cannot share the client is because, uh, that would be sharing the files.

Gonna go make a new thread discussing XDelta, and how we can use that to make patches for the various clients kicking around, allowing everyone to be able to get the optimal version.


All the lines in the .ini were there by default, I just un-commented them to make sure that everything was set to the default settings.

Aye, it's a fresh install.


I found that if I do the following:

My server is listed on the server list as unlocked (I.E, it no longer says "locked", it now says 0), and a couple people have even joined it. I still get the black screen though, which I assume is because my client is too new.


So yeah. The guide on setting up a server for Windows 7 needs to be updated.

Try putting the comments back for this section.

Quote for the guide on the wiki.
Comment out the launcher lines, specifically.

If you know what you are doing, by all means uncomment, comment, change, do whatever you want. If you are a novice like me, I suggest leaving things as they are UNTIL you get things up and running.

If you log in to the loginserver within a few seconds of starting up your server, your server will show locked. Waiting a short time will show different. Either way, it doesn't matter if your system is running proper, you should be able to log in.

As I said, nothing about 'em was changed; I just un-commented them to ensure that the defaults were being applied.


It seems that the server itself is working, as two people with working clients joined it, which led to World.exe printing a bunch of stuff on the command line, unlike when I tried to join with the Steam client.

I don't wish to argue semantics. Try putting the comments back to ensure the defaults are actually used instead of the examples given in those lines.

If zone is not working noone will be able to get in game. Everything you have appears to be fine up to this point.

The lads joined after I posted the copy-pastes from CMD. I'll go host in the hopes that a lad or two will join, to show what World.exe outputs.

Sounds good. I'll log in if I can see it.

Oh, tah cap'n. The name is some pseudo-German gibberish. "Barannach Messersink Fabrenast"

Edit: Alrighty, found that you joined. Here's what World.exe posted:

When I joined, using the Steam Client, I was greeted with a blackscreen, and World.exe just posted "New connection from", and none of that other stuff.

Yes, that was me.

Feel free to delete that char.

I didn't notice anything unusual about the process so, it seems you are fine to login and create an agnostic human warrior out of Qeynos.

You have an extra line You'll notice random logins from time to time if you restart the server frequently. This is due to something with the client when they try to choose the same server they had previously played on. When I saw this at first I thought it was like "field of dreams". In reality it's not.

Alrighty, so the server works at last. The guide needs to be updated, methinks.

Now I've just got to get a hold of the RoF2 client. The latest Steam client isn't compatible, Titanium doesn't really like my computer, and my copy of Ruins of Kunark is old, scratched, cracked and beaten.