Windows: Server will not connect to client

Hello!
New to CasperCG, trying to get a basic setup working.

I’m running the Server 2.4.3 and Client 2.3.1 on Windows 11, and upon starting up the client and it initializing to the server, I get 3 various errors, the first one being “An existing connection was forcibly closed by the remote host”, and none of the functions in the client seem to work

Here’s the log I’m using the default configuration file from the server download.

I would appreciate any help on directions to look in to solve this issue. Thank you!

Several messages in the log relate to attempts to retrieve data about the media list, the template list and the preset data lists. It looks as if you have not started the media scanner application. The media scanner is normally distributed in the same bundle as the main server executable, but is an essential part of the server system. You can also download the scanner task as a stand alone program. The scanner application and server application normally run in the same folder.

The media scanner should be started and running before the server is started. The scanner and the server communicate over localhost.

When the client starts it requests the current media list using an AMCP command. The results returned by the scanner are sent to the client in the AMCP response.

There is a startup batch file that runs the scanner then the server if you do not want to manually start the two applications.

If you have never run the scanner it displays a basic text window with a scrolling list of the files it has detected and indexed into the local database that lives in a sub-folder of the server folder.

I can confirm that I am running the scanner and it appears to be correctly detecting the media.

{"level":30,"time":1741031311865,"pid":73408,"hostname":"HOST","name":"scanner","msg":"Checking for dead media"}
{"level":30,"time":1741031311924,"pid":73408,"hostname":"HOST","name":"scanner","msg":"Finished check for dead media"}
{"level":30,"time":1741031815473,"pid":73408,"hostname":"HOST","name":"scanner","id":"FORBIGGERBLAZES","path":"media\\ForBiggerBlazes.mp4","size":2498125,"mtime":"2025-02-25T17:27:45.621Z","msg":"Scanned"}
{"level":30,"time":1741031815691,"pid":73408,"hostname":"HOST","name":"scanner","id":"ELEPHANTSDREAM","path":"media\\ElephantsDream.mp4","size":169612362,"mtime":"2025-02-25T17:28:00.453Z","msg":"Scanned"}

Would this issue still be related to the communication between the scanner process and the server process?

Yes, it could still be an issue between the server and the scanner processes. For example if another process else is already using port 8000.

I can see from the log that some of the standard client enquires at connection are reporting correct operation, for example asking for the server version and information about the available channels.

For the moment, to assist diagnosis, do not run the client. Just run the scanner then the server. You can then type AMCP commands directly into the server DOS text window confirming the command entry with the return key.

You can check if the media list is returned to the server by entering the command CLS
(or lower case cls). If this does not show your media on the server DOS window there is a scanner to server issue.

You can also check if the server will play your media file using the command

play 1-10 ForBiggerBlazes