Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Rule Creation
Web Site and Web Service Monitoring
Issue: When connecting or saving to the Management Server the following error occurs:
The server, while acting as a gateway or proxy to fulfill the request, received an invalid response from the upstream server it accessed.
Cause: The Configuration Wizard uses HTTP and Background Intelligent Transfer Service (BITS) to upload Web Service Monitoring configuration files to the Management Server. The error indicates the WSS MP Configuration Wizard was unable to connect to http://%ManagmentServer%/Microsoft Web Service Monitoring 2005/.
Workaround: Correct your system-wide proxy settings to guarantee that the machine you are running the WSS MP Configuration Wizard from can establish an HTTP connection with the Management Server.
Issue: When saving a new Request Sequence created by capturing Web site navigation using Internet Explorer, the following error occurs:
Saving Error - Unknown Error
An unknown error occurred while trying to connect to the configured BITS server.
Cause: Internet Explorer is configured to use a proxy server for all addresses, including local servers. The Background Intelligent Transfer Service (BITS) is not able to save the Request Sequence in this configuration.
Workaround: In your Internet Explorer Local Area Network (LAN) settings dialog box, enable the Bypass proxy server for local addresses option.
Issue: When creating a new Request Sequence by capturing Web site navigation using Internet Explorer, requests that use NTLM authentication and a proxy server result in DNS errors.
Cause: Internet Explorer is configured to automatically detect proxy server settings. In some cases, the proxy server is not forwarding user credentials properly.
Workaround: In your Internet Explorer Local Area Network (LAN) settings dialog box, disable the Automatically detect settings option. The settings in the Proxy server area should be manually configured.
Issue: When using Terminal Services on a Windows 2000 computer, saving a new Request Sequence results in the following error:
The operation being requested was not performed because the user has not logged on to the network. The specified service does not exist.
Cause: The Background Intelligent Transfer Service (BITS) 1.5 does not support Terminal Services on Windows 2000.
Workaround: Log on to the computer directly, or use Microsoft NetMeeting instead of Terminal Services.
Issue: Saving Request Sequence Groups containing a very large number of requests might result in the following error:
The job is too large for the server to accept. This job might exceed a job size limit set by the server administrator. Reduce the size of the job, and then try again.
Cause: The Background Intelligent Transfer Service (BITS) has a configurable file size limit. The default value is 100 MB.
Workaround: Increase the maximum file size, or reduce the number of requests in the group.
Issue: Modifications to Request Sequence configuration are not propagated to targeted agents immediately after update.
Cause: By default, MOM Management Server checks for rule changes every 5 minutes. Therefore, changes made by using the WSS MP Configuration Wizard might not be detected by the MOM Management Server for up to 5 minutes. Furthermore, these changes must then be delivered to MOM agents associated with the affected rule group before agent monitoring reflects the rule changes.
Workaround: MOM Management Servers can be forced to process rule changes on demand by performing the following steps:
Open the MOM 2005 Administrator Console, and connect to the Management Server.
Right-click on the Management Packs node, and select Commit Configuration Change.
Issue: When you modify the properties of a Request Sequence or remove it from the Request Sequence Group, it can be difficult to identify the correct Request Sequence in cases where more than one Request Sequence has the same name.
Cause: As with MOM rules, duplicate Request Sequence names are allowed. MOM identifies rules using their unique ID values.
Workaround: Request Sequences that belong to the same group should be assigned unique names to avoid confusion.
Issue: Session state cookies must be manually removed from request headers, especially those created by recording a Web browser session. If the session cookie is not removed, a second session cookie might be set during monitoring. The presence of more than one session cookie in a request can have unpredictable results.
Cause: The WSS MP is unable to automatically identify and remove session headers.
Workaround: After recording one or more requests, open the Request Properties page for each request, select the HTTP headers tab, and manually delete any session cookies from the values saved in the HTTP header named Cookie.
Issue: Memory use can increase significantly while loading large Request Sequences. In some cases, a MOM rule will restart the MOMHost.exe process and raise an alert.
Cause: When memory use exceeds the amount specified by the following registry entry, the MOMHost.exe process is restarted:
HKLM\SOFTWARE\Mission Critical Software\OnePoint\MaxManageCodeHostPrivateBytes
Workaround: Increment the value of the registry entry by about 50 MB until the problem is resolved.
Issue: The MP Authoring Wizard throws an unhandled UnauthorizedAccessException exception while connecting to the Management Server.
Cause: The user running the wizard does not have sufficient privileges to create or modify MOM rules on this Management Server.
Workaround: Add the user to the local MOM Authors or MOM Administrators user group.
Issue: An alert is continuously generated by the rule “Microsoft Operations Manager\Operations Manager 2005\Agent\File transfer response - Could not create, resume or complete a BITS job”, and the description of the alert refers to “http://%ManagementServer%/Microsoft Web Service Monitoring 2005 Downloads/...”.
Cause: The Web Service Monitoring Engine relies on a MOM File Transfer Response to download configuration files from the Management Server. The error indicates the MOM agent was unable to download the named configuration file using HTTP.
Workaround: Make sure that the rule used to download the Request Sequence to the agent is properly configured by performing the following steps:
Open the MOM 2005 Administrator Console, and connect to the Management Server.
Open the Management Packs\Rule Groups\Microsoft Web Service Monitoring 2005 node.
Select the Event Rules node.
Open properties for the Download Request Sequence Data File rule.
Select the Responses tab.
Edit the response named Download from http://... .
Make sure that the server name of the BITS server within the URL is properly configured and resolves to the MOM 2005 Management Server.
Issue: Web servers with invalid SSL server certificates are not supported. Requests that use the HTTPS protocol—and for which the SSL certificate is expired, has an invalid hostname, or does not originate from a trusted certificate authority—will fail, and the ResponseTime and DaysToExpiration values for the response will be considered zero (0).
Workaround: Verify that the server certificate is valid. If the certificate is invalid, performance metrics collected during the test will also be invalid and should not be used in reports.
Issue: The WSS MP creates NT Event log entries containing URL-encoded characters that are not displayed properly.
Cause: Instances of “%n”, where n is any number, are incorrectly treated as insertion string parameters by the NT Event Log Viewer.
Workaround: Use the MOM Operator console to inspect the corresponding MOM events. The Operator console is able to display the encoded characters.
Issue: Response times for a specific URL vary more than expected. In particular, the first request for the URL produces an unusually high response time.
Cause: The WSS MP agent configuration components are managed .NET Framework–based applications. The just-in-time (JIT) compilation of Intermediate Language (IL) code to native code, which is typical of most .NET-based applications, causes a slight delay the first time the code in the application is called. This delay increases the response time for the first request.
Note that if you are monitoring an ASP.NET Web page or Web service, it can experience JIT-related delays the first time it is requested and compiled to native code, which will further increase the response time measured by the WSS MP.
Workaround: Use response time and DNS resolution threshold values that are flexible enough to accommodate any JIT compilation delays in the WSS MP components and in the application you are monitoring.
Issue: When monitoring the response time for a request and the content it references, you might get false error and warning events.
Cause: The response time for the main request is evaluated first. If the main request does not match the monitoring criteria, the total response time is calculated and evaluated in the expected manner. False events can happen when you are monitoring for response times that are less than a specified value. In situations where the main request matches the error or warning criteria, an event is immediately created and further processing does not occur.
Workaround: You should choose a value for the minimum response time based on the response time for the main request.
Issue: *The WSS MP does not support ASP.NET pages that use message authentication codes (MAC) for securing their view state. *
Cause: MAC verification relies on session-specific identifiers that are embedded in the response page HTML.
Workaround: You can disable MAC verification by setting the System.Web.UI.Page.EnableViewStateMac property to false in either the ASP.NET code or in a configuration file. Note that disabling MAC verification will increase security risks for your application. If the EnableViewStateMac property is set to false, the server cannot determine the validity of any state updates it receives for the server controls hosted by the ASP.NET page.