Problem with the MatchServer. DBConnect failed ThreadID=#

[cheaterastic]

Problem with the MatchServer. DBConnect failed ThreadID=3832

This is unexpected problem.
I don't know how this problem exist. I check the configuration of matchserver, agent and locator, and all fine, password and ip address are correct. Players can see the server but I don't know why this DBConnect failed ThreadID=3832 exist..

Anyone can help?

 

[Tannous]

Re: Problem with the MatchServer. DBConnect failed ThreadID=3832

Probably it's because you made the ODBC configuration under user dns or system dns.. i dunnu which one is the corret 1 to add under it lol

 

[cheaterastic]

Re: Problem with the MatchServer. DBConnect failed ThreadID=3832

The problem affect the players connection. Most of the pings are +350 and +400..

 

[medotarek]

Re: Problem with the MatchServer. DBConnect failed ThreadID=3832

The problem affect the players connection. Most of the pings are +350 and +400..

can you get us the full log?

 

[Anju]

Re: Problem with the MatchServer. DBConnect failed ThreadID=3832

Does this problem occur when you start your MatchServer.exe? Or does it deal with your ODBC setup?

 

[cheaterastic]

Re: Problem with the MatchServer. DBConnect failed ThreadID=3832

Does this problem occur when you start your MatchServer.exe? Or does it deal with your ODBC setup?

After I start my matchserver, agent, and locator, after few seconds, the pop up message show.

 

[Anju]

Re: Problem with the MatchServer. DBConnect failed ThreadID=3832

Does it show up in only MatchServer or all the runnables?

 

[GermanGuy]

Re: Problem with the MatchServer. DBConnect failed ThreadID=3832

If you still need help, send me a PM with your skype/steam nick.

 

[cheaterastic]

Re: Problem with the MatchServer. DBConnect failed ThreadID=3832

Does it show up in only MatchServer or all the runnables?

The pop-up message is from the MatchServer. It only pop-up once after few seconds when MatchServer, Agent and Locator has been started.

The OBDC is correct.

 

[sahar042]

Try to re setup everything again.

 

[Gun[Lengend]]

I got this problem on my VPS too, that a first time i got that.
I think something happen with SQL Server 2012, do you using this version like me ?

 

[sahar042]

I got this problem on my VPS too, that a first time i got that.
I think something happen with SQL Server 2012, do you using this version like me ?

I am not sure if it's problem of SQL version, But if yes then use SQL 2005.

 

[Gun[Lengend]]

It happen on Windows Server only, and with SQL 2012 :|.
Locator.exe really need reopen many time even all config certainly.Something wrong....

 

[Anju]

I believe it's only specs here.

 

[cheaterastic]

Not only SQL 2012, but also SQL 2008. Yes, I am using SQL 2008. I keep searching on Google and other people having the same problem even they are using SQL 2005.

The problems that I have encountered because of this:
- On the php/website, the mssql_connect is delay or delay connection to SQL Server. It wait 5 seconds before the page load.
- On the ODBC, on "Test Data Source..", it is also delay (about +5 seconds) after TEST COMPLETELY SUCCESSFUL.

HELP....

 

[sahar042]

what is your sql server name, I think i got it.

 

[cheaterastic]

what is your sql server name, I think i got it.

Server Name: VPS71753

Spoiler

http://forum.ragezone.com/f10/mssql_connect-delay-response-1010211/

 

[sahar042]

Server Name: VPS71753

Spoiler

http://forum.ragezone.com/f10/mssql_connect-delay-response-1010211/

I got it, You installeted wrong the SQL server, Your name server should be like in the picture
With the \SQLEXPRESS part:

Example ^
*I remember I got the same problem from long time ago with this server name.