Jet another "XP Database"-Thread

[Frameboy]

Sorry, but the other thread (viewtopic.php?f=21&t=3307) has been closed!
I currently have another problem with converting the old "war3users".
I followed the docs and I have googled the last hours but found no answer.
The new table are installed in the database automaticly, but the contents of the old war3users won*t be writen in the new tables.
The following error was writen in the error.log:

L 07/22/2008 - 00:09:34: ** Map cs_winter_assault started, version: '3.0 RC11b'
L 07/22/2008 - 00:09:34: [MYSQLX] Error in querying database, location: 12
L 07/22/2008 - 00:09:34: [MYSQLX] Message: Access denied for user: 'xxx@10.' to database 'information_schema' (1044)
L 07/22/2008 - 00:09:34: [MYSQLX] Query statement: SELECT count(*) FROM information_schema.tables WHERE table_schema = 'xxx' AND table_name = 'war3users';

I don't have a database "information_schema" and i can't create it.
What could I do???

Sorry for my bad english, but school is long ago!

Greetz from germany Frameboy

[YamiKaitou]

Search the forums for "information_schema"

[Frameboy]

Now, I have done. But I only found this thread!

[Geesu]

information_schema is a "hidden" table that has more information.

I'm not sure what permissions your user needs to be able to read it - I would google "permissions, information_schema"

[Frameboy]

I'm not sure too. I have a webserver and there I can see und edit the database "information_schema".
But my Gameserver is not a root-server. It is rented. So I can't see or edit the information_schema.

Just another question: why is the ip-adress cut in the logfile? "... user: 'xxx@10.' to ...". Could this be the reason why he could not connect?
It must be xxx.xxx.xxx or not?

[YamiKaitou]

What version of MySQL are you using?

[Geesu]

Your MySQL provider is just locking your user account down - that is all - ask them to grant you READ only to information_schema

[Frameboy]

What version of MySQL are you using?

MySQL-Client-Version: 5.0.54

[YamiKaitou]

Then, you can do 1 of 2 things.


Do what Geesu said and ask for READ access to the table.

Remove the 2.x to 3.x MySQL self update feature.