Using Netstart and Netstop Commands for SiteScope on Windows/Solaris and Linux OS

Windows:

You can also start and stop the SiteScope service by using the netstart and
netstop commands.

To start the SiteScope service using netstart:
1 Open a command line window on the server where SiteScope is installed.
2 Run the netstart utility using the following syntax:
net start SiteScope

To stop the SiteScope service using netstop:
1 Open a command line window on the server where SiteScope is running.
2 Run the netstop utility using the following syntax:
net stop SiteScope

Solaris/Linux:

To start the SiteScope process on Solaris and Linux:
1 Open a terminal window on the server where SiteScope is installed.
2 Run the start command shell script using the following syntax:
/SiteScope/start

To stop the SiteScope process on Solaris and Linux:
1 Open a terminal window on the server where SiteScope is running.
2 Run the stop command shell script using the following syntax:
/SiteScope/stop

General ports required for making connection with Sitescope tool

Below is the prerequisite we require for the new servers in order to establish the connection with Sitescope tool.

WMI/NETBIOS	135-139
Sitescope Web server	8080
FTP Monitor	21
Mail Monitor	25 (SMTP), 110 (POP3), 143 (IMAP) News
Monitor	119
Ping Monitor	packets
SNMP Monitor	161 (UDP)
URL Monitor	80,443
Remote Windows Monitoring	139
Email Alert	25
Post Alert	80,443
SNMP Trap Alert	162 (UDP)
Remote UNIX ssh	22
Remote UNIX Telnet	23
Remote UNIX rlogin	513

Sitescope Monitor Output Error Codes

Below are some of the error code which we get as a monitor run output on Sitescope dashboard:

• URLPermissionDenied = -982               "Permission denied"
• SOAPFaultError = -983 
• XMLElementNotFoundError = -986     "XML element not found"
• XMLFormatError = -987                      "XML format error"
• XMLElementMatchError = -988           "XML element value mismatch"
• URLContentErrorFound = -989             "content error found"
• URLContentElementMissing = -990       "content element missing"
• URLNoStatusError = -991                    "no status in reply from server"
• MonitorSpecificError = -992; 
• URLNoRouteToHostError = -993        "unable to reach server"
• DLLCrashedError = -994                     "internal error in WinInet library"
• URLContentChangedError = -995        "content changed"
• URLTimeoutError = -996                     "timed out reading"
• URLBadHostNameError = -997           "unknown host name"
• URLNoConnectionError = -998           "unable to connect to server"
• URLContentMatchError = -999            "content match error"
• URLUnknownError = -1000
• DNSIPAddressMismatch = -1001        "ip address does not match"
• URLRemoteMonitoringError = -1002    "unable to connect to remote monitoring server"
• URLConnectionClosedError = -1003    "connection reset"