Hello, I don't post a lot as I tend to use the Search to find out the answers but this one has me puzzled. It seems others have the same problems but there isn't a definitive answer out there.
Anyways, let me begin.
First of all, I'm running on Windows Vista Ultimate using Microsoft SQL 2000.
I followed the 'sticky' server setup guide to creating the server, with no errors. I extracted the correct databases, which are viewable in the SQL Server and changed every IP to my LAN address (192.168.0.***). This is repeated throughout the server setup files with no variation in IP address used.
When it came to running my server, I made my account, went through to the character select screen, tried to create my character but failed. No error came up, after I clicked 'OK' no character was displayed. The server name 'Diamond' is shown at the top, so I know it is connected.
When I looked at the gates, I saw that DBserver had the following text:
The last two lines repeated indefinitely.
I also looked at my M2server, which displayed the following text:
With the last line of code being repeated for as long as the DBserver was running.
Obviously I noticed a problem, but I decided to look further into the matter to try and decipher which of the gates was causing the problem. The answer was the Selgate.
I ran every gate except the Selgate, all started fine. The DBserver had not yet said "Gate opened", but the M2server still received the spam.
As soon as I opened Selgate, the DBserver started opening and closing, and the M2server started spamming.
Here is a screenshot adaptation of the problem.
The server BEFORE Selgate is ran [Notice the last line of code in the M2server; what does this mean? The database certainly wasn't connected]:
The server AFTER Selgate is ran, and AFTER I try to create the character:
I searched on LOMCN after this problem and found a few threads that sounded like they had the same problems, but I didn't see any answers.
Note: I recently had to change the Selgate port to 7100, rather than 7200 as it was sending back the Windows socket error. I'm not sure if this has anything to do with it, although the problem was happening BEFORE I changed the port.
I've noticed that a big problem on the forum is people not explaining their problems in enough depth, so I hope I've given adequate evidence for someone to assist. In the meantime I'll keep trying.
Possible solutions to the problem [From my experience of the server]:
Thanks a lot!
Anyways, let me begin.
First of all, I'm running on Windows Vista Ultimate using Microsoft SQL 2000.
I followed the 'sticky' server setup guide to creating the server, with no errors. I extracted the correct databases, which are viewable in the SQL Server and changed every IP to my LAN address (192.168.0.***). This is repeated throughout the server setup files with no variation in IP address used.
When it came to running my server, I made my account, went through to the character select screen, tried to create my character but failed. No error came up, after I clicked 'OK' no character was displayed. The server name 'Diamond' is shown at the top, so I know it is connected.
When I looked at the gates, I saw that DBserver had the following text:
Code:
TFrmDBSrv.starttimer
Gate connected
Gate disconnected
Gate connected
Gate disconnected
Gate connected
Gate disconnectedI also looked at my M2server, which displayed the following text:
Code:
[28/03/2008 18:00:04] Guilds: 0
[28/03/2008 18:00:04] Total Castles: 1
[28/03/2008 18:00:12] DBServer Connected(192.168.0.136:6000)
[28/03/2008 18:00:15] DBServer Connected(192.168.0.136:6000)
[28/03/2008 18:00:18] DBServer Connected(192.168.0.136:6000)
[28/03/2008 18:00:19] Gate[0](192.168.0.136:52729) Opened...
[28/03/2008 18:00:21] DBServer Connected(192.168.0.136:6000)
[28/03/2008 18:00:24] DBServer Connected(192.168.0.136:6000)
[28/03/2008 18:00:27] DBServer Connected(192.168.0.136:6000)
[28/03/2008 18:00:30] DBServer Connected(192.168.0.136:6000)
[28/03/2008 18:00:33] DBServer Connected(192.168.0.136:6000)
[28/03/2008 18:00:34] LoginServer Connected(192.168.0.136:5600)
[28/03/2008 18:00:36] DBServer Connected(192.168.0.136:6000)
[28/03/2008 18:00:39] DBServer Connected(192.168.0.136:6000)With the last line of code being repeated for as long as the DBserver was running.
Obviously I noticed a problem, but I decided to look further into the matter to try and decipher which of the gates was causing the problem. The answer was the Selgate.
I ran every gate except the Selgate, all started fine. The DBserver had not yet said "Gate opened", but the M2server still received the spam.
As soon as I opened Selgate, the DBserver started opening and closing, and the M2server started spamming.
Here is a screenshot adaptation of the problem.
The server BEFORE Selgate is ran [Notice the last line of code in the M2server; what does this mean? The database certainly wasn't connected]:
The server AFTER Selgate is ran, and AFTER I try to create the character:
I searched on LOMCN after this problem and found a few threads that sounded like they had the same problems, but I didn't see any answers.
Note: I recently had to change the Selgate port to 7100, rather than 7200 as it was sending back the Windows socket error. I'm not sure if this has anything to do with it, although the problem was happening BEFORE I changed the port.
I've noticed that a big problem on the forum is people not explaining their problems in enough depth, so I hope I've given adequate evidence for someone to assist. In the meantime I'll keep trying.
Possible solutions to the problem [From my experience of the server]:
- Error with an IP somewhere in the /mirserver/ folder, although I have checked thoroughly.
- Problem with the SQL Server
- Problem with the DBServer, Selgate or M2Server
- An incorrect port somewhere
- Maybe I'll need to reinstall the entire server
- Perhaps it's because I'm running Vista?
- SQL 2000 or SQL 2005?
Thanks a lot!
