Why does the "Error: (code 99) An internal error occurred message" display on the Blue Coat Director?

Solutions ID:    KB4253
Version:    5.0
Status:    Published
Published date:    01/17/2011
Updated:    04/06/2012

Problem Description

Some Command Line interface ( CLI) commands fail when used on the Director, and the UI displays the error "Error:  (code 99) An internal error occurred."

This message is also logged in the var/log/messages file on the Director.

Internal Error - device communication interrupted policy reset % Internal Error - device communication interrupted ;;END MANUAL SETTINGS % Internal Error - device communication interrupted

  1.  We see this message on the target SG.

| Output for device ""
Error:  Internal Error - device communication interrupted
policy reset
Error:  Internal Error - device communication interrupted
Error:  Internal Error - device communication interrupted
Overlay execution complete for device ""


These errors manifest on these versions:

Version of Director: SG-ME #50387 2010.09.

SG version and Model: SG 210 SGOS

Steps to duplicate this error:

  1. Open a Web browser and access the Director Management Console.  You must enter valid credentials for access.
  2. Click the Configure tab.
  3. Choose Overlays from Configuration Library drop down on the right.
  4. Click New then choose New Overlay.
  5. Name the overlay.
  6. From the Add To Overlay menu, choose Using CLI.
  7. Cut and paste the following text in to the new window that displays:

    delete Echo
    import Echo
  8. Click OK to close the open dialogs and save your changes.
  9. Highlight a test ProxySG such as  <TEST-SG>, and execute the overlay you just created.
    1. Click Execute.
    2. Click Yes when prompted to execute overlay <name you chose in step 5> on device ‘<TEST-SG>.

Workaround: While Bluecoat works on a solution to this problem, please execute these commands directly on the SSH interface of the ProxySG.  If you see this problem, please log a Service Request and quote this article. 

NOTE1:  One reason for this symptom is the "policy reset" CLI command is expecting user input of a 'yes/no'. which Director does not provide.

NOTE2: For a similiar symptom, using cipher commands, see KB4250

NOTE3: For details on what we will ask for,  when you log a service request, see FAQ1176

Rate this Page

Please take a moment to complete this form to help us better serve you.

Did this document help answer your question?
If you are finished providing feedback, please click the RATE CONTENT button. Otherwise, please add more detail in the following text box and then click RATE CONTENT.

Your response will be used to improve our document content.

Ask a Question