"Error 0" Error Message In EMOC When Trying To Create A New VServer Type

(Doc ID 1519090.1)

Last updated on FEBRUARY 01, 2018

Applies to:

Oracle Exalogic Elastic Cloud Software - Version 2.0.1.0.0 to 2.0.1.0.0
Linux x86-64

Symptoms

You have an installation of Exalogic Elastic Cloud Software (EECS) 2.0.1.0.0 that you are running as a virtual configuration, using version 2.0.1.1.0 of the Exalogic Control Stack. When using the web interface of the Enterprise Manager OpsCenter Control(EMOC) to define new vServer Types for use within the Virtual Data Center Cloud, you are experiencing an unexpected error when initiating the "vServer Type Creation Wizard".

There are two ways in which the "vServer Type Creation Wizard" can be invoked:

  1. From the context sensitive menu available from the "MyCloud" object in the tree menu.

    1. In the "Navigation" area, expand the "vDC Management" accordion panel
    2. In the tree navigation area, expand the "vDC's" node in the tree graph
    3. Right click on the "MyCloud" icon
    4. In the context sensitive menu that appears, select "Create vServer Type"

  2. From the "vServerTypes" tab in the main area when the "MyCloud" object is selected in the tree menu

    1. In the "Navigation" area, expand the "vDC Management" accordion panel
    2. In the tree navigation area, expand the "vDC's" node in the tree graph
    3. Left click on the "MyCloud" icon
    4. In the main area, click on the "vServer Types" tab
    5. From the "vServer Types" area, click on the icon of the green round symbol containing "+"

In both cases one of two errors may be seen:

  1. An "Error: 0" Dialog box
    • A small dialog box titled "Error" appears. The dialog box does not have an error in the main content region just "0". Below this, an OK button is presented:



  2. A "vDC com.sun.hss.domain:name=Clouds,type=CMClouds does not exist. (117700)" Dialog box

    • NOTE: This error can be seen for the same issue, but occurs with with far less frequency than the above "Error: 0" dialog box.

In addition to the above the latest emoc.log, located under /var/opt/sun/xvm/logs/emoc.log, will contain a Java exception similar to the following:

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms