Problem Logging in

[Vagrant]

I've setted everything, checked it twice but when i click on name nothing is happening(after i add id and pass). Im sure i checked everything now, in ODBC i added everything and tested it sayd TEST SUCCESSFULL, then when i try to do test again says TEST FAILED, i edit all of them and i noticed the sa pass didnt stay remembered there, then i added it again and the test was succesfull again, when i do all over is same thing failed/successfull, after that i tryed KaoriCheck and this came up :
---------- SQL Checking Start ----------
---------- Account Database (ODBC) ----------
Account ODBC is connected successfully.
TBL_ACCOUNT has 1 rows.
---------- Game Database (ODBC) ----------
Game ODBC is connected successfully.
TBL_CHARACTER has 0 rows.
---------- Manage Database (ODBC) ----------
[Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified
---------- Base Data Database (Direct) ----------
Charset 0x0408D00000/MS936 is not supported by the JVM.
---------- Game Database (Direct) ----------
Charset 0x0408D00000/MS936 is not supported by the JVM.
---------- Hero Database (Direct) ----------
Charset 0x0408D00000/MS936 is not supported by the JVM.
---------- SQL Checking Done ----------

 

[Kaori]

Charset 0x0408D00000/MS936 is not supported by the JVM.

means you have to reinstall JAVA and make sure you select all options for languages.

 

[Zordon]

I've setted everything, checked it twice but when i click on name nothing is happening(after i add id and pass). Im sure i checked everything now, in ODBC i added everything and tested it sayd TEST SUCCESSFULL, then when i try to do test again says TEST FAILED, i edit all of them and i noticed the sa pass didnt stay remembered there, then i added it again and the test was succesfull again, when i do all over is same thing failed/successfull, after that i tryed KaoriCheck and this came up :
---------- SQL Checking Start ----------
---------- Account Database (ODBC) ----------
Account ODBC is connected successfully.
TBL_ACCOUNT has 1 rows.
---------- Game Database (ODBC) ----------
Game ODBC is connected successfully.
TBL_CHARACTER has 0 rows.
---------- Manage Database (ODBC) ----------
[Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified
---------- Base Data Database (Direct) ----------
Charset 0x0408D00000/MS936 is not supported by the JVM.
---------- Game Database (Direct) ----------
Charset 0x0408D00000/MS936 is not supported by the JVM.
---------- Hero Database (Direct) ----------
Charset 0x0408D00000/MS936 is not supported by the JVM.
---------- SQL Checking Done ----------

have you got the SQL service pack? I had this same problem and it was because I needed the update. have a look on kaoris site in tools i believe there should be 2 sql service packs, one for developer edition and one for eval edition.

 

[mapadale]

have you got the SQL service pack? I had this same problem and it was because I needed the update. have a look on kaoris site in tools i believe there should be 2 sql service packs, one for developer edition and one for eval edition.

You shouldn't need to install any service pack for SQL in order to gain connection. I would also advise against installing any service pack for any microsoft product on a server, unless you know the service pack won't cause a problem ( this does require you to have a full understanding of service packs under MCSE and MCSA )

As some service packs can cause some dis-comfort on some applications.

 

[Zordon]

---------- Manage Database (ODBC) ----------
[Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified

that was the problem I had and only way i was able to fix was installing the service pack. it stopped me being able to log in for some reason.

 

[mapadale]

---------- Manage Database (ODBC) ----------
[Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified

that was the problem I had and only way i was able to fix was installing the service pack. it stopped me being able to log in for some reason.

That is because SQL isn't able to talk to OBDC, which is a configuration issue and not a service pack issue.

I've never had to install a service pack for SQL or OBDC and never had a problem.

The issue is with the OBDC MANAGE.DAT ENTRY - SQL is unable to locate this and tell OBDC what it is and what it supposed to be doing.

 

[Zordon]

well funny enough i reinstalled and reconfigured sql and obdc so many times, no matter which way i did it didn't change anything until i installed the service pack.

 

[mapadale]

well funny enough i reinstalled and reconfigured sql and obdc so many times, no matter which way i did it didn't change anything until i installed the service pack.

You can't just uninstall SQL though, as SQL has to be removed fully using an SQL remover or it leaves entrys within the reg.

@Vagrant, have you checked the OBDC entry for manage.dat and tested it through OBDC and did it pass or fail - Also which OS build are you using.

 

[Vagrant]

@Vagrant, have you checked the OBDC entry for manage.dat and tested it through OBDC and did it pass or fail - Also which OS build are you using.

yes tested it... and it worked

but wont let me pass when i click server name...

 

[Azura]

Have you edited the EI IP in the DBserver(HolleyDBSvrEiIP.txt)? Alot of people dont do it and it needs to be done.

Also if your using vista you may need to do some extra stuff for the connections.

 

[Vagrant]

Have you edited the EI IP in the DBserver(HolleyDBSvrEiIP.txt)? Alot of people dont do it and it needs to be done.

Also if your using vista you may need to do some extra stuff for the connections.

XP SP 2 , and yes to the DBSvrEIIP.txt

 

[Azura]

tried using 127.0.0.1 and not (local) in ODBC or even your system name DELL-5500383 for example?

Using SQL2005 or SQLEval2000?

 

[mapadale]

So when you created the entry for OBDC did you actually hit the button TEST or did you just add the entry?

 

[Vagrant]

tried using 127.0.0.1 and not (local) in ODBC or even your system name DELL-5500383 for example?

Using SQL2005 or SQLEval2000?

SQLEval2000, i put the server files b4 on this pc, this exact pc....and it worked

So when you created the entry for OBDC did you actually hit the button TEST or did you just add the entry?

yes i did hit the test button and it sayd succesfull