It appears that monitoring is stopped when the server is not logged in. I have installed hostmonitor and web service as a service and all work fine when logged on. When logging off though, no alerts are processed and the web site cannot be accessed.
How do I fix this problem?
Web service stops working if not logged on
Started on evaluation copy then entered the licences so it is a registered version.
The account in the services page is currently set to the Domain admin account but have tried under local account too.
On the day of installation, there is an error message but this has not repeated since:
Event Type: Error
Event Source: HMWebService
Event Category: None
Event ID: 1002
Date: 27/09/2005
Time: 11:56:48 a.m.
User: N/A
Computer: PINFRA1W
Description:
The description for Event ID ( 1002 ) in Source ( HMWebService ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: Cannot open socket (Port: 80, Interface: 0.0.0.0). Probably port is in use..
The web service doesn't work unless you are logged on and it is running as a service.
The account in the services page is currently set to the Domain admin account but have tried under local account too.
On the day of installation, there is an error message but this has not repeated since:
Event Type: Error
Event Source: HMWebService
Event Category: None
Event ID: 1002
Date: 27/09/2005
Time: 11:56:48 a.m.
User: N/A
Computer: PINFRA1W
Description:
The description for Event ID ( 1002 ) in Source ( HMWebService ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: Cannot open socket (Port: 80, Interface: 0.0.0.0). Probably port is in use..
The web service doesn't work unless you are logged on and it is running as a service.
It means Web Service doesn't work at all because some other application uses port #80. May be its another web server (IIS)? Or may be you have started Web Service in service mode while it was already started as application.Cannot open socket (Port: 80, Interface: 0.0.0.0). Probably port is in use..
On the other hand if you have restarted Web Service after 27/09/2005 and there are no new message, it means Web Service works. And you cannot access it? Web browser does not ask for password? It means something block access. E.g. personal firewall or antivirus monitor. Do you have installed such software?
BTW Windows XP and Windows 2003 has built-in firewall that may prevent access.
Strange that you can access web service when its started in application mode...
Regards
Alex
Hi Alex,
I had issues at first with the web service but then moved to port 81 and it is working fine. But only when logged on to the server. The minute I log off hostmonitor stops alerting and web is not available. If I'm logged on everything works perfectly.
Firewalls have been turned off and we are using Symantec Corporate edition. Surely if this was an issue we would get it logged on as well. I'm thinking something needs to be done to allow work interactively. Almost like the service is not running?
Thanks
I had issues at first with the web service but then moved to port 81 and it is working fine. But only when logged on to the server. The minute I log off hostmonitor stops alerting and web is not available. If I'm logged on everything works perfectly.
Firewalls have been turned off and we are using Symantec Corporate edition. Surely if this was an issue we would get it logged on as well. I'm thinking something needs to be done to allow work interactively. Almost like the service is not running?
Thanks