IMPORTANT ANNOUNCEMENT: On May 6, 2024, Carbon Black User eXchange (UeX) and Case Management will move to a new platform!
The Community will be in read-only mode starting April 19th, 7:00 AM PDT. Check out the blog post!
You will still be able to use the case portal to create and interact with your support cases until the transition, view more information here!

HTTP 503 is observed when accessing the Bit9 Console

HTTP 503 is observed when accessing the Bit9 Console




Attempting to connect to the Bit9 console but service is unavailable.


HTTP 503 error after logging in. Restarting IIS works for a short time. Usually when updating agents


Agent upgrades are consuming IIS Application Pool memory limits. Solution 305 provides best practices for agent upgrades


1) Open IIS Manager.

2) In the Connections window, expand the server and select Application Pools.

3) On the Application Pools page, select the DefaultAppPool, and then click Recycling in the Actions window.

4) Select Private memory usage (in KB), allocate between 512000kb and 1gb of memory to the application pool before it recycles.

5) Restart the server

Labels (1)
Was this article helpful? Yes No
No ratings
Article Information
Creation Date: