Why does TMS report "No HTTP response" for an MXP system? "Force Refresh" Clears the Error, but it Returns Later

Available Languages

Updated:April 23, 2015

Document ID:112580

Bias-Free Language

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.

Introduction

Why does TMS report "No HTTP response" for an MXP system? "Force Refresh" clears the error, but it returns later.

Related Information

Introduction

This article relates to Cisco TelePresence Management Suite.

Q. Why does TMS report "No HTTP response" for an MXP system? "Force Refresh" clears the error, but it returns later.

A. If the status can be cleared with Force Refresh, but returns later, this is a symptom that the TMS Database Scanner service cannot reach this system. Check whether a web proxy that requires authentication is present on the network, as this blocks traffic from the TMS services.