How to Troubleshoot the ASP Server Monitor
This monitor is an NT Performance Counter monitor. It is hard-coded to look for the "Active Server Pages" Performance Object.
How to Troubleshoot
1) Since this is a perfex-based monitor all the basic Perfex troubleshooting steps apply:
a) Do you have permissions to access the remote machine?
b) Is the "Active Server Pages" Performance Object available in perfmon?
i. If not this has to be enabled. Use exctrlst.exe from Microsoft to enable it if possible
ii.Are other Performance Objects available? If not maybe the Registry Service needs to be restarted.
2) While logged in to the SiteScope server as the same user that the SiteScope service is running as, open a command prompt and change to the SiteScope ools directory. SiteScope uses a program called perfex to connect to remote Windows Servers. You can run perfex from the command line to see what SiteScope is getting returned.
The specific perfex command to check whether the counters SiteScope needs are available is:
perfex remotemachine -u username -p password -o "Active Server Pages"
You may potentially run into problems with remotes due to network issues (if a firewall is blocking ports 137-139 for example — SiteScope uses Netbios) or server configuration problems (SiteScope, and perfmon, rely on certain services to be running on the remote like Remote Registry Service, RPC Service, Server, and TCP Netbios helper) or permissions issues.
Sometimes (very rarely), you may need to map a drive to the remote server using that same admin user SiteScope is trying to connect as before you can connect via PerfMon.
If the counters the you are looking for aren’t available to PerfMon then they won’t be available to SiteScope.
The important thing is that you should be able to run perfex and get a list of counters back for a particular object. If you don’t then there’s a problem. Perfex may return an error that will give you a good idea where to start:
ERROR: RegConnectRegistry, Unknown error (53)
Perfex – Add Connection Failed
The network path was not found.
It’s also useful to know that when you see an "Unknown error (x)" in relation to perfex or an NT Remote that "x" usually is an actual Windows error code. If you run the command below from a command promt:
net helpmsg x
then you should receive some information back. From that you can usually search Microsoft TechNet for the exact cause and resolution for the error message that Windows is generating.
If you receive only three lines back from your perfex run, like:
then you’ve connected to the machine but there’s likely a problem with the object you’re trying to retrieve info back on. For example, a good perfex run against the Active Server Pages object begins like this
D:SiteScope ools>perfex emoteserver -u username -p password -o "Active Server Pages"
object: Active Server Pages 5530
Debugging Requests: 0 PERF_COUNTER_RAWCOUNT
Errors During Script Runtime: 0 PERF_COUNTER_RAWCOUNT
Errors From ASP Preprocessor: 0 PERF_COUNTER_RAWCOUNT
Errors From Script Compilers: 0 PERF_COUNTER_RAWCOUNT
Errors/Sec: 0 /second PERF_COUNTER_COUNTER
Request Bytes In Total: 0 PERF_COUNTER_RAWCOUNT
Request Bytes Out Total: 0 PERF_COUNTER_RAWCOUNT
Request Execution Time: 0 PERF_COUNTER_RAWCOUNT
Request Wait Time: 0 PERF_COUNTER_RAWCOUNT
Requests Disconnected: 0 PERF_COUNTER_RAWCOUNT
Requests Executing: 0 PERF_COUNTER_RAWCOUNT
Requests Failed Total: 0 PERF_COUNTER_RAWCOUNT
Requests Not Authorized: 0 PERF_COUNTER_RAWCOUNT
Requests Not Found: 0 PERF_COUNTER_RAWCOUNT
Requests Queued: 0 PERF_COUNTER_RAWCOUNT
Requests Rejected: 0 PERF_COUNTER_RAWCOUNT
Requests Succeeded: 0 PERF_COUNTER_RAWCOUNT
Requests Timed Out: 0 PERF_COUNTER_RAWCOUNT
Requests Total: 0 PERF_COUNTER_RAWCOUNT
Requests/Sec: 0 /second PERF_COUNTER_COUNTER
Script Engines Cached: 0 PERF_COUNTER_RAWCOUNT
Session Duration: 0 PERF_COUNTER_RAWCOUNT
Sessions Current: 0 PERF_COUNTER_RAWCOUNT
Sessions Timed Out: 0 PERF_COUNTER_RAWCOUNT
Sessions Total: 0 PERF_COUNTER_RAWCOUNT
Templates Cached: 0 PERF_COUNTER_RAWCOUNT
Template Cache Hit Rate: 0 % PERF_RAW_FRACTION
empty: 0 PERF_RAW_BASE
Template Notifications: 0 PERF_COUNTER_RAWCOUNT
Transactions Aborted: 0 PERF_COUNTER_RAWCOUNT
Transactions Committed: 0 PERF_COUNTER_RAWCOUNT
Transactions Pending: 0 PERF_COUNTER_RAWCOUNT
Transactions Total: 0 PERF_COUNTER_RAWCOUNT
Transactions/Sec: 0 /second PERF_COUNTER_COUNTER
There is a property called _counterObjectsASPMonitor that can be set in the master.config or even the group level that should allow the default Performance object to be modified from the default.
The default instance of Active Server Pages that the monitor checks for is "SINGLE" – if there is one with a different instance then that can be changed using the _counterInstanceASPMonitor property.