Spam Filter ISP Support Forum

  New Posts New Posts RSS Feed - Running spamfilter as service
  FAQ FAQ  Forum Search   Register Register  Login Login

Running spamfilter as service

 Post Reply Post Reply
Author
Jakob Nielsen View Drop Down
Guest Group
Guest Group
Post Options Post Options   Thanks (0) Thanks(0)   Quote Jakob Nielsen Quote  Post ReplyReply Direct Link To This Post Topic: Running spamfilter as service
    Posted: 09 August 2005 at 3:51pm
Are it not possible to use the GUI interface, when the spamfilter running as a service. if i trying to start the exe fil, i get a error message "the ports it already in use"

but if i stop the service before i start the exe files they is no problems

Back to Top
Marcus View Drop Down
Newbie
Newbie


Joined: 25 July 2005
Location: United States
Status: Offline
Points: 21
Post Options Post Options   Thanks (0) Thanks(0)   Quote Marcus Quote  Post ReplyReply Direct Link To This Post Posted: 09 August 2005 at 4:58pm

Go to "properties" of the spamfilter service, "Log On" tab.

Check box "allow service to interact with desktop"

Click OK

Restart service

Back to Top
LogSat View Drop Down
Admin Group
Admin Group
Avatar

Joined: 25 January 2005
Location: United States
Status: Offline
Points: 4106
Post Options Post Options   Thanks (0) Thanks(0)   Quote LogSat Quote  Post ReplyReply Direct Link To This Post Posted: 10 August 2005 at 9:58pm
Jakob,

SpamFilter ISP can be run in two different ways. The first is as a Windows service (the most common - SpamFilterSvc.exe), the second is as a standalone application using SpamFilter.exe. The latter is mostly used for troubleshooting, even though several users have asked to be able to run SpamFilter in non-service mode.

If you are already running SpamFilter as a service, subsequently running the standalone application (SpamFilter.exe) will open a new instance of SpamFilter, it will not be the GUI for your service. Since it's using the same settings as your service, it is trying to listen on the same IPs used by the service, and since it can't it will display the "could not bind socket error".

Please note that the service does show display a GUI (launched from an icon in the tray bar), but if accessing a Windows 2000 server remotely using Terminal Services will not be able to display the GUI. This is because Terminal Services in Win2K is not able to display the server's physical console. Looking at the physical server's screen, or using a product like PCAnywhere, DameWare, VNC etc that display the actual screen will reveal the console. Windows 2003 server's terminal services does not have this limitation.
Roberto Franceschetti

LogSat Software

Spam Filter ISP
Back to Top
Jakob Nielsen View Drop Down
Guest Group
Guest Group
Post Options Post Options   Thanks (0) Thanks(0)   Quote Jakob Nielsen Quote  Post ReplyReply Direct Link To This Post Posted: 11 August 2005 at 4:49am

Thank you.

 

 

 

Back to Top
Greg View Drop Down
Guest Group
Guest Group
Post Options Post Options   Thanks (0) Thanks(0)   Quote Greg Quote  Post ReplyReply Direct Link To This Post Posted: 12 August 2005 at 3:59pm
I am running SpamFilter as a service on Windows 2003 using remote desktop to connect and it does not display an Icon in the system tray. The service is also set to "allow service to interact with desktop", but I still get the same error message when trying to open the GUI. How can I check stats when the program is run as a service?
Back to Top
LogSat View Drop Down
Admin Group
Admin Group
Avatar

Joined: 25 January 2005
Location: United States
Status: Offline
Points: 4106
Post Options Post Options   Thanks (0) Thanks(0)   Quote LogSat Quote  Post ReplyReply Direct Link To This Post Posted: 12 August 2005 at 5:29pm
Greg,

Please note that in Windows 2000 Server, Terminal Services does not provide access to the "real" Console 0 (console 0 is the primary physical display), but rather it displays a "virtual" console that does not allow to display, among other things, the SpamFilter GUI.

Microsoft fixed this in Windows 2003, where Terminal Services instead does allow RDP to connect on the Console 0. Some Terminal Services clients have a checkbox in their settings to connect to the console. In the XP Remote Desktop, Microsoft (in)conveniently decided to not make it available. You'll need to invoke Remote Desktop from the command line as follows to enable this:

mstsc -console

Roberto Franceschetti

LogSat Software

Spam Filter ISP
Back to Top
Greg View Drop Down
Guest Group
Guest Group
Post Options Post Options   Thanks (0) Thanks(0)   Quote Greg Quote  Post ReplyReply Direct Link To This Post Posted: 16 August 2005 at 2:01pm

That worked perfectly! Thanks!

P.S... I have been very impressed with capabilities of SpamFilter. Keep up the excellent work!!

Back to Top
 Post Reply Post Reply
  Share Topic   

Forum Jump Forum Permissions View Drop Down



This page was generated in 0.188 seconds.