One step forward - none back
Going to pick this up tommorow but:
Thank you lerxst2112 - 5 builds no fails :) Noport thank you too - question? Code:
<!-- Loginserver information. Defaults shown --> I havent altered tblserveradministration as I dont recall it asking me to and there is some default value in there? Again thanks |
For security purposes, you can delete the Admin account that's entered by default in tlbloginserveraccounts table tblserveradministration
your answer is table tblserveradministration Requires user name and password put into eqemu_config This is my eqemu_config Code:
<?xml version="1.0"> Code:
[database] Code:
[Debug] [02.20.12 - 15:39:27] Logging System Init. |
Back on this
Hi again, never got this working and had to go on an overseas tour and looking for further assistance - help would be appreciated.
I have started fresh and the latest source (2171) this fails on the compile however 2099 does not, first part, how do I check which server and database revisions work with each other, its not clear to me? I will be working with source 2099 and I am trying to make sure I get the correct server revision. Thanks in advance |
You should be able to use the current SVN for both the server code and the database with no foreseeable issues.
Occasionally, a bug will slip in, but that is not the intended design... In starting a new server with the current revisions (eqemu 2171 and 63 for peqdb) you just need to make sure that you have all of the sql updates applied. Note that the name of the peqdb is called peqdb_rev2142.sql and this was updated from peqdb_rev2133.sql in peqdb revision 62. The name of the database sql file ONLY reflects the cumulative changes to the database to match the eqemulator revision and not the peqdb revision itself. To keep current, you need to not only source in the database, but also ANY patches that equal or exceed the server revision that you plan to run. If you look in two places, you will find sql update files that need to be sourced in as well. First, look in your peqdatabase (source) directory and you will see a folder called updates. Inside of this is a file called rev2142.sql. This is a patch from the PEQ people that needs to be sourced in after the base peqdb_rev2142.sql file. Once a new peqdb is released, you no longer have to apply anything older than the revision in the db filename. Second, look in your eqemuserver\utils\sql\svn (source) directory. In here you will see several sql files that are higher than the peqdb base file. You will need to source these in as well. If you are running a revision that is less than the some of the sql updates, you may or may not run into issues by sourcing in higher files than your server revision, so I'd only recommend sourcing in up to or equal to your actual eqemu revision. Saying which server revisions work with what peqdb revisions is not exactly easy to say. (If you're going to use server rev 2099, you should probably revert your peqdb back to something 2099 or less as well and source in any updates to match. Thing is, you'll miss anything that has been updated/fixed since then if you go that route.) In regards to your issue with compiling, you will need to provide more information. I use both VS 2008 and VS 2010, both in 32-bit compile on a 32-bit OS and have compiled most revisions since 2142 with no problems. There's any number of things that could be causing the failure and there's not enough information in your post to say what the problem is... |
Can anyone see issues with these files assuming the following:
shortname = short, long name = short name tblserveradminregistration have accountname = admin, password = random tblloginserveraccounts have accountname = admin, password = random mysql user = root, password = password Login.ini Code:
[database] Code:
<?xml version="1.0"> |
I played this game once! I could never find that 13th bear though...
|
Quote:
|
Well, the thing is, posting a config without telling us what the issue might be is also sort of random.
You do have the address and localaddress commented out, which might be fine, but since you did change them perhaps you were thinking it would do something but as it sits right now it won't. |
Ahh ok
World.exe is giving this Code:
[Debug] [NET__IDENTIFY] Registered patch Underfoot Code:
[Debug] Starting Log: logs/eqemu_debug_3320.log |
In eqemu_config.xml you are missing a shared key. This line
Code:
<!-- Sets the shared key used by zone/launcher to connect to world --> Code:
<!-- Sets the shared key used by zone/launcher to connect to world --> |
I have entered that in before but just tried again, but still same errors.
Should that key be entered elsewhere aswell? |
I don't think that shared key is entered any where else. The only other thing that looks out of place is the ip address 192.168.0.10 in this section.
Code:
<!-- Loginserver information. Defaults shown --> I don't know that it will help but it just might. |
that's probably it, because 10061 is a standard windows socket error. it means the computer at the address responded, but refused the connection.
|
I have amended the address to 127.0.0.1, and no joy, just looking into the 10061 idea now..
from microsoft Quote:
|
where are your logs from EQEmuLoginServer?
|
All times are GMT -4. The time now is 02:53 AM. |
Powered by vBulletin®, Copyright ©2000 - 2025, Jelsoft Enterprises Ltd.