×
 
 
  •  
$helper.renderConfluenceMacro('{bmc-global-announcement:$space.key}')
BMC BladeLogic Automation Suite 8.6 ... Release notes and notices Known and corrected issues Known issues and workarounds in continuous compliance for servers

Database error when BMC Atrium Orchestrator uses web service for associating a CI

The Entry does not exist in database error appears in the SOAP response when BMC Atrium Orchestrator uses the TMS_TaskInterface/UpdateTaskAndRelationships web service for associating a CI.

Workaround:

  1. Open the BMC Remedy Action Request System Administration Console.
  2. Select Server Information.
  3. Select the Licenses tab, and then change the Submitter Mode to Changeable.
  4. Restart the BMC Remedy Action Request System.
Was this page helpful? Yes No Submitting... Thank you
Last modified by Fran Coughlin on Jan 05, 2012
workarounds known_issues continuous_compliance_servers bmc_restricted

Comments

Log in or register to comment.

Enabling association of an Incident ticket to a configuration item
Configuring Continuous Compliance for Servers when BladeLogic adapter is enabled in BLCLI tunneling mode
BMC Software Confidential.
© Copyright 2024 BMC Software, Inc.
Legal notices

Powered by Atlassian Confluence and Scroll Viewport

© Copyright 2005-2024 BMC Software, Inc. Use of this site signifies your acceptance of BMC’s Terms of Use . BMC, the BMC logo, and other BMC marks are assets of BMC Software, Inc. These trademarks are registered and may be registered in the U.S. and in other countries.