Home  Administration > Monitor Administration > SiteScope Data Collector Configuration > Managing SiteScope > SiteScope Preferences > Windows Remote Preferences > Technical Notes on Remote Windows Monitoring



Technical Notes on Remote Windows Monitoring

The following is additional information relating to the setup of and troubleshooting SiteScope monitoring of remote Win NT and Win 2000 servers.

A general troubleshooting step in working with remote NT servers with SiteScope for Windows NT/2000 is to connect to remote machine using Perfmon. If a connection can not be made using this tool there is likely a problem involving the user access permissions that have been granted to the SiteScope account on the remote server. SiteScope requires certain administrative permissions to be able to monitor server statistics.

For security reasons, SiteScope may not be allowed to use the permissions of a full administrator account. SiteScope can be granted restricted monitoring access by editing certain Windows Registry Keys. See the Enabling Non-Admin Users to Remotely Monitor with PERFMON support note on the Microsoft support site for more information.

When you need to monitor a server which is a stand-alone server or not part of a domain already visible to the SiteScope server, try entering the machine name followed by a slash and then the login name in the Login box. For example, loneserver\sitescope.

Some problems have been found when trying to monitor Win 2000 servers from SiteScope running on Win NT4. In many cases the problem involves incompatibility of the DLL's used by the operating system to communicate between the servers.

Troubleshooting Windows Event Log Access on Remote Windows Servers

Problem
When viewing Remote Windows event logs or getting alerts relating to monitoring a remote Windows machine, you see:
The description for Event ID ( XXXX ) in Source ( XXXX ) could not be found. It contains the following insertion string(s):
The operation has completed successfully.

Cause:
When you view the event log on a computer from a remote computer, if the required registry keys (and referenced files) are not present on the remote computer, SiteScope is unable to format the data; hence it displays the data in a generic format.

Resolution:
The required registry entries and DLL files must be copied to the remote computer on which the event viewer application is being run. Follow these steps to get the remote registry entries and DLL files onto the local SiteScope machine:

  1. Locate on the remote machine which event you are not getting properly in SiteScope by finding the entry in the Event Viewer. Write down the information for the event id, source and description. (For example, Source: MSExchangeSA , Event ID: 5008, Description: The message tracking log file C:\exchsrvr\tracking.log\20020723.log was deleted.)
  2. Open the registry setting: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\EventLog\Application and click the Source (that is, MSExchangeSA)
  3. Click the EventMessageFile and write down the data for where that DLL is located. (that is, C:\EXCHSRVR\bin\madmsg.dll)
  4. Now, you need to locate the DLL on the remote and copy it to the SiteScope machine. You can copy this one of two ways:
    • The Initlog.exe utility, in the "BackOffice Resource Kit, Second Edition," can be used to copy the required registry entries from the Exchange Server computer to the remote computer. This utility can also copy the required DLL files if you are logged on to Windows NT with an account that has Administrator privilege on the Exchange Server computer. (See Microsoft Article Q184719), OR
    • Using ftp, mail, etc to get the file to your local drive.
  5. SiteScope uses the data from the EventMessageFile field in step 3 to determine where to find the DLL on the local machine. So, you must create the same folder structure as in step 3 and place the file in that directory. Otherwise, you can change the directory structure to say c:\Windows\System32 (SiteScope looks in the ADMIN$ by default on the remote machine) and place the DLL In that folder but you MUST have this structure and DLL on BOTH machines. Also, if you do this, you will need to update the registry in step 3 to reflect the directory the DLL is in.

Using Perfex for Troubleshooting Remote Windows Connections

Use the following steps to view the data is being returned when SiteScope is trying to access the remote registry:

  1. Open a command window on the SiteScope server.
  2. Change directory to the <SiteScope install path>\SiteScope\tools directory.
  3. Type in the following command line:
    perfex \\MACHINE -u username -p password -d -elast "Application"
  4. This command will give you the number of entries in your Application log. For example:

    Connected to \\ex-srv as int-ss Next Record: 2369

  5. Usually, you will want to list only the last 10 or 12 events in order to find the one you are looking for. For this example, the command is:
  6. perfex \\MACHINE -u username -p password -d -elog "Application" 2355 | more

    This will produce a lot of output so go through each entry until you find the one you need.

  7. Once you find the record you are looking for, note the Record id for easier searching next time when using the command in Step 3.
  8. This output will tell you what data SiteScope is receiving. For the example given, the following is an example of the data that typically would be returned:

Type: Information
Time: 02:00:24 08/01/102
Source: MSExchangeMTA
ID: 298
Category: 1
Record: 2342
Machine: EX-SRV
FILE=C:\EXCHSRVR\res\mtamsg.dll
REMOTE FILE=
String 835050d is: MTA
Next String 835054d is: OPERATOR
Next String 83505dd is: 34
Next String 835060d is: 0
Next String 835062d is:
File: C:\EXCHSRVR\res\mtamsg.dll
Remote Path:
calling FormatMessage()
Formatted Message 142 bytes long
Raw message is: The most current routing information has been loaded by the MTA, and a text copy was saved in the fileGWART0.MTA. [MTA OPERATOR 34 0] (12) Message: The most current routing information has been loaded by the MTA, and a text copy was saved in the file GWART0.MTA.[MTA OPERATOR 34 0] (12)

The file path is where the remote file is being found. If you copy the DLL to the WINDOWS\SYSTEM,you will see the File and remote file path like this:

Type: Information
Time: 03:15:00 08/01/102
Source: MSExchangeIS Public
ID: 1221
Category: 6
Record: 2350
Machine: EX-SRV
FILE=C:\WINNT\SYSTEM32\mdbmsg.dll
REMOTE FILE=\\ex-srv\ADMIN$\SYSTEM32\mdbmsg.dll
String 835054d is: 0
Next String 835056d is:
File: C:\WINNT\SYSTEM32\mdbmsg.dll
Remote Path: \\ex-srv\ADMIN$\SYSTEM32\mdbmsg.dll
LOADING LIB REMOTE: \\ex-srv\ADMIN$\SYSTEM32\mdbmsg.dllcalling
FormatMessage()Formatted Message 89 bytes long
Raw message is: The database has 0 megabytes of free spaceafter online defragmentation has terminated.Message: The database has 0 megabytes of free space afteronline defragmentation has terminated.
 




Copyright 2006 Mercury Interactive Corporation