hmmm i get some to dl fine but others wont im missing some files but as he said 2214 database might be making me get run time error 53 is there a older database i can use that works with his tools ?
|
In the tool site, there are databases that work pre rev2214
|
ok cool i tried 2197 but pulling same error if i repair it do as rest and give me broken file im tring repack 1871 right now..............hey Georges if i send u my email could u send me the eqitems and ds loot unrar or zip make me copy off your folders on pc....?
|
The rev2214 fixed looteditor is done and will be uploaded tonght.
Send me your email and I will send you anyfile you want. |
Good to hear and thx a ton really enjoy your tools and stuff you come up with thumbs up agine.
|
Ok getting infamous error:
"MYSQL Connection FAILED!- Check db.ini and did you install my PODBC drivers?" host=XXX.XXX.XX.XX user=xxxx password=xxxxxxx database=peq everquest_folder=C:\UF\everquest quest_folder=c:\EQEmu\quests I am connecting remotely into a server, win7 64bit. Steps completed already are: - DL'd newest version of eqitems - 14.5.5 - ran the register_ocx file just fine in admin cmd prompt, all successful - ran the "for %i in (*.ocx) do regsvr32 %i" in admin cmd prompt as well, in resources folder - mqsql is installed and doesn't error out, I get the "mysql>" prompt in the monitor What am I doing wrong? |
There are some troubleshooting steps here: http://www.thegeekstuff.com/2010/08/...nt-connection/
The first two will allow to discover if you have an issue with ports not being forwarded properly or if the remote user is not setup properly depending on the error message you receive. To troubleshoot the actual tools I would recommend installing the database locally and making sure that works to verify if you have an driver (odbc) issue or something wrong with your configuration file. |
Quote:
|
I have given you all the information you need in order to do what you want, you just need to troubleshoot and find out where the problem is.
I know you say that everything is fine with odbc, but the fact remains that something is not working. Installing the database locally to ensure the tools work there eliminates the local issues so you can concentrate on solving the remote access issue versus struggling with that and the possibility that there is something else wrong locally. |
Call to ODBC open connection started
Call to ODBC open connection created Call to ODBC open connection string completed Call to ODBC open connection failed <--- Failing step This was the direct question I was asking about, port 3306 is open on the router |
All times are GMT -4. The time now is 06:16 AM. |
Powered by vBulletin®, Copyright ©2000 - 2025, Jelsoft Enterprises Ltd.