Paladin Server-INvaild User Name/Pass

11/19/2008 21:23 usdachoice#1
Hey guys. I have read thru every post so far for help on the new paladin release, but nothing so far.

My problem is when I try to loin to the game I get "Wrong User name or Password". Now I have account, server, and msg all working 100%, so the problem dose not lie there. I have tried registering for the game via my website as well as using the MYSQL console and adding in

insert into account.account (name,password,reg_date) values ('test','53b6320eb06e2c62888a6d1739cd24bd',now());

The above will make the user name and password test/test but that dose not work either and yes, the accounts DO show up in MYSQL.

I have tried client versions 1091 as well as 1030 but they both end up at the same "Invalid User Name or Password"
11/19/2008 21:24 Rawsteeey#2
at first: stop making threads where you need help, if u needhelp, go to the helping thread next time pls.

back to topic:
you should look at your oem.
11/19/2008 21:41 usdachoice#3
Quote:
Originally Posted by netlog_stefan View Post
at first: stop making threads where you need help, if u needhelp, go to the helping thread next time pls.
At first, no rule is stated that I have to use this "Helping thread". Although I understand what you are saying, but by posting here it will be seen faster.
back to topic:

Quote:
Originally Posted by netlog_stefan View Post
you should look at your oem.
OEM is 100% right. I could have made a mistake but w/ the old 1091 Eudemon Client's oem, I never had a problem.
11/19/2008 21:58 Rawsteeey#4
then post your oem here.
Yes theres no rule, but its better.
11/19/2008 22:03 usdachoice#5
Quote:
Originally Posted by netlog_stefan View Post
then post your oem here.
Yes theres no rule, but its better.
Thank you very much :P

Here is my oem.

[Oem]
Id=2010

[AccountSetup]
Type=1

[ServerInfo]
URL=http://Alpha2009.com

[ServerStatus]
Link=http://Alpha2009.com



[¹??????
¹?????¾=http://Alpha2009.com
?²?????=http://Alpha2009.com
???¹???=http://Alpha2009.com
?µ????=http://Alpha2009.com
?¨??×?¾?=http://Alpha2009.com
???????=http://Alpha2009.com
µ??½????=http://Alpha2009.com

[ExitLink]
Address=http://Alpha2009.com

[VipLink]
URL=http://Alpha2009.com

[Header]
GroupAmount=1

Group1=BlackWorldEO


[Group1]
ServerAmount=1

Server1=BlackWorldEO
Ip1=127.0.0.1:5816
Pic1=Server1
ServerName1=BlackWorldEO


Now if I use 127.0.0.1 with out a port number it says Invalid user name and password BUT if I use 127.0.0.1:5816 it gets stuck at Verifying Account.


I believe the problem lies in the file AuthorizeDB.cfg Do you happen to have a replacement for it?
11/19/2008 22:06 lukonhabr#6
Paladin Web Site + Scripts New By Kabuto

[Only registered and activated users can see links. Click Here To Register...]
11/19/2008 22:17 Rawsteeey#7
i think you should take 127.0.0.1:9888 as ip.
if thatwont work, post your AuthorizeDB.cfg here.
11/19/2008 22:25 usdachoice#8
Quote:
Originally Posted by netlog_stefan View Post
i think you should take 127.0.0.1:9888 as ip.
if thatwont work, post your AuthorizeDB.cfg here.
Tried that but nothing and for the hell of it I used every port that the account, msg, and npc servers use but nothing with that ither.

So heres my AuthorizeBD.cfg

127.0.0.1 root test my2 account name password id
count_stat server_name status
127.0.0.1 root 378b243e220ca493 account
11/19/2008 22:35 Rawsteeey#9
hm... sorry, i cant help you.
try my instead of my2, if that wont work, i cant to anything, sorry
11/20/2008 02:08 Kradel#10
The new Paladin database uses an account table inside the my2 database, instead of the account table inside the account database as before. You should try to change that string as follows:
Quote:
insert into my2.account (name,password,reg_date) values ('test','53b6320eb06e2c62888a6d1739cd24bd',now());
Notice how account.account is changed to my2.account. This will insert the new account into the correct table, if you are using correct server files and all.
11/20/2008 04:59 usdachoice#11
Quote:
Originally Posted by Kradel View Post
The new Paladin database uses an account table inside the my2 database, instead of the account table inside the account database as before. You should try to change that string as follows:

Notice how account.account is changed to my2.account. This will insert the new account into the correct table, if you are using correct server files and all.
OH MY! *Slaps forehead* How did I miss that simple little peace? Now I feel like a moron haha. That you a ton. It works now. *still cant believe he missed that*