How do I narrow down the ProxyClient component that is causing an issue with a particular application?
When another application causes ProxyClient to stop responding, one of the first and most important things to determine is which component of ProxyClient is causing the issue: Acceleration, WebFilter, or Injection. Usually, only one of these components is the cause of the issue. This document describes a standard path and method of recording results to help you identify that component.
To help ensure a timely resolution of the issue, Blue Coat recommends that you complete each step in this document in the specified order. Although the process can take up to a few hours to complete, it can save several days in the response time for analyzing and solving your particular issue.
Before You Begin
The following table lists the files that you will rename to disable components in this procedure, specifies the components affected, and notes the action you must take after renaming the files. Refer to this table as often as needed while performing the steps in this process.
Component File Names
*Rebooting the workstation is required after changing any of the files having to do with Acceleration. For WebFilter only restarting the ProxyClient Services is necessary.
As you go through this procedure, record the results of your testing. Use the following table as a guide.
This process comprises the following steps:
Note: This process assumes knowledge of ProxyClient Data Collector (DC). For more information on the ProxyClient DC, see the ProxyClient Administration and Deployment Guide.
Complete the table in Recording Your Results and upload it to your SR for this issue.
Before escalating the case, you can do additional troubleshooting to determine the cause of the issue.
Rate this Page
Please take a moment to complete this form to help us better serve you.