>From what you're saying I can only suppose that what happens is:
        service is running (without the correct configuration!)
        you start the app (that's a 2nd instance of SA that is running!)
        configure it
        close the app
        you restart the app (again a 2nd instance of SA) and the app loads
the new settings
        all works fine
        you quit the app, and only have the service running.
        BUT the service loaded it's settings at startup of the service, so
before you did the configuration changes.

-> restart the service and test again.

Also if you want to configure SA while running as service, the service
should be running as system account with desktop interaction and on the
system running SA (directly on the system) you will see within the system
tray an icon of SA that can be used to "call" the interface and to configure
it via that. 


Dirk.
Don't forget to vote for Servers Alive in the annual Sunbelt Target Awards
http://www.sunbelt-software.com/targetawards/

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf
Of Ben Helfer
Sent: Tuesday, April 13, 2004 3:50 AM
To: [EMAIL PROTECTED]
Subject: [SA-list] SAWeb

I've installed SA 4.1 and SAWeb 1.73 on Windows 2000 server using IIS, all 
on the same system. I configured SA 4.1 with some entries, configured it to 
run as a service, turned on logging, closed the app and confirmed monitoring

entries being written to the log file. I opened SA 4.1 again, configured 
SAWeb, tested it and all seemed to be working properly. At that point I 
exited SA 4.1, fired up another browser to access SAWeb and got the 
following message:

Error: Cannot connect to server 192.168.0.241:4301.
This could mean that Servers Alive is busy with another task.
Please try again, or change your configuration to correct the problem.

Found that I continue to get this message until I open the SA 4.1 app. I 
don't make any configuration changes, just open the app! I've tried 
different Telnet security settings, doesn't make a difference, if SA 4.1 
isn't open I can't telnet to this server/port and I get the above error 
message when I try to access SAWeb. Am I overlooking something simple?

Ben Helfer

_________________________________________________________________
Is your PC infected? Get a FREE online computer virus scan from McAfeeR 
Security. http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963

---
[This E-mail scanned for viruses by Declude Virus]

To unsubscribe from a list, send a mail message to [EMAIL PROTECTED]
With the following in the body of the message:
   unsubscribe SAlive



---
[This E-mail scanned for viruses by Declude Virus]

To unsubscribe from a list, send a mail message to [EMAIL PROTECTED]
With the following in the body of the message:
   unsubscribe SAlive

Reply via email to