Troubleshoot miscellaneous application dependency issues
This section contains additional troubleshooting tips for the Application Dependencies feature.
The following table describes where to check to ensure Application Dependencies services are functioning. See Application Dependencies log files for log file locations.
|Description||Group Status||Expected results|
|Check nodes that will be polled||Collector Service log||See polling plans for nodes with active applications.|
|Check planned jobs||
Polling Plan log
See jobs created for node active applications.
|Check that a publish-subscribe pattern (pubsub) succeeded||
Business Service log
See the cache that was created, along with inventory messages received for node with active applications.
A networking Windows OS subsystem is implemented as a kernel-mode device driver called the HTTP protocol stack — also called HTTP.sys. This driver listens for HTTP requests from the network, passes requests to IIS or other applications for processing, and returns processed responses to client applications.
Detecting HTTP connections is not the main goal of the Application Dependencies feature. Typically, communication between clients and HTTP servers is not permanent, and Application Dependency polling occurs relatively infrequently so it will not detect short HTTP connections.
HTTP connections may appear in the Application Connections widget in the following circumstances:
- Random capture of common HTTP(s) occurred.
- Orion Server communication was captured during Orion server polling or via user action in the Orion Web Console that initiated a poll.
- HTTP communication persisted for a long time, perhaps due to tunneling of another kind of TCP communication over HTTP(s).
Monitor Windows Communication Foundation (WCF) communication
The Windows Communication Foundation (WCF) application uses the Net.TCP Port Sharing service to share ports across multiple processes to reduce the number of ports that need to be open on a firewall. That service listens on port 17777, which is the same port where several Orion Platform services listen so they can forward communication to the Orion Platform through an internal, non-TCP communication channel.