1 Attachment(s)
Problem with the MatchServer. DBConnect failed ThreadID=#
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?
https://www.mediafire.com/convkey/8b...8xoekiv56g.jpg
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
Re: Problem with the MatchServer. DBConnect failed ThreadID=3832
The problem affect the players connection. Most of the pings are +350 and +400..
Re: Problem with the MatchServer. DBConnect failed ThreadID=3832
Quote:
Originally Posted by
cheaterastic
The problem affect the players connection. Most of the pings are +350 and +400..
can you get us the full log?
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?
Re: Problem with the MatchServer. DBConnect failed ThreadID=3832
Quote:
Originally Posted by
Anju
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.
Re: Problem with the MatchServer. DBConnect failed ThreadID=3832
Does it show up in only MatchServer or all the runnables?
Re: Problem with the MatchServer. DBConnect failed ThreadID=3832
If you still need help, send me a PM with your skype/steam nick.
Re: Problem with the MatchServer. DBConnect failed ThreadID=3832
Quote:
Originally Posted by
Anju
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.
https://www.mediafire.com/convkey/62...a7une03p6g.jpg
Re: Problem with the MatchServer. DBConnect failed ThreadID=#
Try to re setup everything again.
Re: Problem with the MatchServer. DBConnect failed ThreadID=#
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 ?
Re: Problem with the MatchServer. DBConnect failed ThreadID=#
Quote:
Originally Posted by
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 ?
I am not sure if it's problem of SQL version, But if yes then use SQL 2005.
Re: Problem with the MatchServer. DBConnect failed ThreadID=#
It happen on Windows Server only, and with SQL 2012 :|.
Locator.exe really need reopen many time even all config certainly.Something wrong....
Re: Problem with the MatchServer. DBConnect failed ThreadID=#
I believe it's only specs here.
Re: Problem with the MatchServer. DBConnect failed ThreadID=#
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....
Re: Problem with the MatchServer. DBConnect failed ThreadID=#
what is your sql server name, I think i got it.
Re: Problem with the MatchServer. DBConnect failed ThreadID=#
Quote:
Originally Posted by
sahar042
what is your sql server name, I think i got it.
Server Name: VPS71753
http://forum.ragezone.com/f10/mssql_...ponse-1010211/
Re: Problem with the MatchServer. DBConnect failed ThreadID=#
Quote:
Originally Posted by
cheaterastic
I got it, You installeted wrong the SQL server, Your name server should be like in the picture
With the \SQLEXPRESS part:
http://www.lvitweb.com/images/report...ver%20Name.jpg
Example ^
*I remember I got the same problem from long time ago with this server name.