- Joined
- Jan 6, 2007
- Messages
- 4
- Reaction score
- 0
Alright, I am having problems setting up this server on a dedicated box, and its getting extremely frustrating... To start off, I had no problem getting these same files running on a closed LAN. But after I moved to a dedicated, I have been presented with problems that are driving me insane. And without the search function here, I am finding it hard to solve this issue, so Im hoping the direct approach might help a little bit.
Ok, the specifics
Windows Server 2k3 x64
MSSQL via sa account
All the ini's and sql DB files were set to 127.0.0.1 *with the exception of the 127.0.0. in the sql*
The only ip entered differently was in the config.txt under dev ip in auth\etc set to WAN.
The file DSN's have been set up, and to my knowledge are working correctly, i dont get repeated prompts for SQL login information during server boots.
When I start up the server, this is the sequence of events..
after starting cache, i fire up the Auth server, and get this.
I have found other posts with this error, and none of the solutions corrected the problem, including the manual injection to register the server table in l2db
* I repeat* the server table has the ID#,Name,OutterIp, InnerIp, xxx, xxx, xxx, port all configured
if I go on to boot the server, I then get this
I have never gotten those malloc (>32K) errors before on the closed LAN setup, and I have no idea what it means or where they came from.
anyways, all goes well for a few seconds, then it gets to the end of the server boot, and I get this
I have seen these 4 errors on other posts as well, but none of the solutions have worked, or the thread died. To start, I am not sure what the cause of the Inspector.u or the PGFCV error is, I never had it on my last set up... so I am not sure whats causing it... And last but not least, the famous AuthSocket error, to which ALSO, no fix has worked for =/ So, as the Auth rejects the server, the server tries to connect one last time, then shuts down.
Now, when you go back to the Auth window, after getting that server error.. you get the same error thats often attached to the Authsocket problem
Now to me, after looking at all these errors, it looks like its one simple problem... the servers arnt properly connected to the SQL DB's.. I may be wrong, but its just what it looks like to me.. A cant connect to B, then its just a castcade failue from there. So, does ANYONE know whats going on here? or could anyone help me with this.. its going to turn me grey... I am not sure if its a port problem, socket problem, security issue, file issue, incompatability with the software.. Any other people experienced in dedicated hosting run into this before? Anyways,.. any and all input would be greatly appreciated..
Cheers..
Ok, the specifics
Windows Server 2k3 x64
MSSQL via sa account
All the ini's and sql DB files were set to 127.0.0.1 *with the exception of the 127.0.0. in the sql*
The only ip entered differently was in the config.txt under dev ip in auth\etc set to WAN.
The file DSN's have been set up, and to my knowledge are working correctly, i dont get repeated prompts for SQL login information during server boots.
When I start up the server, this is the sequence of events..
after starting cache, i fire up the Auth server, and get this.

I have found other posts with this error, and none of the solutions corrected the problem, including the manual injection to register the server table in l2db
* I repeat* the server table has the ID#,Name,OutterIp, InnerIp, xxx, xxx, xxx, port all configured
if I go on to boot the server, I then get this

I have never gotten those malloc (>32K) errors before on the closed LAN setup, and I have no idea what it means or where they came from.
anyways, all goes well for a few seconds, then it gets to the end of the server boot, and I get this

I have seen these 4 errors on other posts as well, but none of the solutions have worked, or the thread died. To start, I am not sure what the cause of the Inspector.u or the PGFCV error is, I never had it on my last set up... so I am not sure whats causing it... And last but not least, the famous AuthSocket error, to which ALSO, no fix has worked for =/ So, as the Auth rejects the server, the server tries to connect one last time, then shuts down.
Now, when you go back to the Auth window, after getting that server error.. you get the same error thats often attached to the Authsocket problem

Now to me, after looking at all these errors, it looks like its one simple problem... the servers arnt properly connected to the SQL DB's.. I may be wrong, but its just what it looks like to me.. A cant connect to B, then its just a castcade failue from there. So, does ANYONE know whats going on here? or could anyone help me with this.. its going to turn me grey... I am not sure if its a port problem, socket problem, security issue, file issue, incompatability with the software.. Any other people experienced in dedicated hosting run into this before? Anyways,.. any and all input would be greatly appreciated..
Cheers..