[User Retest] Unable to connect RAT to my local server

[fyresoul]

I'm unable to successfully connect RAT to my local server using the "Server Connection" button. I am able to telnet in from the command line successfully.

The following is what the RAT Log:


2023-02-01 10:43:21 - ************************** RAT Startup **************************
2023-02-01 10:43:21 - Checking for RAT Upgrade
2023-02-01 10:43:21 - No upgrade necessary, DB version is: 3022
2023-02-01 10:43:21 - Created telnet object
2023-02-01 10:43:21 - Loaded server config
2023-02-01 10:43:21 - Set display defaults
2023-02-01 10:43:21 - Creating timers
2023-02-01 10:43:21 - Loaded events
2023-02-01 10:43:21 - Loaded player list
2023-02-01 10:43:21 - Updated console commands
2023-02-01 10:43:21 - Loaded Buffs
2023-02-01 10:43:21 - Loaded Entities
2023-02-01 10:43:21 - Display player list
2023-02-01 10:43:21 - Created Discord bot object
2023-02-01 10:43:21 - ************************** RAT Startup, Completed **************************
2023-02-01 10:43:40 - Error disconnecting telnet session.
2023-02-01 10:43:40 - ----------------------------------
Current Time: 2/1/2023 10:43:40 AM
Thrown by: Boolean get_Connected()
Method: VB$StateMachine_30_disconnect.LogException
Message: Object reference not set to an instance of an object.
Stack Trace:
at System.Net.Sockets.TcpClient.get_Connected()
at RAT3.telnet.VB$StateMachine_30_disconnect.MoveNext()
----------------------------------

2023-02-01 10:43:41 - ----------------------------------
Current Time: 2/1/2023 10:43:41 AM
Thrown by: Boolean get_Connected()
Method: telnet.LogException
Message: Object reference not set to an instance of an object.
Stack Trace:
at System.Net.Sockets.TcpClient.get_Connected()
at RAT3.telnet.get_IsConnected()
----------------------------------

2023-02-01 10:43:41 - ----------------------------------
Current Time: 2/1/2023 10:43:41 AM
Thrown by: Boolean get_Connected()
Method: telnet.LogException
Message: Object reference not set to an instance of an object.
Stack Trace:
at System.Net.Sockets.TcpClient.get_Connected()
at RAT3.telnet.get_IsConnected()
----------------------------------

And here is the server Log:


2023-02-01T10:48:12 1273.191 INF Telnet connection from: 127.0.0.1:58674
2023-02-01T10:48:12 1273.191 INF Started thread TelnetClient_127.0.0.1:58674
2023-02-01T10:48:12 1273.204 ERR IOException in ReadLine for TelnetClient_127.0.0.1:58579: Unable to write data to the transport connection: An existing connection was forcibly closed by the remote host.
2023-02-01T10:48:12 1273.204 EXC Unable to write data to the transport connection: An existing connection was forcibly closed by the remote host.
2023-02-01T10:48:12 1273.217 ERR IOException in ReadLine for TelnetClient_127.0.0.1:58674: Unable to write data to the transport connection: An existing connection was forcibly closed by the remote host.
2023-02-01T10:48:12 1273.217 EXC Unable to write data to the transport connection: An existing connection was forcibly closed by the remote host.
2023-02-01T10:48:12 1273.229 ERR Exception in thread TelnetClient_127.0.0.1:58579:
2023-02-01T10:48:12 1273.230 EXC The operation is not allowed on non-connected sockets.
2023-02-01T10:48:12 1273.230 INF Exited thread TelnetClient_127.0.0.1:58579
2023-02-01T10:48:12 1273.242 ERR Exception in thread TelnetClient_127.0.0.1:58674:
2023-02-01T10:48:12 1273.243 EXC The operation is not allowed on non-connected sockets.
2023-02-01T10:48:12 1273.243 INF Exited thread TelnetClient_127.0.0.1:58674

 

[Trekkan]

That looks like a corrupt DB. Usually that happens from a power outage or closing down RAT incorrectly (stopping the process directly, etc). In order to fix it, do the following.


Corrupt DB
Follow these steps to fix your corrupt data base file.
This will delete all your information from RAT.
Backing up your RAT DB file regularly is advised.

RAT NEEDS TO BE CLOSED TO DO THIS
Step 1
Close RAT
Step 2
Go to %appdata%/nomadsoft/rat3
Step 3
Copy the *.db file somewhere else
Step 4
If there is a .SHM or .WAL file, delete them

Run RAT and see if the problem is resolved, if not, proceed to Step 5
Step 5
Delete the *.db file
Step 6
In Add/remove programs, run the repair on RAT and a new DB file will be created
Step 7
Reconfigure RAT