Microsoft KB Archive/830229

= The HTTP monitor for Fully Qualified Domain Name (FQDN) in hosts file fails if you do not use a proxy server entry =

Article ID: 830229

Article Last Modified on 5/27/2005

-

APPLIES TO


 * Microsoft Application Center 2000 Service Pack 2

-



SYMPTOMS
When you specify a Fully Qualified Domain Name (FQDN) that is defined in your hosts file as the URL that is monitored in an HTTP data collector, the HTTP data collector displays an http status code of 400 on the statistics tab. You also see the following error message on the statistics tab:

cannot find server or DNS error.

The data collector will display a status of critical when it is not expected.

If the HTTP data collector is configured to log errors in the Websitefailures.log file, you may see an entry in Websitefailures.log that is similar to the following:

System: MYSTYSTEM

Time: 2/17/2004 4:12:08 PM

Name: http://mysite.bob

URL: http://mysite.bob

Status Code: 400

Status Text:

Error Description: Error: Cannot find server or DNS Error

Response Time (msec): 0

WMI Status: 0

Text Response (HTTP body):



CAUSE
This problem occurs because of a change in behavior in Application Center 2000 Service Pack 2.



RESOLUTION
To resolve this problem, specify localhost on port 80 as the proxy server for this HTTP data collector:
 * 1) In the Application Center 2000 console, right-click the data collector, and then click Properties.
 * 2) Click the Details tab.
 * 3) Select the Proxy server check box.
 * 4) In the Address box, type localhost.
 * 5) In the Port box, type 80.



STATUS
This behavior is by design.

Additional query words: health monitor ac2k fqdn dns

Keywords: kbprb KB830229

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.