Print Page | Close Window

Interface disappearing when running as a service

Printed From: LogSat Software
Category: Spam Filter ISP
Forum Name: Spam Filter ISP Support
Forum Description: General support for Spam Filter ISP
URL: https://www.logsat.com/spamfilter/forums/forum_posts.asp?TID=3588
Printed Date: 27 December 2024 at 11:56pm


Topic: Interface disappearing when running as a service
Posted By: Guests
Subject: Interface disappearing when running as a service
Date Posted: 11 May 2004 at 1:57pm

I have installed v 2.0.1.302 (the latest free version) on my personal machine, which hosts email and web for my personal domain.

In this version, when SpamFilter is created as a service and the service is started, the interface suddenly disappears and is not minimized to the taskbar.  Furthermore, when SpamFilter.exe is re-executed, a duplicate copy is apparently started, as the error message "Could not bind socket. Address and port are already in use" appears.  (Note, at this point, the version numbers do not display on the interface either).

In the previous version I used, v 1.2.0.212, the interface came up automatically upon reboot, and "closing" the interface would minimize it to the clock area of the taskbar.

Any ideas on the nature this problem and how to fix it?

--Clator




Replies:
Posted By: LogSat
Date Posted: 11 May 2004 at 2:03pm

Clator,

The SpamFilter.exe is the standalone, non-service version of SpamFilter. SpamFilterSvc.exe is used when SpamFilter runs as a service. You cannot run them both concurrently, as they will try to use the same settings and listen on the same IPs.

The behavior of the service application (starting on reboot, minimizing in the taskbar) should be the same as in previous versions. Please note that Terminal Services on Windows 2000 servers, as in previous versions, does not allow the display of the service GUI.

Roberto F.
LogSat Software



Posted By: Guests
Date Posted: 11 May 2004 at 3:08pm

Terminal Services must be the problem.  The box has been moved off-site and I'm now using TS to access the box.

Is there any workaround to the TS problem?



Posted By: BillStewart
Date Posted: 11 May 2004 at 4:15pm

If the server is Windows Server 2003, you can use TS to access the server's console using the /console command-line option; e.g. mstsc /console /v:servername. Otherwise, you'll need to install a remote control tool such as VNC.

Regards,

Bill



Posted By: LogSat
Date Posted: 11 May 2004 at 4:46pm

As Bill correctly pointed out, if you use Win2K3 his solution will work. Otherwise, from a similar thread:

=============
Please note that using Windows 2000 you will not be able to Terminal Service in to the server and see the GUI. This is because Terminal Services in Windows 2000 (MS fixed this ini Windows 2003) does not let you have access to the real console. You can use PCAnywhere, McAfee's Remote Desktop, DameWare utilities, or anything else that lets you remote in a server and see the actual screen to do so.
=============

Roberto F.
LogSat Software



Posted By: Guests
Date Posted: 12 May 2004 at 11:43am

Using PCAnywhere after reading this thread and similar threads on the board.  Thanks to all for your help.

--Clator




Print Page | Close Window