Error "Error processing context menu item: An error occurred calling web service.undefined." when trying to create a new resource type

Article:TECH159820  |  Created: 2011-05-11  |  Updated: 2011-05-11  |  Article URL http://www.symantec.com/docs/TECH159820
Article Type
Technical Solution


Issue



When trying to create a new resource type in Symantec Management Console (Settings > All Settings > Notification Server > Resource and Data Class Settings > Resource Types), the error "Error processing context menu item: An error occurred calling web service.undefined." occurs.


Error



Error processing context menu item: An error occurred calling web service.undefined.

Cause



Views that include the name "New_Resource_Type" already exist in the Symantec_CMDB database. As CMDB should create a new resource type named "New_Reource_Type_2" in "New_Resource_Type" already exists, it is unknown why it how this can occur.


Solution



When a new resource type is created, it creates nine new views in the Symantec_CMDB database with the name "New_Resource_Type". These are:

  1. vRM_New_Resource_Type
  2. vRM_New_Resource_Type_ExactType
  3. vRM_New_Resource_Type_Hierarchy
  4. vRM_New_Resource_Type_Item
  5. vRM_New_Resource_Type_Item_ExactType
  6. vRM_New_Resource_Type_Item_Hierarchy
  7. vRM_New_Resource_Type_Item_Partitioned
  8. vRM_New_Resource_Type_Partitioned
  9. vRMNonLocalized_New_Resource_Type

Note: When a user changes the new resource name, these views all change to the new name as well, replacing "New_Resource_Type" with the new name.

The solution is to drop the views of any "New_Resource_Type" views.

  1. Determine what "New_Resource_Type" views exist by running the following SQL script in Microsoft SQL Server Management Studio:

    USE Symantec_CDMB
    SELECT *
    FROM sysobjects
    WHERE name like 'vRM%New_Resource_Type%'
     
  2. If any matches are returned for "New_Resource_Type" (excluding any additional matches, such as for "New_Resource_Type_2", etc.), drop the views by running the following SQL script in Microsoft SQL Server Management Studio:

    USE Symantec_CMDB
    DROP VIEW [dbo].[<view name>]

    Where "<view name>" is the name of the specific view to drop. This may need to be done up to nine times, depending on how many are found from the above list.
     
  3. In the Symantec Management Platform console, create a new resource type. This now works correctly.

Related Article

Unable to Create Resource Type from a Custom Security Role
http://www.symantec.com/business/support/index?page=content&id=TECH127666




Article URL http://www.symantec.com/docs/TECH159820


Terms of use for this information are found in Legal Notices