Run-time error with all tools

[kaos00723]

Hi, I can get all the tools to work and everything seems fine but when I actually go to do something like execute diablo random loot or fix npc loot tables I get the following error:

Run-time error '-2147467259 (80004005)':

[MySQL][ODBC 3.51 Driver][mysqld-5.1.56-community]Column count doesn't match value count at row 1

Any idea what may be causing this?

[kaos00723]

Still need help with this please. Can't do much customizing without these tools...

From the sound of the error, a table column isn't matching or something. This is latest PEQ DB with MySQL 5.1.56 and 5.1.63. Have not tried 5.5+ yet.

I've never had this problem before with the tools, something is causing this.

[wolfwalkereci]

Only tool I see this error with is the diablo ranloot
I'm sure George will see this thread and post up soon.

[GeorgeS]

I just saw the message.

These should run on the latest build (as of several weeks ago).
What I need is what does not work on a particular tool so I can investigate.
I get the impression nothing works..

GeorgeS

[kaos00723]

Hi GeorgeS.

This error is happening when I either use the Diablo loot tool to assign loot to level ranges or to fix broken npc loot tables.

This also happens in the npc editor when I try to fix broken loot tables through there as well.

I am sure it is happening with other functions similar to these but those are what I need the most so I've only tested those.

I think there is a table column not matching what your tools are looking for or at least that's what the error sounds like to me. PEQ DB rev2142 is causing the problem since I didn't have this problem with older revisions of the DB and your tools.

Thanks for looking into this!

[kaos00723]

Any news on this?

I have even dropped and re-sourced the db and SQL updates and this error still occurs. :(

[GeorgeS]

I found the problem and a fix will be uploaded tonight.

GeorgeS


edit - newest version is uploaded

[kaos00723]

I found the problem and a fix will be uploaded tonight.

GeorgeS


edit - newest version is uploaded

Nice, will try it out later. Thank you!

Btw, this was also happening with the npc and loot editor when you go to fix broken loot tables, same error the diablo loot tool was giving. I guess I can just use the diablo loot tool to do it now if it works but you might want to look into the npc/loot editor too.

[iwolf]

Im seeing this problem on d2 loot column count doesn't match value count at row 1

[GeorgeS]

I assume you're using v.1.7.3?

What button/function causes this?

[iwolf]

yes version 1.7.3
happens when i try to execute.

[kaos00723]

Yeah, I pretty much gave up on this.

Same error, same problem with both tools. The update to the Diablo loot tool didn't help either.

Both tools give this error when you either try to fix broken loot tables or add loot with the diablo loot tool.

Your tools are out dated for the current db is all I can think of.

[GeorgeS]

No, the fix did work,unfortunately the site was hacked and I lost the fixed binary and the current binary is the older one. Now I have to redo everything to fix this and it takes time.

George

[GeorgeS]

Ok I worked on this and I uploaded the newest binary.
Let me know if you have issues with it.

GeorgeS

[kaos00723]

Ok I worked on this and I uploaded the newest binary.
Let me know if you have issues with it.

GeorgeS

Both tools are working now.

Big thank you!

[FievelMousey]

says caint connect to DB etc and i run your tool check says all is ok older version used run but gave error and crashed. I have checked all settings over and over no go yet

[GeorgeS]

says caint connect to DB etc and i run your tool check says all is ok older version used run but gave error and crashed. I have checked all settings over and over no go yet

This is due to schema compatibility. You need the latest DB because the columns in loottables changed.

[FievelMousey]

i have newest DB where i get newer one?

[arcadius]

Having some issues myself. Just downloaded the most recent version. Registered all of the ocx files fine. When I start eqitmes it gives the db connection error, suggests some missing version fields in variables tables, then if I click off the music on the splash screen and click lets start, the gui actually launches. Not sure if this means it should work because at the splash screen it said db connect FAIL.

Here is my logfile contents:


creating log entry
Identified user:root
Identified database:peq
Identified host:localhost
Identified everquest_folder:D:\Everquest\
Completed getting user info
credential output to screen ok
Call to ODBC open connection started
Call to ODBC open connection created
Call to ODBC open connection string completed
Call to ODBC open connection open
Call to ODBC open recordset started
Call to ODBC open connection completed
Open RS with sql: SELECT value FROM variables WHERE varname='DBVersion'
Recordset version returned: 070_pop_cvs
Starting music: D:\Everquest\deaththeme.mp3
Splash returned an error-connection fail
Splash request to load MAIN program started
Started Main ok
Started to read all init *.txt files
Started to read all init *.txt files - ok done
MAIN exectuted ok - Form Load done and exiting
Splash request to load MAIN program done. Splash unloaded ok

[arcadius]

Update: although it says db connection fail on splash screen, I am still able to edit items, restart server, and the new items are there.

So all seems good :)

Very fun tool, btw. Nicely done.

[opyrus]

diablo_loot.exe v1.2.5

Run-time error '-2147467259 (80004005)':

[MySQL][ODBC 3.51 Driver][mysqld-5.5.28]Column count doesn't match value count at row 1

using the latest peq database each time it stops after the first item.

[GeorgeS]

D2 Loot editor is not compatible yet.

[opyrus]

D2 Loot editor is not compatible yet.

is it something your working on? i would like to be able to use this tool.

[kimura]

any chance this will get updated? or is it a dead work?

[vithmiris]

diablo_loot.exe v1.2.5

Run-time error '-2147467259 (80004005)':

[MySQL][ODBC 3.51 Driver][mysqld-5.5.28]Column count doesn't match value count at row 1

using the latest peq database each time it stops after the first item.

Using the latest peq database, I am also receiving the above error.

Thanks for your work George!