176778 - Troubleshooting Guide CMDB 7.6.04

March 26, 2018 | Author: maps1301 | Category: Class (Computer Programming), System Administrator, Trademark, Technical Support, Computer File
Share
Report this link


Comments



Description

BMC Atrium Core 7.6.04 Troubleshooting Guide January 2011 www.bmc.com Contacting BMC Software You can access the BMC Software website at http://www.bmc.com. From this website, you can obtain information about the company, its products, corporate offices, special events, and career opportunities. United States and Canada Address BMC SOFTWARE INC 2101 CITYWEST BLVD HOUSTON TX 77042-2827 USA Telephone 713 918 8800 or 800 841 2031 Fax 713 918 8000 Outside United States and Canada Telephone (01) 713 918 8800 Fax (01) 713 918 8000 If you have comments or suggestions about this documentation, contact Information Design and Development by email at [email protected]. © Copyright 2006–2007, 2009–2011 BMC Software, Inc. BMC, BMC Software, and the BMC Software logo are the exclusive properties of BMC Software, Inc., are registered with the U.S. Patent and Trademark Office, and may be registered or pending registration in other countries. All other BMC trademarks, service marks, and logos may be registered or pending registration in the U.S. or in other countries. All other trademarks or registered trademarks are the property of their respective owners. DB2 and IBM are registered trademarks of International Business Machines Corporation in the United States, other countries, or both. Linux is the registered trademark of Linus Torvalds. Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners. UNIX is the registered trademark of The Open Group in the US and other countries. Java, Javadoc, and Sun are registered trademarks of Sun Microsystems, Inc., in the U.S. and other countries. The information included in this documentation is the proprietary and confidential information of BMC Software, Inc., its affiliates, or licensors. Your use of this information is subject to the terms and conditions of the applicable End User License agreement for the product and to the proprietary and restricted rights notices included in the product documentation. Restricted rights legend U.S. Government Restricted Rights to Computer Software. UNPUBLISHED -- RIGHTS RESERVED UNDER THE COPYRIGHT LAWS OF THE UNITED STATES. Use, duplication, or disclosure of any data and computer software by the U.S. Government is subject to restrictions, as applicable, set forth in FAR Section 52.227-14, DFARS 252.227-7013, DFARS 252.227-7014, DFARS 252.227-7015, and DFARS 252.227-7025, as amended from time to time. Contractor/Manufacturer is BMC Software, Inc., 2101 CityWest Blvd., Houston, TX 77042-2827, USA. Any contract notices should be sent to this address. Customer Support You can obtain technical support by using the Support page on the BMC Software website or by contacting Customer Support by telephone or email. To expedite your inquiry, please see “Before Contacting BMC Software.” Support website You can obtain technical support from BMC Software 24 hours a day, 7 days a week at http://www.bmc.com/support. From this website, you can: s s s s s s s Read overviews about support services and programs that BMC Software offers. Find the most current information about BMC Software products. Search a database for problems similar to yours and possible solutions. Order or download product documentation. Report a problem or ask a question. Subscribe to receive email notices when new product versions are released. Find worldwide BMC Software support center locations and contact information, including email addresses, fax numbers, and telephone numbers. Support by telephone or email In the United States and Canada, if you need technical support and do not have access to the Web, call 800 537 1813 or send an email message to [email protected]. (In the Subject line, enter SupID:<yourSupportContractID>, such as SupID:12345.) Outside the United States and Canada, contact your local support center for assistance. Before contacting BMC Software Have the following information available so that Customer Support can begin working on your issue immediately: s Product information — — — Product name Product version (release number) License number and password (trial or permanent) s Operating system and environment information — — — — — Machine type Operating system type, version, and service pack System hardware configuration Serial numbers Related software (database, application, and communication) including type, version, and service pack or maintenance level s s s Sequence of events leading to the problem Commands and options that you used Messages received (and the time and date that you received them) — Product error messages — Messages from the operating system, such as file system full — Messages from related software License key and password information If you have a question about your license key or password, contact Customer Support through one of the following methods: s E-mail [email protected]. (In the Subject line, enter SupID:<yourSupportContractID>, such as SupID:12345.) In the United States and Canada, call 800 537 1813. Outside the United States and Canada, contact your local support center for assistance. Submit a new issue at http://www.bmc.com/support. s s . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Atrium Explorer issues . . . . . . . . . . . . . . . . . . Multiple CI match issues. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Troubleshooting unidentified instances issue . . . . . . . . . . . . . . . . . . Troubleshooting ARERR 623 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Resolving Reconciliation Engine performance issues due to insufficient thread settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Troubleshooting logging issues . . . . Troubleshooting definition export issues . . . . . . . . . . . . . . . . Troubleshooting ARERR 9391 . . . . . CIs merge more than once during a Merge activity . . . . . . . Contents 5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Contents BMC Atrium Core documentation Chapter 1 Reconciliation Engine issues 9 13 14 14 15 15 15 20 21 24 26 26 28 30 30 30 31 31 32 33 34 35 37 38 38 38 39 Reconciliation Engine startup issues. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Merge activity issues . . . . . Reconciliation Engine configuration issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Resolving multiple CI matches in the source dataset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Troubleshooting the mid tier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Troubleshooting ARERR 9280 . . . . . . . . . Chapter 2 BMC Atrium Core Console and Atrium widget issues Troubleshooting Atrium widget issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Resolving Reconciliation Engine performance issues due to incorrect database settings . Performance issues . . . . . . . Missing endpoints during the Merge activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Asset. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Failed jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Job issues . . . . . . . . Error messages . . . . . . . . . . . Troubleshooting multiple CI matches in BMC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Aborted jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 Rule Helper does not populate views and tables . . . . . . . . . . . . . . . . . . . . . . . . 51 Troubleshooting ARERR 341 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 Troubleshooting auditing issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70 Troubleshooting federation plug-in loading issue . . . . . . . . 66 About warnings generated when synchronizing BMC Atrium CMDB forms with other BMC applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 Instance management issues. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Verify. . . . . . . . . . . . . . . . . . . . . . . . . . 44 Troubleshooting errors displayed in Spoon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 Troubleshooting an Atrium Integration Engine connection error . . . . . . . . . . . . . . . . . . 54 BMC Atrium Integration Engine service issues . . . . . . 42 Job not displayed on the Atrium Integrator console . . . . . . . . . . . . . . . . . . 46 Error connecting to a Microsoft SQL Server database using Windows Authentication in Spoon. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 Troubleshooting a fatal BMC Atrium Integration Engine service error . . . . 66 Troubleshooting CMDB Sync-UI command issues. . . . . . . . . . . . . . . . . . . . . . . . . . . . or Test Connection buttons not responding . . . . . . . . . . . . . . . . . . . . 68 Federation issues. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 Troubleshooting a data handler error . . . . . . . 56 SQL adapter not working in UNIX or Linux environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 RPC error when creating federation plug-in . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 Troubleshooting Oracle database connection issue . . . 55 Troubleshooting a stopped BMC Atrium Integration Engine service after a password change . . . . . . . . . . . . . . . . . 42 Job fails to run. . 52 Server groups incorrectly used when triggering data exchanges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 BMC Atrium Integration Engine RPC port error. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 Troubleshooting data mapping issues . . . . . . . . . . . . 62 Data exchanges not running correctly after you upgrade BMC Atrium Integration Engine on BMC Remedy AR System where the database was restored from another environment . . . . . . . 47 Chapter 4 BMC Atrium Integration Engine issues 49 Troubleshooting data exchange issues . . . . . . . . . 70 Troubleshooting federated data class issue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Chapter 3 Atrium Integrator issues 41 Troubleshooting Atrium Integrator console issues . . . . . . . . . . 57 Troubleshooting instance management issues . . . . . . . . . . . . 69 Troubleshooting Launch Definition issues . . . . . . . . . . . . . . . . . . . . . . . . . 53 Troubleshooting Run Now. . . . . . . . . . . . . . . . . . . 50 Data exchange error messages . . . . . . . . . . . . . . . . . . . . . . . . 63 Chapter 5 Other BMC Atrium Core issues 65 Class form generation issues. . . . . . . . . . . . . . 55 AR System server stopped when running the BMC Atrium Integration Engine service on UNIX. . . . . . . 46 Location of log files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62 Displaying new attributes in the Data Field Mapping window . . . . . . . . . . . . 71 6 Troubleshooting Guide . . . . . . . . . . . . . . . . . . 43 Job not running from the Atrium Integrator console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deleting instances in a dataset. . . . . . . . . . . . . . . . . . . . . Chapter 7 Using logs to troubleshoot issues BMC Atrium Core Console client-side logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Troubleshooting normalization configuration . . . . . Verifying your data model manually . . . . . . . Deleting orphaned weak members . . . . . . . . . . . . . . . . . . . . Atrium Impact Simulator permissions issue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configure your Adobe Debug Flash Player Debugger . . . . . . Verifying version information for BMC Atrium CMDB components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deleting relationships that violate cardinality . . . . . . . Correcting orphaned weak members . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BMC Atrium CMDB logging . . . . . . . . . . . . . . . . . . . . . . Troubleshooting a failed data model change. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Contents . . . . . . . . . . .Troubleshooting invalid column lengths in federated classes with an IBM DB2 database . . . . . . . Working with the Data Integrity Checker option. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Data decompression issue in cmdbdriver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Web services startup issue . . . . . . BMC Atrium CMDB permission issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BMC Atrium Core Console server-side logging . . . . . . . . . . . . . . . . . . . . . . . . Troubleshooting invalid dataset IDs . . . . . . . . . Troubleshooting AR System server plug-in not responding . . . . . . . . . . . . Business service CIs not available in the Service Catalog issue . . . . . . Troubleshooting invalid CI relationships . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Chapter 6 Data model issues 72 72 73 73 74 74 75 75 75 76 76 76 77 78 78 79 79 80 81 82 82 82 82 83 83 84 84 85 85 86 87 87 88 89 90 93 94 94 95 95 96 96 97 98 99 7 Verifying your data model using the cmdbdiag program. . . . . . . . . . . . . . Server-side API logging . . . . . . . Deleting orphan relationships . Working with the CI and Relationship Correction Tool option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Resetting reconciliation identities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Troubleshooting Normalization Engine initialization errors . . . . . . . Correcting invalid relationship instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Java API configuration properties . . . . . . . . . . . . . . . . . . . Accessing the cmdbdiag program. . . . . . . . . . . . . . . . . . . . . . Troubleshooting a disabled Create button in Product Catalog . . . . . . . . . . . . . . Determining Adobe Flash Player Debugger version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Troubleshooting invalid relationships . Reconciliation Engine logging . . . . . . . . . Java API logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Data Visualization Form module issue. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Troubleshooting Normalization plugin not working properly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deleting instances for a given class . . . . . . . . . . . . . . . Viewing API version information . . . . . . . . . . . . Atrium Impact Simulator issues . . . . Troubleshooting BMC Atrium Core configuration issues . . . . Troubleshooting maximum number of records returned in Product Catalog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110 Atrium Impact Simulator logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115 Enabling Atrium Impact Simulator cell logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Troubleshooting Reconciliation Engine errors in the log file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188 Appendix G Index Atrium Integrator Error messages 191 197 8 Troubleshooting Guide . . . . . . . . . . . 118 Appendix A Appendix B Appendix C Appendix D Appendix E Appendix F BMC Atrium CMDB C API error messages BMC Atrium Core Console active link error messages BMC Atrium Core Console filter error messages Reconciliation Engine error messages Product Catalog error messages Federation plug-in error messages 119 153 157 163 177 185 AR System plug-in error messages . . . . . . . . . . . . . . . . . . . . 104 Enabling debug logging . . . . . . . . . . . . . . . . . . 102 Setting log levels for BMC Atrium Core web service logs. . . . . . . 107 Debug messages . . . . . . . . . . . 116 AR System server logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115 Normalization Engine logging . . . . . . . . . . . . . . . . . . . . . . . . 186 JDBC plug-in error messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104 BMC Atrium Integration Engine logging and debugging . . . . . . . . . . 117 Bundling the BMC Atrium Core log files . . . . . . 114 Enabling Atrium Impact Simulator plug-in logging . . . . . . . . . . . . . . . . . . . 102 Web services logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114 Atrium Impact Simulator plug-in logging . . . . . . . . . 105 Log messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106 Data exchange log messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . 04 User's Guide Description Information about defining source and target connections. and so on. Administrator's Guide federation. attributes. BMC Atrium CMDB 7.6. BMC Atrium CMDB 7. and asset analysts.BMC Atrium Core documentation This section describes the complete set of BMC Atrium Core documentation. and asset analysts. documentation is available free of charge on the BMC Atrium Core documentation media (DVD or Electronic Product Download bundle) and on the BMC Customer Support site. and other Atrium Integrator concepts.6. at http://www. focusing on the use of multiple related CIs to model an entity rather than on general information about a class or attribute. Note: This Help is provided in HTML and is available Configuration managers.6.04 Best practices for using the classes that BMC application administrators.6. subclasses. application administrators. Unless otherwise noted. Diagram applicable relationships. Data Modeling Guide provides for BMC Atrium CMDB (both the CDM and extensions) to model complex business entities. help systems. Contains only information about the CDM at first. BMC Atrium CMDB 7.6. Audience Users who are responsible for setting up data transfer integrations between external data stores and BMC Atrium CMDB.04 Information about setting permissions. and other administrative tasks in and asset analysts. To find this documentation on the BMC Customer Support site. Common Data Model Data Model (CDM).6. modifying the data model. configuring Configuration managers. but you can update it to include information about data model extensions that you install. It is not available on the BMC Customer Support site.04 Title Atrium Integrator 7. choose Product Documentation > Supported Product A-Z List > BMC Atrium CMDB Enterprise Manager >7.04 Data Model Help Description and details of superclasses. BMC Atrium Core documentation 9 . an impact model. and relationship classes for each class. BMC Atrium Configuration Management Database (BMC Atrium CMDB). on the BMC Atrium Core media.com/support. and asset analysts. configuring application administrators. including manuals.bmc. including unique attributes and application administrators. BMC Atrium CMDB 7. creating jobs and transformations. Configuration managers. editing and monitoring jobs. videos.04 Hierarchical diagram of all classes in the Common Configuration managers. 04 Javadoc Help Description Audience Information about Oracle Java classes. BMC Atrium Product Catalog. and asset analysts.6. BMC Atrium Core 7. It is not available on the BMC Customer Support site.bmc. methods. IT leaders. Reconciliation Guide providers into a single production dataset. User's Guide including searching for and comparing CIs and relationships.04 Compatibility Matrix Information about the BMC Atrium Core configurations that are expected to work together based on design.6.6. Configuration managers. and the functionality of BMC Atrium CMDB in particular. It is not available on the BMC Customer Support site.04 Online Help Help for using and configuring BMC Atrium CMDB.04 Information about normalizing data in BMC Atrium Configuration managers. Normalization and CMDB and reconciling CIs from different data application administrators. variables that integrate with BMC Atrium CMDB.6. configuration managers. BMC Atrium CMDB 7. relating CIs.6. application administrators. application administrators. application administrators. Note: This Flash video is available on the BMC Atrium Core media. It is not available on the BMC Customer Support site. Configuration managers. asset analysts. and viewing federated data. Compatibility Matrix from the BMC Customer Support site at http://www.04 Concepts and Planning Guide Information about CMDB concepts and high-level steps for planning and implementing BMC Atrium Core. testing.04 Information about using BMC Atrium CMDB. BMC Atrium CMDB 7. BMC Atrium CMDB 7. and asset analysts.6. running impact simulations. BMC Atrium Core: Taking Your Data Into Production End to End End-to-end high-level steps for bringing data into BMC Atrium CMDB from a third-party source and making it available in your production dataset. CMDBs in general. Reconciliation Engine.6. Users that work with CIs and need to understand the relationships that exist within BMC Atrium CMDB. user interface. viewing history.6. Anyone who wants to learn about and understand BMC Atrium Core products. Note: This Help is provided in HTML and is available on the BMC Atrium Core media.com/support/ reg/remedy-compatibility-tables. and so on. and users that work with CIs and need to understand the Note: This Help is provided in HTML and is available relationships that exist through the Help links in the BMC Atrium CMDB within BMC Atrium CMDB. and asset analysts. application administrators.04 Title BMC Atrium CMDB 7. and asset analysts are some who will benefit from this information. or general understanding of the interaction between products.BMC Atrium Core 7. BMC Atrium Core 7. including Atrium Integrator. 10 Troubleshooting Guide . Normalization Engine.html?c=n.04 Configuration managers. Note: Download the BMC Atrium Core 7. and Application programmers. 6. Combined index of all guides.04 Troubleshooting Guide BMC Atrium Core 7. interfaces in the Web Services Registry. and use BMC Atrium Core Web Services data structures and operations. managers. and creating aliases for managers. disambiguate web services.04 ADK Developer's Guide Information about how to build adapters that can transfer information between an external data store and either BMC Remedy AR System forms or BMC Atrium CMDB.6. IT and DML. upgrading. and BMC console error messages and their solutions. adding products.04 Web Services Help on the BMC Atrium Core media.6.Title Description Audience Application administrators and programmers.04 Product Catalog and DML Guide Information about installing. Information about configuring the Product Catalog System administrators.6. and Everyone. It is not or BMC Remedy available on the BMC Customer Support site.04 Online Help Integration Engine.04 Master Index BMC Atrium Core 7. manufacturers.04 Installation Guide BMC Atrium Core 7. Developers who have a basic understanding of BMC Atrium Integration Engine and want to build adapters that can exchange data between two data sources. Note: This Help is provided in HTML and is available BMC Atrium Core 7. Support personnel. including how to publish and find and programmers. Users who are responsible for setting up data transfer integrations between Note: This Help is provided in HTML and is available external data stores and through the Help links in the BMC Atrium either BMC Atrium CMDB Integration Engine user interface. Everyone.6. filter. BMC Atrium Integration Help for using and configuring BMC Atrium Engine 7. Atrium Core components. network products.04 Release Notes BMC Atrium Core 7. set versions.6.6. Information about resolving issues with BMC Application administrators. configure security policies and encryption. It is not available on the BMC Customer Support site.04 Information about creating API programs using C Developer’s Reference Guide API functions and data structures. and programmers. and other qualified personnel who are familiar with their computing and networking environment.6. BMC Atrium Core 7. BMC Atrium Core documentation 11 . including API. BMC Atrium Integration Engine 7. AR System. Information about new features. Application administrators. known issues. BMC Atrium Core 7. and uninstalling BMC Atrium Core features. other late-breaking topics.6. and categorizations. Information about using BMC Atrium Core Web Application administrators Services. activating event-driven data exchanges. and best practices for creating normalized relationships.04 appropriate class. BMC Atrium Integration Information about creating data exchanges and data Engine 7.04 Title Description Audience Users who are responsible for setting up data transfer integrations between external data stores and either BMC Atrium CMDB or BMC Remedy AR System.04 User's Guide mappings. defining connection settings. defining rules and queries. 12 Troubleshooting Guide .6. Mapping Your Data to Spreadsheet that maps common IT objects to the BMC Atrium CMDB 7.BMC Atrium Core 7. whether part of the CDM or an Classes extension. and other BMC Atrium Integration Engine concepts.6. Configuration managers. This spreadsheet also includes information about further categorizing instances using key attributes. application administrators. and asset analysts.6. Chapter 1 Reconciliation Engine issues This section provides information about troubleshooting various Reconciliation Engine issues. such as Reconciliation Engine job. and definition export issues. log. This section also lists Reconciliation Engine error messages and their solutions. The following topics are provided: Reconciliation Engine startup issues (page 14) Reconciliation Engine configuration issues (page 14) Job issues (page 15) Troubleshooting unidentified instances issue (page 20) Troubleshooting logging issues (page 21) Troubleshooting definition export issues (page 24) Multiple CI match issues (page 26) Merge activity issues (page 30) Performance issues (page 31) Chapter 1 Reconciliation Engine issues 13 . the value specified for the -i parameter must be the same as the Monitor-directory parameter in the armonitor.cfg file. To make sure that the configuration changes are implemented in the Reconciliation Engine 1 Query the Application Pending form for the configuration changes record. you might need to query the Application Pending form to view the configuration changes record.04 Reconciliation Engine startup issues The Reconciliation Engine process is started using armonitor. make sure that the -i parameter points to /etc/arsystem/ARInstanceName/. 2 Verify that the configuration file contains an entry for the arrecond process and that and it is not commented out. restart the AR System service to run the Reconciliation Engine process.conf) file. 3 Depending on the platform you have installed. see the BMC Remedy Action Request System 7. UNIX—In the arrecond.cfg file. If the Reconciliation Engine is not running. 4 If you modified the armonitor. perform the following steps: Windows—In the armonitor. If you do not view the record anymore.6.cfg file.conf on UNIX®. The record will no longer be visible if the changes have been implemented. 2 If you view the record in the Application Pending form. 14 Troubleshooting Guide . perform the following steps: 1 Open the armonitor. Reconciliation Engine configuration issues The BMC Atrium Core server notifies the Reconciliation Engine when configuration changes are made using the Settings link from the navigation bar on the Reconciliation Manager tab. you might need to wait longer for the changes to be implemented.cfg on Windows or armonitor.cfg (armonitor. The Reconciliation Engine then periodically checks whether a signal failed to be successfully delivered. For more information about the armonitor.sh script file.6. it means that the changes have already taken affect.04 Configuration Guide. If you are still able to view the record. NOTE If the configuration changes are not immediately implemented in the Reconciliation Engine.BMC Atrium Core 7.cfg file. wait for a few minutes and then try again. correct the error with the instance and either manually identify and merge the instance. When you manually start a job or when the Reconciliation Engine runs a scheduled job. the job is aborted or paused. the job is aborted or paused. Aborted jobs To determine the cause of the incomplete job issue. Unless the problem is corrected. which you can view on the Administrative Information tab of the Reconciliation menu.Job issues Job issues This section provides information about troubleshooting Reconciliation Engine job issues. in case of non-fatal instance errors. No space left on device. Failed jobs are started at the next scheduled time.—If the Reconciliation Engine stopped responding because of insufficient temporary disk space for AR System server operations. the service was down). use the troubleshooting steps discussed in this section. This error message is displayed if the Class Instance ID and the Attribute Instance ID attributes of the class and attribute specified in the Precedence Group contain a NULL value. The Reconciliation Engine does not automatically retry jobs that fail or attempt to catch up with jobs that were not executed (for example. Unspecified details in the job—If you did not specify the required details in the job definition. the job will continue to fail. the job is canceled. As a result a related event is created. but the job moves to the next activity. the job is aborted or paused. it can be aborted or paused for the following reasons: ARERR 101008 The job is already running—If the Reconciliation Engine attempts to start a job that is already running. if a schedule exists. or use the CMDBStartJobRun C API. the job might continue to run. such as dataset ID. and the reason for the failure. An error event is still created. However. the job that was already running is aborted or paused. The instance for which the error was generated is not successfully identified or merged. To resolve this issue. ARERR[101041] Class id <classId> of namespace <namespace> does not exist— If the IDs of the class name or attribute name specified in the Precedence Group does not exist. identifying the job. Chapter 1 Reconciliation Engine issues 15 . Failed jobs If a fatal error occurs during any activity that is processing information. Failure with a temporary file. the activity that failed. the arrecond. log in to your AR System server as an Administrator. 9 From the main menu. 7 Open the Reconciliation Job Runs form in Search mode and click the Search button on the toolbar.BMC Atrium Core 7. all jobs that are currently running are aborted or paused.log and the Reconciliation Engine log file for errors. 5 Make sure that there are no records displayed in the results table.6. 10 Verify that the Application Pending form contains no extra records that instruct the Reconciliation Engine to trigger the same job. the job is aborted or paused. For more information about setting the log file location for the Reconciliation Engine. the Related Runs table might indicate that the job has started. choose Actions > Delete. Extra records that trigger the same job might be created when you manually start a job and click the Start Job button several times. To resolve the aborted job error that results from restarting the AR System server. but the job might not be actually running. 6 Using BMC Remedy User. select Started. 2 Click the History tab. examine the arrecond. Rebooting AR System server abruptly—If the Reconciliation Engine job is running and you reboot the AR System server. Troubleshooting aborted jobs due to abruptly restarting the Reconciliation Engine If you abruptly restarted the Reconciliation Engine. 11 To resolve the unspecified details error.log and Reconciliation Engine log files are located in the C:\Program Files\BMC Software\AtriumCore\logs subdirectory of by default. To troubleshoot issues caused due to abrupt restarting of the Reconciliation Engine 1 Log in to the BMC Atrium Core Console and click Application Launcher > Applications > Reconciliation. 4 Specify the start date and end date for the job. 16 Troubleshooting Guide . 3 From the Show all Job Runs With Status list.04 Malloc failed on server—If the computer on which you are running the Reconciliation Engine does not have enough memory. restart the job. If you did not specify a path for the Reconciliation Engine log file using the Settings option on the Reconciliation Manager console. 8 Select the record that has a value of “Started” in the Run Status column. see “Reconciliation Engine logging” on page 99. Chapter 1 Reconciliation Engine issues 17 . see “Reconciliation Engine logging” on page 99. Due to intensive data manipulation. if a class with such a name does not exist. search for the RE:Precedence form. your reconciliation jobs might abort. 3 Clear the Visible box on the Display page and save the form.6. Troubleshooting aborted jobs due to the Classid does not exist error message You might encounter the Class ID of namespace does not exist error message if the class ID you specified is hidden. 2 Monitor the amount of memory available on your computer and check the processes that are consuming large amounts of memory. 6 If the reconciliation job uses the Copy activity. see the BMC Atrium Core 7. see “AR System server logging” on page 117. 4 Examine arrecond. For more information about the software and hardware requirements for BMC Atrium Core.Job issues Troubleshooting aborted jobs due to insufficient memory If your computer does not have enough memory space. search for the Precedences form from the Object List.log file. For more information about the arerror. such as virtual memory and space for BMC Atrium CMDB tasks.04 Installation Guide. 5 Open the Precedences form in Search mode and click Search again. 5 Make sure that the server has enough resources. or if the class ID field is blank. 4 In BMC Remedy User. the Reconciliation Engine might need to use more virtual memory than available. 2 Double-click the Debug_pag field that contains the Debug tab. 3 Add more disk space to the server TEMP disk or redirect TEMP to another disk that has more disk space. 6 Select the specific precedence from the Search results list and make sure that the Class Instance ID and the Attribute Instance ID fields are not blank.log and the Reconciliation Engine job log files to determine the operation that the Reconciliation Engine was performing when the insufficient memory error was generated. make sure that Copy Relationship field is set to By Qualifier to avoid insufficient memory issues. To troubleshoot classId does not exist error message 1 In BMC Remedy Developer Studio. To troubleshoot jobs aborted due to insufficient memory 1 Check the arerror.log file to determine whether problems with the AR System server or arrecond executable occurred. For more information about Reconciliation Engine logs. BMC Atrium Core 7.6.04 7 Delete the job entry that is assigned with the given Precedence Group. 8 In the Reconciliation Manager Console, create the job entry again and run the job. Troubleshooting a job that does not start Perform the following procedure when you notice that the jobs on the Job History Console are not running even though they were scheduled to run. To troubleshoot scheduled jobs that did not start 1 Log in to the BMC Atrium Core Console and click Reconciliation. For information about logging in to the console, see the BMC Atrium CMDB 7.6.04 User's Guide. 2 Click the Administrative Information tab and verify that the Job status for the specific job is set to Active. 3 Verify that the arrecond.exe process (Reconciliation Engine) is running and that its process ID (PID) is not changing every minute. The Reconciliation Engine process ID must remain the same, which denotes that the dispatcher is not abruptly restarting. 4 In the armonitor.log file, check whether there is an entry indicating that the arrecond.exe process is restarting every few seconds. 5 Verify that the Reconciliation Engine is connected to the correct AR System server instance. For information about how to verify that the Reconciliation Engine is connected to the correct AR System server instance, see step 8 of “Troubleshooting logging issues” on page 21. TIP To verify that a specific process is running on a Windows computer, view the Processes tab on the Task Manager. On UNIX, use the ps - ef | grep process name command. 6 If the Reconciliation Engine is not running or if it is not connecting to the AR System server, search the arerror.log, and armonitor.cfg (armonitor.conf) files for errors. 7 Wait for a few seconds for the record in the Application Pending form to be processed and the job to start. The job usually starts within a few seconds when the dispatcher is running properly. The dispatcher instructs the Reconciliation Engine to perform tasks based on the entry in the Application Pending form. TIP With BMC Remedy User, search for the Application Pending form and open it in Search mode to view the job record. 18 Troubleshooting Guide Job issues 8 Perform the following steps to verify that the dispatcher is running: a To verify that the dispatcher is configured to run, search for the arsvcdsp.exe process in the armonitor.cfg file. b From the Windows Task Bar or UNIX console, verify that the dispatcher process is running and that its process ID is not changing every minute. The dispatcher process ID must remain the same, which denotes that the dispatcher is not abruptly restarting. 9 If the dispatcher is not running, wait for the amount of time specified in the Polling Interval field on the Server Configuration Editor dialog box. TIP You can also reduce the Polling Interval time. This ensures that the arrecond.exe process polls the Reconciliation Engine job queue more often. 10 If the arrecond and arsvcdsp processes are running, but the Application Pending entry is not processed, perform the following steps to enable dispatcher logging. a In the ar.cfg (ar.conf) configuration file, set the Dispatch-Log-File entry to fullPath/dispatch.log. b Restart the AR System server. 11 For jobs that are started by way of workflow or Execute Job activities, verify that the job name is correct and that the status of the specified job is “Active” on the Job History Console. 12 Examine arerror.log to verify that the server was down for maintenance during a scheduled run of the Reconciliation Engine Job. Troubleshooting a job that does not finish At times, the Reconciliation Engine might take several minutes to update the status of your job to Successful or Failed. This might cause you to believe that the job did not finish. In such a case, perform the following procedure to verify that the job is still running and that the Reconciliation Engine did not generate any errors. To troubleshoot scheduled jobs that did not finish 1 Check the arerror.log log to determine whether any errors occurred with the AR System Server or the arrecond.exe process. If the AR System server or the arrecond.exe process stops responding, they are restarted and the status of the Reconciliation Engine job is changed to Aborted. However errors, such as ARERR 93 in the arerror.log log, can point to failures caused by performance or AR System connection issues. Chapter 1 Reconciliation Engine issues 19 BMC Atrium Core 7.6.04 2 Check the Reconciliation Engine Job log for any information about Reconciliation Engine activities. Verify that the last line of the Reconciliation Engine Job log indicates that an activity was completed. 3 Check the Reconciliation Engine Job logs for any plug-in errors. For example, an ARERR[8755] The specified plugin does not exist error message might indicate an issue with the BMC Service Impact Manager extensions to the BMC Atrium CMDB. TIP The Reconciliation Engine job logs follow the job name_file number naming convention, where the job name refers to the name of the job to be executed and the file number indicates the number of files created for the job + 1. If you specified a file size limit, multiple files for a single job run will be created, for example, MergeComputers_1, MergeComputers_2, and so on. 4 Check the arrecond.log log for errors. Troubleshooting unidentified instances issue If the Reconciliation Engine cannot find a match for an instance after applying all the identification rules, or if the instance is part of an Identification group that you did not specify to be auto-identified, the instance remains unidentified. In such a case, you must manually identify the instance or modify the identification rules. For information about manually identifying data, see the BMC Atrium CMDB 7.6.04 Administrator's Guide. To troubleshoot the unidentified instances issue 1 Log in to the BMC Atrium Core Console and click Reconciliation. For information about logging in to the console, see the BMC Atrium CMDB 7.6.04 User's Guide. 2 Click the History tab and verify that the specific job was successfully executed after the modified date of the configuration item (CI). Reconciliation Engine jobs are typically named after the dataset that is used in the job. To determine the datasets that the job identifies, from the Administrative Information tab view the Identification activity. 3 Verify that the Dataset ID of the CI matches one of the defined Dataset IDs. 4 Verify that a qualification group is defined for the Identification activity. 5 If a qualification group is defined, verify that the CI meets the qualification. 6 Verify that the superclass and subclasses of the unidentified instance are included in the Identification rule of the Identification Group. 20 Troubleshooting Guide Troubleshooting logging issues 7 Perform the following steps to troubleshoot the issue using Reconciliation Job Logs. a Choose a test case from the Manual Identification Console, and click View. b Note the value in the Name, Instance ID, Class ID, Dataset ID, and Modified Date fields. 8 Click Edit Server Configuration on the toolbar and configure the following settings for the Reconciliation Engine log: a Max Log File Size (kilobytes) = 20000 This setting enables you to zip the multiple log files for the same job and save them to another system in case the log files exceed 20 megabytes (MB). b Logging level = Debug 9 Start the Reconciliation Engine Job again and wait for it to complete. 10 Search for the Instance ID of your test instance in the Job log to find the entry, such as the following entry: [DETAILS] [TID: 000006] : Started identifying instance <class = BMC.CORE:BMC_ComputerSystem, instance id = OI 1F94C10B39834F35BFDB59EEC3791F96> NOTE The DETAILS and TRACE entries appear only if you set the logging level to Debug. For information about how to search the log file for the identifying instance entry, see “Interpreting entries in the log file” on page 100. Troubleshooting logging issues If the Reconciliation Engine contains incorrect log path settings or insufficient permissions to write to the log directory, or if the Reconciliation Engine stopped responding, logging might be abruptly stopped. To troubleshoot log issues 1 Log in to the BMC Atrium Core Console. For information about logging in to the console, see the BMC Atrium CMDB 7.6.04 User's Guide. 2 From the Application Launcher, click Reconciliation. Chapter 1 Reconciliation Engine issues 21 query the Application Pending form for records where ‘Category’ = "Reconciliation". C:\RELog. On UNIX. type 1000. specify a short log file path with no spaces.conf file to match the entries in the Modify Server Configuration window of the Reconciliation Manager and restart the Reconciliation Engine to configure the settings. The ar.cfg file.cfg or ar. The Reconciliation Engine has permissions to create files in that directory. It is a directory. If you do not specify a log file path or if the log file path is empty. for example. for example. a From the Logging Level list.cfg (ar. When you specify the log file path.conf) configuration file. c In the Log File Path field. verify that the settings you configured in step 3 are updated on the AR System server. see the BMC Remedy Action Request System 7. For more information about the ar. BEST PRACTICE For testing purposes. This level also includes class-level and dataset-level information.04 3 Click Edit Server Configuration on the toolbar and configure the following settings on the Server Configuration Editor window.6. 4 In the ar.04 Configuration Guide. TIP You can also manually update the ar.BMC Atrium Core 7. 5 If you configured the server configuration settings (see step 3) using the BMC Atrium Core Console and if these settings are not updated in the ar. /tmp/RELog/. make sure that: The directory exists on the AR System server. On Windows. see “Reconciliation Engine logging” on page 99. Setting this option enables the log to capture information about warnings and error messages.conf file.cfg or ar. select Info.cfg configuration file contains AR System server configuration changes. the Reconciliation Engine log is generated in the Db subdirectory of your AR System server installation directory by default. This enables you to verify that the Application Pending form contains an UpdateConfig record for the Reconciliation Engine. b In the Maximum Log File Size (kilobytes) list. This file is located in the C:\Program Files\BMC Software\ARSystem\Conf subdirectory of your AR System server installation directory. 22 Troubleshooting Guide . For more information about the log settings. not a file name. specify the correct log path. This sets the maximum size of the log file to 1000 KBs.6. which must be the same as the AR System server installation directory. script file.6.exe on Windows and arrecond on UNIX. The value in the process ID field is not changing. search for the line entry that runs the arrecond. The Reconciliation Engine creates the arrecond.Troubleshooting logging issues 6 On the AR System server. Therefore.conf) configuration file is set up correctly: a Open the armonitor. open it in a UNIX editor. c Note the value that is specified for the -i parameter. On Windows. reconciliationJobName_integer. d If the directory name for the -i parameter is different than the AR System server installation directory.log file exists on the AR System server. change it to match the AR System directory name. see “Reconciliation Engine logging” on page 99.cfg (ar. it is located in the /etc/arsystem/ ARInstanceName/ subdirectory. On UNIX. The process name for the Reconciliation Engine is arrecond. note its value every few minutes. The armonitor. see the BMC Remedy Action Request System 7. TIP To verify that the process ID frequently changes.log and a log file named for example. this configuration file is located in the C:\Program Files\BMC Software\ARSystem\Conf subdirectory of your AR System server installation directory. When the Reconciliation Engine process stops abruptly. TIP To view the arrecond.log. The value specified for this parameter is a directory name.log tracks Reconciliation Engine scheduling.log.sh (UNIX). verify that: The Reconciliation Engine is running. Chapter 1 Reconciliation Engine issues 23 . For more information about the armonitor. For more information about Reconciliation Engine logging. the changing process ID value indicates that the Reconciliation Engine is constantly restarted. The arrecond.04 Configuration Guide.cfg file.cfg (armonitor.sh. the armonitor configuration file restarts the process and a new process ID is assigned to it. BMCAsset Identification_5. 8 Perform the following steps to verify that the ar. 7 Verify that the arrecond.exe executable (Windows) or arrecond.conf) file on the AR System server.cfg file contains the commands that the armonitor binary executes. b In the configuration file. it is written to the same directory as aruser. Table 1-1 provides a list of error conditions and their causes for definition export failures. as it does each export.6. Ensure that you have enough disk space.04 Troubleshooting definition export issues Exporting Reconciliation Engine definitions in BMC Atrium CMDB is a client-side operation using native AR System workflow. see the BMC Atrium CMDB 7. The file will not be created. This issue occurs because several reports There is no solution for this issue. 24 Troubleshooting Guide .exe. 3 If you specified a File Name for exporting definitions. NOTE If you do not specify a full path for the file. The screen flickers during the export. For more information about exporting Reconciliation Engine definitions. Cause Solution This error occurs if you specify an invalid Verify the path you specified for location on the client computer. are run to append the data in each form to the export file. occurs multiple times. 2 Make sure that the directory to which you want to export the definitions is located on the computer on which you are running BMC Remedy User.ARX extension and the path for the file is valid. By default aruser. To troubleshoot definition export issues 1 Make sure that the version of BMC Remedy User matches the version of the AR System server that you have installed to export the definitions. The error exporting the definition. Table 1-1: Definition export errors and solutions (Sheet 1 of 2) Error message Report to file failed.exe is available under C:\Program Files\AR System\User\.04 Normalization and Reconciliation Guide. verify that the file has a.BMC Atrium Core 7.6. Chapter 1 Reconciliation Engine issues 25 . This error occurs because of a reporting When exporting limitation in the mid tier. a new entry is created. overwrite the existing data using the following command: “complete-path-toarimportcmd. the application prompts for a separate export file name for each form.exe -x machinename -u user-name -p userpassword -o complete-file name -e 179 -D4” The -e 179 option enables you to verify that a definition you are importing already exists. SW00244518.Troubleshooting definition export issues Table 1-1: Definition export errors and solutions (Sheet 2 of 2) Error message Some data records are included in the export file more than once. reconciliation rules from the browser. If no match is found. BMC recommends that you always use BMC Remedy User to export definitions. This check is performed based on the GUID values. Cause This is a defect. Solution If you import the data into a target system. Specifying the -D4 option updates an entry if a match is found. 04 Multiple CI match issues Your reconciliation jobs might fail because the Reconciliation Engine finds multiple matches in the source or target (BMC. “Reconciliation Engine error messages. Found multiple matches in the dataset: Cannot identify the instance of class <className> with instance ID <instanceId>.Asset) dataset.” on page 163.BMC Atrium Core 7.Asset A CI remains unidentified in the source dataset after an Identification activity. see Appendix D. and the Reconciliation Engine log shows the error message.6. This error occurs because the Find in Dataset field for the specific Identification Rule contains two or more CIs that share the same value for the attribute defined in the Identification Rule. This section explains the symptoms and solutions for such errors. Figure 1-1 illustrates the overall steps you need to perform to troubleshoot the duplicate CIs in your source dataset issue. 26 Troubleshooting Guide . Troubleshooting multiple CI matches in BMC. For more information about Reconciliation Engine error messages. Multiple CI match issues Figure 1-1: Flowchart of troubleshooting duplicate CIs in the BMC.Asset dataset Chapter 1 Reconciliation Engine issues 27 . search for the duplicate CIs using these values in the Datasetid and Tokenid fields on the BMC.6. You create a new CI to represent a rediscovered object rather than unmarking a soft-deleted CI. Only one CI must exist in the Find in Dataset with the specific dataset ID and reconciliation ID combination.CORE:BMC_BaseElement form. Resolving multiple CI matches in the source dataset A CI remains unidentified in the source dataset after an Identification activity.Asset 1 In the BMC. delete all other duplicate entries. search for the duplicate CIs using the attribute values specified in the Find in Dataset field and any other attributes that you defined in the Identification Rule. 3 Run the Reconciliation Engine Identification activity to identify the CI. If you find multiple CIs in the dataset that represent the same CI instance in your environment. You use the Modify All option of BMC Remedy User to modify all CI instances and you include a value in the ReconciliationIdentity attribute.CORE:BMC_BaseElement form. This error might occur when: You use the Copy to New option on the Edit menu of BMC Remedy User to copy an existing identified CI.ASSET in the Find in Dataset field and 'TokenId' != $\NULL$ AND'TokenId' = $TokenId$ in the Qualification field of the Identification Rule. 2 Perform the following steps to determine the problem: Reexamine the Identification Rule to verify that the qualification that you specified fails to return unique CIs. make appropriate corrections to the qualification.04 To resolve duplicate CIs in BMC.ASSET dataset. Figure 1-2 illustrates the overall steps you need to perform to troubleshoot the duplicate CIs in your source dataset issue. and the Reconciliation Engine log shows the message. Examine the quality of data in the BMC. if you specified BMC. If so. 28 Troubleshooting Guide . For example.BMC Atrium Core 7. The dataset ID and Reconciliation Identity combination is not unique. The search might return more than one CI in the Source dataset with the same reconciliation ID and dataset ID. If so.CORE:BMC_BaseElement form. 4 Run the Reconciliation Engine Identification activity to identify the CI. 3 If the duplicate CI is not soft deleted. are there two same CIs with different PK values each? Yes The CIs are not duplicates in the source database No The Primary Key value should not change if it is used for linking BMC Atrium CMDB with the external database To resolve duplicate CIs in the source dataset 1 In the BMC. If so.ASSET and Purge from the provider dataset Are PrimaryKey values matching for the duplicate CIs? No Yes Confirm Import mechanism uses the Primary Key to update CI in database rather than create a new one Both CIs exist in the Source database? Yes No Import mechanism should propagate MarkAsDeleted to CMDB when the CI is deleted from the source database In the source database. delete the soft-deleted CI. 2 If the search returns multiple CI records. make appropriate corrections to the qualification. determine whether any of them has been soft deleted. search for the CI in the source dataset using the specific reconciliation ID and dataset ID.Multiple CI match issues Figure 1-2: Flowchart of troubleshooting duplicate CIs Start Is “Mark as Delete” =Yes? No Identify the Primary Key attribute used to maintain the link between CMDB and the external database Yes Run RE job to merge with BMC. Chapter 1 Reconciliation Engine issues 29 . reexamine the Identification Rule to verify that the qualification that you specified fails to return unique CIs. see Appendix D. “Reconciliation Engine error messages. For more information about Reconciliation Engine error messages. The error message displayed in the Reconciliation Engine log includes Cannot find the endpoint of relationship::<className>. This section explains the symptoms and solutions for such errors. the Reconciliation Engine might generate errors if it finds erroneous endpoint information or if the job attempts to merge the same CIs multiple times. a child CI in a composite object is merged once on its own and once as part of the composite object. This error occurs if you manually modify a CI and fail to modify its relationship. 2 Start the Identification and Merge activity. the same CI seems to be merged more than once. In this case.04 Merge activity issues When you create a Merge activity in your reconciliation job.” on page 163. select the Stand Alone option for the Include Child CIs option of the Merge activity or attach a Qualification group to the activity to exclude CIs that will also be merged as part of a composite object. CIs merge more than once during a Merge activity During a Merge activity. 30 Troubleshooting Guide . To resolve this issue 1 Reset reconciliation ID to 0 for all instances in the specific dataset.6. causing data integrity issues. The error message displayed on the Job History Console includes “Algorithm: Including child CIs and committing together. Missing endpoints during the Merge activity The Reconciliation Engine fails to merge CIs during a Merge activity because of missing endpoint for a relationship. To resolve this issue.” This error likely occurred because you selected Commit Together or Commit Separately for the Include Child CIs? option of the Merge activity but did not use a Qualification group to restrict the CIs to be merged.BMC Atrium Core 7. Performance issues Performance issues The Reconciliation Engine might demonstrate performance issues if it finds that the number of threads you configured for the AR System server were insufficient or if the database settings that you specified were incorrect. This section explains the symptoms and solutions for such errors. For more information about Reconciliation Engine error messages, see Appendix D, “Reconciliation Engine error messages,” on page 163. Resolving Reconciliation Engine performance issues due to insufficient thread settings When processing any type of activity, the Reconciliation Engine demonstrates performance issues. The Reconciliation Engine log file contains no more than one or two different thread IDs (TID). This indicates that the AR System server is not configured to use multi-threads. This problem might occur if you have not configured the Reconciliation Engine to create multiple threads for different activities. To resolve this issue 1 Log in to the BMC Atrium Core Console as an administrator, and click Reconciliation from the Application Launcher menu. 2 Click Edit Server Configuration on the toolbar and specify 390698 or 390699 in the RPC Socket field of the Server Configuration Editor window. 3 Click Save. After you make the RPC Socket changes, the ar.cfg (ar.conf) configuration file is updated with the RE-RPC-Socket: 390698 or 390699 entry. 4 Log in to your AR System server with BMC Remedy User. 5 Open the AR System Administration: Server Information form in Search mode and click the Search button on the toolbar. The Server Information for your AR System server is displayed. 6 Click the Ports and Queues tab. The thread information for the server is displayed in the Server Queue table. 7 In the Server Queue table, increase the Max threads for any of the types of threads: Fast, List, or Private. The threads that you specify here are used when processing activities. BMC recommends that you create CPU x 5 for the List queue and CPU x 3 for the Fast queue or CPU x 1.5 for the Private queue. After you increase the threads, the ar.cfg (ar.conf) configuration file is updated with an entry for each of the thread types, for example, Private-RPC-Socket: 390698 2 4. Chapter 1 Reconciliation Engine issues 31 BMC Atrium Core 7.6.04 WARNING If you assign too many threads, for example 10 or 15, for any of these types, it can cause a system resource issue. The number of threads you can assign for activities depends on the number of CPUs available in your computer and the number of connections the database can accept. To avoid the Reconciliation Engine from locking out any users, BMC recommends that you create 1.5 threads x # of CPUs where maximum number of threads configured is n-1 compared to the max fast or list thread. Resolving Reconciliation Engine performance issues due to incorrect database settings When processing any type of activity, the Reconciliation Engine demonstrates performance issues. If the Reconciliation Engine takes more time than usual to complete a job, make sure your database setting are correct. This issue can occur because of any of the following reasons: The default cursor_sharing parameter in Oracle® 10g is set to “exact.” The Oracle database instance is allocated only a small amount of memory. SQL Server is allocated insufficient amount of space in the tempdb database. To resolve this issue 1 In Oracle, set the cursor_sharing parameter to “force” or “similar” to boost performance by up to 30%. 2 Request your Oracle DBA to run Oracle Statspack. This enables you to identify the database performance bottleneck. 3 Allocate extra dedicated disk space for the tempdb database in SQL Server. 4 Verify that: The attributes used in qualification are also indexed if you are using a qualification in the Identification Group. The index statistics are regularly updated. 5 Request your Oracle DBA to collect and analyze the Automatic Workload Repository (AWR) performance reports that were logged during the execution of the reconciliation job. 32 Troubleshooting Guide Chapter 2 BMC Atrium Core Console and Atrium widget issues This section provides troubleshooting information about issues related to the BMC Atrium Core Console and Atrium Widgets, such as Atrium Explorer and Atrium Query. This section also provides a list of error messages with their descriptions and solutions. The following topics are provided: Troubleshooting Atrium widget issues (page 34) Atrium Explorer issues (page 35) Troubleshooting the mid tier (page 37) Error messages (page 38) Chapter 2 BMC Atrium Core Console and Atrium widget issues 33 BMC Atrium Core 7.6.04 Troubleshooting Atrium widget issues This section provides possible solutions for resolving Atrium widget issues. To resolve Atrium widget issues 1 Confirm whether you can access the following mid tier URL from a browser. http://<midTierName>:<portNumber>/arsys In some cases, Atrium widgets might work from the browser, but not in BMC Remedy User. This issue occurs when the mid tier path is not configured for the server in BMC Remedy User. You must restart the mid tier after you install BMC Atrium Core. This ensures that all the required Atrium widget files are properly initialized. 2 Verify that you can access the mid tier from BMC Remedy User: a In BMC Remedy User, open the AR System Administration: Server Information form. b Click the Advanced tab and verify that the value in the Default Web Path field is correct. c If the Default Web Path field is blank, add the value http:// <midTierName>:<portNumber>/arsys TIP To verify that the web path is correct, you should be able to view the Welcome window on the mid tier when you copy the URL in the Default Web Path field and paste it in a browser. If you encounter a Server Not Found error message, verify that the mid tier is working. d Check whether you are able to log in to the mid tier. If you receive an authentication error (ARERR[623]), see “Troubleshooting ARERR 623” on page 38. For additional mid tier troubleshooting steps, see “Troubleshooting the mid tier” on page 37. 3 Make sure that BMC Remedy Flashboards is working. If a Server Not Found or Page Not Found error message is generated when you access the BMC Atrium Core Console, confirm whether you have installed the mid tier correctly. You must resolve this error before you proceed to the next step. 4 To verify that the Atrium Widgets are working, perform the following steps: a Log in to the BMC Atrium Core Console. If an error is generated when opening the BMC Atrium Core Console, see “Error messages” on page 38. b Click Application Launcher > Explorer > Classes from the Navigation Pane. You must be able to view the list of CI classes in the Navigation pane. 34 Troubleshooting Guide mouse over the Filter Name text box. To work around this issue: 1 Click the selection list with the Duplicate CI names in source datasets due to inconsistent default CI naming in the Atrium Explorer. This denotes that an error occurred. This issue occurs when you close the Atrium Explorer session after creating new CIs and then create CIs in a new session. 3 Press the Enter key. mouse to open the list. SW00304034 Mouse does not work for drop-down lists. the CIs with the default value in the Name attribute. Cause Solution If you reboot your computer on which Restart the mid tier after the you have installed the mid tier and the AR System server starts up. To view the error message. The OK button is disabled when creating a new filter. BMC_ComputerSystem CIs in a new change the value in the Name View from the Atrium Explorer and save attribute. Duplicate CIs in the source dataset will cause issues when you reconcile the new CIs with the BMC.ASSET dataset. This issue occurs because the your Filter Name exceeds the maximum length allowed for the field. you cannot select items in a combo box by clicking them with the mouse. the OK button is disabled (Grayed out). If you create a new filter from the Atrium Make sure that the Filter Name does Explorer and specify a name in the Filter not exceed its maximum character Name field that is more than 32 limit. In such a case. 2 Use the up and down arrow keys to select the list item. the Filter Name text box is displayed with a Red border. duplicate CIs are created in the source dataset. the mid tier might start up before the AR System server is back online. characters long. Table 2-1: Atrium Explorer issues and solutions (Sheet 1 of 2) Issue/Error number Send failed with the Atrium Explorer login screen.Atrium Explorer issues Atrium Explorer issues This section provides troubleshooting information for common Atrium Explorer issues. AR System server.[ If you use BMC Remedy User to access the Atrium Explorer. This issue occurs if you have installed other BMC applications on the mid tier. If you create new When you create new CIs in a View. Chapter 2 BMC Atrium Core Console and Atrium widget issues 35 . regedit. 2 In the Registry.0\Tomcat5\Parameters 3 Verify whether the value in the Parameters key is set to path=C:\PROGRA~1\BMC This path is incomplete. Error loading Federation Manager and Atrium Impact Simulator Cause Solution This issue occurs if the cache memory on Flush the cache memory on the mid the mid tier is slow. locate the HKEY_LOCAL_MACHINE folder and go to SOFTWARE\Wow6432Node\Apach e Software Foundation\Procrun 2. set the Parameters key to path=C:\Program Files (x86)\BMC Software\AR Server\midtier\WEB-INF\lib. tier after you create new objects in the Atrium Explorer. 36 Troubleshooting Guide . This issue occurs on 64-bit Windows To troubleshoot this issue: computers with a Tomcat based mid tier 1 Click Start > Run and type installation.6.04 Table 2-1: Atrium Explorer issues and solutions (Sheet 2 of 2) Issue/Error number New classes. attributes. 4 If yes.BMC Atrium Core 7. or other objects not visible in the Atrium Explorer. An entry for the BMC Remedy Mid Tier must appear in the Add/Remove programs list on your Windows computer. To troubleshoot the mid tier 1 Make sure that the mid tier is installed. Any issues with the mid tier might result in Atrium widget errors. perform the following steps: a ServletExec—Choose NewAtlanta > Administration and verify that the ARSYS application is installed.6. Verify if you have an arsys. If the Atrium Explorer is not working. Chapter 2 BMC Atrium Core Console and Atrium widget issues 37 . ServletExec is usually installed as an ISAPI plug-in. verify that the Apache Tomcat service is started. Perform the following steps to verify if Tomcat is set up correctly: Type http://server:8080 on your browser Address field. 3 Launch any of the Atrium Widgets to verify that it is working. If you do not view this file. b Apache Tomcat—From the Control Panel on your Windows computer. the mid tier must be correctly configured and running. For instructions about resolving mid tier issues on a UNIX computer. this service uses port 8080. 2 Depending on the application server you are using for the mid tier. either stop the Apache Tomcat service or use Microsoft IIS administration to stop the ISAPI plug-in. By default. reinstall the mid tier and the Apache Tomcat application server.xml file installed in your apachetomcat\conf\Catalina\localhost subdirectory. You should be able to view the application server home page. The following procedure provides the steps to resolve mid tier issues on a Windows computer. see “Troubleshooting Atrium widget issues” on page 34 for troubleshooting steps. TIP To restart the application server.Troubleshooting the mid tier Troubleshooting the mid tier For the Atrium Widgets to work properly. see the BMC Remedy Action Request System 7.04 Mid Tier Guide. 2 Enter the password in the BMC Remedy Mid Tier . 4 Check DELETE/EDIT for your server in the AR Server Settings table and click Edit.BMC Atrium Core 7. To troubleshoot ARERR [623] Perform the following steps to resolve this issue: 1 From the Start menu. choose Programs > Action Request System > BMC Remedy Mid Tier > Configure ARSYSTEM on localhost. such as RoboServer.Configuration Tool login window. The error message is Mid tier authentication error. 38 Troubleshooting Guide .com works. 2 Verify that adding a short name.6.6. such as RoboServer and a fully qualified name. To troubleshoot ARERR [9280] Perform the following steps to resolve this issue: 1 Make sure that the server name you specify in the server name field exists in the mid tier AR System server list.04 Mid Tier Guide. The error message is Server not present in the configured servers list <serverName>.04 Error messages This section provides a list of error messages that might be generated when you access BMC Atrium Core Console or Atrium Widgets. 5 Enter your mid tier administrator password in the Admin Password field. 3 Click the AR Server Settings link. 7 For more information about configuring mid tier password settings.mydomain. 6 The password you specify on this window must match with the password in the Connections Settings tab of the BMC Remedy AR System Administration: Server Information form. Troubleshooting ARERR 623 The login credentials that you specified for the mid tier might be incorrect. see the BMC Remedy Action Request System 7. Troubleshooting ARERR 9280 You are attempting to connect to a server that is not configured in the AR System server list. or if you did not install BMC Atrium Core on the Data Visualization server.Error messages Troubleshooting ARERR 9391 This error might occur if you did not specify the correct password or Data Visualization Module server name in the mid tier. Make sure that BMC Atrium Core is installed on the server that you specified in the Data Visualization Module Server (s) field. provide a server name in the Data Visualization Module Server (s) field on the General Settings page in the BMC Remedy Mid Tier Configuration Tool. The error message is No module with name “AtriumWidget” was found in the following configured module server [<serverName>]. To troubleshoot ARERR [9391] To resolve this module name not found error: If no server name was specified in the error message. Chapter 2 BMC Atrium Core Console and Atrium widget issues 39 . Make sure that the password that you provided on the AR System Server Settings window for the specified server matches the password in the Connections Settings tab of the BMC Remedy User AR System Administration: Server Information form. BMC Atrium Core 7.04 40 Troubleshooting Guide .6. The following topics are provided: Troubleshooting Atrium Integrator console issues (page 42) Troubleshooting errors displayed in Spoon (page 46) Location of log files (page 46) Error connecting to a Microsoft SQL Server database using Windows Authentication in Spoon (page 47) Chapter 3 Atrium Integrator issues 41 .Chapter 3 Atrium Integrator issues This section describes the steps that you can take to debug and troubleshoot errors that might occur when you execute a data transfer job. 6. Figure 3-1: Logging Details in the Atrium Integrator console View Log Details button 4 In the Logging Details area.BMC Atrium Core 7. To troubleshoot a job that failed to run 1 In the Atrium Integrator console. 42 Troubleshooting Guide . Job fails to run If the Job Name in the left side of the Atrium Integrator console is in red and has a next to it. the job failed to run. click View Log Details .04 Troubleshooting Atrium Integrator console issues This section describes how you can troubleshoot some common Atrium Integrator console issues. 2 In the History tab. The log file appears. click next to the last run of the failed job. 3 Click Logging details (below the Job Run Details area). select the failed job. xml NOTE If the pluginsvr_config.ATRIUM.xml file contains the following entry: BMC. 10 After the job completes running. change Log level to Rowlevel (very detailed). For information on opening a job in Spoon.NGIE Chapter 3 Atrium Integrator issues 43 . follow the steps in “Troubleshooting errors displayed in Spoon” on page 46. see Chapter 5.04 Installation Guide. Some . To troubleshoot Atrium Integrator console issues 1 Open the following file: AtriumCoreInstallationDirectory\cmdb\plugins\shared\ pluginsvr_config. 9 Click Launch to run the job. consider the following possible causes: The CMDB plugin might not be available on the server on which you installed the Spoon application.” 7 Click Run .6. 2 Ensure that the pluginsvr_config.xml file does not exist at this location. see the BMC Atrium Core 7. For more information. Job not displayed on the Atrium Integrator console If a job was created successfully through the Integration Job Builder wizard but does not appear on the Atrium Integrator console.jar files might be missing. you may need to reinstall Atrium Integrator.ARDBC. 8 In the Execute a job dialog box.Troubleshooting Atrium Integrator console issues Figure 3-2: Log file in the Atrium Integrator console 5 Click Export to File and save the log file to the desired location. “Editing jobs and transformations. open the job in Spoon. 6 If the log file does not contain enough information for you to debug the error. navigate to the location of the JDK on your computer. if you restart the operating system. Figure 3-3: NGIE:Config form 2 The Dir Path field displays the location of the Carte. Carte is automatically installed on the same computer.04 3 Ensure that all the . 44 Troubleshooting Guide . Job not running from the Atrium Integrator console You can run a job from the Atrium Integrator console only if the Carte server is running. The repository and Carte details are displayed. For example: C:\Program Files\Java\jdk1.ATRIUM. you might have to start the Carte server manually.jar files listed in the BMC.NGIE section exist at the specified locations. and runs in the background. open the NGIE:Config form and click Search.6.ARDBC. To view the Carte server details 1 In the BMC Remedy User tool on the computer where you have installed the Atrium Integrator server. When you install the Atrium Integrator server. To verify that the Carte server is running by using the command line 1 In a command line window.0_12\bin 2 Type jps.BMC Atrium Core 7.6. However.bat file. type: http://HostName:PortNumber HostName is the host name of the computer where the Atrium Integrator server is installed. Chapter 3 Atrium Integrator issues 45 . click Show status. and PortNumber is the number displayed in the Port field of the NGIE:Config form. 3 Log in using cluster for the user name and the password.Troubleshooting Atrium Integrator console issues The Carte server details are displayed.bat aus-idd-w28r2-vm1 20000 3 Click Enter. 2 Click Enter. The Carte server is started. The status of the jobs and transformations that have been run from the Atrium Integrator console are displayed. For example.bat HostName portNumber. and PortNumber is the number displayed in the Port field of the NGIE:Config form. To verify that the Carte server is running by using a browser 1 In a browser window. you might type: Carte. 5 Click on a job to display the log details. To start the Carte server manually 1 In a command line window. 4 In the Status window. HostName is the host name of the computer where the Atrium Integrator server is installed. navigate to the following directory: AtriumIntegratorInstallationDirectory\server\data-integration\ 2 Type Carte. txt 46 Troubleshooting Guide . 5 Open the specified file to see the error details. 4 To get more information about the errors. double-click the Error logging step.log The error files for each job or transformation that you run are located in the following directory: AtriumIntegratorInstallationDirectory\server\dataintegration\ngie\bin\error\jobName_transformationName_Error. the Atrium Integrator console log files are located in the following directory on the computer where you installed the mid tier: C:\Program Files\Apache Software Foundation\Tomcat 6. the Execution Results area in the Spoon window displays the results.0\logs\stdout_currentDate.04 Troubleshooting errors displayed in Spoon When you run a job or transformation in Spoon. The text file output dialog box displays the location of the error file in the Filename field. Figure 3-4: Execution Results area in the Spoon window 2 Click the Logging tab.BMC Atrium Core 7. click Refresh to get the latest results.6. 3 Click Show error lines . Location of log files If you are running the Tomcat web server. The job or transformation errors are displayed. To troubleshoot Spoon errors 1 In the Execution Results area. 3 Navigate to the following URL: http://sourceforge.net/projects/jtds/files/jtds/1. Use the following steps to fix the error.5-dist.5/jtds-1.5-dist\x64\SSO\ntlmauth.Error connecting to a Microsoft SQL Server database using Windows Authentication in Spoon Error connecting to a Microsoft SQL Server database using Windows Authentication in Spoon On a 32-bit JVM.zip/download 4 Download the jtds-1.2. 7 Launch Spoon. enter domain and in the Value column.dll. enter the domain of the database server. 11 In the Database Connection dialog box (General tab). 14 Click Test to ensure that the database connection is valid. 15 Click OK. specify appropriate values for the following fields: Connection Name Host Name Database Name Port Number 12 Click the Options tab.zip file and unzip it.dll file to the AtriumIntegratorInstallationDirectory\server\data-integration\libswt\win32 directory. 13 In the Parameter column. 8 Open your job or transformation. But. Chapter 3 Atrium Integrator issues 47 .dll file as ntlmauth_32.2.5dist.2. Windows Authentication displays an error on a 64-bit JVM. 5 Copy the \jtds-1. 10 Click New (next to the Connection field). 6 Close the Spoon window.2. 9 Double-click the table input step. Windows Authentication when connecting to a Microsoft SQL Server in Spoon works properly. 1 Navigate to the following directory: AtriumIntegratorInstallationDirectory\server\dataintegration\libswt\win32 2 Rename the ntlmauth. 04 48 Troubleshooting Guide .6.BMC Atrium Core 7. or Test Connection buttons not responding (page 53) Troubleshooting data mapping issues (page 54) BMC Atrium Integration Engine service issues (page 55) SQL adapter not working in UNIX or Linux environment (page 57) Instance management issues (page 57) Rule Helper does not populate views and tables (page 61) BMC Atrium Integration Engine RPC port error (page 62) Displaying new attributes in the Data Field Mapping window (page 62) Data exchanges not running correctly after you upgrade BMC Atrium Integration Engine on BMC Remedy AR System where the database was restored from another environment (page 63) Chapter 4 BMC Atrium Integration Engine issues 49 . Verify. The following topics are provided: Troubleshooting data exchange issues (page 50) Data exchange error messages (page 51) Server groups incorrectly used when triggering data exchanges (page 53) Troubleshooting Run Now. such as data exchange.Chapter 4 BMC Atrium Integration Engine issues This section provides information about troubleshooting various BMC Atrium Integration Engine issues. and other common issues. data mapping. click the Close link to close the form. make sure that your system has enough memory. use this formula: Number of data keys per exchange * 1.BMC Atrium Core 7.04 User’s Guide. according to the following formulas: To estimate memory for a first time transfer. confirm that your data exchange is configured correctly by using the Verify button on the Data Exchange Console. 3 Before you run the data exchange.2 KB * Number of records in vendor data + Number of records in AR target form For example. create multiple data exchanges with a query to reduce the number of records transferred at one time.000) + (1. For information about data exchange errors.000 records in your BMC Remedy Action Request System Server (BMC Remedy AR Server) target form: (3 x 1. If you encounter data exchange performance issues.2 KB * 11.000) = 49200 KB or 49. Use the following steps to troubleshoot common data exchanges issues. perform the following steps: a On the top-right corner of the BMC Atrium Integration Engine Console.6. 5 If you cannot verify a data exchange because the Data Exchange button froze at the Get Results stage. the data exchange will not be executed. use this formula: Number of data keys per exchange * 1.000 = 36000 KB or 36 MB To estimate memory if updating records. Running BMC Atrium Integration Engine in debug mode generates a debug file that you can use to diagnose issues.2 KB * Number of records in vendor data For example. you have three data keys in your exchange and 10.000 records in your external data store. you have three data keys in your exchange.6. 4 Verify that 8-bit characters are used in the external data store user name and password. and 11. 10. b Reopen the Data Exchange form. see the BMC Atrium Integration Engine 7. You must use only 8-bit characters in English strings. Otherwise. 50 Troubleshooting Guide . see “Data exchange error messages” on page 51. To troubleshoot data exchange issues 1 If BMC Atrium Integration Engine does not generate a debug file.2 MB If your system does not have sufficient memory.04 Troubleshooting data exchange issues Your data transfer might fail if the data exchange definitions are not configured correctly. 2 On the Data Mappings tab of the Data Exchange Console.2 KB * 10. make sure that the data exchange is linked to at least one data mapping.2 KB * 10.000 records in your external data store: 3 * 1. For more information about setting fields on the Advanced Settings tab of the Data Exchanges Information window. verify whether you enabled debugging by selecting Yes for the Enable Debug Logging option on the Advanced Settings tab of the Data Exchanges Information window. To troubleshoot a data handler error Perform the appropriate action depending on the database you installed: IBM® DB2®—Verify the AIE_DB2_LIB_DIR path in the instance script. such as aie001. b Change the Execute Exchange As option to Event Driven Only. To troubleshoot a Atrium Integration Engine connection error 1 Verify that you specified the correct AR System server user name and password. perform the following steps: a Open the data exchange in the BMC Atrium Integration Engine Console. Chapter 4 BMC Atrium Integration Engine issues 51 . Error code—Error: Adapter. you might encounter data handling.OpenConnection completed with errors issued. Troubleshooting an Atrium Integration Engine connection error This error occurs when BMC Atrium Integration Engine is unable to connect to the external data store during a data exchange. you can review the exchange log in the debug directory.Data exchange error messages 6 If you triggered a data exchange by using the Application Pending form or the aiexfer workflow utility. Troubleshooting a data handler error This error occurs if the library path for UNIX or Linux® refers to an invalid data store location. Oracle—Verify the AIE_ORACLE_LIB_DIR path. d Restart the AIE service. e Verify that the status of the record changes to Deleted in the Application Pending form. and AR System filter and active link errors. Error code—Data Handler failed to load. c Verify that the record appears in the Application Pending form with a Pending status. f If logging is enabled. and the data exchange does not occur. database connectivity. Data exchange error messages When configuring and running data exchanges. StartDataHandlers: Vendor Data Handler failed to start. Error code—Error: ARERR [39] Filter/escalation ‘set fields’ process timed out before completion.04 2 Test the external data store connection by using the Test Connection button on the Connection Settings tab before you trigger the data exchange. Set fields active link running a process failed (ARERR 1603).6. 2 If you encounter an ORA-12514 issue in the debug file.04 User's Guide.BMC Atrium Core 7. To troubleshoot an ARERR 39 error message 1 From BMC Remedy User. 3 Search for the service name for the appropriate SID. Error code—ORA-12514: TNS:listener does not currently know of service requested in connect descriptor To troubleshoot incorrect database settings 1 Examine the BMC Atrium Integration Engine debug file and search for any database errors. 2 Increase the Process Timeout setting for the AR System server. 2 If not.6. 52 Troubleshooting Guide . see the BMC Atrium Integration Engine 7. Error code—Error: ARERR [341] Cannot run the requested process. The default value for the Timeout setting is 5 seconds. go to AR System Administration Console > System > General > Server Information > Timeouts. examine the TNSNAMES. the cause might be incorrect database settings. Set fields active link running a process failed (ARERR 1603). To troubleshoot an Atrium Integration Engine aiexfer error 1 Verify whether the installer copied the aiexfer utility in the AR System installation directory. For more information about setting fields on the Connection Settings tab of the Data Exchanges Information window. Troubleshooting ARERR 39 This error occurs when the aiexfer workflow utility generates a delayed response in executing the request.ora file. Troubleshooting ARERR 341 This error occurs when the BMC Atrium Integration Engine process cannot find the aiexfer workflow utility. verify whether BMC Atrium Integration Engine was successfully installed. Troubleshooting Oracle database connection issue If the data exchange that you scheduled does not yield any results. the priority rankings that you set for a specific service in a server group environment will not take effect. Verify. 5 After you correct the database connectivity parameters for Oracle in the BMC Atrium Integration Engine. Data Exchanges should connect to the Server Group Alias. 2 If the utility is not copied. These rankings are set on the AR System Server Group Operation Ranking form.Verify that the Oracle listener service is running on the Oracle database computer by running the lsnrctl command. verify whether BMC Atrium Integration Engine was successfully installed. Server groups incorrectly used when triggering data exchanges If the Data Exchange that you scheduled is not triggered on the correct server in a server group environment. MyServer). or Test Connection buttons not responding When you click the Run Now. your connection settings for the Data Exchange might be incorrect. Chapter 4 BMC Atrium Integration Engine issues 53 . or Test Connection buttons 1 Verify whether the installer copied the aiexfer utility in the AR System installation directory. BMC Atrium Integration Engine might not respond due to: Installation issues with BMC Atrium Integration Engine Issues with the port that you configured for BMC Atrium Integration Engine Issues with the aiexfer workflow utility To troubleshoot issues with the Run Now. test the Connection again. Otherwise. the data exchange must point to the Server Group Alias. 2 Verify that the AR System server specified for the data exchange is the name of the Server Group Alias and not the name of a particular server group computer (for example.ora file does not match with the SID on the Connection Settings tab in BMC Atrium Integration Engine. To set the correct server in the server group for a data exchange 1 Open the Connection Settings tab on the Data Exchange Console. and not to a specific server. change the name on the Connection Settings tab. Verify. Troubleshooting Run Now. Verify. For server groups.Server groups incorrectly used when triggering data exchanges 4 If the SID for the service specified in the TNSNAMES. or Test Connection buttons on the Data Exchange console. such as 0001-001-AA-01. Otherwise. which is specified on the Primary Key Mapping tab of the mapping consoles for AR System.04 3 Verify whether the BMC Atrium Integration Engine instance that is executing the current data exchange is running. the size of that field must be at least the size of the largest possible value. 3 Verify that you specified default values set for the BMC Atrium Integration Engine required and core fields. go to AR System Administration Console > System > General > Server Information > Timeouts and increase the Process Timeout setting for the AR System server. 4 From the AIEInstallationDirectory/debug folder. To troubleshoot data mapping issues 1 If all your records are not transferred to the destination data source and no errors are generated in the data exchange debug file. BMC Atrium CMDB. you might receive AR API or CMDB API error. you might receive AR System API or BMC Atrium CMDB API error messages. verify that you are using the correct data key for the primary key mapping. Your data exchange might stop abruptly if the data mapping rules are violated. For example. you must map fields.BMC Atrium Core 7.6. Otherwise.dbg file and make sure that the BMC Atrium Integration Engine instance is listening to the port that you configured for it. You must use the AIE:MappingInfo form where the primary key mapping can be referred.04 User's Guide. and Relationship data exchanges. For example. such as Name and DatasetId. in case of CMDB Data Mapping. The primary key field for the data exchange. Troubleshooting data mapping issues Use the following procedure to troubleshoot data mapping issues with the BMC Atrium Integration Engine. see the BMC Atrium Integration Engine 7. must have unique values. if a field is created to hold the contents of a functional location number. 2 Verify that the BMC Remedy AR System or BMC Atrium CMDB data field size is large enough to accommodate the data.6. make sure that you use them correctly. NOTE AIE:DataMapping and AIE:CMDBDataMapping are backend forms used to store data. For more information about data mapping rules. in BMC Atrium Integration Engine. 5 From BMC Remedy User. 54 Troubleshooting Guide . 4 If you configured rules to manipulate the data from the data source. open the AIEInstance_EventListener. type . make sure that your data exchange is using the correct instance ID. aie001 might be the ID associated with the first instance of BMC Atrium Integration Engine that you install. The system displays the following error message when you type the (Ctrl+C) command to stop the BMC Atrium Integration Engine service: 390600: Another copy of the server is already running on the same RPC socket 390600: AR System server terminated -./AIEInstanceId start parameters. For example. To start the service in the background.BMC Atrium Integration Engine service issues 5 Make sure that you have not selected any systemGenerated numbered fields for your data mappings. When you check the following options and select systemGenerated from the menu list on the corresponding console forms for AR System. BMC Atrium Integration Engine service issues This section provides information about resolving the BMC Atrium Integration Engine service issues. Update Record Only if Checksum for Mapped Field Has Changed—The field must be of the Integer data type. and to stop the service. where AIEInstanceId is the ID associated with a particular instance of BMC Atrium Integration Engine. type . AR System server stopped when running the BMC Atrium Integration Engine service on UNIX If you use the same terminal window as the AR System server to start and stop the BMC Atrium Integration Engine service. the AR System server disconnects abruptly. the options generate a numbered field: Maintain Change History for Fields—The field must be of the Diary data type. Troubleshooting a stopped BMC Atrium Integration Engine service after a password change If the BMC Atrium Integration Engine service stopped running after you changed the password for your user name. perform the following steps.fatal error encountered To avoid stopping the BMC Atrium Integration Engine service Use different terminal windows to start the AR System server and the BMC Atrium Integration Engine service. Chapter 4 BMC Atrium Integration Engine issues 55 ./AIEInstanceId stop. TIP If you have more than one instance of BMC Atrium Integration Engine installed on your computer. dbg log file contains the entry.cfg file is less than 50000. type CTRL+O to open the Object List window and search for the User form. When the value in the ChunkSize parameter is reduced.BMC Atrium Core 7. specify the BMC Atrium Integration Engine installation directory. This error occurs when BMC Atrium Integration Engine cannot transfer data. The service cannot run until it is corrected. Troubleshooting a fatal BMC Atrium Integration Engine service error If the BMC Atrium Integration Engine service stopped responding due to a fatal error and the AIEServiceInstance_eiemain. -y AIEInstallDirPath—If you did not choose the default path during installation. -p password—The password to reset for the user name. 7 In the Admin Password field.6. 56 Troubleshooting Guide . Line Number: 2012. 6 On the BMC Atrium Integration Engine Console.cpp. 2 Open the User form in Search mode and click Search to view your user name details. Type: calloc. When the value in the ChunkSize parameter is reduced.cfg configuration file: -l userName—The user name for which you want to change the password. 2 If the error occurred due to a size issue. A size error might occur when BMC Atrium Integration Engine cannot transfer data. specify the new password. such as the following entry: CMDBGetListIntances Error: (120149) Size: 5379225. (EIEMSG 3317). click the Configuration Integration Engine Application Console link.dbg file for any size errors. make sure that the value specified for the ChunkSize parameter in the aie. BMC Atrium Integration Engine collects data in smaller chunks and avoids overloading AR System and BMC Atrium CMDB.04 To troubleshoot the password change issue 1 In BMC Remedy User. perform the following steps. BMC Atrium Integration Engine collects data in smaller chunks and avoids overloading AR System and BMC Atrium CMDB. 5 Run the aiecfedit utility with the following command-line parameters to change the BMC Atrium Integration Engine password in the aie. To troubleshoot BMC Atrium Integration Engine service EIEMSG 3317 fatal error 1 Examine the dataexchange. 8 Save the changes and restart the BMC Atrium Integration Engine service.\aroscinstanceutil. 3 Reset the password for your user name and click Save. Source File: . 4 From the command prompt. A fatal setup error occurred. navigate to the service\bin subdirectory of your BMC Atrium Integration Engine installation. deleting. or stopped—might occur if the AR System server does not respond. or stop an instance service. the BMC Atrium Integration Engine uses the SQL OLEDB APIs. Fails to update the Instance Console even though the instance is successfully created. These APIs are not supported on UNIX or Linux. started. start. creates the instance on primary server but not on secondary server—might occur if the primary and secondary server settings are incorrect. Chapter 4 BMC Atrium Integration Engine issues 57 . write a custom adapter using the Adapter Developer Kit provided with the BMC Atrium Integration Engine. To access Microsoft SQL Server from a UNIX computer. deleted. and any third-party driver. which are proprietary to Microsoft. NOTE To run the aiexfer utility in a server group environment. Generates a timeout error before completing the process—might occur if the connection to the server takes longer than the timeout period specified in the AR System Administration Console. In a server group environment.SQL adapter not working in UNIX or Linux environment SQL adapter not working in UNIX or Linux environment The BMC Atrium Integration Engine can integrate data from the MS SQL Server. Instance management issues When you use the Instances Console in the BMC Atrium Integration Engine to create. delete. starting. or stopping instances—might occur if the BMC Atrium Integration Engine service encountered a connection issue. you might encounter issues due to the following reasons: Error creating. To communicate with SQL Server. access it from the primary server. the value is always 1 For delete operations. The password for the AR System server login. The host name of the BMC Atrium Integration Engine instance. Combine the AIE hostname and Internal instance name. The name of the AR System server to use. The RPC port number to use. for example. -path (optional) -noi -del 58 Troubleshooting Guide . Table 4-1: Aiexfer command line parameter descriptions (Sheet 1 of 2) Command -CI/-DI/-START/STOP Description The type of instance management command to execute: CI—Create an instance DI—Delete an instance START—Start an instance STOP—Stop an instance The alias name of the instance The type of start up for the aiexfer utility: 3—Manual 2—Automatic -l -p -x -a -rpcport -inst (optional) -os The user name for the AR System server login. D:\Program Files\BMC Software\AtriumCore\aie\ service Number of instances. Table 3-1 lists the commands that you can use with the aiexfer utility. -d (optional) -n -t Enable detailed logging for the instance management commands. The location of the BMC Atrium Integration Engine installation directory. you need to use the command line prompt. The operating system on which the BMC Atrium Integration Engine is installed: Windows UNIX -ir (optional) The status of the instance (whether running) specified in the -inst parameter: ‘YES’—If running ’NO’—If not running This name is needed only for remote installations.6. Include the path up to the service subdirectory in the installation directory. Separate AIE hostname and Internal instance name with a comma. This name is needed only for remote installations.BMC Atrium Core 7.04 To enable logging when executing instance management commands. The internal name of the BMC Atrium Integration Engine instance. Combine the AIE hostname and Internal instance name.ARS_VM1-W23-PREM10(0)_EIE_VM1W23-PREM10_Inst_006. start. Example 1: Creating an instance aiexfer -CI -noi "1" -n "aie" -t 3 -l "Demo" -p "" -x "vm1-w23prem10" -a "VM1-W23-PREM10" -rpcport "0" -inst "ARS_VM1-W23PREM10(0)_EIE_VM1-W23-PREM10_Inst_006" -os "WINDOWS" -ir "No" -d Example 4: Deleting an instance aiexfer -DI -del "VM1-W23-PREM10." -l "Demo" -p "" -x "vm1-w23-prem10" -a "VM1W23-PREM10" -rpcport "0" -d Example 3: Stopping an instance aiexfer -STOP -stp "VM1-W23-PREM10. -stp Although the -path parameter is optional. and stop instance management commands. Combine the AIE hostname and Internal instance name. delete.Instance management issues Table 4-1: Aiexfer command line parameter descriptions (Sheet 2 of 2) Command -st Description For start operations. Otherwise. The following code constructs show examples of the aiexfer parameters to use with the create. For stop operations." -l "Demo" -p "" -x "vm1-w23-prem10" -a "VM1W23-PREM10" -rpcport "0" -inst "ARS_VM1-W23-PREM10(0)_EIE_VM1-W23PREM10_Inst_007" -d Chapter 4 BMC Atrium Integration Engine issues 59 .ARS_VM1-W23-PREM10(0)_EIE_VM1W23-PREM10_Inst_007." -l "Demo" -p "" -x "vm1-w23-prem10" -a "VM1W23-PREM10" -rpcport "0" -d Example 2: Starting an instance aiexfer -START -st "VM1-W23-PREM10.ARS_VM1-W23-PREM10(0)_EIE_VM1W23-PREM10_Inst_007. the BMC Atrium Integration Engine might use an incorrect installation directory value that is specified in the ATRIUMCORE_HOME environment variable. include it in the aiexfer command to specify the exact BMC Atrium Integration Engine installation directory. Separate AIE hostname and Internal instance name with a comma. Separate AIE hostname and Internal instance name with a comma. 6. see Table 3-1. open the EIE:BackUpLoadFlag form. 60 Troubleshooting Guide . The internal instance names of all host computers should be the same. For more information about how to use the instance management commands from the command line prompt. and IsPrimaryServer fields.04 Troubleshooting instance management issues Use the following procedure to troubleshoot instance management issues. All other host computers in the server group should have a value of “No” in the IsPrimaryServer field. The default value for the Timeout setting is 5 seconds.BMC Atrium Core 7. verify that the service is running. b Clear the Hide check box in the Properties dialog for the Internal Instance Name. 5 As a workaround.out log if you have enabled detailed logging. e Verify that only one of the host computers in the server group has the IsPrimaryServer flag is set to “Yes”. You can view the instance name and port number in the aiexferutil. d Verify that all host computers in the server group have the same values in the Internal Instance Name field. 4 From BMC Remedy User. perform the following steps: a From BMC Remedy Administrator. execute your instance management commands from the command line prompt.1. To troubleshoot instance management issues 1 Enable detailed logging for your instance management commands. go to AR System Administration Console > System > General > Server Information > Timeouts and increase the Process Timeout setting for the AR System server. 2 If you are connecting to the BMC Atrium Integration Engine service on a remote computer. 3 If you installed BMC Atrium Integration Engine in a server group. c From BMC Remedy User. Host. For more information about how to use the instance management commands from the command line prompt and how to enable detailed logging. open the AIE:BackUpLoadFlag form in Search mode and search for all BMC Atrium Integration Engine service instances. see Table 3. 8 Run the command that you noted in step 6. deactivate logging.. go to the Database Field Menus Console and click on the Refresh Table List button.. login name. For more information about using different adapters with BMC Atrium Integration Engine. 2 Select the Active Link logging option to activate client-side logging. go to the Bin subdirectory of your BMC Atrium Integration Engine installation directory... see the BMC Atrium Integration Engine 7." -od . -to. To troubleshoot the missing required tables and views 1 From BMC Remedy User.. go to Tools > Options > Logging. -ol .. SID." -os . -ar ". -ol .. <ACTL> Process: rlshelper -ax . 5 Search for the following string in the log file." -od . Alias. For information about populating a table or table fields from external datastores. the tables and views might not be populated.04 User's Guide." -ap "..." -os ..6. 10 In the command that you noted.. replace the password variable with a text string to verify that it is not an encryption issue.. and open the log file created." -ap ".." -al ". Chapter 4 BMC Atrium Integration Engine issues 61 .04 User's Guide.Rule Helper does not populate views and tables Rule Helper does not populate views and tables When you specify the connectivity parameters on the Database Field Menus Console of the Configuration tab and click the Load Tables & View Names button...... -op ". 3 From the Database Field Menus Console. -to <ACTL> Success NOTE The parameters displayed in the log file might vary depending on the adapter used. go to Tools -> Options -> Logging.6. 7 From the command prompt. such as incorrect values for the database name. 9 If the command runs successfully. see the BMC Atrium Integration Engine 7... In the bin directory you will find the rule helpers binaries. 4 From BMC Remedy User.. or password.... You should be able to view the Database Field Menus. -ar "... -op "." -al ". 6 Note the command that appears before the string: -ax ....... This issue might occur if the Rule Helper Utility encounters database connectivity problems or incorrect information. click the Load Tables & View Names button. BMC Atrium Core 7. To display newly added BMC Atrium CMDB attributes on the Data Field Mapping window 1 In BMC Remedy User. The attribute list on the Data Field Mapping table is refreshed. “Using logs to troubleshoot issues. For more information about AR System and BMC Atrium CMDB logging.6. If the function fails using the cmdbdriver program.04 User's Guide. Displaying new attributes in the Data Field Mapping window If you added an attribute for a class in BMC Atrium CMDB and the new attribute does not appear on the Data Field Mapping window. 5 Save the AIE:FieldNames form and open the specific mapping from the CI Class Mapping Console. 4 Delete the new attributes from the AIE:FieldNames form. perform the following steps. see the BMC Atrium Integration Engine 7. 2 Open the form in Search mode and click Search on the toolbar. If any of the BMC Atrium CMDB APIs fail. For more information about the BMC Atrium CMDB reserved port numbers. see Chapter 7. 3 Select the BMC Atrium CMDB class to which you added attributes. check for errors in the AR System server and BMC Atrium CMDB log file.” on page 93.6. 62 Troubleshooting Guide . open the Object List and search for the AIE:FieldNames form. confirm whether BMC Atrium Integration Engine is using any port numbers reserved for BMC Atrium CMDB.04 BMC Atrium Integration Engine RPC port error If you receive an RPC port error. verify that you can call the same function with the cmdbdriver program. clean the old AIE instances and ensure that the data exchanges point to the new AIE instances. select the new AIE instance. open the Object List and search for the AIE:backUpLoadFlag form. existing data exchanges may not run correctly as they may point to the old AIE instances. 2 Open the form in Search mode and click Search on the toolbar. 3 In the Instance Name field. 6 Repeat steps 2 through step 5 for each data exchange. To assign the correct instance to data exchanges 1 Open the AIE Console. Chapter 4 BMC Atrium Integration Engine issues 63 . To clean old AIE instance entries 1 In BMC Remedy User. 3 Delete the AIE instance entries belonging to the old AIE setup. 4 Click Save. and then upgrade BMC Atrium Integration Engine. To fix this issue.Data exchanges not running correctly after you upgrade BMC Atrium Integration Engine on BMC Remedy AR System Data exchanges not running correctly after you upgrade BMC Atrium Integration Engine on BMC Remedy AR System where the database was restored from another environment If you restore a BMC Remedy AR System database on a computer from another environment. 5 Click Close. Data exchanges are now executed correctly. 2 Select a data exchange and click Open. 4 Save and close the AIE:backUpLoadFlag form. BMC Atrium Core 7.04 64 Troubleshooting Guide .6. class form generation. The following topics are provided: Class form generation issues (page 66) Troubleshooting auditing issues (page 68) Federation issues (page 69) Data Visualization Form module issue (page 72) Data decompression issue in cmdbdriver (page 73) Verifying version information for BMC Atrium CMDB components (page 73) Business service CIs not available in the Service Catalog issue (page 74) Web services startup issue (page 75) Troubleshooting BMC Atrium Core configuration issues (page 75) Atrium Impact Simulator issues (page 78) BMC Atrium CMDB permission issues (page 79) Troubleshooting a failed data model change (page 80) Chapter 5 Other BMC Atrium Core issues 65 .Chapter 5 Other BMC Atrium Core issues This section provides troubleshooting information about miscellaneous issues. auditing. and federation interface issues. such as. permissions. open the Task Manager and click Processes. 3 Verify that the arcmdbd server process is running. Therefore. TIP To view the processes that are running on a Windows computer. 5 Verify that the record in the Application Pending form is deleted. see the BMC Atrium CMDB 7.6. 4 Examine the arerror. On UNIX. To troubleshoot CMDB Sync-UI issues 1 When you create a class in BMC Atrium CMDB. WARNING Do not open the updated forms in BMC Remedy Developer Studio when synchronization is in progress.04 Administrator's Guide. you might encounter errors. After the arcmdbd server process starts.6. it deletes the record. see the BMC Atrium CMDB 7. or corresponding BMC Atrium Core forms not created in the other application. such as a missing entry in the Application Pending form. verify that a record is created in the SHR:SchemaNames form.BMC Atrium Core 7. Use the following procedure to troubleshoot these issues.04 Class form generation issues This section provides troubleshooting information about the Sync-UI utility that enables you to synchronize forms in BMC Atrium CMDB with other BMC applications. 2 After you click the Update Asset UI button. Troubleshooting CMDB Sync-UI command issues When you synchronize the BMC Atrium Core class forms with the forms in other applications by using the Sync-UI command. type the ps -ef command at the UNIX prompt.log. For more information about generating forms for other applications. see “AR System server logging” on page 117.log file for any errors logged for the arcmdbd server process. The AR System server uses the Admin thread to open forms and perform the synchronization process.04 Administrator's Guide. you might encounter performance issues and the data in the forms might be incomplete. if you try to open forms during the synchronization process.6. For more information about generating forms for other applications. For more information about arerror. verify that a record is created in the Application Pending form. 66 Troubleshooting Guide . the SyncUI process finds fields defined by a categorization class on the parent form.log or arsql. However. indicate that the resulting UI form has a missing field. This log file is located in the program files\ARSystem\Arserver\db subdirectory of your installation directory. you might receive warnings as listed: {DATE TIME] [WARNING] [TID: 00000n] : Could not create Field: FIELD_NAME on form FORM_NAME on server: SERVER [DATE TIME] [WARNING] [TID: 00000n] : Message: Field does not exist on current form . 8 If the synchronization process was not successful. A log file using this naming convention is created when the user interface in the BMC Remedy Asset Management application is updated. which are recorded in the CMDBSynchronizedUI. On UNIX. You should not create these fields on the UI form because they are not defined by the super class.nnnnnnnn These warnings.Class form generation issues 6 Examine the output in the CMDBSynchronizeUI_integer. On Windows. view the arapi. You can enable the API and SQL logging options from the AR System Administration: Server Information > Log Files tab in BMC Remedy User. You can change their file names and location at any time. these logging options create the log files under the program files\ARSystem\Arserver\db subdirectory of your installation directory by default. 7 Verify that the libcmdb2asset. TIP If you do not see an “Application UI synchronization completed” entry in the log file. In such cases. you can safely ignore these warnings if the field meets the following conditions: The field does not correspond to an attribute defined by the superclass The field corresponds to an attribute defined by a categorization class. they are created under serverInstallationDirectory/db.log.log file.sl/. About warnings generated when synchronizing BMC Atrium CMDB forms with other BMC applications When you synchronize forms in BMC Atrium CMDB with other BMC applications.log file for detailed information about any errors that might have occurred. such as BMC Remedy Asset Management. the operation is still in progress.dll file is in the same directory as the arcmdb server process. Chapter 5 Other BMC Atrium Core issues 67 .sl/. 3 Examine the attributes that have the Audit Option set to either Audit or Audit and Copy.BMC Atrium Core 7. see the BMC Atrium CMDB 7. 2 Examine the cmdbengdebug. To troubleshoot Log Auditing issues 1 Verify that a log form is specified for the class. To troubleshoot Copy Auditing issues Verify that the audit form exists in BMC Remedy Developer Studio. the logging option creates the arfilter. This log file is located in the Program Files\BMC Software\ARSystem\Arserver\Db subdirectory of your installation directory. You can change the file name and location at any time.6. perform the following procedure to troubleshoot the issue. it means that the changes that you made to the class definitions are incorrect and auditing will not be performed for the class. they are created under serverInstallationDirectory/db. enable API logging.6. You can enable the filter logging options from the AR System Administration: Server Information > Log Files tab in BMC Remedy User. For information about how to use the auditing feature. 2 Verify that the qualification specified in the Qualification field on the Audit tab of the class executes with no errors.04 Troubleshooting auditing issues If you do not see any audit history for your class definitions even though you have configured the correct audit options.log file for any errors. To troubleshoot Audit form issues 1 In BMC Remedy User. 2 Verify that the audited values are saved in a Diary field. To troubleshoot other Auditing issues 1 Verify that the Audit Type field on the Auditing tab of the class is set to either Copy or Log. 3 Enable filter logging to save information about Log Auditing operations.04 Administrator's Guide. 68 Troubleshooting Guide . The audit form is created when you synchronize the class. If you encounter an error when saving an instance of the class. On UNIX. The naming convention of the form is classFormName_AUDIT.log file under the program files\ARSystem\Arserver\db subdirectory of your installation directory by default. On Windows. 3 To use the Run Process federation method successfully. Do not modify these class definitions because doing so might cause errors. Chapter 5 Other BMC Atrium Core issues 69 .CONFIG namespaces to store federated data.CORE. 3 Verify that the link that you specified displays the correct page. 2 In the Address list.6. Troubleshooting Launch Definition issues For information about federation and how to configure federation data. and supporting files are in place. Federation access method—URL 1 Open a browser and paste the value in the Access String field into the Address list. Federation access method—run process 1 Verify that the specified path works when you execute the process from the command line on the client system.04 Administrator's Guide. permissions. only use BMC Remedy User.Federation issues Federation issues This section provides information about troubleshooting federation issues. 2 Verify that the path. replace attribute parameters such as $Name$ with their values from the CI. see the BMC Atrium CMDB 7. NOTE BMC Atrium Core uses the classes in the BMC. BMC Atrium Core 7.6.04 RPC error when creating federation plug-in When you create a plug-in to connect to an external data source for retrieving federated data, you might encounter the following error: Exception while processing RPC call. java.io.IOException: An established connection was aborted by the software in your host machine at sun.nio.ch.SocketDispatcher.write0(Native Method) at sun.nio.ch.SocketDispatcher.write(Unknown Source) at sun.nio.ch.IOUtil.writeFromNativeBuffer(Unknown Source) at sun.nio.ch.IOUtil.write(Unknown Source) at sun.nio.ch.SocketChannelImpl.write(Unknown Source) at com.bmc.arsys.arrpc.nio.ArNioXdrTcpEncodingStream.streamFlush(Unkn own Source) at org.acplt.oncrpc.XdrTcpEncodingStream.flush(Unknown Source)... This error occurs when the external data source that you are connecting to (for example, the Oracle database) contains several tables and large volumes of data. To resolve this issue, add the following parameters to the ar.cfg (ar.conf) configuration file and restart the AR System server: Server-Plugin-Default-Timeout: 120—For the ardbc plug-in. Filter-Api-Timeout: 60—For the filter plug-in. If you encounter the plug-in error even after you add these entries to the AR System configuration file, increase the timeout period (in seconds) and retry until the issue is resolved. Troubleshooting federation plug-in loading issue When you create a federation plug-in using the Configure Repository Plugins And Adapters option in the Federation Manager, the Loaded column in the plug-in editor displays the status of the plug-in. A value of No in this column indicates that your plug-in did not load successfully. This issue might occur if you provided an incorrect user name and password, or an incorrect connection string. To troubleshoot plug-in loading issues. 1 After adding the plug-in, reopen the plug-in editor to refresh the plug-in status. If the plug-in loaded successfully, the Loaded column displays a value of Yes. 2 If the Loaded column displays a value of No, from the AtriumCore install Dir\Logs directory, open the AtriumPluginSvr.log file and check for errors. 70 Troubleshooting Guide Federation issues 3 Depending on the type of plug-in you created, open one of the following log files and check for errors: Federation-ar.log—If you created an AR System plug-in Federation-cmdbf.log—If you created a cmdbf plug-in Federation-jdbc.log—If you created a jdbc plug-in 4 After fixing the errors, restart the AR System server and the mid tier. 5 From the BMC Atrium Core Console, open the Federation Manager and check the status of the plug-in again. Troubleshooting federated data class issue You might receive validation errors (120186–120190), such as incorrect table or field mapping with the external data store when you create a federated data class. These issues can occur if the maximum length of the field in the external store does not match the field length in the federated data class or if the table name that you specified in the plug-in adapter is incorrect. NOTE If you are unable to create a federated data class, make sure that the plug-in for your data store is loaded. If the plug-in is not loaded, see “Troubleshooting federation plug-in loading issue” on page 70. To troubleshoot federated data class issues 1 Log in to the AR System driver program. For more information about logging in to the driver program, see the BMC Remedy Action Request System 7.6.04 C API Reference. 2 To retrieve a list of external schema candidates, type the glxsc command. 3 At the Schema Type prompt, type 5 and verify that the vendor table that you created is listed in the results. 4 To retrieve a list of external field candidates, type the gmxfc command. 5 At the Schema Type prompt, type 5. 6 At the Vendor name prompt, type the vendor name that you created. 7 At the Vendor table name prompt, specify the name of the table that you are mapping from the external data store. 8 Confirm that the properties of the external data store, such as the Field type, External Field Name, and Maximum length, are correct. The vendor table and field properties should match the class and attribute properties that you specified for the federated data class. Chapter 5 Other BMC Atrium Core issues 71 BMC Atrium Core 7.6.04 Troubleshooting invalid column lengths in federated classes with an IBM DB2 database Federation problems with an IBM DB2 database can occur under the following conditions: When creating a federated class that brings in data from a DB2 database, you create a federated relationship class to retrieve the data. In this federated relationship class, you create a qualification that relates the source class in the BMC Atrium CMDB to the federated class. For example, specifying 'Name' = $ComputerName$, creates a relationship between the Name field of the source class and the ComputerName field of the federated class. But when you are creating a query and the size of the field in the source class exceeds the field column length of the federated class, a DB2 error is returned. For example, your DB2 database has a field (FNAME) with a column length of 10 characters. If the field referenced in the source class exceeds 10 characters (as in 'BMC_Account_1' = Fed_Class.FNAME), the 10-character limit is exceeded and you see the following error: SQLCODE -302, Error: THE VALUE OF INPUT VARIABLE OR PARAMETER NUMBER IS INVALID OR TOO LARGE FOR THE TARGET COLUMN OR THE TARGET VALUE To troubleshoot federated data class issues Change the column width of the key attribute in the federated source to be equal to or greater than the comparable field in the source class. Data Visualization Form module issue If the Data Visualization Form module that you created and the BMC Atrium Core module use different versions of the same third-party open-source library, you might receive an error message. Because the BMC Remedy Mid Tier (mid tier) expects only the library versions that the BMC Atrium Core module uses, it generates an error message when it finds different versions. For example, you might have a Data Visualization Form module that uses the commons-lang version 2.1 third-party library for Apache Commons, which is different from the commons-lang version 2.4 that BMC Atrium Core uses. To avoid this issue, deploy only those versions of third-party libraries on the mid tier that BMC Atrium Core uses. 72 Troubleshooting Guide Data decompression issue in cmdbdriver Data decompression issue in cmdbdriver If you are using the cmdbdriver program to retrieve data in bulk and it returns a large chunk of data, you might receive an error message that states, Decompression has failed. For example, you might receive this error with cmdbdriver commands such as impdt and gli. The Decompression has failed error occurs when a result-set returned from the BMC Atrium CMDB database to the AR System server was too large to decompress. To resolve this issue, make sure that there is enough space available for the AR System server in the %TEMP% and %TMP% directories. Verifying version information for BMC Atrium CMDB components When troubleshooting issues with BMC Atrium Core or when contacting Customer Support at BMC, you might require version information, such as version number, and the build date and time of various BMC Atrium CMDB components. The version information for the BMC Atrium CMDB Java API is included in its Java archive (JAR) file. For the C API, you can view the version information from Windows Explorer. When you view the information on Windows, a message is displayed, as shown in Figure 5-1. Figure 5-1: API version information Chapter 5 Other BMC Atrium Core issues 73 cmdbapi76..jar. such as cmdbapi76.6.04 Viewing API version information You can view the BMC Atrium CMDB version installed in your environment by querying the SHARE:Application_Properties form.dll) and choose Properties from the menu. edit the value of ServiceType to make it appear. NOTE On Windows. and did not specify the ServiceType attribute. NOTE The version information for the C API is not available on UNIX systems.” Other BMC applications that create BMC_BusinessService CIs. This is because the Service Catalog displays only instances of BMC_BusinessService where the attribute is set to “BusinessService” or “TechnicalService. On Windows. 2 Type java –jar cmdbapi76. 4 The C API version number is displayed in the File Version field. as shown in Figure 5-1. such as Atrium Explorer and Service Model Editor. Business service CIs not available in the Service Catalog issue If you created a BMC_BusinessService CI using the Atrium Explorer or any other BMC application. To view Java API version information 1 Open a command-line window and navigate to the appropriate directory: Windows—Program Files\BMC Software\AtriumCore\cmdb\sdk\bin. 3 Click the Version tab. If an existing business service CI does not appear in the Service Catalog. To make sure that your BMC_BusinessService CIs appear in the Service Catalog. navigate to the sdk\bin subdirectory of your BMC Atrium Core installation directory. do not correctly set the value for ServiceType. you can view the version information for JAR files. by double-clicking the file. the CI might not be available in the Service Catalog.BMC Atrium Core 7. a message window is displayed.jar. 2 Right-click any DLL file (for example. UNIX—BMC Software/AtriumCore/cmdb/sdk/bin. 74 Troubleshooting Guide . To view C API version information 1 On Windows. use the Service Catalog to create them. deploy the BMC Atrium CMDB web service and the mid tier on separate application server instances. Troubleshooting a disabled Create button in Product Catalog Use this information if the Create button on the BMC Atrium Product Catalog Setup form is disabled. To resolve this issue. Troubleshooting BMC Atrium Core configuration issues These are common configuration issues that you might encounter with BMC Atrium Core. Chapter 5 Other BMC Atrium Core issues 75 . if you are running the BMC Atrium Console and the BMC Atrium CMDB web service on the same instance of Apache Tomcat.Web services startup issue Web services startup issue If you have installed web applications that use the BMC Atrium CMDB Java APIs on a single application server. you might not be able to run the BMC Atrium Core web services successfully. you might encounter this issue. For example. Contact your system administrator. To troubleshoot a disabled Create button You do not have the required permissions to create a BMC Atrium Product Catalog setup. Two web applications that use the same java classes to load native object libraries cannot coexist on an application server. unless the native object libraries are preloaded from a common location. If the entry is missing. some jar files might not have been installed.FILTERAPI. Successfully loaded Java Plugin BMC. 2 Verify the setting for Inline error handling: If set to Reject.log file.NORM. Verify that the dataset settings are not preventing the common data model update. If set to Accept. during normalization.6. Enable logging to see the error messages. the dataset is not configured correctly to create or update instances. the CMDB is updated even if there is a normalization error.ENGINE.BMC Atrium Core 7. To troubleshoot maximum number of records returned in Product Catalog 1 Open BMC Remedy User. 3 If the Normalization mode is set to Continuous.04 Troubleshooting maximum number of records returned in Product Catalog Use this information if you cannot view more than 1. 2 Run the Atrium Core installer again. 3 Clear the Limit Number of Items Returned check box and click OK Troubleshooting Normalization plugin not working properly Use this information if the Normalization plugin is not working properly. To troubleshoot Normalization plugin 1 In the ROOT\Software\AtriumCore\hostName\Logs\AtriumPlugin. select Tools > Options > Behaviors tab. the data model changes are not normalized. 2 From the Menu bar. verify that the event or time is configured.000 records at a time in any of the Product Catalog forms. 76 Troubleshooting Guide . search for the message. To troubleshoot normalization configuration 1 Click Dataset Configuration. and verify that the dataset is not set to Trusted. the CMDB is not updated if there is a normalization error. If the dataset is marked as Trusted. Troubleshooting normalization configuration Use this information if. <BMC. Chapter 5 Other BMC Atrium Core issues 77 .Troubleshooting BMC Atrium Core configuration issues Troubleshooting Normalization Engine initialization errors Use this information if the Normalization Engine generates errors during initialization. This issue might occur due to the following reasons: The User ID and Password that you specified for the AR System server are incorrect.stopped initializing. try to connect to the AR System server with a user User ID that does not have a password (for example.com/support/reg/remedy-compatibility-tables. 2 If the error occurred due to incorrect user name and password.FILTERAPI. the Demo user). 4 If you are not able to connect to the server.ENGINE>Initialization of NE is not done. When you start the AR System server after installing BMC Atrium Core. To troubleshoot Normalization Engine initialization errors Perform the following steps to resolve this issue: 1 Examine the neAPI. The Product Catalog version that you installed is not the latest.FILTERAPI. see http:// www.log: <BMC. 5 From the SHARE:Application_Properties form. This issue can also occur if the Normalization Engine is accessing another AR System server. For more information about Product Catalog version compatibility.html?c=n. 3 If the error occurred due to connection issues. The Normalization Engine is waiting for the AR System server to complete the start up process. Will try again after 2 minutes WARN ( ?:? ) .ENGINE>Maximum number of attempts reached while trying to initialize . it could not connect to the AR System server.NORM. your network might be down. verify that the AR System server is running using the Ping MS DOS command from the computer on which the Normalization Engine is installed. you might encounter the following error in the AtriumPlugin.NORM.log file for additional error details. Therefore.bmc. verify that the Product Catalog version that you have installed is the latest. log for port configuration errors: a Check for bind error for the port 1825. If the service is not running. Troubleshooting AR System server plug-in not responding When working with the Atrium Impact Simulator. b If a port conflict occurred. If the mcell process is not running. This issue occurs if the default port configured for the cell is unavailable or if you did not choose the Atrium Impact Manager option in the BMC Atrium Core installer. NOTE You do not need to restart the AR System server after you change the port number in the AIS:GlobalPreferences form.6. 78 Troubleshooting Guide . d From the Atrium install directory/AtriumCore/host name/ais/etc/ directory.04 Atrium Impact Simulator issues This section provides information about troubleshooting Atrium Impact Simulator issues. 2 Examine the ais_cell. c In the AIS Cell Port field.BMC Atrium Core 7. This issue occurs if the Atrium Impact Simulator plug-in is not available. the AR System server plug-in might not respond due to the following possible causes: If the Atrium Impact Simulator cell failed to respond or was configured incorrectly.d/S99ais start”.dir file. open the mcell. On UNIX Execute the ps -ef | grep mcell command to confirm if the mcell process is running. go to the command prompt and type net start “BMC Atrium Impact Simulator”. switch permissions to the appropriate user (root) prompt and type “/etc/rc2. from BMC Remedy User open the AIS:GlobalPreferences form. Atrium plug-in server failed to respond or was configured incorrectly. To troubleshoot the AR System plug-in server not responding issue 1 Verify if the Atrium Impact Simulator cell is running: On Windows Go to Start > Control Panel > Administrative Tools > Services and check if the Atrium Impact Simulator service is running. specify a different port number. BMC Atrium CMDB permission issues e In the cell ais ais 127. you might encounter issues with accessing data by using the BMC Atrium Core Console. Solution Make sure that you have CMDBRowLevelSecurity access. verify with your system administrator that you have the required role and permissions. Table 5-1: Troubleshooting permissions issues in BMC Atrium CMDB (Sheet 1 of 2) Error description Can view the class in the list of objects. you must have the Atrium Impact Simulator User role and the permissions to query the CIs stored in BMC Atrium CMDB. 3 Verify if the Atrium Impact Simulator cell is correctly configured: a In BMC Remedy User. such as classes not being visible in the list of objects.0. Make sure that you have the CMDB Data Change and CMDBWriteSecurity access Chapter 5 Other BMC Atrium Core issues 79 . Can view the class in the list of objects. b If the Atrium Impact Simulator cell is not configured to the default host and port values. c On the AIS:GlobalPreferences form. The role and the permissions are mapped to the CMDB Data View group by default. If no instances of the form exist. change the port number to what you specified in the AIS:GlobalPreferences form. The value in the Test Results field changes to Success if the test was successful. and can view the instance. f Restart the Atrium Impact Simulator cell.6.0.1:portNumber entry. with its attributes. create instance of the AIS:GlobalPreferences form. search for an instance of the AIS:GlobalPreferences form. with its attributes. but cannot view the instances of the class. cannot modify the instances of the class. the Atrium Impact Simulator cell uses the default host and port number of localhost and port 1825. click the Test button to verify if the host and port number are configured correctly. If you encounter a permissions issue with Atrium Impact Simulator. Atrium Impact Simulator permissions issue To view data and to work with the CIs in Atrium Impact Simulator. For more information about BMC Atrium CMDB permissions. Table 5-1 lists various scenarios in which you might encounter a permissions issue and provides information about how to resolve the issue. see the BMC Atrium CMDB 7.04 Administrator's Guide. BMC Atrium CMDB permission issues When working with BMC Atrium CMDB. the the a Solution Make sure that you have CMDBWriteSecurity access. Can view the class in list of objects. Can view the class in list of objects. Make sure that you have the Attribute View permission.BMC Atrium Core 7. Make sure that you have CMDB Data Change role and CMDBWriteSecurity access. objects.04 Table 5-1: Troubleshooting permissions issues in BMC Atrium CMDB (Sheet 2 of 2) Error description Can view the class in the list of with its attributes.6. but cannot modify the instance data by using workflow started in another class. enable the AR System server API logging. Make sure that you have the CMDB Data View role and Visible permission for the class. open your application server log file (for example. and can view instances of the class. modifying instances of the class results in permissions error. Cannot view the class in list of objects. 80 Troubleshooting Guide .log and the cmdbengdebug.log for Apache Tomcat). catalina. and Change permission for the attribute. your changes might not have been saved to your data model. 2 From BMC Remedy Developer Studio. To troubleshoot a failed data model change 1 From the mid tier. but cannot view the attributes of the class. Troubleshooting a failed data model change If the class or the attribute that you modified in the Class Manager displays a Change Pending icon or if its status changes to Error. The BMC Atrium Core API calls and their results are written to the arapi.log and stdout. CMDB Data Change role.log files. You can view and troubleshoot issues with your data model by using the cmdbdiag program and by using manual steps. The following topics are provided: Verifying your data model using the cmdbdiag program (page 82) Working with the CI and Relationship Correction Tool option (page 84) Verifying your data model manually (page 90) Chapter 6 Data model issues 81 .Chapter 6 Data model issues This chapter provides instructions about verifying your data model. BMC Atrium Core 7. To start the cmdbdiag program 1 Navigate to the appropriate location where you copied the cmdbdiag program and perform the following step: On Windows. Troubleshooting invalid relationships Check for invalid relationships—relationship instances that point to nonexistent CI instances or relationships that contain incorrect endpoint information. type cmdbdiag. Accessing the cmdbdiag program When you launch cmdbdiag. 3 At the Data Integrity Checker prompt. The cmdbdiag program Main Menu appears. On UNIX. provide your BMC Remedy AR System login credentials for the computer hosting BMC Atrium Core.exe. such as incorrect dataset ID or class ID.6. To troubleshoot invalid relationships 1 Start the cmdbdiag program. double-click cmdbdiag.04 Verifying your data model using the cmdbdiag program The cmdbdiag program is a command-line tool. 82 Troubleshooting Guide . Working with the Data Integrity Checker option The Data Integrity Checker validates BMC Atrium CMDB for the various issues based on the menu option you choose. type 1. which is located in the server\bin directory of your BMC Atrium Core installation. type 1. see “Accessing the cmdbdiag program” on page 82. For information about starting the cmdbdiag program. it creates a report that contains information about the invalid relationship instances and datasets. log in to the AR System server. If the Data Integrity Checker finds invalid data. 2 At the Main Menu prompt. 2 From the initial screen for the cmdbdiag program. This program allows you to check for any invalid data in BMC Atrium CMDB and correct it. the program saves the report file in the same directory as the cmdbdiag program.txt). 2 At the Data Integrity Checker prompt. If you manually enter a name. 2 At the Main Menu prompt. type 2. Chapter 6 Data model issues 83 . If you enter a file name manually. type y.txt). For information about starting the cmdbdiag program. specify an absolute path for the file (for example. Otherwise. or press Enter to accept the default file name. Otherwise. A dataset ID might be incorrect if it refers to: A nonexisting dataset Contains a value of 0 or NULL To troubleshoot invalid dataset IDs 1 Start the cmdbdiag program. 3 At the Data Integrity Checker prompt. press Enter and provide a dataset ID. see “Accessing the cmdbdiag program” on page 82. To view invalid relationships for a specific dataset.Verifying your data model using the cmdbdiag program 4 At the All datasets [y . perform the appropriate action: To view invalid relationships for all datasets. For information about starting the cmdbdiag program. see “Accessing the cmdbdiag program” on page 82. Troubleshooting invalid dataset IDs Check for invalid dataset IDs—Incorrect dataset IDs specified for CI and relationship instances. Troubleshooting invalid CI relationships Check for relationship cardinality issues—invalid relationships that are caused by a violated relationship cardinality. type 1.n] (n) prompt. type 3. the program saves the report file in the same directory as the cmdbdiag program. C:\DIC_Invalid_Relationships. you must specify an absolute path for the file (for example: C:\dataset_ids. 4 Specify a name for the output file or press Enter to accept the default file name. which occurs when a relationship between CI classes does not fall into one of the following categories: One to one One to many Many to one To troubleshoot invalid CI relationships 1 Start the cmdbdiag program. 5 Enter a name for the output file. see “Accessing the cmdbdiag program” on page 82. if you reset the IDs of BMC_ComputerSystem instances. You might need to reset reconciliation IDs of CIs in your source or destination dataset if they are identified incorrectly or if your reconciliation rules are configured incorrectly. 2 At the Main Menu prompt. type 2. To reset reconciliation identities 1 Start the cmdbdiag program. 84 Troubleshooting Guide . To check for relationship cardinality issues for a specific dataset. Otherwise.txt). test_cardinality. Step 5 To exit the Data Integrity Checker option. 3 At the CI and Relationship Correction Tool submenu prompt.04 3 At the All datasets [y . you must specify an absolute path for the file (for example. 4 Specify a name for the output file or press Enter to accept the default file name. Resetting reconciliation identities This procedure resets reconciliation IDs to 0. type 1. type y. C:\DIC_Cardinality.txt. IDs of component instances related to weak relationships are also reset. Working with the CI and Relationship Correction Tool option The CI and Relationship Correction Tool option provides options to clean up data in BMC Atrium CMDB. the program saves the report file in the same directory as the cmdbdiag program. the IDs of components (such as BMC_DiskDrive and BMC_Monitor) that are related to those instances through BMC_HostedSystemComponents relationships are also reset. perform the appropriate action: To check for relationship cardinality issues for all datasets.BMC Atrium Core 7. which allows the Reconciliation Engine to assign correct reconciliation IDs during the next reconciliation process. type 4. For information about starting the cmdbdiag program.6. For example.n] (n) prompt. press Enter and provide a dataset ID. If you enter a file name manually. When you reset reconciliation IDs by using the By Class option. Working with the CI and Relationship Correction Tool option 4 At the By dataset or class prompt. To troubleshoot invalid relationship instances 1 Start the cmdbdiag program. 2 Log in to the AR System server and type 2 at the Main Menu prompt. Enter the namespace within which the class exists. 2 For information about starting the cmdbdiag program. 3 At the CI and Relationship Correction Tool submenu prompt. their relationships are also deleted automatically to maintain data integrity. Correcting invalid relationship instances Use this procedure to delete relationships for which either of the CI endpoints does not exist. see “Accessing the cmdbdiag program” on page 82. press Enter and provide a dataset ID. Enter the name of the class. To delete instances in a dataset 1 Start the cmdbdiag program. or press Enter to reset the reconciliation ID for specific instances. If you are resetting IDs for all instances in the class. If you are resetting IDs for specific instances. type y to reset reconciliation identities Deleting instances in a dataset Use this procedure to delete instances that you no longer need (for example.n] (n) prompt. perform the appropriate action: To delete instances in all datasets. Enter the ID of the first instance for which you want to reset the reconciliation ID and follow the prompts to specify each instance that you want to reset. skip to the next step. press Enter and provide a dataset ID. When deleting instances. type class. perform the appropriate action: To reset reconciliation IDs in all datasets. For information about starting the cmdbdiag program. enter the number of instances for which you want to reset the reconciliation IDs. type y. To reset reconciliation IDs in a specific dataset. Chapter 6 Data model issues 85 . 5 At the Do you want to continue prompt.CORE. 4 At the All datasets [y . type 2. Type y to reset reconciliation IDs for all instances of the class. To delete instances in a specific dataset. and reconciliation ID. or press Enter to accept the default value of BMC. dataset ID. see “Accessing the cmdbdiag program” on page 82. the program can correct the class ID. For each endpoint of a relationship instance. datasets created in a test environment). For information about starting the cmdbdiag program. the program saves the report file in the same directory as the cmdbdiag program. To correct invalid relationship instances in a specific dataset. If you enter a file name manually. perform the appropriate action: To delete orphan relationship instances in all datasets. 5 At the All datasets [y . Otherwise. or press Enter to accept the default file name. 3 At the CI and Relationship Correction Tool submenu prompt. If you enter a file name manually. type 4. 86 Troubleshooting Guide . 6 At the Do you want to continue prompt. type 2. see “Accessing the cmdbdiag program” on page 82. 7 At the Do you want to continue prompt. press Enter and provide a dataset ID. you must specify an absolute path for the file (for example. To delete orphan relationships 1 Start the cmdbdiag program. To delete orphan relationship instances in a specific dataset. 2 Log in to the BMC Remedy AR System server and at the Main Menu prompt. press Enter and provide a dataset ID. type y to delete orphan relationships. 4 At the All datasets [y . 6 Enter a name for the output file.04 3 Log in to the BMC Remedy AR System server and at the Main Menu prompt. C:\DeleteOrphanedRelsReport. type y.6. Deleting orphan relationships Use this procedure to delete relationships that might have nonexistent CI endpoints. or press Enter to accept the default file name.n] (n) prompt. 4 At the CI and Relationship Correction Tool submenu prompt. you must specify an absolute path for the file (for example.txt). 5 Enter a name for the output file.n] (n) prompt. type y. type 2. Otherwise. the program saves the report file in the same directory as the cmdbdiag program. C:\CorrectRelationshipsReport. perform the appropriate action: To correct invalid relationship instances in all datasets. type y to correct invalid relationships.txt).BMC Atrium Core 7. type 3. one-to-many. type 5. Deleting instances for a given class Use this procedure to delete instances of a class altogether to clean up data.txt). The automatically delete option deletes instances based on their create date and time. When you delete instances of a given class. For information about starting the cmdbdiag program. If you type n at the prompt. 7 Enter a file name for the output file. or press Enter to accept the default file name. The violated instance that is created most recently will be deleted.xml in the current directory. If you enter a file name manually. 5 If you want to delete all the instances in violation automatically. press Enter and provide a dataset ID. To delete relationships that violate cardinality 1 Start the cmdbdiag program. n] (n): prompt. the program saves the report file in the same directory as the cmdbdiag program. Chapter 6 Data model issues 87 . 2 Log in to the BMC Remedy AR System server and at the Main Menu prompt. Otherwise. For information about starting the cmdbdiag program. 3 At the CI and Relationship Correction Tool submenu prompt. perform the appropriate action: To delete violated cardinality relationships in all datasets. see “Accessing the cmdbdiag program” on page 82. C:\FixCardinalityViolations. press Enter to accept the default value of n. type 2. type y at the Do you want to automatically delete all instances ? [y. the orphaned weak relationship is also deleted to maintain data integrity. A copy of the deleted instance is saved in an XML file called <instanceId>. you must specify an absolute path for the file (for example. An XML backup is generated. To delete violated cardinality relationships in a specific dataset. 6 Type y again to confirm automatically deleting all instances in violation. 4 At the All datasets [y . see “Accessing the cmdbdiag program” on page 82. To delete instances for a given class 1 Start the cmdbdiag program.Working with the CI and Relationship Correction Tool option Deleting relationships that violate cardinality Use this procedure to delete relationships that might have violated the one-to-one. type y. Otherwise. or many-to-one cardinality. the list of violated instances is displayed and you are prompted for confirmation before deleting each instance.n] (n) prompt. When you correct a weak member. a At the All datasets [y .04 2 At the CI and Relationship Correction Tool submenu prompt.6. If you correct orphaned weak relationships of a specific class in any dataset. see “Accessing the cmdbdiag program” on page 82. To correct orphaned weak members 1 Start the cmdbdiag program. type 7. If you want to correct orphaned weak relationship members for a specific class. 4 At the Fixing Orphaned Weak Members menu. To delete instance for a class in a specific dataset. only the instances of that specific class are corrected. For orphaned weak members. 4 Enter the namespace name of the class for which you want to delete all instances.BMC Atrium Core 7. attributes of orphaned instances of all classes are set to NULL. type y to correct orphaned weak members in all datasets. type 6. you are prompted to choose to fix or delete the weak member. 88 Troubleshooting Guide . Correcting orphaned weak members A weak member of a weak relationship is orphaned when you delete a strong member and leave the weak member of the composite relationship pointing to a nonexistent CI instance. If you correct orphaned weak relationships for all datasets. b At the Do you want to continue prompt. For orphaned weak relationships. If you type n at the prompt.n] (n) prompt. 3 At the All datasets [y . 5 Enter the class name to which the instances that you want to delete belong. type y. 3 At the CI and Relationship Correction Tool submenu prompt. 6 At the Do you want to continue prompt. you are prompted to choose to delete the weak relationship. skip to step 5. type y. type y to delete all instances of the specified class. press Enter and provide a dataset ID. perform the appropriate action: To delete instance for a class in all datasets. the CI and Relationship Correction Tool submenu is displayed. 2 Log in to the BMC Remedy AR System server and at the Main Menu prompt. For information about starting the cmdbdiag program. type 1 to correct orphaned weak members in all datasets. type 2. it remains in the BMC Atrium CMDB as an independent CI instance with no relationships. You can correct an orphaned weak member of a weak relationship by setting NULL values for the attributes that are propagated from the strong member.n] (n) prompt. Chapter 6 Data model issues 89 . a At the All datasets [y . type y to delete orphaned weak members in all datasets. b To correct orphaned weak members in a specific dataset. type y to delete orphaned weak members in all datasets. type 2 to delete orphaned weak members for a specific class. type 8. skip to step 5. Deleting orphaned weak members Use this procedure to delete an orphaned weak member of a weak relationship.Working with the CI and Relationship Correction Tool option c To correct orphaned weak members in a specific dataset. press Enter and provide a dataset ID. a At the All datasets [y . b To delete orphaned weak members in a specific dataset. 5 At the Deleting Orphaned Weak Members menu. 3 At the CI and Relationship Correction Tool submenu prompt. 2 Log in to the BMC Remedy AR System server and at the Main Menu prompt. press Enter and provide a dataset ID. type 1 to delete orphaned weak members in all datasets. type y. a At the All datasets [y . press Enter and provide a dataset ID. 5 At the Fixing Orphaned Weak Members menu.n] (n) prompt. type 2. b At the Do you want to continue prompt. type y to correct orphaned weak members in all datasets. c To delete orphaned weak members in a specific dataset. 4 At the Deleting Orphaned Weak Members menu. d Enter the class name to which the orphaned weak members that you want to correct belong. To delete orphaned weak members 1 Start the cmdbdiag program. A weak member of a relationship is orphaned when you delete a strong member and leave the weak member of the composite relationship pointing to a nonexistent CI instance.n] (n) prompt. press Enter and provide a dataset ID. If you want to delete orphaned weak relationship members for a specific class. For information about starting the cmdbdiag program. c Enter the namespace name of the class for which you want to correct all orphaned weak members. see “Accessing the cmdbdiag program” on page 82.n] (n) prompt. type 2 to correct orphaned weak members for a specific class. For more information about cmdbengdebug.log. The following example shows the error message that you might view in arerror. it means that those classes were either not properly created or were not properly deleted. To manually verify your data model 1 Examine the arerror.04 c Enter the namespace name of the class for which you want to delete all orphaned weak members. 3 Perform the following steps to verify that all attributes for the classes are Active. b Choose File > Open Object List. c Choose View > Advanced Search Bar. Super Class ID: OB005056C00008F1V3RQd#IYAAD90C (ARERR 120132) For more information about arerror. b Choose View > Advanced Search Bar. When the cmdbEngine is started. Search for the string cmdbEngine to find errors. see “AR System server logging” on page 117.log. Verifying your data model manually Perform the following steps to verify that the class definitions in your data model are correct. e Check the classes listed in the result window to investigate the issue. specify the following query: 'OSStatus' != "Active" OR 'Pending ID' != "0" OR 'System Status*' != "Active" OR 'Record Status' != "Active" OR 'Status' != "Active" If this query returns any rows.log and cmdbengdebug. see “Server-side API logging” on page 96.log: Mon Dec 11 16:10:18 2006 390600 : The specified super class with given classId is not found. a From BMC Remedy User. : Class ID: OB005056C00008PlV3RQU3oZAAHO8C. it validates the class definitions. 2 Perform the following steps to verify that all classes in your data model are active: a Log in to BMC Remedy User as an administrator. d Enter the class name to which the orphaned weak members that you want to delete belong.BMC Atrium Core 7. and open the Attribute Definitions form in Search mode. and open the OBJSTR:Class form in Search mode. choose File > Open Object List.log files for any errors about starting the cmdbEngine.6. d In the Advanced Search Bar at the bottom of the window. 90 Troubleshooting Guide . 6 Accept default values for all prompts displayed for this command. verify that the cmdbEngine is running.Verifying your data model manually c In the Advanced Search Bar at the bottom of the window.6. see the BMC Atrium Core 7. Chapter 6 Data model issues 91 . 4 Run cmdbdriver from the server. A list of classes is displayed. it means that those attributes were either not properly created or not properly deleted. This error might also occur if the class definitions in the your data model are incorrect. specify the following query: 'OSStatus' != "Active" OR 'Pending ID' != "0" OR 'Record Status' != "Active" If this query returns any rows.04 Developer’s Reference Guide. NOTE If the cmdbdriver program generates an AR 91 RPC call failed error. 5 Type the glc command to get the list of classes. For information about using the cmdbdriver program. 6.04 92 Troubleshooting Guide .BMC Atrium Core 7. Chapter 7 Using logs to troubleshoot issues This section provides logging and debugging information for BMC Atrium CMDB. BMC Atrium Integration Engine. and AR System server. The following topics are provided: BMC Atrium Core Console client-side logging (page 94) BMC Atrium Core Console server-side logging (page 95) BMC Atrium CMDB logging (page 96) BMC Atrium Integration Engine logging and debugging (page 104) Atrium Impact Simulator logging (page 114) Normalization Engine logging (page 116) AR System server logging (page 117) Bundling the BMC Atrium Core log files (page 118) Chapter 7 Using logs to troubleshoot issues 93 . For example.txt file. you might find intermixed log messages from both these instances.04 BMC Atrium Core Console client-side logging BMC Atrium Core logs the BMC Atrium Core Console client-side processing in the flashlog. which helps you to debug user interface errors.6. To log the client-side processing.html 2 In the lower-right corner of the Adobe Flash Player movie that is displayed. NOTE The Adobe Flash Player log combines messages from all its instances running on your computer. The BMC Atrium Core Console requires a minimum of Adobe Flash Player version 9 to run. click I and scroll the information to see the Adobe Flash Player Debugger version information. 0. If the version you determined using each method differs.com and BMC Atrium Core each on the same computer. 94 Troubleshooting Guide . Figure 7-1: Determining Adobe Flash Player Debugger version Using this component BMC Atrium Core Console Perform these steps Right-click inside the BMC Atrium Core Console and select About Adobe Flash Player version. The version of the Adobe Flash Player installed is displayed.com/devnet/flex/ articles/client_debug_02. uninstall all versions of the Adobe Flash Player Debugger and install again. 14. In such a case. install and configure the 7.adobe. Determining Adobe Flash Player Debugger version Use the following methods to determine the version of the Adobe Flash Player Debugger that you have installed. but this will not distinguish between the release and debug player.BMC Atrium Core 7. 112 or newer version of Adobe Flash Player Debugger. the debug logging might encounter issues. if you were running two instances of Adobe Flash Player with CNN. Adobe website 1 Go to http://www. 6. Windows 2000. error. the following files are copied to the webapps directory of your installation for the client-side logging: Readme.txt—Contains information about downloading.BMC Atrium Core Console server-side logging Configure your Adobe Debug Flash Player Debugger When you install BMC Atrium Core. mm. for an Apache Tomcat application server installed on the mid tier.macromedia/Flash_Player/ Logs/ Each entry in the log provides the following details: Timestamp—The date and time of the log entry. Mid tier logs are located in the AR SystemServerInstallation/mid tier/logs subdirectory of the AR System installation. Windows ME. see the BMC Remedy Action Request System 7. see “BMC Atrium Core web services deployment logs” on page 102. Message—The message for the log entry. The mid tier log file location depends on the application sever that you have installed.txt file for your operating system.04 Mid Tier Guide.log file. as listed in Table 6-1. Windows XP Windows Vista Apple Macintosh OS X Linux Log file location C:\Documents and Settings\userName\Application Data\Macromedia\Flash Player\Logs C:\Users\username\AppData\Roaming\ Macromedia\Flash Player\Logs /Users/username/Library/Preferences/ Macromedia/Flash Player/Logs/ /home/username/.txt log file depends on your operating system. and configuring the Adobe Flash debugger.cfg—Contains the configuration information to enable logging on the client side. Copy this file to the location specified in the readme. Table 7-1: Log file location by operating systems Operating system Windows 95. For more information about application server logging. Chapter 7 Using logs to troubleshoot issues 95 . or information. Windows 98. For more information about mid tier logging. the log is stored in the AR SystemServerInstallation/tomcat/logs/stdoutdate. For example. Log Type—The type of log entry such as warning. installing. BMC Atrium Core Console server-side logging The BMC Atrium Core Console server-side processing is recorded in the mid tier and application server logs. The location of the flashlog. graph query. This the default logging level. warning. which helps you to debug your API program. Server-side API logging BMC Atrium CMDB logs the engine processing in the cmdbengdebug.log file. the BMC Atrium CMDB records details about operations. 96 Troubleshooting Guide .04 Developer’s Reference Guide. if you need finer logging you can still set the logging level to 5. The logging levels are inclusive of their preceding levels. which are used for debugging errors. see “C API functions” and “C API data structures” in the BMC Atrium Core 7. If you attempt to lower the debug logging level to 1. NOTE The CMDB Engine logs all warnings and error messages by default. 2. or information. and 3. 5: Detail—Logs additional details for the errors. add CMDB-DebugLevel: loggingLevel to the configuration file and restart the AR System server.BMC Atrium Core 7. 2: Warning—Logs messages for warnings. Each entry in the log provides the following details: Timestamp—The date and time of the log entry. such as the APIs. For example. Message—The message for the log entry. The BMC Atrium CMDB Engine classifies the messages into error. depending on your platform: CMDB-Debug-Level—Specifies the level of logging that you require for your API calls. you receive log messages for levels 1. However. When you enable logging.6. Class Manager. You can specify the following additional parameters for the logging option in the ar. The debug levels are: 1: Error—Logs messages for fatal or severe errors. if you set the debug level to 3. and web services. Log Type—The type of log entry: warning. To set the debug logging to a different level. 4: Trace—Logs trace messages. the cmdbEngine automatically updates it to 2. and information categories. such as SynchMetaData. error. These levels determine the types of messages that are logged for the calls. and export and import. For more information about related API functions.cfg (ar. This is the highest level of logging.6. 3: Information—Logs informational messages. The engine logging is enabled by default and the CMDBDebug-Flag parameter is ignored. Reconciliation Engine.conf) configuration file.04 BMC Atrium CMDB logging This section contains logging information about the various BMC Atrium CMDB components. BMC Atrium CMDB logging CMDB-Log-File-Location—Enables you to specify the directory location on your system where the log file is written. You can specify any location on your system. On Windows, the log file is written to the Program Files\ARSystem\Arserver\db subdirectory of your installation directory by default. On UNIX, it is created under serverInstallationDirectory/db. CMDB-Max-Log-File-Size—Enables you to specify a maximum size, in kilobytes (KB), for your log file (for example, CMDB-Max-Log-File-Size: 50000). When the log file reaches the specified limit, the system automatically creates a backup of the log file and continues to store the log entries in a new log file. The default value for the CMDB-Max-Log-File-Size parameter is 0, which specifies an unlimited size for the log file. Java API logging The BMC Atrium CMDB Java API processing is logged in the log4j_cmdbapi.xml file, which helps you to debug your Java API program. When you enable logging, the BMC Atrium CMDB records details about the Java calls you make in your program, including the list of the calls, the input arguments, and the return values for each call. To enable logging, copy the log4j_cmdbapi.xml file from the cmdb\sdk subdirectory of your installation directory and paste it to a location on your local drive. After you copy the log file to the new location, add the directory path to the Java class path. The BMC Atrium CMDB Java API classifies the messages into error, warning, information, and debug categories. The logging levels are inclusive of their preceding levels. For example, if you set the debug level to 3, you receive log messages for levels 1, 2, and 3. 1: Fatal—Logs messages for severe errors that cause premature termination. 2: Error—Logs messages for other runtime errors or unexpected conditions. 3: Warning—Logs messages for incorrect usage of the API calls. The runtime issues that are logged might be incorrect but not wrong. This is the default logging level. 4: Information—Logs informational messages, such as the list of Java calls made by the client. 5: Debug—Logs details for the calls, such as the list of arguments and the return values for each call. 6: Trace—Logs finer level of details for debugging errors. Each entry in the log provides the following details: Timestamp—The date and time of the log entry. Log Type—The type of log entry: fatal, warning, error, information, or debug. Message—The message for the log entry. Chapter 7 Using logs to troubleshoot issues 97 BMC Atrium Core 7.6.04 To change the logging level for Java API, set the value element with the appropriate setting for the com.bmc.cmdb.api logging component. For more information about BMC Atrium CMDB Java logging, see http:// logging.apache.org/log4j/1.2/. Java API configuration properties If you notice that the server response time is slow when executing your Java program, you can modify the timeout properties in the cmdbapi_sample.properties Java API configuration file. The configuration file is located in the sdk\bin subdirectory of your BMC Atrium Core installation directory. You can configure the following properties in the configuration file: minimumSupportedServerCMDBRpcVersion—the minimum CMDB RPC Version supported by JAVA API. The default value is 3. maxCMDBProxiesPerServer—the maximum number of CMDB Proxy connections that you can specify per server. The default value is 100. timeoutNormal—the time out value in seconds for the server. You can specify values for the timeoutLong and timeoutXLong parameters for an extended time out time for the server. timeoutCMDBMetaData—the time out value for meta data operations. The default value is 259200 seconds. To override the default values: 1 Rename the cmdbapi_properties.sample file to cmdbapi.properties. 2 Modify the configuration properties in the file as appropriate. 3 Place the cmdbapi.properties file in the directory that is specified in the Java ClassPath. For more information about related Java API functions, see the BMC Atrium CMDB 7.6.04 Javadoc Help. 98 Troubleshooting Guide BMC Atrium CMDB logging Reconciliation Engine logging The Reconciliation Engine logs all activities that it performs: Identification, Compare, Merge, Delete, and Purge. A log file for a job is created each time the Reconciliation Engine runs that job. The Reconciliation Engine logging is enabled by default. Each entry in the log provides the following details: Timestamp—The date and time of the log entry. Log Type—The type of log entry: Error—Logs detailed messages for errors and warnings (default). Info—Logs class-level details, such as dataset name and class name. Debug—Logs trace messages, which are used for debugging errors. All these logging levels are inclusive of their preceding levels. For example, if you set the Logging Level at Debug, you receive log messages for Error, Info, and Debug types. You can specify the Logging Level for the log files from the Modify Server Configuration window of the Reconciliation Engine Console. Message—The message for the log entry. You can specify additional settings for the log files in the Modify Server Configuration window of the Reconciliation Engine Console. For more information about these settings, see the BMC Atrium CMDB 7.6.04 Normalization and Reconciliation Guide. Log file naming convention The Reconciliation Engine log files use the following naming convention: jobName_ctr.log jobName is the name of the job that you created in the Reconciliation Manager (for example, BMCAsset - Identification and Purge). <ctr> is a numeric value that starts from 1 and is incremented when a new log file is created for the job run. The Reconciliation Engine continues to log errors in a new log file when an existing log reaches its size limit. For example, if multiple files are created for the BMCAsset - Identification and Purge job run, the job log files will be named as: BMCAsset - Identification and Purge_1.log BMCAsset - Identification and Purge_2.log Viewing Reconciliation Engine events in the log file When the log file for the Reconciliation Engine job is created, an event associated to the job is added to the Reconciliation Engine Console. This event contains the job file name and location. Chapter 7 Using logs to troubleshoot issues 99 BMC Atrium Core 7.6.04 To view the event for the log 1 Log in to the CMDB Console with BMC Remedy User. For information about logging in to the CMDB Console, see the BMC Atrium CMDB 7.6.04 User's Guide. 2 Click the Reconciliation Manager tab. 3 From the navigation link on the left, click Job History. The Job History Console is displayed. 4 From the Jobs table on the top of the window, choose the specific job. The Related Runs table is populated with the run status of the job. 5 Select the specific job run for the job. The Related Events table is populated with event information for the job. 6 Click the RE Log File & Location event and click View. The Job Event Information window is displayed. 7 Click the Diary field to view the log file path information. Interpreting entries in the log file The Reconciliation Engine is a multithreaded program with all threads writing to the same log file. The log files are divided by activity names. Each of these activities has a start or run entry, indicating the start of the activity, and an end or completed entry indicating the end of the activity. The following examples illustrate both these entries. Example 1: Starting an activity [Tue Apr 24 2007 12:07:15.0067] [ INFO ] [TID: 000011] : Running activity: BMC Topology Import - Identification Activity Example 2: Ending an activity [Tue Apr 24 2007 12:10:08.4748] [ INFO ] [TID: 000011] : Activity completed: BMC Topology Import - Identification Activity Each entry contains a thread ID (TID) that identifies a unique activity. If multiple instances need to be identified, the Reconciliation Engine creates separate threads for each instance identification. Therefore, the log file contains mixed entries for various threads instead of having one section for each thread. The following code is an example of a Reconciliation Engine log file. [2007/03/30 10:35:36.1370] [DETAILS] [TID: 003720] : Started waiting for all the threads to finish [2007/03/30 10:35:39.7710] [DETAILS] [TID: 002696] : Started identifying instance <class = QA_Patch2_No_Ident_Multi_Match: Patch2_1Class_No_Ident_Multi_Match, id = ID00087492D05D8nFOQw8SSKBAawAA> 100 Troubleshooting Guide 1310] [ ERROR ] [TID: 002696] : Cannot identify the instance of class <QA_Patch2_No_Ident_Multi_Match:Patch2_1Class_No_Ident_Multi_Match > with instance id <ID00087492D05D8nFOQw8SSKBAawAA> in dataset <Data Set 02> [2007/03/30 10:35:40.7810] [ ERROR ] [TID: 002696] : Found multiple matches (instances) for class <QA_Patch2_No_Ident_Multi_Match:Patch2_1Class_No_Ident_Multi_Match > in look-up dataset <Data Set 01> [2007/03/30 10:35:39.6720] [DETAILS] [TID: 003720] : Finished waiting In this example. Chapter 7 Using logs to troubleshoot issues 101 .Recon ID (Below) should remain 0 > [2007/03/30 10:35:40. As a result of the error.7810] [ ERROR ] [TID: 002696] : < Character_Field = All Match Error During Identification .7710] [ TRACE ] [TID: 002696] : Found matching rule group <Patch002-Identify D2 against D1> for class <QA_Patch2_No_Ident_Multi_Match:Patch2_1Class_No_Ident_Multi_Match > in dataset <Data Set 02> [2007/03/30 10:35:39.7710] [DETAILS] [TID: 002696] : Substituting values in the qualification [2007/03/30 10:35:39. An error is generated for this job because the Reconciliation Engine finds multiple matches in the lookup dataset against which the CI is to be identified. the CI in the source dataset is not identified and the Reconciliation ID remains 0.Recon ID (Below) should remain 0> [2007/03/30 10:35:39. the Identification Rule looks for a match based on the value of the Character_Field attribute.1310] [ INFO ] [TID: 002696] : Processed instance without finding a match for instance <ID00087492D05D8nFOQw8SSKBAawAA> for class <QA_Patch2_No_Ident_Multi_Match:Patch2_1Class_No_Ident_Multi_Match > in dataset [2007/03/30 10:35:40.7710] [DETAILS] [TID: 002696] : Replaced field <id = 536870999 and name = Character_Field> with value <All Match Error During Identification .7710] [ TRACE ] [TID: 002696] : Applying rule <'Character_Field' = $Character_Field$> and looking in dataset <Data Set 01> [2007/03/30 10:35:39.1310] [ INFO ] [TID: 002696] : Cancelled the processing of rest of the sub-tree for instance of class = QA_Patch2_No_Ident_Multi_Match:Patch2_1Class_No_Ident_Multi_Match and instance id = ID00087492D05D8nFOQw8SSKBAawAA [2007/03/30 10:35:40.BMC Atrium CMDB logging [2007/03/30 10:35:39.7810] [ ERROR ] [TID: 002696] : for qualification <'Character_Field' = $Character_Field$> of group <Patch002-Identify D2 against D1> with values [2007/03/30 10:35:39. BMC Atrium Core web service logs BMC Atrium CMDB web service logs provide information about troubleshooting TIBCO or other web service issues. For more information about the BMC Atrium CMDB API logging. 2 Note the thread ID (TID) specified in this error entry. NOTE The BMC Atrium Core web services use the BMC Atrium CMDB APIs to communicate with the AR System server.bmc. BMC Atrium WS [ INFO ] Thread:1402 Date:2009-0820T23:20:44. The web services log files are located in: AtriumCoreInstallationDirectory/shared/tomcat/logs/ if the Tomcat path is bundled with BMC Atrium Core. BMC Atrium Core web services deployment logs BMC Atrium Core web services deployment logs are located in the AtriumCoreInstallationDirectory/Logs directory.025+0530 Class:com.BMC Atrium Core 7. 3 Trace back to the beginning of the log file while looking for more entries with the specific TID. Therefore. TOMCAT_HOME/logs if you are using your own Tomcat installation. To debug Reconciliation Engine errors using the log file 1 Search for the entry in the Reconciliation Engine log file that contains [ERROR] in its description.04 Troubleshooting Reconciliation Engine errors in the log file The Reconciliation Engine logs errors that can help you to troubleshoot reconciliation issues.6.atrium_classes Method:getClass File:atrium_classes.ws.atrium. The following code is an example of the output from invoking the GetClass method of the atrium_classes web service.classes. You will find several entries for the specific TID. Web services logging The BMC Atrium Core web services provide logs that can help you to troubleshoot issues related to web service operations. see “Server-side API logging” on page 96.java Line:1644 + Operation exited normally + Artifacts follow: 102 Troubleshooting Guide . Each entry reports the task that the Reconciliation Engine performs at each stage. you can also examine the BMC Atrium CMDB API logs for any errors. The BMC_ComputerSystem class corresponds to the DMTF class CIM_ComputerSystem. firewall. You can use the attributes in this class to identify the purpose of each computer CI in your organization.-1091. operating systems. They could also define computer systems further by placing them in one of its subclasses: BMC_Mainframe. BMC_Printer. load balancer. a workstation.CORE</namespaceName> <className>BMC_System</className> </superclassNameId> <classId>BMC_COMPUTERSYSTEM</classId> <classType>REGULAR</classType> <formName>BMC.bmc. making it easy to import this data from a vendor as an industry-standard item in their CMDB. or a network device (router. and virtual systems.CORE:BMC_ComputerSystem</formName> </classInfo> <status/> <extensions> Chapter 7 Using logs to troubleshoot issues 103 . nonvolatile. such as a server. For example.-1099. the class contains several attributes that represent any network-addressable system. or storage). or BMC_VirtualSystem.com/2009/01/ classes/types"> <classInfo> <properties> <regular> <isAbstract>NO</isAbstract> <exposure>USED_VISIBLE</exposure> <hiddenPerms/> <visiblePerms>-1098. The managed system elements provide computing capabilities and serve as aggregation points to relate one or more of the following elements: file systems. printers. So CMDB planners might use the PrimaryCapability element to define a vendor-specific switch used in their network. The BMC_ComputerSystem class is the primary class that you will use to model the computers in your organization.BMC Atrium CMDB logging -----------------------------------------------------------------------<typ:GetClassOutput xmlns:typ="http://atrium. as well as mainframes. processors. and so forth).</visiblePerms> <categorizationSubclass>false</categorizationSubclass> <description>Class that stores configuration items (CIs) relating to collections of managed system elements. switch.-1090. hub.</description> <isFinal>false</isFinal> <isSingleton>false</isSingleton> <author/> <auditInfo> <auditType>NONE</auditType> <qualifierString/> </auditInfo> </regular> </properties> <indexList/> <customCharacList/> <superclassNameId> <namespaceName>BMC. and memory (volatile storage. BMC Atrium Core 7. Each log line provides the service class and method name that the error occurred in.level property.04 <clas:ClassDeprecationInfo xmlns:clas="http://atrium.cfg file. The default logging level for the web services is set to WARN. BMC Atrium Integration Engine logging and debugging You can diagnose BMC Atrium Integration Engine errors and verify the completion of data exchanges by using the logging and debugging facilities in BMC Atrium Integration Engine. and includes fault messages or other error conditions. which is specified in the aie.atrium. aids in long-term management of data exchanges. Trace—The highest level of logging possible.bmc. and includes trace level statements. Each line also provides the filename and line number in which the log occurred. The various logging levels are: Info—Lowest level possible. Error—Contains the same information as Info. Contains the same information as Debug. To set logging levels for all other Atrium Core web services. 104 Troubleshooting Guide . along with artifacts (like incoming and outgoing SOAP messages.6.log. Warning—Contains the same information as Error and includes information about warnings.cmdbws.log. Debug—Contains the same information as Warning and includes debug level statements. The error logging. For more information about configuring BMC Atrium Core web services. or stack traces).level property enables you to set logging levels for the cmdbws web services. It provides the entrance and exit points for operation and loading operations.com/2009/ 08/extensions/classes"> <classId>BMC_COMPUTERSYSTEM</classId> <isDeprecated>false</isDeprecated> <mappedClass xsi:nil="true" xmlns:xsi="http://www. These levels determine the types of messages that BMC Atrium Core logs for each web service call. The bmc.org/2001/ XMLSchema-instance"/> </clas:ClassDeprecationInfo> </extensions> </typ:GetClassOutput> ================================================================== Setting log levels for BMC Atrium Core web service logs You can use the atrium_serviceconfig service to configure logging level for the deprecated cmdbws and the BMC Atrium Core web services. use the bmc.w3. see the BMC Atrium Core Web Services Help. either the backup file is created or the new information wraps to the top of the file. To enable debug logging 1 On the Data Exchanges Information window. updated. To preserve the log files and their contents. SQL Statements—Logs SQL commands sent to the database. depending on the Log-File Creation settings. depending on the value in the Max Debug Size field. and whether the record is successfully added. 7 Click Apply To All Exchanges. overwriting the old information. If you enable debug logging but do not specify a path for the file. updated. The name of the log file would be formatted as follows: dataExchangeName_TthreadNumber. Information is logged on entry and exit of every API call. browse to select the location for the debug files. how it is getting converted to the Destination field after applying any rules. click Append To Existing. 2 In the Enable Debug Logging field. the log is written to the default debug path that you specified during installation of BMC Atrium Core.BMC Atrium Integration Engine logging and debugging Enabling debug logging You can configure and test data exchanges by using the debug option. click Create Backup. Record Details—Logs detailed level information for each record. and whether that operation was successful. Summary information includes whether the record is being added. click Yes. You can log various levels of debug information from the Data Exchanges Information window. perform one of the following steps: To create new log files and write the contents of the previous log files to the dataExchangeName_timeStamp. click Yes to create thread-based log files. New information is appended to the existing file or is wrapped to the top of the file. When the log file reaches the maximum limit. 5 In the Enable Thread Based Logging field. or deleted. including a time stamp. The debugging files provide detailed operational information to diagnose errors in a data exchange. or deleted. Record Summary—Logs summary information for each record. NOTE You cannot set the log file size smaller than 4096 because that could be the length of a single log line. Details are provided at the field level. type the maximum size (in bytes) for the log file. Information can include the value for each Source field. click the Advance Settings tab. 4 In the Max Debug Size field.In the Debug File Creation area. Chapter 7 Using logs to troubleshoot issues 105 . Information is logged for each SQL command issued. 6 In the Debug Level area. 3 In the Debug File Path.dbg. select any of the following check boxes: API Calls—Logs information about all API calls made by BMC Atrium Integration Engine.bak file. updated. All log events are recorded both in the BMC Atrium Integration Engine log file and the AIE:Log form. Session Statistics—Provides statistics about the number of records processed for the main mapping of a data exchange. to the individuals in your company who are responsible for managing various parts of the data exchanges. Log messages Log messages record all major events about data exchanges and individual record transfers. and so on. such as a data conversion error. based on log message numbers or categories. The key of the request is provided in the message text. 106 Troubleshooting Guide . You can use the log message categories to determine what kind of workflow to generate. This could be the result of an invalid registry entry.BMC Atrium Core 7.6. More detailed information about why a record was not transferred is recorded in the debug file (if debugging is activated). Transfer Error—Indicates that a transfer was not made due to a problem. Use the log of debug events to help you understand the nature of problems that you encounter and how to correct them. or not transferred due to an error.dll file not in the correct path. For example. you might want workflow to send notifications. such as data truncated to fit a field.04 The debug settings are applied to all exchanges that are in the Active state. The error message indicates the key of the record that failed and any associated AR System server error messages. Log messages provide broad information about events and errors. a . 8 Click Save. Service Error—Indicates an error that prevents the data exchange from taking place. Log messages are sorted into the following event categories: Service Status—Indicates when a data exchange starts and when it ends. Adapter Error—Indicates that the adapter could not be used by BMC Atrium Core. Each category has both informational messages and error messages. Transfer Warning—Indicates that a transfer was made despite a possible problem. The count includes records added. indicating that a call to the AR System server failed. The BMC Atrium Integration Engine service ran out of available memory and cannot continue. An additional error message precedes this error. This is a fatal error. field mapping definition ignored. the BMC Atrium Integration Engine service uses this request. Required configuration parameter is missing — <%1>. Verify that the form exists and that the login used by the BMC Atrium Integration Engine service has permission to create. No requests exist on the Data Field Mapping tab of the AIE:ARMappingInfo form for the BMC Atrium Integration Engine service to use. and delete requests. such as %1. After rules are defined. and so on. The BMC Atrium Integration Engine service received an error from the AR System server that was trying to create a request in the specified form. indicating which calls to the AR System server failed. The BMC Atrium Integration Engine service ignores this request and continues. 3307 Failed to create request in form <%1>. Additional errors precede this one. The BMC Atrium Integration Engine service received an error while trying to process the specified form and request ID. Verify that the configuration file exists and is accessible. 3308 3310 Failed to open configuration file <%1>. No rules were defined for the specified field mapping. The BMC Atrium Integration Engine service does not process requests without field mapping rules defined. The specified form does not exist or is not accessible. 3303 3304 Malloc failed. The specified configuration parameter was missing or typed incorrectly. Failed to add request <%1> to form <%2>. BMC Remedy Link Terminating <%1>. An error condition caused the BMC Atrium Integration Engine service to terminate at the indicated time.BMC Atrium Integration Engine logging and debugging Data exchange log messages Table 6-2 lists log messages that you might receive during a data exchange. Add or correct the entry in aie. 3311 3312 Chapter 7 Using logs to troubleshoot issues 107 . Form <%1> does not exist or is not accessible. The BMC Atrium Integration Engine service received an error while trying to add a unique identifier to the specified form.cfg. %2. Some messages contain placeholders.cfg. 3305 No Rules defined for field mapping <%1>. Table 7-2: Log file messages (Sheet 1 of 4) ID number 3301 3302 Message BMC Remedy Link starting to process requests <%1>. No Field Mapping entries defined for VendorApp: <%1>. Description The BMC Atrium Integration Engine service started a data exchange session at the time indicated. These placeholders represent text that is inserted during run time. modify. 3306 Failed to update form <%1> request-id <%2>. The BMC Atrium Integration Engine service could not find or open aie. and cannot be run.BMC Atrium Core 7. The BMC Atrium Integration Engine service completed a data exchange at the indicated time. Previous messages indicate what is wrong. 3314 3315 3317 A fatal setup error occurred. A nonrecoverable error occurred while the BMC Atrium Integration Engine service was being set up to process requests. and relationship classes to create or modify all the field mappings. completed setup and will begin a data exchange. or create valid rules. Failed to load message DLL — <%1>. 3318 3319 3320 Setup completed successfully. 108 Troubleshooting Guide . 3322 3323 3324 BMC Remedy Link does not have The BMC Atrium Integration Engine service does a license. Make sure that the account being used by the BMC Atrium Integration Engine service has permission to delete requests. The request is not updated. 3316 One or more required fields are missing from form <%1>. Failed to update form <%1> request <%2>. The BMC Atrium Integration Engine service could not delete the specified request in the form. CI classes. A previous message indicates what is wrong. No data was returned using field mapping definition <%1> for request <%2>.6. service cannot run until it is corrected. Description No valid requests exist in the corresponding mapping consoles for AR and CMDB. The BMC Atrium Integration Engine service received an error from the AR System server while trying to update the indicated request in the specified form. A recoverable error occurred while the BMC Atrium Integration Engine service was being set up to process requests. The BMC Atrium Integration Engine service deletes requests that do not have a matching primary form request. A setup error occurred. daemon cannot run. the service will try again at its next scheduled time. Correct the existing requests’ rules. not have a license. The BMC Atrium Core service could not load the indicated message . Use the respective Mapping Information windows for BMC Remedy Action Request System Server (BMC Remedy AR Server) forms. BMC Remedy Link finished processing requests <%1>. 3321 Could not find the field mapping name <%1> for request <%2> in form <%3>.dll file. The specified form is missing one or more required fields.04 Table 7-2: Log file messages (Sheet 2 of 4) ID number 3313 Message No valid field mapping rules are defined. The BMC Atrium Integration Engine service starting to process requests. Failed to delete request <%1> for form <%2>. The BMC Atrium Integration Engine service was unable to locate the indicated field mapping name in the specified form for the indicated request. The BMC Atrium Integration Engine service did not receive data from the AR System server for the indicated request. The BMC Atrium Integration Engine service failed to allocate memory for adapter object. Adapter <%1>: Failed to initialize adapter: <%2>. warnings: <%5>. this issue might occur on a UNIX computer if the LD-LIBRARY-PATH environment variable does not contain the correct path. <%3> — Number of external data store keys processed. This issue can occur on UNIX and Windows computers. Adapter <%1>: Failed to terminate the adapter: <%2>. <%2> — Number of AR System keys processed. <%5> — Number of requests updated and added. errors: <%4>. Adapter <%1>: Cannot find adapter file at<%2>. The BMC Atrium Integration Engine service was unable to get function address in the Adapter library. <%2> — Number of requests added. Check the BMC Atrium Integration Engine installation directory. Session <%1>: Request <%2> warning: one or more fields not processed. For example. but some fields were ignored due to an error.BMC Atrium Integration Engine logging and debugging Table 7-2: Log file messages (Sheet 3 of 4) ID number 3325 Message Session <%1> statistics: AR System requests: <%2>. updated: <%3>. <%3> — Number of requests updated. Vendor requests: <%3>. 3328 3329 3330 3331 Adapter <%1>: GetProcAddress() failed. The BMC Atrium Integration Engine service failed to close the adapter connection and release resources. 3326 Session <%1> statistics: Requests added: <%2>. <%4> — Number of requests ignored due to an error. An BMC Atrium Integration Engine adapter is not present at the specified path. Verify that the session ID tag and the data key are correct in the field mapping. The adapter library might fail to load due to incorrect environment variable settings. Check external data store configuration parameters. Adapter <%1>: Failed to load adapter <%2>. Adapter <%1>: Failed to create adapter object: <%2>. 3332 3333 3334 Chapter 7 Using logs to troubleshoot issues 109 . Statistics about the BMC Atrium Integration Engine service transactions: <%1> — Name of the session ID tag from the AIE:FieldMapping form. The record was not exchanged for the named session ID tag and the named data key. 3327 Session <%1>: Request <%2> error: record ignored due to error. The BMC Atrium Integration Engine service failed to initialize adapter object. Verify that the session ID tag and the data key are correct in the field mapping. Description Statistics about the BMC Atrium Integration Engine service transactions: <%1> — Name of the session ID tag from the AIE:DataExchange form. The fields were not processed for the named session ID tag and the named data key. 6. The data exchange is activated with improper configuration. The adapter cannot obtain a license because the maximum number of exchanges for a Demo license has been exceeded. 110 Troubleshooting Guide .dbg—Logs messages specific to the current event-driven data exchange.dbg—Logs messages for event-driven data exchanges that are not active.dbg file and records diagnostic information about the initialization errors.04 Table 7-2: Log file messages (Sheet 4 of 4) ID number 3336 Message Adapter <%1>: Failed to open connection to data source: <%2>.dbg—After each data exchange starts. It does not record events that occur for individual data exchanges. Using the instanceName_aiemain. engine exit. These debug messages are of the following types: instanceName_aiemain. instanceName_aieEventMgr. Data exchange: <%1>. 3339 3340 Debug messages BMC Atrium Integration Engine generates debug messages that help you detect errors and events in the data exchange process. you have the option of running it with debugging enabled or not.dbg—A special. Description The BMC Atrium Integration Engine service failed to open an adapter connection with data store. %s adapter cannot obtain a license as the maximum number of exchange for a Demo license has exceeded. depending on whether you specify the debug startup parameters on the command line. the BMC Atrium Integration Engine service creates a unique debug file for the exchange. exchangeName.dbg—Logs messages when the Verify and Run Now commands or the event-driven data exchange is not working correctly. the BMC Atrium Integration Engine service creates the instanceName_eiemain.BMC Atrium Core 7. instanceName_aieEventCleanup.dbg debug file When you start the BMC Atrium Integration Engine service. Exit the specified instance on this machine. high-level debug file that records details and problems with the BMC Atrium Integration Engine service. instanceName_aieEventListener. Data exchanges using that adapter cannot run. If you specify the debug startup parameters. of BMC Atrium Integration Engine. 3337 There is another Atrium BMC Another BMC Atrium Integration Engine process is Atrium Core process running running on this computer. Active event request without a configured data exchange. The following text is an example of instanceName_eiemain. or relationship classes.dbg. NOTE If you configure multiple concurrent data exchanges on the Main tab of the AIE:DataExchange form.dbg file is created. licenses issued. and AIE:CMDBRelMapping are backend forms used to store information. You cannot interact directly with these forms. the instanceName_eiemain. Chapter 7 Using logs to troubleshoot issues 111 . The debug file also indicates on which tabs of the forms these rules are entered. Using the example in the previous paragraph.dbg. if the data exchange is named GetDiskDetail. Adapter Version: 7. when a data exchange starts. and event requests. the debug file names are getdiskdetail_1. if two concurrent data exchanges are configured.dbg if your data exchange fails to start and no exchangeName. NOTE Only one instanceName_eiemain. CI classes. or if an event request fails to run.5. Consult instanceName_eiemain. the debug file will have the name GetDiskDetail.BMC Atrium Integration Engine logging and debugging In addition to startup information. Event Request cleanup thread started. NOTE AIE:DataMapping.dbg and getdiskdetail_2. licenses absent.dbg debug file is created regardless of how many data exchanges are configured. Each data exchange debug file provides a list of all rules entered in the Data Exchange application in the order that they are entered on the respective Mapping Information window for BMC Remedy Action Request System Server (BMC Remedy AR Server) forms. assigning it the name of the data exchange.dbg: Starting to look for changes to data exchange definitions Service has detected 1 active data exchanges on AR System Location of 'FlatFile' adapter obtained License granted to FlatFile.00 Thread started to manage exchange: SamplePullExchange_2 Starting threads to manage event driven requests Immediate async thread started. Waiting for 5 minutes to look for changes to data exchange definitions. the BMC Atrium Integration Engine service creates a unique debug file for it. Using an exchangeName. AIE:CMDBDataMapping.dbg file records high-level information about data exchanges found. the BMC Atrium Integration Engine service debug files are assigned the name of the data exchange with a sequence number appended to it.dbg debug file If you enable the logging of debug events. For example. Initialization phase debug logging During the initialization phase. StartDataHandlers: Connection established to both AR/CMDB and vendor >>>ARS Form Fields: Field mappings in: 'FlatFileSamplePull' Rule 1: <First Name (id: 536870914)> Set to data type: 4 (Character) Rule 2: <Salary (id: 536870916)> Set to data type: 3 (Real) Rule 3: <Gender (id: 536870917)> Set to data type: 6 (Enum) >>>ARS Form Key Fields: Key Rule 1: <Last Name (id: 536870913)> Set to data type: 4 (Character) >>>ARS System Query: No query defined. >>>Vendor Rules: Field mappings in: 'FlatFileSamplePull' Rule 1: <FNAME> Set to data type: 4 (Character) Rule 2: <SALARY> Set to data type: 3 (Real) Rule 3: <GENDER> Set to data type: 2 (Integer) >>>Vendor Keys: Key Rule 1: <LNAME> Set to data type: 4 (Character) >>>Vendor Query: No query defined: All entries will be processed. StopDataHandlers: Disconnected from both AR/CMDB and Vendor applications 112 Troubleshooting Guide .04 Each data exchange debug file records the following events as they take place when a data exchange is run: Data retrieved Any values generated by rule syntax Data conversions performed Data updated.6. the BMC Atrium Integration Engine debug facilities record all data exchange and data handling rules.BMC Atrium Core 7. or deleted Errors or warnings For detailed information about the problems that occur in specific data exchanges. enable the log of debug events in aie.cfg. The following example shows the information collected when all Debug Level options are selected on the Advanced Settings tab of the Data Exchanges Information window. created. All entries will be processed. Value: '135' Rule 3: 'GENDER'. Value: '234' Rule 3: 'GENDER'. CI classes. Value: 'Mary' Rule 2: 'SALARY'. and the data type of the data defined by the rule.BMC Atrium Integration Engine logging and debugging Processing phase debug logging During the processing phase. Value: '1' Key Rule 1: 'LNAME'. When a data exchange starts. The debug file identifies the success or failure of the data transfer and provides a detailed error message for each error. the debug file shows all rules retrieved from the Data Exchange application and the page of the respective Mapping Information window for BMC Remedy Action Request System Server (BMC Remedy AR Server) forms.dbg file records the number of records obtained from each data store. or relationship classes from which it was retrieved. Value: 'Tom' Rule 2: 'SALARY'. When a data exchange stops. Number of AR System Keys obtained 0. only the statistics for the main mapping are recorded in the debug file. Start comparing list of records on Mon Jul 02 16:29:21 2008 SessionID=SamplePullExchange direction=VendorDataIntoAR updateType=Both New and Changed AR System Data Server Data obtained from Source for mappings: 'FlatFileSamplePull' Rule 1: 'FNAME'. For each data exchange. Value: 'Poulos' Setting field values of Target for mappings 'FlatFileSamplePull' Rule 1: <First Name (id: 536870914)> set to 'Mary' Rule 2: <Salary (id: 536870916)> set to '135' Rule 3: <Gender (id: 536870917)> set to '1' Key Rule 1: <Last Name (id: 536870913)> set to 'Poulos' Adding entry Poulos to form 'AIE:FlatFileSample' Data obtained from Source for mappings: 'FlatFileSamplePull' Rule 1: 'FNAME'. Statistics for other data mappings are not recorded. Value: '0' Key Rule 1: 'LNAME'. Chapter 7 Using logs to troubleshoot issues 113 . the exchangeName. The following example shows the error messages when all Debug Level options are selected on the Advanced Settings tab of the Data Exchanges Information window. the exchangeName. Value: 'Smith' Setting field values of Target for mappings 'FlatFileSamplePull' Rule 1: <First Name (id: 536870914)> set to 'Tom' Rule 2: <Salary (id: 536870916)> set to '234' Rule 3: <Gender (id: 536870917)> set to '0' Key Rule 1: <Last Name (id: 536870913)> set to 'Smith' Adding entry Smith to form 'AIE:FlatFileSample' Data exchange statistics The BMC Atrium Integration Engine service debug file also lists the data exchange statistics.dbg file shows statistics of the number of records actually transferred. Number of Vendor Keys obtained 0. 04 Session statistics: AR requests: 0. Atrium Impact Simulator logging Atrium Impact Simulator logs errors in the ais. Timestamp—The date and time of the log entry. The ais.log file records messages generated by the Atrium Impact Simulator plug-in. which are used for debugging purposes. errors: 0. The debug levels are: Debug—Logs messages for severe errors. Log Type—The type of log entry: debug. Atrium Impact Simulator plug-in logging Atrium Impact Simulator uses the Apache log4j mechanism to log messages. updated: 0.log file records errors that are generated by the Atrium Impact Simulator computation cell. This is the highest logging level. Message—The message for the log entry. add CMDB-Debug-Level: loggingLevel to the configuration file and restart the AR System server. Warning—Logs messages for warnings.log and ais_cell. 114 Troubleshooting Guide . You can specify additional logging options for Atrium Impact Simulator plug-in in the log4j_pluginsvr. Each entry in the log provides the following details: Thread—The thread that the transaction used when the message was generated.6. To set the debug logging to a different level. information.log files. Vendor requests: 5 Session statistics: Requests added: 5. error. see http://logging. Error—Logs messages for errors.xml configuration file. The ais_cell. deleted: 0. warning. For more information about the additional parameters that you can specify for the Atrium Impact Simulator plug-in. such as notifying you that Atrium Impact Simulator is starting up and that the Atrium Impact Simulator receiver started on a specific port number. or fatal. Fatal—Logs messages and details for the fatal errors.apache.org. Information—Logs informational messages. warning Sleep until next poll interval or scheduled time for data transfer StopDataHandlers: Disconnected from both AR/CMDB and Vendor application.BMC Atrium Core 7. This is the default logging level. The debug level parameter specified level of logging that you require for your Atrium Impact Simulator plug-in transactions. For this reason.trace file. To enable Atrium Impact Simulator cell logging 1 From the AtriumInstallation/AtriumCore/hostName/ais/etc/directory.cell also logs internal messages from other BMC Atrium Core components. 3 For the com.ais and com. search for the "Logger for AIS" string.trace file.bmc. On UNIX—at the prompt type “/etc/rc2. which is a separate process.atrium. 2 Search for the ALL ALL entry at the end of the file. 2 In the file.Atrium Impact Simulator logging Enabling Atrium Impact Simulator plug-in logging Use this procedure to enable Atrium Impact Simulator plug-in logging To enable Atrium Impact Simulator plug-in logging 1 From the <AtriumInstallation>/AtriumCore/<hostName>/cmdb/plugins/ shared/ directory. set the level value parameter to DEBUG.atrium. Otherwise add the ALL ALL stderr entry. add a comment entry character "# " at the beginning of the ALL ALL entry.d/S99ais start”. open the log4j_pluginsvr.ais loggers. open the mcell. set it to stderr. Enabling Atrium Impact Simulator cell logging The Atrium Impact Simulator cell. go to the command prompt and type “net start “BMC Atrium Impact Simulator”.filterplugin. 3 If you find the entry and if it is commented. After you finish logging. BMC recommends that you do not change any additional configuration settings in the mcell.bmc. NOTE The ais. Your changes will take effect shortly or after the next time you restart the AR System server. 4 Restart the Atrium Impact Simulator cell for the value to take effect: On Windows. Chapter 7 Using logs to troubleshoot issues 115 . is the engine that performs the calculations for the impact simulations in the background.xml file. DatasetId. This information is not logged in the neContinuous. The Normalization Engine logs. The default value for the CMDB-Max-Log-File-Size parameter is set to 5 MB. User name—The user that started a specific Normalization Engine job. and debug categories. When the log file reaches the specified limit. in megaytes (MB).BMC Atrium Core 7. which classify the messages into error. The Normalization Engine log files are located in the atriumInstallationDirectory/Logs directory by default. File name and line number—The file name and line number on which the error occurred.6. information. Each entry in the log provides the following details: Timestamp—The date and time of the log entry.g. the cache is loading up. The DatasetId component in the file name indicates the dataset ID on which the normalization activity is to be performed and the NNNN component is a four-digit sequence number. API MAx File Size (MB)—Enables you to specify a maximum size. for your log file. Log Type—The type of log entry: warning.log—Records the messages that are generated by the Normalization Engine API calls. neJob. You can specify the following additional parameters for logging in the Configuration Editor window of the Normalization Engine console.NNNN. warning.log files. Message—The message for the log entry. e.log—Records information. and so on. neJob. API Log File Location—Enables you to specify a directory location different than the default location on your system where the log files are to be written.log nePluginServer. the system automatically creates a backup of the log file and continues to store the log entries in a new log file. such as the Normalization Engine is starting up.SAMPLE.log—Records the messages that are generated by the Normalization Engine continuous job processing. or information. for example.log—Records the messages that are generated by the Normalization Engine batch job processing. neContinuous.log and neBatchtimeStamp. error.BMC. are enabled by default.0000. TID—The thread that the Normalization Engine job used when the message was generated.04 Normalization Engine logging The Normalization Engine logs errors in the following log files: neAPI. 116 Troubleshooting Guide . Additionally. you might receive an ARERR [92] Timeout during database update error on the BMC Atrium Core client.log and cmdbengdebug. and so on. On UNIX. This is the highest level of logging. These levels determine the types of messages that are logged for the Normalization Engine.log file traces all AR System API calls that are run on the server.6. You can change the file names and location of any of these logs at any time.log and arapi. The debug levels are: Error—Logs messages for error. BMC Atrium Core might not function correctly.log file under certain circumstances.log file records all AR System server error messages. such as the following scenarios: Chapter 7 Using logs to troubleshoot issues 117 . see the BMC Atrium CMDB 7.log file.log and arapi. such as arerror. Information—Logs informational messages. One of the possible causes for this timeout error might be that the AR System server stopped responding. On Windows. Make sure that you examine the arerror. If any errors occurred when loading the library during AR System server starts up. AR System server logging The AR System server also provides error logs.log files are located by default in the C:\Program Files\BMC Software\ARSystem\Arserver\Db subdirectory of your AR System server installation directory.log. you can enable the Filter and SQL logging options from the AR System Administration: Server Information > Log Files tab in BMC Remedy User. The arerror. The logging levels are inclusive of their preceding levels. which are used for debugging purposes. To troubleshoot this error. they are created under serverInstallationDirectory/db.04 Normalization and Reconciliation Guide. BMC Atrium Core also writes to the arerror. In addition to logging errors to the cmdbengdebug. these logging options create the log files by default under the Program Files\BMC Software\ARSystem\Arserver\Db subdirectory of your installation directory. For example. For more information about setting the log file parameters for the Normalization Engine. such as notifying you that your AR System server stopped responding. Warning—Logs messages for warnings. Both arerror. The arapi. This the default logging level. try to reproduce the error and examine other logs to identify the cause of the error.AR System server logging API Log Level—Specifies the level of logging for the log files. Debug—Logs additional details for errors.log files for any CMDB Engine library loading errors. install. you might need to zip up all the BMC Atrium Core log files and send it to BMC. an ARERR [9755] error is written to arerror.install. such as the following example.product.atriumfoundation.base. Bundling the BMC Atrium Core log files When calling BMC Customer Support regarding any issues.atriumfoundation.BMC Atrium Core 7.zip Example: java -cp "C:\Program Files\BMC Software\AtriumCore\rietvm02cl1\UninstallBMCAtriumCore\uninstaller.LogZipper com.log.bmc.bmc.jar" com.LogZipper com. an error is written to arerror.04 If the RPC program was not registered when making a BMC Atrium Core API call from a BMC Atrium Core client.04 Optimizing and Troubleshooting Guide.product. see the BMC Remedy Action Request System 7.install.bmc.install.AtriumFoundationLogZipp erProfileListBuilder "C:\Program Files\BMC Software\AtriumCore\rietvm02-cl1\AtriumCoreLogs.zipper.zip" 118 Troubleshooting Guide .zipper. This error occurs because the AR System server did not load the CMDB Engine library.product.cmdbEngine Thu May 03 15:01:22 2007 390600 : Form does not exist on server : OBJSTR:Class (ARERR 303) For more information about these AR System server log files.6.log.6.product. To create a zip file of the logs.bmc.AtriumFoundationLogZipper ProfileListBuilder destinationDirectory/AtriumCoreLogs. and the CMDB Engine library fails to load: Thu May 03 15:01:21 2007 390600 : Error encountered while initializing (Initialization routine) the shared library (ARERR 9755) Thu May 03 15:01:21 2007 bmc.cmdb. run the following command: java -cp <JAR file path> <LogZipper path> <output profile> <output file path> com. If the OBJSTR:Class form that holds BMC Atrium CMDB metadata is not available on the server.base. Solution Contact your CMDB administrator. (CMDB_ERROR_NO_SUCH_CLASS) Description The class that you are attempting to view does not exist in the CMDB. message type. Table A-1: C API error messages (Sheet 1 of 34) Message type Error Message. 120002 Error Class does not exist. message text. (CMDB_ERROR_SYSTEM_NOT_INITIALIZED) Description You did not initialize the CMDB API session in your API calls. Solution Provide a non-empty parameter to the BMC Atrium CMDB C API function call. and solution for errors that are generated by BMC Atrium CMDB C API. Solution You must call the CMDBInitialization function before calling another BMC Atrium CMDB C API function. Appendix A BMC Atrium CMDB C API error messages 119 .A Error number 120000 Appendix BMC Atrium CMDB C API error messages Table A-1 lists the error number. 120003 Error A required parameter is empty. description. The CMDB system cannot be initialized. Solution Specify a valid class name or class ID. 120001 Error A fatal error occurred during CMDB initialization. and solution The CMDB API session is not initialized. description. (CMDB_ERROR_REQUIRED_PARAM_EMPTY) Description You did not specify a value for a required function parameter. (CMDB_ERROR_SYSTEM_CANNOT_BE_INITIALIZED) Description A system error prevented the CMDB from being initialized. Solution Contact your CMDB administrator. 120007 Error CMDB system error occurred during processing.h file. (CMDB_ERROR_CLASS_NAME_ID_NOT_UNIQUE) Description The specified class name already exists within the given namespace. 120009 Error The class name is not unique. see “AR_DATA_TYPE” section of the ar.04 Table A-1: C API error messages (Sheet 2 of 34) Error number 120004 Message type Error Message. Solution Specify a valid instance ID. 120006 Error Instance not found. (CMDB_ERROR_INSTANCE_NOT_FOUND) Description The specified instance is not found. 120 Troubleshooting Guide . and solution Attribute does not exist. (CMDB_ERROR_ATTRIBUTE_NAME_NOT_UNIQUE) Description An attribute with the specified name already exists. For more information about data types. Solution Make sure that the supplied attribute data type is valid for BMC Atrium CMDB. Solution Provide a valid attribute name or ID.BMC Atrium Core 7. The attribute name is already in use. Solution Specify an unused attribute name. 120011 Error Class already exists. (CMDB_ERROR_NO_SUCH_ATTRIBUTE) Description The attribute that you are attempting to view does not exist. Solution Specify an unused class name. (CMDB_ERROR_UNSUPPORTED_ATTRIBUTE_DATA_TYPE) Description The data type specified for the attribute does not exist in the CMDB. 120014 Error The attribute name is not unique. The class name is already in use. description. (CMDB_ERROR_SYSTEM_ERROR) Description An unexpected system error occurred during CMDB processing. Solution Create a class with a different class ID. 120005 Error The supplied attribute data type is not supported.6. (CMDB_ERROR_CLASS_ALREADY_EXISTS) Description A class with the specified class ID already exists. BMC Atrium CMDB C API error messages Table A-1: C API error messages (Sheet 3 of 34) Error number 120015 Message type Error Message. Solution Specify a valid cardinality value. (CMDB_ERROR_ROLE_NAMES_MUST_BE_DIFFERENT) Description You cannot create a relationship class with two roles of the same name. description. (CMDB_ERROR_INVALID_LIST_FORMAT) Description The format is Ln. Appendix A BMC Atrium CMDB C API error messages 121 . Solution Provide a different role name for each role. (CMDB_ERROR_INVALID_CARDINALITY_VALUE) Description The cardinality that you specified is not one of the defined values. Solution Decrease the number of items in the attribute for the current instance or change the attribute’s definitions to increase the number defined in its List Format. Solution Specify an enumeration value that is defined for the attribute. 120018 Error (CMDB_ERROR_EXCEED_MAX_LIST_ITEMS) Description The number of semicolon-separated items in a character attribute exceeds the number defined in the List format. (CMDB_ERROR_INVALID_ENUM_DEFAULT) Description The default value specified for the enumeration attribute is not one of its defined values. Solution Specify a different attribute ID. 120017 Error The specified list format is not valid. (CMDB_ERROR_ATTRIBUTE_ALREADY_EXISTS) Description An attribute with the same attribute ID already exists. 120016 Error The default enumeration value is invalid. Solution Modify the list format to Ln. and solution Attribute already exists. 120019 Error The relationship role names must be different. where n is the maximum number of items. 120020 Error An invalid cardinality value was supplied. 120022 Error The role name does not match the superclass role name. the derived class cardinality can be one-to-one but cannot be many-to-many. Solution Do not attempt to modify the relationship parameter. Solution Make sure that you derive a relationship only from a relationship class. (CMDB_ERROR_SUBCLASS_CARDINALITY_LESS_RESTRICTIVE) Description If the superclass cardinality is one-to-many. Solution Derive a role class from the super class’s role class. 120023 Error The Configuration Item Class for the role is not a derived class of the superclass’s role. 122 Troubleshooting Guide . and solution Cannot create a relationship class that is derived for a nonrelationship class. the configuration item role classes must be the same as or derived from the superclass's configuration item role classes.6. the role name properties must match the superclass’s role name properties. (CMDB_ERROR_RELATIONSHIP_PARAM_CANNOT_BE_CHANGED) Description You cannot modify the relationship parameter. Solution Supply the same role name as the superclass. Solution Specify a cardinality that is the same as the superclass or is more restrictive than the superclass. description. (CMDB_ERROR_SUPERCLASS_MUST_BE_REL_CLASS) Description You are attempting to derive a relationship class from a class of another type. (CMDB_ERROR_CLASS_ROLE_NOT_SUPERCLASS_DERIVED) Description When you create a derived relationship class. 120024 Error The cardinality of the derived relationship class cannot be less restrictive than the superclass.04 Table A-1: C API error messages (Sheet 4 of 34) Error number 120021 Message type Error Message.BMC Atrium Core 7. 120025 Error The supplied relationship parameter cannot be modified. (CMDB_ERROR_ROLE_NAME_DOES_NOT_MATCH_SUPERCLASS) Description When you create a derived relationship class. BMC Atrium CMDB C API error messages Table A-1: C API error messages (Sheet 5 of 34) Error number 120026 Message type Error Message. Solution Select a valid class type—CI or Relationship. 120031 Error The parameters for the categorization class are invalid. (CMDB_ERROR_INVALID_ABSTRACT_CLASS_INST_OPERATION) Description You are attempting to perform an abstract class operation on an instance. Solution Contact your CMDB administrator. Solution Perform the operation on a non-abstract class. (CMDB_ERROR_ATTRIBUTE_INFO_CORRUPT) Description Information for the attribute is corrupt. description. 120030 Error Invalid instance operation on the abstract class. 120028 Error The attribute cannot be set. (CMDB_ERROR_INVALID_CLASS_TYPE) Description The class type that you specified is not one of the system-defined class types. 120029 Error The attribute information is corrupt. Appendix A BMC Atrium CMDB C API error messages 123 . Solution Do not attempt to modify an existing class type. (CMDB_ERROR_INVALID_CATEGORAIZATION_SUBCLASS) Description The parameter value that you specified for the categorization class does not match the class definition. 120027 Error The class type cannot be modified. (CMDB_ERROR_ATTRIBUTE_CANNOT_BE_SET) Description You cannot set the attribute. and solution The supplied class type is invalid. (CMDB_ERROR_CLASS_TYPE_CANNOT_BE_CHANGED) Description You cannot modify the class type. Solution Make sure that the parameters for the categorization class are correct. Solution Contact your CMDB administrator. (CMDB_ERROR_INVALID_FINAL_CLASS) Description The parameter value that you specified for the final class does not match the class definition. Solution Make sure that you specify the starting node information in the graph query. (CMDB_ERROR_QUERY_GRAPH_HAS_NO_STARTNODE) Description You omitted the starting node parameter in a graph query. (CMDB_ERROR_INVALID_SINGLETON_CLASS) Description The parameter value that you specified for the singleton class does not match with the class definition. (CMDB_WARN_INVALID_EXPORT_ITEM_TYPE) Description The item type you are attempting to export is invalid. Solution The export item should be either of type CMDB-ITEM-TYPE-META-DATA (1) or CMDB-INSTANCE-DATA (2).04 Table A-1: C API error messages (Sheet 6 of 34) Error number 120032 Message type Error Message. (CMDB_ERROR_QUERY_GRAPH_HAS_AMBIGUOUS_NODE) Description More than one node has the same name for the query graph. 120035 Error The permission list must be a list of group IDs separated by semicolons. 124 Troubleshooting Guide .6. Solution Use an extension ID to distinguish between nodes within the same class and namespace. and solution The parameters for the final class are invalid. 120037 Error A specified node is ambiguous. 120036 Error The specified query graph does not have a starting node. Solution Make sure that the parameters for the singleton class are correct. Solution Make sure that the parameters for the final class are correct. (CMDB_ERROR_PERMISSION_LIST_INVALID) Description You are attempting to use an invalid character to separate group IDs in a list.BMC Atrium Core 7. 120033 Error The parameters for the singleton class are invalid. 120034 Warning The specified export item type is invalid. Solution Use semicolons to separate the groups IDs in the permission list. description. (CMDB_ERROR_RELATION_CARDINALITY_CHECK) Description The operation that you are performing violates the cardinality constraint of the relationship. 120042 Error Because the relationship superclass is a weak relationship. (CMDB_ERROR_CATSUBCLASS_REQD_ATTR_NOT_ALLOWED) Description You are specifying the entry mode option as Required for the categorization class. This option is not allowed. Solution Change the entry mode to Optional. 120041 Error Required attributes are not allowed in categorization classes. this class must also be a weak relationship. and solution Creating more than one instance in a singleton class is not allowed. make sure that the operation does not violate the cardinality constraint. Appendix A BMC Atrium CMDB C API error messages 125 . 120039 Error The operation violates the cardinality constraint of the relationship. Solution Do not create more than one instance from a singleton class. Solution Define this class as a weak relationship. Solution Using the Atrium Explorer. (CMDB_ERROR_INVALID_SINGLETON_CLASS_INST_OPERATION) Description You can create only one instance from a singleton class.BMC Atrium CMDB C API error messages Table A-1: C API error messages (Sheet 7 of 34) Error number 120038 Message type Error Message. description. 120040 Error The relationship endpoint instance does not exist. (CMDB_ERROR_RELATION_END_PT_DOES_NOT_EXIST) Description You are attempting to create a relationship for a CI instance that does not exist. (CMDB_ERROR_SUBCLASS_MUST_BE_RS_WEAK_REFERENCE) Description You cannot derive a regular relationship subclass from a weak relationship superclass. Solution Make sure that the instance exists. 120049 Error The primary key must be a unique index. (CMDB_ERROR_INVALID_CARDINALITY_FOR_WEAK_REFERENCE) Description You are attempting to specify an incorrect cardinality for a weak relationship. Solution Set the cardinality for a weak relationship to either one-to-many or one-toone.6. (CMDB_ERROR_SETTING_LEAD_CLASS_REF_DISALLOWED) Description You cannot modify the attributes propagated from the lead class. Solution You must set the primary key characteristic using an index. Solution Define the weak class of the weak relationship as non-abstract. (CMDB_ERROR_WEAK_INSTANCE_ALREADY_ASSOCIATED) Description You are attempting to specify more than one lead instance for a weak instance.BMC Atrium Core 7. Solution Dissociate the weak instance before trying to associate it with another lead instance. read-only attributes values. description. 126 Troubleshooting Guide . (CMDB_ERROR_PRIMARY_KEY_ISNT_UNIQUE) Description The attribute that you are attempting to set as primary key contains duplicate values. 120046 Error Setting lead class reference values is not allowed. Solution Specify a unique index as the primary key. Solution Do not attempt to modify propagated. 120048 Error You cannot set a primary key characteristic on an attribute. (CMDB_ERROR_NO_WEAK_RELATION_ABSTRACT_CLASS_ALLOWED) Description You cannot create a weak class of the abstract type for a weak relationship. 120044 Error The weak instance is already associated with another lead instance. (CMDB_ERROR_CANNOT_MODIFY_PRIMARY_KEY_ON_ATTRIBUTE) Description You can set an attribute as the primary key only using a unique index. 120045 Error The weak class of the weak relationship cannot be abstract. and solution Invalid cardinality for the weak relationship.04 Table A-1: C API error messages (Sheet 8 of 34) Error number 120043 Message type Error Message. (CMDB_WARN_DELETE_CLASS_FAILED_DEP_REG_CLASS) Description This is a warning that the class being deleted had a derived class. description. 120054 Error The class cannot be deleted because there are class dependencies on this class. 120051 Error The weak class for the weak relationship class cannot be a categorization class. (CMDB_ERROR_NO_RHS_CATSUBCLASS_FOR_WEAK_REFERENCE) Description You are attempting to create the right-hand class as a categorization class in a week relationship. Solution To delete a class that contains data. and solution You can have only one primary key per class. specify Delete With Data as the delete option. 120053 Error The class cannot be deleted because this class has instance data. (CMDB_ERROR_MORE_THAN_ONE_PRIMARY_KEY_DISALLOWED) Description You are attempting to set more than one primary key for a class. Solution To delete a class with dependencies. CMDB_ERROR_NO_SUCH_INDEX Description The index that you specified might be incorrect. specify Delete With Dependencies as the delete option. Solution Define the weak class as a noncategorization class. WARNING: The Delete With Dependencies option also deletes all dependent classes even if they contain data. Appendix A BMC Atrium CMDB C API error messages 127 . 120052 Error The specified index could not be found. Solution Make sure that the index that you provide exists. 120055 Warning This class is a derived class of the class being deleted. (CMDB_ERROR_DELETE_CLASS_FAILED_DATA_EXISTS) Description You are attempting to delete a class that contains data. (CMDB_ERROR_DELETE_CLASS_FAILED_DEPENDECIES_EXISTS) Description You are attempting to delete a class that has a subclass or is a CI instance for a relationship.BMC Atrium CMDB C API error messages Table A-1: C API error messages (Sheet 9 of 34) Error number 120050 Message type Error Message. Solution Specify only one primary key per class. 120061 Error The specified target attribute on the weak class cannot be a derived attribute from a superclass.04 Table A-1: C API error messages (Sheet 10 of 34) Error number 120056 Message type Warning Message. (CMDB_WARN_DELETE_CLASS_FAILED_DEP_WEAK_REF_CLASS) Description This is a warning that the specified weak class of the relationship class is being deleted. Solution Specify a target attribute for the weak class that is not derived from its superclass. 128 Troubleshooting Guide . 120060 Error The data types for the source and target attributes do not match.6. (CMDB_ERROR_NO_SUCH_SOURCE_ATTRIBUTE_FOR_WEAK_REL) Description You are attempting to propagate an attribute that does not exist in the source class. and solution An endpoint for this relationship class is the class being deleted. Solution Make sure that the source attribute exists in the lead class. (CMDB_ERROR_NO_SUCH_TARGET_ATTRIBUTE_FOR_WEAK_REL) Description You are attempting to propagate a nonexistent attribute of the weak class.BMC Atrium Core 7. 120059 Error The target attribute on the weak class for attribute propagation does not exist. (CMDB_ERROR_ATTRIBUTE_DATATYPE_MISMATCH_FOR_WEAK_REL) Description The attributes being propagated from the lead and weak classes must have the same data type. Solution Make sure that the target attribute exists in the weak class. 120057 Warning This class is a weak class of the relationship class being deleted. (CMDB_ERROR_TARGET_WEAK_ATTR_CANNOT_DERIVED_ATTR) Description You are attempting to specify a derived attribute as the target attribute in the weak class. description. Solution Make sure that the data type of the propagated attributes matches. 120058 Error The source attribute on the lead class for attribute propagation does not exist. (CMDB_WARN_DELETE_CLASS_FAILED_DEP_REL_CLASS) Description This is a warning that a CI instance for the specified relationship class is being deleted. (CMDB_ERROR_MISMATCHING_ATTR_DATATYPE) Description The value that you specified for the attribute does not match the attribute definition.BMC Atrium CMDB C API error messages Table A-1: C API error messages (Sheet 11 of 34) Error number 120062 Message type Error Message. 120063 Error Instances cannot be deleted from this form. Appendix A BMC Atrium CMDB C API error messages 129 . 120067 Error An entry in the import item list is invalid. (CMDB_ERROR_CATGORIZATION_SUB_PERM_LIST_INVALID) Description The categorization class permissions must match the permissions of its superclass. Solution Make sure that the item exists in the specified directory. (CMDB_ERROR_CREATE_GUID_FAILED) Description The system was unable to generate a unique identifier. 120064 Error The system failed to create a unique identifier. (CMDB_ERROR_INSTANCE_DELETE_ON_FORM_DISALLOWED) Description You cannot delete an instance from the regular subclass form. Solution Specify appropriate values that match the attribute data type definition. restart your process to generate the GUID. and solution Permissions for a categorization class must be the same as the permissions for the superclass. description. Solution Delete the instance by using the join form of the class. Solution If required. 120068 Error Data type does not match the data type defined for this attribute. Solution Make sure that the categorization class permissions match those of its superclass. (CMDB_ERROR_IMPORT_ITEM_ITEM) Description An item in the specified import directory is not available. 04 Table A-1: C API error messages (Sheet 12 of 34) Error number 120069 Message type Error Message. (CMDB_ERROR_SETTING_FORM_NAME_CHARAC_DISALLOWED) Description The Form Name characteristic is an invalid option for the class. 120070 Error Index list is invalid. 130 Troubleshooting Guide . Solution Specify a valid value for the class characteristic. 120071 Error Setting the form name class characteristic is not allowed. 120074 Error The class name is too long. (CMDB_ERROR_CLASS_NAME_TOO_LONG) Description The class name that you specified cannot exceed its character limit. Solution You cannot set the Form Name class characteristic. Solution Make sure that the index properties that are specified in the error message are valid. Solution Make sure that the attribute value is within the defined range. 120072 Error The data type for the class characteristic value is invalid. Solution Specify a namespace name that is 70 or fewer characters. Solution Specify a class name that is 80 or fewer characters.BMC Atrium Core 7. description. (CMDB_ERROR_INVALID_DATATYPE_FOR_CLASS_CHARAC) Description The value that you specified for class characteristic subclasses does not match its data type. (CMDB_ERROR_NAMESPACE_NAME_TOO_LONG) Description The namespace name that you specified cannot exceed its character limit. and solution Attribute value does not fall within the limits defined for this attribute. Must be 70 or fewer characters.6. (CMDB_ERROR_INVALID_INDEX_LIST) Description You specified an invalid index list. (CMDB_ERROR_ATTRIBUTE_VALUE_OUT_OF_LIMITS) Description The attribute value that you specified is not within the defined range for the attribute. Must be 80 or fewer characters. 120073 Error The namespace name is too long. Solution Specify one of the valid values: 0-None. Appendix A BMC Atrium CMDB C API error messages 131 . Solution Create an alphanumeric name containing any of the wildcard characters: underscore (_) or period (. Solution Specify an attribute name that is 80 or fewer characters. 120080 Error Invalid value for the entry mode. Solution If required. 2-Optional.BMC Atrium CMDB C API error messages Table A-1: C API error messages (Sheet 13 of 34) Error number 120075 Message type Error Message. (CMDB_ERROR_INVALID_ATTRIBUTE_ENTRY_MODE) Description You specified an invalid value for the entry mode subclasses. 1-Required. Must be 80 or fewer characters. and solution The subclass namespace must match the superclass namespace. (CMDB_ERROR_SUBCLASS_SUPERCLASS_NAMESPACE_MISMATCH) Description The namespace that you specified for the subclass does not match its superclass. delete this class and create a new one. 120078 Error The supplied character is not allowed in the name. Solution Specify a value for the required attribute. (CMDB_ERROR_REQUIRED_ATTRIBUTE_VALUE_MISSING) Description You did not specify a value for a required attribute. description. 120077 Error Modifying the namespace name after class creation is not allowed. 3System. (CMDB_ERROR_MODIFY_NAMESPACE_NAME_IS_DISALLOWED) Description You cannot modify the namespace name after the class is created. (CMDB_ERROR_ATTRIBUTE_NAME_TOO_LONG) Description The attribute name that you specified cannot exceed its character limit. 120076 Error No value supplied for a required attribute. (CMDB_ERROR_CHARACTER_DISALLOWED_IN_NAME) Description You specified invalid characters for the name.). or 4-Display_Only. 120079 Error The attribute name is too long. Solution Specify the same subclass namespace as the superclass. 4-Primary_Key. 6-Create_Mode. (CMDB_ERROR_REL_END_POINT_CLASS_NAMESPACE_MISMATCH) Description You are attempting to create a CI instance in a namespace different from that of the relationship class. (CMDB_ERROR_ATTR_subclasses_ID_NOT_UNIQUE) Description The subclass ID you specified is already in use within the specified class hierarchy. (CMDB_ERROR_ENUM_NAME_INVALID) Description The enumeration name you specified is invalid. description. 5-Propogated_Owner.6. 132 Troubleshooting Guide . 120084 Error Setting the propagated owner attribute characteristic is not allowed. 120083 Error Setting the primary key attribute characteristic is not allowed. (CMDB_ERROR_INVALID_DATATYPE_FOR_ATTR_CHARAC) Description The data type that you specified for the attribute characteristic is invalid. 1-View_Perms. 7Audit_Option.BMC Atrium Core 7. 120082 Error Invalid data type for the attribute characteristic. Solution You cannot set the propagated owner attribute characteristic. 2-Change_Perms. Solution Specify a different subclass ID. Solution Specify an attribute ID that is unique within the class hierarchy. 3-Hidden. (CMDB_ERROR_SETTING_PROP_OWNER_CHARAC_DISALLOWED) Description The propagated owner characteristic is an invalid option for the attribute.04 Table A-1: C API error messages (Sheet 14 of 34) Error number 120081 Message type Error Message. or 8-Namespace. Solution You cannot set the primary key attribute characteristic. Solution Specify one of the valid values: 0-None. (CMDB_ERROR_SETTING_PRIMARY_KEY_CHARAC_DISALLOWED) Description The primary key characteristic is an invalid option for the attribute. Solution Specify a CI instance from the same namespace as the relationship class. 120085 Error The namespace for the relationship endpoint class does not match the namespace of the relationship class. 120086 Error Enum name is invalid. and solution The subclass ID is not unique within the class or within the class hierarchy. description. Solution Change one of these values to make the combination unique.BMC Atrium CMDB C API error messages Table A-1: C API error messages (Sheet 15 of 34) Error number 120087 Message type Error Message. (CMDB_ERROR_INVALID_ATTR_LIMIT_DATA_TYPE) Description You specified an invalid value for the attribute limit structure. (CMDB_ERROR_ATTRIBUTE_ID_NOT_UNIQUE) Description You specified an attribute ID that is not unique within the class hierarchy. 120089 Error You do not have access to the class. 120092 Error The dataset ID and Reconciliation Identity combination is not unique. (CMDB_ERROR_DATASET_ID_RECON_ID_NOT_UNIQUE) Description The combination of reconciliation ID and dataset ID is not unique. Solution Contact your CMDB administrator. Solution Contact your CMDB administrator. (CMDB_ERROR_NO_ACCESS_TO_CLASS) Description You do not have permissions to access the class. and solution Attribute ID is not unique within the class or within the class hierarchy. Appendix A BMC Atrium CMDB C API error messages 133 . 120093 Error The class ID is not valid. 120088 Error Invalid data type for the attribute limit structure. Solution Verify that you have specified the correct class ID. Solution Specify a unique attribute ID within the class hierarchy. Solution The data type for the attribute limit structure must either match the data type of the attribute or be NULL. CMDB_ERROR_INVALID_CLASS_ID Description No such class with the class ID that you specified exists. (CMDB_ERROR_NO_ACCESS_TO_ATTRIBUTE) Description You do not have permissions to the access the attribute. 120090 Error You do not have access to the attribute. 120100 Error One of the endpoints specified for the relationship has an invalid class ID.6. 134 Troubleshooting Guide . Solution Specify one of these valid values: CMDB_DELETE_CLASS_OPTION_NONE. Solution Upgrade to the current version of the CMDB API. CMDB_DELETE_CLASS_OPTION_WITH_DATA. 120095 Error Current object store API version is deprecated. 120099 Error The metadata status value specified is invalid. (CMDB_ERROR_QUERY_GRAPH_INVALID_DIRECTION) Description You specified an invalid direction value for the graph query. Solution Specify a valid class ID for the instance. (CMDB_ERROR_INVALID_META_DATA_STATUS) Description You specified an invalid value for the metadata status.BMC Atrium Core 7. and solution The direction provided for graph query is not valid. 120096 Warning Instances skipped during import. (CMDB_ERROR_CURRENT_API_IS_DEPRECATED) Description You are attempting to use an API call that is now deprecated. Solution Specify one of these valid values: CMDB_META_DATA_STATUS_DELETE_PENDING or CMDB_META_DATA_STATUS_CHANGE_PENDING. or 1-Direction_In. CMDB_ERROR_INVALID_DELETE_OPTION) Description You specified an invalid delete option for the class. Solution Specify one of these valid values: 0-Direction_Out. or CMDB_DELETE_CLASS_OPTION_ALL_DEPENDENCIES. 120098 Error The deleteOption value specified is invalid. description.04 Table A-1: C API error messages (Sheet 16 of 34) Error number 120094 Message type Error Message. (CMDB_ERROR_INVALID_REL_ENDPOINT_CLASS_ID) Description You specified an invalid class ID for one of the CI instances in the relationship. (CMDB_WARN_IMPORT_INST_SKIPPED) Description Certain instances were not imported during the import activity. (CMDB_INFO_IMPORT_INST_SUMMARY) Description This message signifies that the instance import summary follows. 120097 Information Instance import summary. Solution Contact your CMDB administrator. (CMDBRE_ERROR_CANCEL_JOB_RUN_FAILED) Description An internal error has caused an unsuccessful cancellation of your reconciliation job. (CMDB_ERROR_UNRECOGNIZED_VERSION_PATCH_STRING) Description The version string for the CMDB patch is invalid. Solution Contact BMC Customer Support for help. Appendix A BMC Atrium CMDB C API error messages 135 . Solution Specify a cardinality of one-to-many or one-to-one for the relationship. Solution Wait until the job finishes to start it again. (CMDB_ERROR_INVALID_CASCADE_DELETE_VALUE) Description You specified an invalid cascade delete option for the relationship. 120105 Error Failed to cancel reconciliation job. 120102 Error A version string in the SHARE:Application_Properties form is invalid. 120103 Error Cascade Delete cannot be enabled for the relationship because its cardinality is invalid for cascade deletes. (CMDB_ERROR_ACCESS_TLS_BLOCK_FAILED) Description Access to the thread local storage block failed. Solution Contact BMC Customer Support for help.BMC Atrium CMDB C API error messages Table A-1: C API error messages (Sheet 17 of 34) Error number 120101 Message type Error Message. Solution Replace the patch string with a valid version string. (CMDBRE_ERROR_START_JOB_RUN_FAILED) Description An internal error has caused your reconciliation job to fail. 120104 Error Reconciliation job cannot be started. description. and solution Internal system error. 120106 Error Job that is already in queue. CMDBRE_ERROR_JOB_ALREADY_QUEUED Description You are attempting to start a job that is already in queue. Solution Make sure that the associated job ID is correct. 120113 Error Number of IDs and Values does not match. Solution Before you cancel a job. (CMDBRE_ERROR_JOB_LOOKUP) Description The job that you are referring to does not exist. Solution Wait until the currently running job is completed and start it again. which is already running. 120109 Error Failed to start an inactive job. 136 Troubleshooting Guide . Solution Make sure that the job exists. Solution Make sure that the Enum ID is valid. (CMDBRE_ERROR_JOB_ALREADY_RUN) Description You cannot start a job that is already running. 120108 Error Failed to find the specified job.BMC Atrium Core 7. 120111 Error Failed to start a job. 120114 Error Invalid Enum ID.6. description.04 Table A-1: C API error messages (Sheet 18 of 34) Error number 120107 Message type Error Message. Solution A job must be in an active state before you start it. Solution Make sure that the number of IDs and the values match. and solution Failed to cancel a job not running. (CMDB_ERROR_ENUM_ID_INVALID) Description You have specified an invalid Enum ID. 120110 Error Job does not exist. (CMDB_ERROR_ENUM_ID_VALUE_LEN_MISMATCH) Description The number of IDs and their values that you specified do not match. (CMDBRE_ERROR_INACTIVE_JOB_START) Description You are attempting to start an inactive job. (CMDBRE_ERROR_JOB_NOT_EXIST) Description The job that you are referring to does not exist. (CMDBRE_ERROR_JOB_NOT_RUNNING) Description You are attempting to cancel a job that is not running. make sure that the job is running. 120121 Error The dataset ID does not exist. Appendix A BMC Atrium CMDB C API error messages 137 . and Delete operations. Solution Make sure that the source dataset exists and is provided. If the problem persists. its superclasses cannot contain the Log audit option setting. Solution Make sure that the superclass and subclasses have the same audit option settings. (CMDB_ERROR_DATASET_OVERLAY_SOURCE_MISSING) Description You did not specify the source dataset ID. Create. Solution Perform the Set.CORE:BMC_Dataset class. Solution Make sure that the If instance for the dataset ID that you specified exists in the BMC. description. 120117 Error You can not set the audit type as "Log" as the derived class has audit type as "Copy". (CMDB_ERROR_INVALID_AUDIT_COPY_TYPE) Description The session ID that you specified for the login information is invalid. make sure that the ID is the same as the DatasetId passed in the API call signature.BMC Atrium CMDB C API error messages Table A-1: C API error messages (Sheet 19 of 34) Error number 120116 Message type Error Message. Solution Make sure that the control structure is correct and your API session is properly initialized. If the DatasetId attribute value is given in the attribute value list. restart the AR System server. 120120 Error Invalid dataset ID reference by the instance. 120122 Error The source dataset ID is missing. (CMDB_ERROR_INVALID_AUDIT_LOG_TYPE) Description If you specified the Copy audit option for your derived class. (CMDB_ERROR_NO_SUCH_DATASET) Description The dataset ID that you specified does not exist. (CMDB_ERROR_INVALID_DATASET_ID) Description The dataset ID that you specified for the instance is invalid. and solution The session ID in the supplied control structure is invalid. (CMDB_WARNING_FOREIGN_KEY_EXPAND_FAILED) Description An error occurred when attempting to expand a federated link. 120124 Error Access to the dataset denied. Solution Make sure no other bulk transaction function is in progress. (CMDB_WARNING_DATASET_CACHE_LOADING) Description An internal error occurred when accessing federated data. (CMDB_ERROR_DATASET_UNDERLAY_INTERNAL_ERROR) Description The specified class ID and reconciliation ID for the underlay dataset do not exist. 120125 Warning Federated data corruption.BMC Atrium Core 7. Solution Make sure that the federated foreign key link has the appropriate BMC_FederatedKeyLink class name.6. Solution Contact your CMDB administrator. description.04 Table A-1: C API error messages (Sheet 20 of 34) Error number 120123 Message type Error Message. and solution An internal error occurred. 138 Troubleshooting Guide . 120126 Error Federation foreign key expansion failed. (CMDB_ERROR_DATASET_NO_PROPER_ACCESS) Description You are attempting to access a dataset for which you do not have appropriate access. Solution Make sure that the control structure is correct and that your API session is properly initialized. 120128 Error Cannot start another bulk transaction because a bulk transaction has already been started. 120127 Error The session ID in the supplied control structure is invalid. Solution Make sure that the access for the dataset is not set to read-only or writable by the client. (CMDB_ERROR_BULK_TRAN_ALREADY_BEGUN) Description You cannot start more than one bulk transaction function at a time. Solution Make sure that the specified class ID and reconciliation ID exist. (CMDB_ERROR_BULK_TRAN_API_SESSION_ID_BAD) Description The API session information that you specified in the bulk transaction function is incorrect. Solution Correct the qualification based on the error message description provided. Solution Specify a valid CMDB RPC port number. 120130 Error Failed to promote class. 390696. and solution The attempted operation cannot be performed because the bulk transaction has not started.BMC Atrium CMDB C API error messages Table A-1: C API error messages (Sheet 21 of 34) Error number 120129 Message type Error Message. Solution You cannot promote a class that is derived from an abstract class. Solution Make sure that the specified superclass exists. Solution Contact your CMDB administrator. and 390697 (Admin thread). 120133 Error The CMDB RPC port specified is invalid. Valid port numbers are 0. (CMDB_ERROR_FEDLINK_LAUNCH_FAILED) Description The federation link that you are attempting to launch failed. (CMDB_ERROR_SUPER_CLASS_NOT_FOUND) Description The superclass that you specified is not found. Appendix A BMC Atrium CMDB C API error messages 139 . (CMDB_ERROR_SUPERCLASS_OF_TYPE_ABSTRACT) Description You are attempting to promote a class that is derived from an abstract class. 120131 Error Federation launch failed. 120132 Error Superclass not found. (CMDB_ERROR_FAILED_TO_RUN_QUALIFICATION) Description The application failed to parse the specific qualification. 120134 Error Failed to parse the qualification. Solution The attempted operation can be performed only after a bulk transaction session is started. (CMDB_ERROR_RPC_SOCKET_RANGE) Description The RPC port that you specified for the BMC Atrium Core is invalid. (CMDB_ERROR_BULK_TRAN_NOT_BEGUN) Description You are attempting to perform a bulk transaction operation before starting a bulk transaction session. which has abstract superclass. description. (CMDB_WARNING_REQUESTED_IMPORT_OBJECT_NOT_FOUND) Description The import item list object (class or attribute) that you requested does not exist in the .6. (CMDB_ERROR_DUPLICATE_DATASET_ID) Description The CoreDatasetId that you specified already exists. 120141 Error Can’t set MarkAsDeleted to “No” on the relationship instance because one or both of the relationship endpoints are MarkAsDeleted. Solution Set MarkAsDeleted to No on both endpoints of the relationship before setting MarkAsDeleted to No on the relationship instance. 120137 Error Cannot import instance because the instance ID already exists. Solution Specify a unique instance ID for the instance or select an import option other than 1.xml (import) file. Solution Select the correct import option.xml (import) file. and solution The requested object was not found in the import buffer. Solution Make sure that the requested import object (class or attribute) exists in the . (CMDB_ERROR_ATTRIBUTE_BELONGS_TO_SUPERCLASS) Description The attribute that you specified is inherited from a superclass and cannot be deleted from this subclass. (CMDB_ERROR_INVALID_DATA_IMPORT_OPTION) Description The import option value that you specified is incorrect. 120140 Error Attribute does not belong to the class specified. 120139 Error The CoreDatasetId specified already exists. 120138 Error Invalid import data option. (CMDB_ERROR_REL_ENDPOINT_MARK_AS_DELETED) Description You are attempting to set MarkAsDeleted to No for a relationship instance for which one or both endpoints are soft deleted (MarkAsDeleted). description.BMC Atrium Core 7. Solution Delete the specified attribute from the superclass. (CMDB_ERROR_INSTANCE_ID_ALREADY_EXISTS) Description The instance ID that you specified already exists.04 Table A-1: C API error messages (Sheet 22 of 34) Error number 120136 Message type Error Message. 140 Troubleshooting Guide . Solution Specify a different CoreDatasetId. Solution You cannot modify the attributes of a relationship instance.InstanceId.096-byte limit on qualifications passed to the CMDBStartJobRun function. description. Solution You cannot retrieve Copy audit data from a class whose audit type is set to a value other than Copy.ClassId. Solution Make sure that you specify a value in correct format for the decimal attribute. Source. 120147 Error Bad decimal value was supplied. (CMDB_ERROR_RE_START_JOB_RUN_INFO_EXCEED_LIMIT) Description After encoding. 120145 Error Class ID and qualification information exceeded the limit of 4. 120146 Error Instance ID is not unique. Solution Specify a unique instance ID for the instance. Destination. Appendix A BMC Atrium CMDB C API error messages 141 . (CMDB_ERROR_MODIFYING_REL_ENDPOINT_VAL_DISALLOWED) Description You are attempting to modify attributes such as. (CMDB_ERROR_DUPLICATE_INSTANCE_ID) Description The instance ID that you specified for the new instance already exists. 120144 Warning Delete class is failed because it has audit data.BMC Atrium CMDB C API error messages Table A-1: C API error messages (Sheet 23 of 34) Error number 120142 Message type Error Message. Solution Divide the classQualList information into more than one API call. the combined length of your specified classQualList and datasetList parameters exceeds the 4. Source. and solution Audit type Copy is not set for this class.096 bytes. (CMDB_ERROR_NO_AUDIT_COPY_CLASS) Description You are attempting to retrieve Copy audit data from a class whose audit type is set to a value other than Copy. (CMDB_ERROR_ATTRIBUTE_BAD_DECIMAL_VALUE) Description The value that you specified for the decimal attribute is invalid. and Destination. (CMDB_WARN_DELETE_CLASS_FAILED_AUDIT_DATA) Description You are attempting to delete a class (without dependencies) and the class or its subclasses has auditing turned on.ClassId.InstanceId of a relationship instance. 120143 Error Modifying the attributes of a relationship endpoint is not allowed. description. Verify your attribute value list when you modify the instance. 142 Troubleshooting Guide .6. Solution You cannot change the instance ID of the instance. Solution Alternate the ordering of query objects between CI (C) and Relationship (R) types (for example C-R-C-R-C). 120152 Error Nested subquery cannot contain recursive query. Cannot allocate additional memory. Report this error message to your administrator. Solution Contact your CMDB administrator. Solution Contact your CMDB administrator. and solution Cannot modify the InstanceId attribute value. Solution Specify the list of class or attribute definitions to export in the exportItemList parameter of the CMDBExportDef function. Once an instance is created. 120150 Error A zero byte memory allocation was performed. (CMDB_ERROR_STRUCT_EXPORT_ITEM_EMPTY) Description You did not specify the list of class or attribute definitions to export in the CMDBExportDef function. (CMDB_ERROR_QUERY_INVALID_OBJECT_SEQUENCE) Description The sequencing of the query objects is invalid. the InstanceId value cannot be modified.BMC Atrium Core 7. (CMDB_ERROR_OUT_OF_MEMORY) Description An internal error occurred when performing an operation.04 Table A-1: C API error messages (Sheet 24 of 34) Error number 120148 Message type Error Message. (CMDB_ERROR_MODIFYING_INSTANCE_ID_VAL_DISALLOWED) Description You are attempting to modify the instance ID of an existing instance. (CMDB_ERROR_ZERO_BTYE_MEMORY_ALLOCATION) Description An internal error occurred when performing an operation. 120151 Error The list of class or attribute definitions to export is empty. 120149 Error Out of memory error. Make sure the alias in the selector list matches with the alias specified in the query list. 120157 Error The selector list provided for the value set operation is invalid. Solution Specify only one attribute in the selector list of the value set operation. (CMDB_ERROR_INVALID_ALIAS_IN_SELECTOR_LIST) Description The alias that you specified for the class does not exist. (CMDB_ERROR_INVALID_VALUESET_QUERY_SELECTOR ) Description You are attempting to specify either no attributes or multiple attributes in the selector list of the value set operation. and solution The qualification operator provided in the query is invalid. Solution Make sure that the objects that you specify in the selector list is a subset of the objects in the query list. Solution Specify one of the following values for the qualification operator: 1—(CMDB_QUERY_QUAL_OP_NONE) 2—(CMDB_QUERY_QUAL_OP_AND ) 3—(CMDB_QUERY_QUAL_OP_OR) 4—(CMDB_QUERY_QUAL_OP_NOT) 5—(CMDB_QUERY_QUAL_OP_SIMPLE) 6—(CMDB_QUERY_QUAL_OP_SET) 120154 Error The alias supplied in the selector list is invalid. (CMDB_ERROR_INVALID_QUERY_QUAL_OP) Description The qualification operator that you provided in the query is invalid.BMC Atrium CMDB C API error messages Table A-1: C API error messages (Sheet 25 of 34) Error number 120153 Message type Error Message. (CMDB_ERROR_ALIAS_MISMATCH) Description You are attempting to specify two different sets of objects in the selector list and query list. 120156 Error There is a mismatch between aliases in the selector list and the query list. description. Solution Make sure the alias that you specified in the selector list matches the alias specified in the query list. Appendix A BMC Atrium CMDB C API error messages 143 . first derive a subclass from the given abstract class. (CMDB_ERROR_QUERY_DISALLOWED_FOR_CLASS) Description You are attempting to create a query for the federated abstract classes listed in the error message. Solution Do not include the given abstract classes in your query. and solution You cannot query data using class. 120168 Error An invalid value set type has been specified in the query qualification. 120160 Warning The abstract class specified will not contain a view because it has no subclasses. (CMDB_ERROR_INVALID_QUERY_VALUESET_TYPE) Description You specified an invalid value set type in the query qualification. Solution Contact your CMDB administrator. The BMC_FederatedBaseRelationship class is specified in the relationship list.6.FED:BMC_FederatedBaseRelationship or BMC. BMC. Because abstract classes do not have any attributes. 120167 Error Query processor has encountered an internal error.FED: BMC_FederatedBaseElement.04 Table A-1: C API error messages (Sheet 26 of 34) Error number 120159 Message type Error Message. you cannot construct a query that uses them. This error might occur if: The start node of your query is the BMC_FederatedBaseElement class. (CMDB_WARN_ABSTRACTVIEW_NO_SUBCLASS_FOR_VIEW) Description To create a database view for an abstract class. Creating a view from an abstract class is not allowed.BMC Atrium Core 7. description. Solution Make sure that the value set type that you specified in the query is either 1—(CMDB_QUERY_QUAL_VALUESET_TYPE_VALUESET) or 2—(CMDB_QUERY_QUAL_VALUESET_TYPE_QUERY). 144 Troubleshooting Guide . (CMDB_ERROR_QUERY_INTERNAL) Description An internal error occurred with the query processor. Solution Make sure that the simple query operation type that you specified in the query qualification is one of the following values: 1—(CMDB_QUERY_QUAL_SIMPLEOP_EQUAL) 2—(CMDB_QUERY_QUAL_SIMPLEOP_GREATER) 3—(CMDB_QUERY_QUAL_SIMPLEOP_GREATER_EQUAL) 4—(CMDB_QUERY_QUAL_SIMPLEOP_LESS) 5—(CMDB_QUERY_QUAL_SIMPLEOP_LESS_EQUAL) 6—(CMDB_QUERY_QUAL_SIMPLEOP_NOT_EQUAL) 7—(CMDB_QUERY_QUAL_SIMPLEOP_LIKE) 120173 Error String Operation on a null pointer was attempted. and solution An invalid simple query operation has been specified in the query qualification. (CMDB_ERROR_NULL_STRING_POINTER_OPERATION) Description An internal error occurred when performing a string function. Solution Contact your CMDB administrator. 120175 Error The federation relationship has no join condition qualification. Solution The federated relationship specified in the query does not appear to have any join condition. 'InstanceId' = $RequestId$). Appendix A BMC Atrium CMDB C API error messages 145 .BMC Atrium CMDB C API error messages Table A-1: C API error messages (Sheet 27 of 34) Error number 120169 Message type Error Message. (CMDB_ERROR_FEDERATED_ATTRIBUTE_DEFAULT_NOT_ALLOWED) Description An attribute of the federated class contains a NULL value. Specify a value for the CMDB_CLASS_CHARAC_RELATION_LINK_QUALIFIER characteristic for the federated relationship class. (CMDB_ERROR_INVALID_QUERY_SIMPLEOP) Description You specified an invalid simple query operation type in the query qualification. 120174 Error Federation class attribute cannot have default values. description. Solution Make sure that the federated class attribute contains a value other than NULL. (CMDB_ERROR_MISSING_RELATIONSHIP_LINK_QUALIFICATION) Description You are attempting to create a federated relationship for a class with no qualification (for example. Solution Create attributes for only nonabstract federated data classes.6. 120179 Error Federation class cannot have indices. (CMDB_ERROR_FEDERATED_INVALID_CHARACTERISTIC) Description You are attempting to specify an invalid class characteristic for a federated class. Solution Federated classes and subclasses are created based on the external data that you want to federate with BMC Atrium CMDB. For more information about these characteristics. (CMDB_ERROR_FEDERATED_ATTRIBUTE_CREATE_NOT_ALLOWED) Description You are attempting to create attributes for a Federated Relationship class or an abstract Federated Data class. description. You cannot create a subclass of a federated class. Create an index in your external data store. (CMDB_ERROR_FEDERATED_SUBCLASSING_NON_ALLOWED) Description You are attempting to create a federated subclass. Solution Federated classes cannot have indices. 120180 Error Audit is not allowed on federation classes. 120177 Error You are not allowed to create a federation subclass.04 Developer’s Reference Guide 146 Troubleshooting Guide . see the BMC Atrium Core 7. (CMDB_ERROR_FEDERATED_INDEX_NOT_ALLOWED) Description You are attempting to create indices on a federated class. Solution Auditing is not supported on federated classes.BMC Atrium Core 7. (CMDB_ERROR_FEDERATED_AUDIT_NOT_ALLOWED) Description You are attempting to set the Audit option for a federated class. and solution You are not allowed to create attributes on this federation class.6.04 Table A-1: C API error messages (Sheet 28 of 34) Error number 120176 Message type Error Message. 120181 Error The federation characteristic specified is invalid. Solution Specify only those characteristic that are defined for federation. This error occurs if you attempt to call: The CMDBGetInstance. CMDBImportData. 120185 Error This operation is not allowed on federation class. Appendix A BMC Atrium CMDB C API error messages 147 . CMDBCreateInstance. Solution Make sure that such a vendor exists. CMDBSetInstance. Solution Make sure that only one federated data interface exists for each federated data class. Solution Do not perform the listed operations. The CMDBExportData. 120183 Error There are more than one federated data interfaces for the given federated data class. (CMDB_ERROR_FEDERATED_NO_SUCH_VENDOR) Description The vendor plug-in that you specified for the federated class does not exist. CMDBGetlistInstance. (CMDB_ERROR_FEDERATED_NOT_LAUNCHABLE_FEDERATION) Description You are attempting to launch a federated interface that is not of the Launch type.BMC Atrium CMDB C API error messages Table A-1: C API error messages (Sheet 29 of 34) Error number 120182 Message type Error Message. and solution Federation relationship class cannot be weak. CMDBGetInstanceBLOB. or CMDBGraphQuery function on federated data and federated relationship classes. 120186 Error No such external data source exists. 120184 Error The given federated interface is not a launch type interface. Solution Specify the correct federated interface for the launch. description. Solution You cannot propagate a federated relationship as a weak relationship. (CMDB_ERROR_FEDERATED_MORE_THAN_ONE_INTERFACE_MATCH) Description You are attempting to create multiple federated data interfaces for the given federated data class. (CMDB_ERROR_FEDERATED_WEAK_RELATION_NOT_ALLOWED) Description You are attempting to propagate a federated relationship as a weak relationship. (CMDB_ERROR_FEDERATED_OPERATION_NOT_ALLOWED) Description You are attempting to perform an operation that is not supported for a federated class. CMDBDeleteInstance. or CMDBGetmultipleInstances function on federated relationship classes. (CMDB_ERROR_FEDERATED_NO_SUCH_VENDOR_TABLE) Description The vendor table that you specified for the federated class does not exist.BMC Atrium Core 7. and solution No such table exists in the given external data source. Solution Make sure that such a vendor table exists. 120188 Error No such field exists in the given table of the external data source. Solution Specify the attribute limit of the federated class greater than that of the external field. 120191 Error BMC Remedy AR System plugin server for BMC Atrium CMDB federation is not running. (CMDB_ERROR_FEDERATED_PLUGIN_SERVER_NOT_RUNNING) Description The plug-in server for the federation is not running. you cannot set the attribute limit to 10 characters. 120190 Error The limit for the attribute does not fall within the range defined for the corresponding field in the external data source. Solution Make sure that such a vendor field exists. if the limit of the external field is a maximum size of 5 characters. For example.6. Solution Match the vendor field data type and make sure that it matched the data type of the federated attribute. (CMDB_ERROR_FEDERATED_NO_SUCH_VENDOR_FIELD) Description The vendor field that you specified for the federated class does not exist. (CMDB_ERROR_FEDERATED_EXCEEDS_EXTERNAL_LIMIT) Description The limit of a federated class attribute that you are creating exceeds the field limit of the external field to which it is mapped. description. 120189 Error Data type of the attribute does not match the data type of the field in the external data source. Solution Restart the plug-in server before you perform any federation operation. 148 Troubleshooting Guide .04 Table A-1: C API error messages (Sheet 30 of 34) Error number 120187 Message type Error Message. (CMDB_ERROR_FEDERATED_ATTRIBUTE_DATATYPE_MISMATCH) Description The data type of the vendor field does not match the federated attribute to which the federated data is to be imported. (CMDB_ERROR_FEDERATED_QUERY_NO_RESTRICTIVE_QUAL) Description You are attempting to create a query for a federated data class that requires a qualification. Solution Specify query objects before and after the federated relationship object in your CMDBQueryByPath function. Solution Set the FederationActionType attribute to Data. Solution Set the FederationAccessMethod attribute to Class. 120193 Error You must provide a source or destination when querying a federated relationship. (CMDB_ERROR_FEDERATED_ACTION_TYPE_MUST_BE_DATA) Description You are attempting to create an instance of BMC. 120196 Error You must provide a qualification to search this federated class.CORE. 120194 Error Federation Access Method must be of type 'Class'. with no query objects before or after the federated relationship query object.BMC Atrium CMDB C API error messages Table A-1: C API error messages (Sheet 31 of 34) Error number 120192 Message type Error Message. Solution If you set the CMDB_CLASS_CHARAC_REQUIRES_QUALIFIER_FOR_QUERY characteristic as 1.CORE. 120195 Error Federation Action Type must be of type 'Data'. and solution Federated relationship class cannot be the first or last query object. (CMDB_ERROR_FEDERATED_INVALID_QUERY_OBJECT_INDEX) Description You are attempting to create a query for the federated data class with the federated relationship class as the first or the last object in the query.CONFIG:BMC_FederatedDataInterface class for which the FederationAccessMethod attribute is set to a value other than Class. (CMDB_ERROR_FEDERATED_ACCESS_METHOD_MUST_BE_CLASS) Description You are attempting to create an instance of the BMC.CONFIG:BMC_FederatedDataInterface class for which the FederationActionType attribute is set to a value other than Data. specify a qualification for the federated data class. Solution Make sure that your query follows the C->R->C construct. Appendix A BMC Atrium CMDB C API error messages 149 . where C indicates class and R indicates federated relationship. description. The source dataset from which to import the data is not specified. (CMDB_ERROR_FEDERATED_FEDREL_MISSING_SOURCE_DEST) Description This error occurs when you specify a federated relationship as one of the query objects for the CMDBQueryByPath function. 120204 Error The relation passed in CMDBGraphWalkRelationList is not of type Relationship or Federated relationship. 120202 Error The structure CMDBGraphWalkState is invalid. Solution Do not include a qualification for the federated relationship class query object. No more CIs or relationships exist that match the query that you executed. description. (CMDB_ERROR_QUERY_QUALIFIER_NOT_ALLOWED) Description You specified qualification against a federated relationship class query object when querying by using the CMDBQueryByPath function. call the CMDBGraphWalkBegin function before calling the CMDBGraphWalkNext function.6. or you did not call the CMDBGraphWalkBegin function before calling the CMDBGraphWalkNext function. (CMDB_ERROR_FEDERATION_CLASSES_NOT_SUPPORTED) Description The action that you are performing is not supported for a federated data class. Also. (CMDB_ERROR_GW_INVALID_GRAPH_STATE_STRUCTURE) Description You are either attempting to modify the CMDBGraphWalkState structure. This operation is not allowed. Solution Do not modify the CMDBGraphWalkState structure. (CMDB_WARN_GW_NO_MORE_CHUNK) Description The query has completed the search. (CMDB_ERROR_GW_CLASS_NOT_RELATIONSHIP_TYPE) Description You are attempting to specify a CI class in the CMDBGraphWalkRelationList structure for the graph walk. Solution Make sure that the class that you specify is of the relationship or federated relationship type.BMC Atrium Core 7. 120203 Warning No more chunks available. Solution Verify the action that you are performing.04 Table A-1: C API error messages (Sheet 32 of 34) Error number 120197 Message type Error Message. 120200 Error Super class and subclass class types are not the same. 150 Troubleshooting Guide . and solution Federated classes are not supported for this action. This operation is not allowed 120206 Warning The query matched more than the maximum number of results specified by the CMDB server. (CMDB_WARN_GW_CLASS_IGNORED_FROM_LIST) Description You are attempting to assign the CMDBGraphWalkSelectOrAndFilterList array with a BMC_Dependency class.cfg configuration file. 120207 Error The operation or tag used in the federated relationship qualification is not supported for walking the graph. description. (CMDB_ERROR_GW_OP_OR_TAG_NOT_SUPPORTED_FED_RELSHIP) Description The qualification you defined for the federated relationship class contains operations that the graph walk function cannot perform. (CMDB_WARN_MAXIMUM_QUERY_RESULST_LIMIT) Description The number of rows matched by your query exceeds the number specified for the CMDB-Max-Results-Per-Query parameter in the ar. Solution Update the federated relationship class definition to exclude the following illegal operations and tags: Illegal operation: AR_COND_OP_FROM_FIELD (External) Illegal tags: AR_STAT_HISTORY (Status History field) AR_VALUE_SET (In clause) Appendix A BMC Atrium CMDB C API error messages 151 . Solution Either specify additional qualifications for the query to return fewer rows or increase the number specified for the CMDB-Max-Results-Per-Query parameter.BMC Atrium CMDB C API error messages Table A-1: C API error messages (Sheet 33 of 34) Error number 120205 Message type Warning Message. and solution This class will be ignored from the CMDBGraphWalkSelectOrAndFilterList array because this is of relationship type. 120209 Error (CMDB_ERROR_CONFIGURATION_LABEL_NOT_FILLED) Configuration label is missing. The default level is set to 505. cmdbengine libraries. By default. Set the environment variable MAXIMUMQUALLEVEL to a value higher than 500 to increase the maximum qualification level. 152 Troubleshooting Guide . 120213 Error Graph format is not supported by the server Description You used the BMC Atrium CMDB client to request a Query By Path with the result format of Graph to a server that does not support the graph output. (CMDB_ERROR_EXCEED_MAXIMUM_QUAL_NESTING_LEVEL) Description The query qualification you defined contains too many AND/OR operators. field ID: 530017300) Solution Make sure that you specify a value for the ComponentName attribute of the CMDB Server configuration instance.6. a maximum of 500 AND/OR operators are allowed in the qualification.CONFIG:BMC_UIComponent (CMDB Server configuration instance) class that you are attempting to update or create. cmdbengine libraries are built with 1 MB stack memory. Description You failed to provide a configuration label for the instance of the BMC. Solution Perform the following steps: Change the complex qualification to use fewer AND/OR operators. the cmdbapi. and solution The qualification used for the query API has too many levels of nesting involved. Try using an IN operation in the qualification. you can increase the memory allocation for the cmdbapi. By default. If you modified the stack memory allocated for the binaries to a higher value.CORE.04 Table A-1: C API error messages (Sheet 34 of 34) Error number 120208 Message type Error Message. Solution Request the output in the list format instead.BMC Atrium Core 7. (Attribute Name: ComponentName. or connect to a server that supports graph output. description. Appendix B BMC Atrium Core Console active link error messages Table B-1 lists the error number. You do not have access permissions to perform this operation. Description You are attempting to view the audit history of the instance. Appendix B BMC Atrium Core Console active link error messages 153 . To view audit history. at least one class must be audit enabled. No changes were saved. Solution Contact your CMDB administrator. Solution To save your changes before closing a form. 13204 Error You do not have access to any audited entry for this instance. Table B-1: BMC Atrium Core Console active link error messages (Sheet 1 of 4) Error number 13015 Message type Error Message. Description The Audit option is not enabled for any class in the Common Data Model (CDM). Description The instance for which you want to view audit history has no data. description. Solution Make sure there is data for the specific instance. and solution for each BMC Atrium Core Console error that is generated by active links. description. message type. message text. (OBJSTR:OnCancel_Cancel_Close/Undisplay) Description Your changes were not saved. 20152 Warning Close operation canceled. and solution Auditing not enabled for any class. Solution Contact your CMDB administrator to make sure the Audit option for classes is enabled both at the class and attribute level. use the Cancel button. 13205 Warning There is no audited entry for this instance. 125002 Error Please specify Data Type. Solution Specify a data type for the field on the Characteristics tab.6.6. (OBJSTR:AttributeDef_OnSelect_CharacteristicsTab01) Description You did not specify a data type for a field on the Characteristics tab. Solution Specify a data type for the field. description. and solution Online Help has not been installed.04 Table B-1: BMC Atrium Core Console active link error messages (Sheet 2 of 4) Error number 44000 Message type Error Message. 125004 Error Please specify Data Type.04 Help.04 Administrator's Guide.BMC Atrium Core 7. 120065 Error You must provide ID Values for a Custom Selection. (OBJSTR:Help_OpenHelpFile) Description You have not installed the BMC Atrium CMDB 7. Solution Specify a data type for the field on the Characteristics tab. see the BMC Atrium CMDB 7. (OBJSTR:AttributeDef_OnSelect_CharacteristicsTab04) Description You did not specify the data type for a field on the Characteristics tab. (OBJSTR:AttributeDef_CheckCustomSelection ) Description You did not specify ID values for the field values when creating a custom selection field. 125005 Error Please specify Data Type. Solution Specify ID values for the custom selection field. (OBJSTR:AttributeDef_OnSelect_CharacteristicsTab03) Description You did not specify the data type for a field on the Characteristics tab. 154 Troubleshooting Guide . (OBJSTR:AttributeDef_OnSelect_CharacteristicsTab02) Description You did not specify the data type for a field on the Characteristics tab. 125003 Error Please specify Data Type. Solution Specify a data type for the field on Characteristics tab. Solution To install the online Help.6. Role 2. Solution Specify a different name for your class. Appendix B BMC Atrium Core Console active link error messages 155 . 125008 Error Invalid superclass. 125007 Error There is already an existing class with class name $490001100$ in the namespace $400109900$. Solution Specify these values before saving. (OBJSTR:AttributeDef_OnSelect_CharacteristicsTab05) Description You did not specify the data type for a field on the Characteristics tab. 125009 Error Namespace and Class Name are required subclasses. (OBJSTR:ClassDef_ChkSuperclassIsNotFinalClass02) Description You are attempting to derive a subclass from a final class. Solution Specify the class name and namespace attributes. and solution Please specify Data Type. Class $400103900$ is a final class and cannot be used as a superclass. (OBJSTR:ClassDef_ChkDuplicateClass02) Description The class name that you specified is not unique within the class namespace. and Association Enforcement are required subclasses for relationship classes. Class 2. Solution Specify a data type for the field on Characteristics tab. (OBJSTR:ClassDef_OnSaveChkReqsubclassesForRelationship) Description You did not specify the required attributes for the relationship class. 125006 Error Namespace and Class Name must be entered before you can add or search attributes. Solution Specify a namespace and class name. description. Solution You cannot derive a subclass from a final class. (OBJSTR:ClassDef_OnSaveChkReqsubclasses) Description You did not specify the class name and namespace attributes for the subclass. (OBJSTR:ClassDef_Attrib_AddSearchBtns_CheckForClassAndName space_Msg) Description You did not specify a namespace and class name for the attribute. 125010 Error Class 1. Role 1.BMC Atrium Core Console active link error messages Table B-1: BMC Atrium Core Console active link error messages (Sheet 3 of 4) Error number 125005 Message type Error Message. (OBJSTR:AttributeDef_SaveChanges ) Description The attribute number specified in the message is saved. and solution This attribute is already part of the Index. 125028 Error Please select an Attribute from Class 1 and Class 2. (OBJSTR:IdxCon-IndexNameLooseFocus01a) Description You are attempting to specify an attribute for the index that is already in use.BMC Atrium Core 7. (OBJSTR:WRdlg-cmdMapWeakRel01) Description You did not specify the attribute that you want to propagate in the weak relationship. You can only map Attributes with the same data type. Please use a different name. 125014 Error There is already an index by the name of: $400111200$.6. 125029 Error Invalid data type mismatch. 156 Troubleshooting Guide . (OBJSTR:WRdlg-cmdMapWeakRel02) Description The data types of the attributes that you specified do not match. 125013 Error Please enter the Index Name first. 125030 Information Attribute '$400009700$' has been saved. description. (OBJSTR:IdxCon-AttribAlreadyExist) Description You are attempting to specify an attribute for the index that is already in use. Solution Specify a different attribute. Solution You must specify an attribute from Class 1 and Class 2. (OBJSTR:IdxCon-GainFocusProperty_tbl) Description You must specify a name for the index before you create it.04 Table B-1: BMC Atrium Core Console active link error messages (Sheet 4 of 4) Error number 125012 Message type Error Message. Solution Make sure that the data types of the attributes match. Solution Specify a different attribute. Solution Specify an index name. description. message type. or between this $490021100$ and another $490021101$. Solution Make sure that the instance name is correct. and solution No entry found in SHARE:AssociationType with associationTypeId = $500000041$. 20279 Error The relationship $490005100$ between $490021100$ and $490021101$ is defined as 1 to 1. and solution for each error that is generated by the filters. Appendix C BMC Atrium Core Console filter error messages 157 . Table C-1: CMDB Console filter error messages (Sheet 1 of 6) Error number 20163 Message type Error Message. message text. (OBJSTR:Lookup Association Name5) Description The association type that you specified is not found. To create more than one relationship for the specified instance. and there is already an association of type $490005100$ between this $490021101$ and another $490021100$. (BSM:AUD_AssocEnforce1-1Relationship 2) Description You are attempting to create a relationship for an instance that is already related to another instance.Appendix C BMC Atrium Core Console filter error messages Table C-1 lists the error number. Solution Make sure that the association type exists. specify a many-to-one or one-tomany cardinality for it. description. Solution Make sure that the instance name is correct.” and there is already an association of type $490005100$ between this $490021100$ and another $490021101$.04 Table C-1: CMDB Console filter error messages (Sheet 2 of 6) Error number 20280 Message type Error Message. 20369 Error No entry found in SHARE:Object with Form Name = $-5$. 20366 Error No entry found in SHARE:MenuItem_LT with Developer Name = $300132000$. Solution Contact your CMDB administrator. (OBJSTR:Instance_CheckAbstractClassNoInstantiate) Description You cannot derive an instance from an abstract class. 158 Troubleshooting Guide . To create more than one relationship for the specified instance. 50030 Error Invalid instance related operation on this abstract class. (OBJSTR:Lookup Form Name5) Description The form name that you specified is not found. Solution Make sure that the superclass name that you specified for the instance is correct. specify a many-to-one or one-tomany cardinality for it. (OBJSTR:Lookup Localized String5) Description The localized string for the menu item is not found.6. and there is already an association of type $490005100$ between this $490021101$ and another $490021100$. and solution The relationship $490005100$ between $490021100$ and $490021101$ is defined as “1 to Many”. To create more than one relationship for the specified instance. (BSM:AUD_AssocEnforce1-ManyRelationship 2) Description You are attempting to create a relationship for an instance that is already related to another instance. specify a many-to-one or one-tomany cardinality for it.BMC Atrium Core 7. Solution Contact your CMDB administrator. Solution Make sure that the instance name is correct. 20281 Error The relationship $490005100$ between $490021100$ and $490021101$ is defined as “Many to 1. description. (BSM:AUD_AssocEnforceMany-1Relationship 2) Description You are attempting to create a relationship for an instance that is already related to another instance. Appendix C BMC Atrium Core Console filter error messages 159 . and solution Class $400124700$ is a Singleton class and can only have one instance. 50063 Error Instances cannot be deleted from this form. This instance is already a part of another weak relationship. Class ID: $490008100$. Solution Make sure that the instance name that you specified for the weak instance is correct. Solution Do not modify the reference values for the lead class. Weak instance is already associated to another lead instance. (OBJSTR:Instance_CheckSingleton02) Description You cannot derive more than one instance from a singleton class. 50040 Error The role <number> instance does not exist. Instance ID: $490008000$.BMC Atrium Core Console filter error messages Table C-1: CMDB Console filter error messages (Sheet 3 of 6) Error number 50038 Message type Error Message. Solution Make sure that you are using the join form to delete the instance. 50044 Error Weak relationship instance cannot be created. The Class ID and Instance ID combination was not found. Solution Make sure that the class name that you specified for the singleton class is correct. description. Solution Make sure that the Instance ID for the specified Class ID exists. (OBJSTR:Instance_CheckRelationshipEndpoint <endpointNumber>) Description The instance ID specified in the role number for the specified class is not found. 50046 Error Modifications to the lead class references values are not allowed. (OBJSTR:Instance_RelWeakRef:BMC:<className>:<stepNumber>) Description You are attempting to modify the reference values of the lead class in a weak relationship. (OBJSTR:Instance_CheckDeleteOp) Description You cannot delete an instance from the instance base form. (OBJSTR:Instance_RelWeakRef:<className>:<stepNumber>) Description You cannot specify the instance as a weak instance more than once. 125019 Error Invalid Default Value for selection subclasses. and solution Duplicate subclasses ID $400004800$ for attribute $400009700$. (OBJSTR:Class_ChkDuplicateClass02) Description The class name and namespace combination that you specified for the class is not unique.04 Table C-1: CMDB Console filter error messages (Sheet 4 of 6) Error number 125016 Message type Error Message.h header file. description.6. 125018 Error Invalid subclasses ID for attribute $400009700$. Solution Make sure that the ID that you specify is not a system-reserved value. (OBJSTR:AttributeDef_CheckForDupsubclassesID_Msg) Description The field ID that you specified for the attribute is already in use in the class. 125020 Error There is already an existing class with class name $490001100$ in the namespace $400109900$. Please specify a different class name. (OBJSTR:AttributeDef_CheckSelectionDefaltValue) Description The default value that you specified for the subclass is invalid. 125016 Error Duplicate subclasses Name for attribute $400009700$. (OBJSTR:AttributeDef_CheckForDupsubclassesName_Msg) Description The field name that you specified for the attribute is already in use in the class. Solution Specify values for these required fields. Solution Specify a different field name. 160 Troubleshooting Guide . Solution Specify a default value from the list of approved values. Subclasses IDs below 100 are reserved for Core subclasses. 125017 Error Data Type and Attribute Name must be specified. (OBJSTR:AttributeDef_CheckReservedsubclassesID) Description The ID that you specified for the subclass is a reserved value. For more information about reserved values. (OBJSTR:AttributeDef_CheckRequiredsubclasses) Description Data type and attribute name are required fields for the subclass.BMC Atrium Core 7. Solution Specify a different field ID. Solution Make sure that the class name is unique within the specified namespace. see the cmdb. 125027 Error The relationship between $400126800$ and $400126900$ is defined as “Many to 1. (OBJSTR:Instance_EnforceMany-1Relationship02) Description The relationship cardinality for the specified instances is violated.” and there is already a relationship instance between $400126900$ and $400126800$.” and there is already a relationship instance between $400126800$ and $400126900$. (OBJSTR:Instance_Enforce1-ManyRelationship02) Description The relationship cardinality for the specified instances is violated. Solution Do not specify more than one relationship between the two instances. and solution This is an invalid combination of the Abstract and Final subclasses. Solution Make sure that you specify only one class type for the subclass. 125033 Error Spaces are not allowed in the Attribute Name Field. (OBJSTR:AttributeDef_CheckSpaceInName02) Description You are attempting to create an attribute name that has a blank character.BMC Atrium Core Console filter error messages Table C-1: CMDB Console filter error messages (Sheet 5 of 6) Error number 125021 Message type Error Message. 125025 Error The relationship between $400126800$ and $400126900$ is defined as 1 to 1. description. and there is already a relationship instance between $400126800$ and $400126900$. Solution Do not specify more than one relationship between the two instances. Solution Create attribute name fields with no space or wildcard characters. (OBJSTR:Instance_Enforce1-1Relationship02) Description The relationship cardinality for the specified instances is violated. Solution Do not specify more than one relationship between the two instances. 125026 Error The relationship between $400126800$ and $400126900$ is defined as “1 to Many. (OBJSTR:Class-ChkAbstractFinal) Description You are attempting to derive a subclass as an abstract and final class. Appendix C BMC Atrium Core Console filter error messages 161 . (OBJSTR:Class_CheckSpaceInSuperClass02) Description You are attempting to create a superclass field that has a blank character. 125035 Error Spaces are not allowed in the Superclass Field. 162 Troubleshooting Guide .04 Table C-1: CMDB Console filter error messages (Sheet 6 of 6) Error number 125034 Message type Error Message.6. Solution Create class name fields with no space or wildcard characters. (OBJSTR:Class_CheckSpaceInName02) Description You are attempting to create a class name that has a blank character.BMC Atrium Core 7. description. and solution Spaces are not allowed in the Class Name Field. Solution Create superclass fields with no space or wildcard characters. Error The job is already running. Table D-1: Reconciliation Engine error messages (Sheet 1 of 14) Message type Error Message. Solution Contact your CMDB administrator. 3 If you still encounter this error after performing the previous steps. message text. Note: If you do not see any problems in the API log. and solution for each Reconciliation Engine error. 2 Stop the Reconciliation Engine (arrecond. Description An error in the operating system might have occurred.D Error number 101000 101008 Appendix Reconciliation Engine error messages Table D-1 lists the error number. and solution Cannot create a new thread of execution. you might need to restart the AR System server. Description You are attempting to start a job that is already running.exe) process and start it again. Solution To resolve this issue: 1 Make sure that the job definition name is correct. 101010 Error Cannot find job definition with this name. Appendix D Reconciliation Engine error messages 163 . Solution Wait until the current job run is completed and then restart the job. message type. description. Description The job definition name that you specified does not exist. description. enable AR System API logging to verify any AR System issues. 3 If you still encounter this error after performing the previous steps. enable AR System API logging to verify any AR System issues. 2 Stop the Reconciliation Engine (arrecond.6.exe) process and start it again. Description The job definition ID that you specified does not exist.04 Table D-1: Reconciliation Engine error messages (Sheet 2 of 14) Error number 101011 Message type Error Message.BMC Atrium Core 7. Note: If you do not see any problems in the API log. 3 If you still encounter this error after performing the previous steps. 101012 Error The job is not active. description. Solution To resolve this issue: 1 Make sure that the job definition ID is correct. and solution Cannot find job definition with this ID. you might need to restart the AR System server. 101013 Error Activity run failed because in the object store cache class does not exist. 164 Troubleshooting Guide . 2 Stop the Reconciliation Engine (arrecond. you might need to restart the AR System server. enable AR System API logging to verify any AR System issues. Solution Modify the Change Pending job status to Active before you run it again. Description The activity that you attempted to run failed because the cache data for the Reconciliation Engine job definition does not exist. Description The job that you are attempting to run is not available. Note: If you do not see any problems in the API log. Solution To resolve this issue: 1 Make sure that the job definition is correct.exe) process and start it again. Note: If you do not see any problems in the API log.Reconciliation Engine error messages Table D-1: Reconciliation Engine error messages (Sheet 3 of 14) Error number 101014 Message type Error Message. you might need to restart the AR System server. 3 If you still encounter this error after performing the previous steps. Solution To resolve this issue: 1 Make sure that the job definition is correct. 2 Stop the Reconciliation Engine (arrecond.exe) process and start it again. 3 If you still encounter this error after performing the previous steps. you might need to restart the AR System server. Solution Specify a unique name for the dataset. and solution Error in loading datasets. description. 101015 Error Error in creating dataset entry. enable AR System API logging to verify any AR System issues. 2 Stop the Reconciliation Engine (arrecond.exe) process and start it again. Appendix D Reconciliation Engine error messages 165 . Note: If you do not see any problems in the API log. Description An error occurred with the Reconciliation Engine cache data for job definitions or with BMC Atrium Core class metadata. Description An error occurred with the Reconciliation Engine cache data for job definitions or with BMC Atrium Core class metadata. 101016 Error Rename failed. dataset name <{1}> already exists. Solution To resolve this issue: 1 Make sure that the job definition is correct. Description You are attempting to rename a dataset with a name that already exists for a different dataset. enable AR System API logging to verify any AR System issues. Description The dataset that you are attempting to rename does not exist. Note: If you do not see any problems in the API log. Note: If you do not see any problems in the API log. enable AR System API logging to verify any AR System issues.exe) process and start it again. 3 If you still encounter this error after performing the previous steps. you might need to restart the AR System server. you might need to restart the AR System server. Description An error occurred with the Reconciliation Engine cache data for job definitions or with BMC Atrium Core class metadata. enable AR System API logging to verify any AR System issues. 101019 Error Loading of configuration definition failed as there is no previous steps.BMC Atrium Core 7.exe) process and start it again. Description An error occurred with the Reconciliation Engine cache data for job definitions or with BMC Atrium Core class metadata. 3 If you still encounter this error after performing the previous steps. 2 Stop the Reconciliation Engine (arrecond.exe) process and start it again. description. 101018 Error Error in loading job definitions. you might need to restart the AR System server. Note: If you do not see any problems in the API log. and solution Rename failed. dataset <{1}> does not exist. enable AR System API logging to verify any AR System issues. 2 Stop the Reconciliation Engine (arrecond. 166 Troubleshooting Guide . Solution To resolve this issue: 1 Make sure that the job definition is correct. Solution To resolve this issue: 1 Make sure that the job definition is correct. 3 If you still encounter this error after performing the previous steps.04 Table D-1: Reconciliation Engine error messages (Sheet 4 of 14) Error number 101017 Message type Error Message.6. 2 Stop the Reconciliation Engine (arrecond. Solution To resolve this issue: 1 Make sure that the job definition is correct. Note: If you do not see any problems in the API log. Note: If you do not see any problems in the API log. Solution To resolve this issue: 1 Make sure that the job definition is correct. 3 If you still encounter this error after performing the previous steps.Reconciliation Engine error messages Table D-1: Reconciliation Engine error messages (Sheet 5 of 14) Error number 101020 Message type Error Message. Appendix D Reconciliation Engine error messages 167 . 101022 Error Error in loading activity qualifications Description An error occurred with the Reconciliation Engine cache data for job definitions or with BMC Atrium Core class metadata. enable AR System API logging to verify any AR System issues. 2 Stop the Reconciliation Engine (arrecond. Note: If you do not see any problems in the API log.exe) process and start it again. enable AR System API logging to verify any AR System issues. Description An error occurred with the Reconciliation Engine cache data for job definitions or with BMC Atrium Core class metadata. you might need to restart the AR System server. Solution To resolve this issue: 1 Make sure that the job definition is correct. enable AR System API logging to verify any AR System issues. you might need to restart the AR System server.exe) process and start it again. 101021 Error Error in loading job schedules. 3 If you still encounter this error after performing the previous steps. description. 3 If you still encounter this error after performing the previous steps. Description An error occurred with the Reconciliation Engine cache data for job definitions or with BMC Atrium Core class metadata. you might need to restart the AR System server. and solution Error in loading activity definitions. 2 Stop the Reconciliation Engine (arrecond.exe) process and start it again. Solution To resolve this issue: 1 Make sure that the job definition is correct. 2 Stop the Reconciliation Engine (arrecond. 168 Troubleshooting Guide . 2 Stop the Reconciliation Engine (arrecond. 101025 Error Error in loading activity to group associations Description An error occurred with the Reconciliation Engine cache data for job definitions or with BMC Atrium Core class metadata. 101024 Error Error in loading attribute precedences Description An error occurred with the Reconciliation Engine cache data for job definitions or with BMC Atrium Core class metadata.BMC Atrium Core 7. 2 Stop the Reconciliation Engine (arrecond. enable AR System API logging to verify any AR System issues. you might need to restart the AR System server.exe) process and start it again. you might need to restart the AR System server. 2 Stop the Reconciliation Engine (arrecond. Solution To resolve this issue: 1 Make sure that the job definition is correct. enable AR System API logging to verify any AR System issues. 3 If you still encounter this error after performing the previous steps. enable AR System API logging to verify any AR System issues. and solution Error in loading group definitions. description. you might need to restart the AR System server. Solution To resolve this issue: 1 Make sure that the job definition is correct.exe) process and start it again. Solution To resolve this issue: 1 Make sure that the job definition is correct.6. Note: If you do not see any problems in the API log. Note: If you do not see any problems in the API log. 3 If you still encounter this error after performing the previous steps.exe) process and start it again. Description An error occurred with the Reconciliation Engine cache data for job definitions or with BMC Atrium Core class metadata.04 Table D-1: Reconciliation Engine error messages (Sheet 6 of 14) Error number 101023 Message type Error Message. 3 If you still encounter this error after performing the previous steps. Note: If you do not see any problems in the API log. description. 2 Stop the Reconciliation Engine (arrecond.Reconciliation Engine error messages Table D-1: Reconciliation Engine error messages (Sheet 7 of 14) Error number 101026 Message type Error Message. and solution Error in loading identification rules. Solution To resolve this issue: 1 Make sure that the job definition is correct. Solution To resolve this issue: 1 Make sure that the job definition is correct. you might need to restart the AR System server. 3 If you still encounter this error after performing the previous steps. Description An error occurred with the Reconciliation Engine cache data for job definitions or with BMC Atrium Core class metadata. you might need to restart the AR System server. Note: If you do not see any problems in the API log. Description An error occurred with the Reconciliation Engine cache data for job definitions or with BMC Atrium Core class metadata. enable AR System API logging to verify any AR System issues. you might need to restart the AR System server. 3 If you still encounter this error after performing the previous steps. Note: If you do not see any problems in the API log. 2 Stop the Reconciliation Engine (arrecond. enable AR System API logging to verify any AR System issues.exe) process and start it again.exe) process and start it again. 3 If you still encounter this error after performing the previous steps.exe) process and start it again. Note: If you do not see any problems in the API log. Solution To resolve this issue: 1 Make sure that the job definition is correct. 2 Stop the Reconciliation Engine (arrecond. enable AR System API logging to verify any AR System issues. 101028 Error Activity run failed because there are no datasets. 101027 Error Error in loading comparison rules. Appendix D Reconciliation Engine error messages 169 . Description An error occurred with the Reconciliation Engine cache data for job definitions or with BMC Atrium Core class metadata. Solution This error occurs because of incorrect data. 101034 Error Reconciliation identity of one endpoint is NULL for relationship class. Solution This error occurs because of incorrect data.6. description. Note: If you do not see any problems in the API log. With BMC Remedy User. Solution Correct the identification rule in the job definition. Description An error occurred with the Reconciliation Engine cache data for job definitions or with BMC Atrium Core class metadata.04 Table D-1: Reconciliation Engine error messages (Sheet 8 of 14) Error number 101029 Message type Error Message. 101033 Error Class id of one endpoint is NULL for relationship class. 2 Stop the Reconciliation Engine (arrecond. specify a value for the class ID attribute. Description You specified incorrect job definitions for the Reconciliation Engine job. enable AR System API logging to verify any AR System issues. In BMC Remedy User. Solution To resolve this issue: 1 Make sure that the job definition is correct. specify a value for the class ID attribute.exe) process and start it again. 170 Troubleshooting Guide . 3 If you still encounter this error after performing the previous steps. 101032 Error Error in loading unique datasets from the association Table.BMC Atrium Core 7. you might need to restart the AR System server. Description The class ID attribute for one of the endpoints in the relationship class contains a NULL value. and solution Activity run failed because there is no object store class cache. Description The reconciliation ID attribute for one of the endpoints in the relationship class contains a NULL value. 2 Stop the Reconciliation Engine (arrecond.exe) process and start it again. you might need to restart the AR System server. enable AR System API logging to verify any AR System issues. you might need to restart the AR System server.exe) process and start it again. 2 Stop the Reconciliation Engine (arrecond. Description An error occurred with the Reconciliation Engine cache data for job definitions or with BMC Atrium Core class metadata. Description An error occurred with the Reconciliation Engine cache data for job definitions or with BMC Atrium Core class metadata. 3 If you still encounter this error after performing the previous steps. 2 Stop the Reconciliation Engine (arrecond. Solution To resolve this issue: 1 Make sure that the job definition is correct. Note: If you do not see any problems in the API log. enable AR System API logging to verify any AR System issues. 3 If you still encounter this error after performing the previous steps. Appendix D Reconciliation Engine error messages 171 . Solution To resolve this issue: 1 Make sure that the job definition is correct. 101038 Error Attribute id <{1}> not found in class <{2}> of namespace <{3}>. enable AR System API logging to verify any AR System issues. 3 If you still encounter this error after performing the previous steps. Solution To resolve this issue: 1 Make sure that the job definition is correct. description. 101037 Error Attribute name <{1}> not found in class <{2}> of namespace <{3}>.exe) process and start it again. Description An error occurred with the Reconciliation Engine cache data for job definitions or with BMC Atrium Core class metadata. and solution Activity run because dataset id not found for target dataset name. Note: If you do not see any problems in the API log. you might need to restart the AR System server.Reconciliation Engine error messages Table D-1: Reconciliation Engine error messages (Sheet 9 of 14) Error number 101036 Message type Error Message. Note: If you do not see any problems in the API log. 172 Troubleshooting Guide . 3 If you still encounter this error after performing the previous steps. you might need to restart the AR System server. you might need to restart the AR System server. Description Within the specified dataset. 3 If you still encounter this error after performing the previous steps. Note: If you do not see any problems in the API log. you might need to restart the AR System server. 2 Stop the Reconciliation Engine (arrecond. Note: If you do not see any problems in the API log. enable AR System API logging to verify any AR System issues.04 Table D-1: Reconciliation Engine error messages (Sheet 10 of 14) Error number 101039 Message type Error Message. enable AR System API logging to verify any AR System issues. Description An error occurred with the Reconciliation Engine cache data for job definitions or with BMC Atrium Core class metadata.BMC Atrium Core 7.exe) process and start it again. Solution To resolve this issue: 1 Make sure that the job definition is correct.exe) process and start it again. description. 3 If you still encounter this error after performing the previous steps. Description Within the specified dataset. Solution To resolve this issue: 1 Make sure that the job definition is correct. 2 Stop the Reconciliation Engine (arrecond.exe) process and start it again. the class name does not exist. Solution To resolve this issue: 1 Make sure that the job definition is correct. the class ID does not exist. 2 Stop the Reconciliation Engine (arrecond. 101040 Error Class name <{1}> of namespace <{2}> does not exist. enable AR System API logging to verify any AR System issues. Note: If you do not see any problems in the API log.6. 101041 Error Class id <{1}> of namespace <{2}> does not exist. and solution Attribute of AR field id <{1}> not found in class <{2}> of namespace <{3}>. enable AR System API logging to verify any AR System issues. enable AR System API logging to verify any AR System issues. 101043 Error Error in opening log file. 3 If you still encounter this error after performing the previous steps. Description The Reconciliation Engine cannot access the log file. Solution To resolve this issue: 1 Make sure that the job definition is correct. Error in opening log file. JSolution Verify that you have sufficient disk space on your system and that you have the appropriate permissions to write to the file system. 3 If you still encounter this error after performing the previous steps. Appendix D Reconciliation Engine error messages 173 . Description Within the specified dataset. Note: If you do not see any problems in the API log. you might need to restart the AR System server.exe) process and start it again. description. Note: If you do not see any problems in the API log. you might need to restart the AR System server. Solution To resolve this issue: 1 Make sure that the job definition is correct. 2 Stop the Reconciliation Engine (arrecond. 2 Stop the Reconciliation Engine (arrecond. and solution Relationship <{1}> of namespace <{2}> has no lead class. Description An error occurred with the Reconciliation Engine cache data for job definitions or with BMC Atrium Core class metadata.Reconciliation Engine error messages Table D-1: Reconciliation Engine error messages (Sheet 11 of 14) Error number 101042 Message type Error Message.exe) process and start it again. 101044 Error In merge activity <{1}>. the relationship does not exist. dataset merge precedence set value is empty. enable AR System API logging to verify any AR System issues. Description An error occurred with the Reconciliation Engine cache data for job definitions or with BMC Atrium Core class metadata. 101046 Error In merge activity <{1}>. 3 If you still encounter this error after performing the previous steps. enable AR System API logging to verify any AR System issues. Solution Perform the following steps to resolve this issue: 1 Make sure that the job definition is correct. Note: If you do not see any problems in the API log. Solution Perform the following steps to resolve this issue: 1 Make sure that the job definition is correct. you might need to restart the AR System server. 2 Stop the Reconciliation Engine (arrecond. enable AR System API logging to verify any AR System issues.exe) process and start it again. 3 If you still encounter this error after performing the previous steps.exe) process and start it again. you might need to restart the AR System server.04 Table D-1: Reconciliation Engine error messages (Sheet 12 of 14) Error number 101045 Message type Error Message. description. Description An error occurred with the Reconciliation Engine cache data for job definitions or with BMC Atrium Core class metadata. 101047 Error Error in loading dataset merge precedence sets. Note: If you do not see any problems in the API log. there is no source dataset specified. Solution To resolve this issue: 1 Make sure that the job definition is correct. you might need to restart the AR System server. 3 If you still encounter this error after performing the previous steps. 2 Stop the Reconciliation Engine (arrecond. 174 Troubleshooting Guide . 2 Stop the Reconciliation Engine (arrecond. Description An error occurred with the Reconciliation Engine cache data for job definitions or with BMC Atrium Core class metadata. Note: If you do not see any problems in the API log.BMC Atrium Core 7.6.exe) process and start it again. and solution Dataset merge precedence set <{1}> has no entry. No error number Error Cannot find the endpoint of relationship::<className>:Merging of record failed. Description You are attempting to merge a CI that has more than one instance with the same dataset ID and Reconciliation ID combination. 3 Increase the virtual memory. Solution See “CIs merge more than once during a Merge activity” on page 30. No error number Error Found multiple matches in the dataset: Cannot identify the instance of class <className> with instance ID <instanceId>. Description More than one instance of the specified class was found in the dataset. Appendix D Reconciliation Engine error messages 175 . Solution Perform the following steps to resolve this issue: 1 Make sure that the AR System server has allocated enough system resources to support both AR System and Reconciliation Engine operations. description.Asset” on page 26. and solution Memory allocation failed. 2 From BMC Remedy Developer Studio. Solution See “Resolving multiple CI matches in the source dataset” on page 28. Description The AR System server failed to allocate the memory that you are attempting to allocate. Description You are attempting to merge an orphan instance. Solution See “Troubleshooting multiple CI matches in BMC. Solution See “Missing endpoints during the Merge activity” on page 30. Description The option that you specified in the Include child CIs? menu is complicated. reduce the number of concurrent Reconciliation Engine threads. No error number Error Algorithm: Including child CIs and committing together.Reconciliation Engine error messages Table D-1: Reconciliation Engine error messages (Sheet 13 of 14) Error number 101048 Message type Error Message. ARERR[120092] Error ARERR[120092] The dataset ID and Reconciliation Identity combination is not unique. BMC Atrium Core 7.6. Description You encounter Reconciliation Engine performance issues. 176 Troubleshooting Guide . such as the job takes a long time to complete or the Reconciliation Engine freezes. Solution See “Resolving Reconciliation Engine performance issues due to incorrect database settings” on page 32. Description The number of activities that you are attempting to run require more than the total number of threads that you allocated. No error number Error The Reconciliation Engine demonstrates performance issues due to incorrect database settings. description. Solution See “Resolving Reconciliation Engine performance issues due to insufficient thread settings” on page 31. and solution The Reconciliation Engine log only shows two unique TIDs (Thread IDs).04 Table D-1: Reconciliation Engine error messages (Sheet 14 of 14) Error number No error number Message type Error Message. 'Origin'. 105002 Error Please do enter the mandatory fields 'Product Model/ Version'. Table E-1: Product Catalog error messages (Sheet 1 of 7) Error number 105001 Message type Error Message. 'Product Categorization Tier 3'. Description You did not specify a value for the required field listed in the error message when creating a product.Appendix E Product Catalog error messages Table E-1 lists the error number. 'Manufacturer'. Solution Specify a value for the Patch Last Build ID field. Description The signature that you are attempting to associate to the product does not exist. message type. description. 'Status-PDC' and 'Product Type'. message text. Solution Specify values for the required fields. and solution for each Product Catalog error. Solution Make sure that the Signature ID exists in the PCT:Signature form. Appendix E Product Catalog error messages 177 . 'Suite Definition'. Solution Specify values for the required fields. description. 105004 Error This Signature ID does not exist in Signature Table. Description You did not specify values for the required fields listed in the error message when creating a product. 'Product Name'. 105003 Error Please do enter the mandatory field 'Patch Last Build ID'. Description You did not specify values for the required fields listed in the error message when creating a product. 'Requires Contract' and 'Model/Version State'. and solution Enter the mandatory fields 'Product Categorization Tier 1'. 'Product Categorization Tier 2'. 6.04 Table E-1: Product Catalog error messages (Sheet 2 of 7) Error number 105005 Message type Error Message.BMC Atrium Core 7. Description The Company that you are attempting to associate to the product does not exist. 105011 Note The selected version has been successfully related with $420000341$ and associated status flags. Solution Make sure that the company exists in the COM:Company form. description. 105007 Error The selected combination of Approved Flag and Blacklisted Flag is Invalid. 105006 Note Product has been created successfully. Description The product with the given Product Catalog Key was successfully created. 105010 Note The selected patch has been successfully related with $420000400$ and associated status flags. Product Catalog Key is $PCTKey$. Solution Specify a unique company name for the company. Description An association with the product patch and the Managed/Blacklisted/ Hidden flags and Company field was successfully created. Please enter a different Company name if you want to create a new Company record. and solution Company $Company$ does not exists. 105009 Note The Company record that you are trying to create already exists. 178 Troubleshooting Guide . Description The record that you created has been saved. 105008 Note Saved successfully. Solution Check the values that you specified for the Approved Flag and Blacklisted Flag fields. Description The combination of values that you specified for the Blacklisted Flag and the Approved Flag when creating a product is invalid. Description The company name that you specified for the new company record already exists. Description An association with the product Version and the Managed/ Blacklisted/Hidden flags and Company field was successfully created. Description You did not specify values for the required fields listed in the error message when you were creating a signature. Version. 105015 Note Setting associated versions as blacklisted for product $Product Name$ and company $Company$. Solution Specify values for the PCTKey and SignatureId fields. Solution Specify unique values for the record. SignatureId.Product Catalog error messages Table E-1: Product Catalog error messages (Sheet 3 of 7) Error number 105012 Message type Error Message. and Attachment fields. description. Description The Company field cannot contain a NULL value when you create a product Version and Company association. Description You are attempting to create a signature and product association with NULL values in the PCTKey and SignatureId fields. 105014 Note Setting associated versions as hidden for product $240001002$ and company $1000000001$. Please verify or reselect your field entries and try again. Description The product versions of the given Product and Company were successfully set as Hidden. Attachment. Description You are attempting to create a duplicate record. Description The product versions of the given product and company were successfully set as BlackListed. 105016 Note Setting associated versions as approved for product $Product Name$ and company $Company$. 105013 Error Select a Company value. Solution Specify values for the Logical Data Group. and solution This record already exists. Solution Specify a value in the Company field. 105021 Error Please fill in the mandatory fields: PCTKey. 105022 Error Please fill in the mandatory fields: Logical Data Group. Description The product versions of the given product and company were successfully set as Approved. Appendix E Product Catalog error messages 179 . Version. Description You are attempting to search for products in the Product Catalog without specifying search criteria. fr. Description You are attempting to delete a product that does not exist. ko.BMC Atrium Core 7. Solution Before you click Delete. it. model version. Solution Before you click Delete. ja. Solution Specify values for the fields as listed: For Selection Code: any values. Model Version or Patch to delete. Selection Code. Please select different values. For Selection Code: any number between -2147483647 and 2147483647. specify a product. 105028 Note Entry Saved. Solution Before you click Search. and Locale already exist. Solution Specify a value for the Model/Version field. Description You are attempting to save a software item with a NULL value in the Model/Version field. 105024 Error Select a Product. Description The combination of Selection Type. 105026 Error The combination of Selection Type. and solution Select a Product or Model Version to delete. This operation is invalid. Description You are attempting to delete a product that does not exist. or patch. ru. description. de. specify a product or model version. Selection Code. 180 Troubleshooting Guide . 105027 Warning Software Library Item can't be created for empty (NULL) 'Model/Version'.6. select a location or product in the Product Catalog View list to search. Description The record that you created on the current form was saved. 105025 Note Choose a Product Catalog View. For Locale the possible values are: zh_CN.04 Table E-1: Product Catalog error messages (Sheet 4 of 7) Error number 105023 Message type Error Message. es and en. and Locale that you specified already exists. 105053 Warning Are you sure you want to delete discovered product"+$Discovered Product$)+" ?. 105050 Information Product $Discovered Product$ has been successfully created as alias of Existing Product $z1D_ExistingProduct$. Description The discovered manufacturer has been successfully added in the BMC Atrium Product Catalog as an alias of the manufacturer mentioned in the message. Description The combination of values that you specified for the Blacklisted Flag and the Approved Flag when creating a product is invalid. Description The discovered product has been successfully added in the BMC Atrium Product Catalog as an alias of the product mentioned in the message. description. 105030 Error The selected combination of Version Life Cycle Status is Invalid with Product Life Cycle combination. 105051 Information Manufacturer $Discovered Manufacturer$ has been created as Alias of Existing Manufacturer $z1D_ExistingManuf$ successfully. Description The combination of values that you specified for the Version Life Cycle Status and Product Life Cycle fields is invalid. Make sure you click OK only if you want to delete the product." Description Your action will delete the product that was discovered.Product Catalog error messages Table E-1: Product Catalog error messages (Sheet 5 of 7) Error number 105029 Message type Error Message. Solution Select correct values. Description The combination of values that you specified for the Patch Life Cycle Status and Version Life Cycle fields is invalid. Solution Check the values that you specified for the Approved Flag and Blacklisted Flag fields. and solution The selected combination of Patch Life Cycle Status is Invalid with Version Life Cycle combination. Solution Select appropriate values. 105031 Error The selected combination of Approved Flag and Blacklisted Flag is Invalid. Description The manufacturer has been successfully added to the Normalization Alias form as an alias of the = manufacturer mentioned in the message. 105054 Information Manufacturer $z1D_Manufacturer$ has been successfully added to the Normalization Alias form as an alias of $Manufacturer$. Appendix E Product Catalog error messages 181 . 105058 Error Attribute Name is required field.04 Table E-1: Product Catalog error messages (Sheet 6 of 7) Error number 105055 Message type Information Message. 105059 Error AliasName is required field.6. 105060 Warning "Are you sure you want to make the Discovered product $420000518$ an alias of $420000548$ ?. Solution Assign the alias only if you want to mark the discovered product as Offline. Description Alias Name is a required field. Description The product has been successfully added to the Normalization Alias form as an alias of the product mentioned in the message. Only Offline products can be deleted. Solution Mark the product as Enabled before you create an alias for it." Description You are attempting to assign an alias for the discovered product that will mark it as Offline.Clicking O. Solution Alias Name is a required field. Description Attribute Name is a required field. 105056 Information The product $Product Name$ has been successfully updated. and solution Product $z1D_Product$ has been successfully added as Alias of $Product Name$ to Normalization Alias form. Description You are attempting to delete a product that is currently available. 182 Troubleshooting Guide . description. will mark the product $420000518$ Offline. Solution Mark the product as Offline before you delete it.K. Solution Make sure that you specify a value for the Attribute Name field. 105057 Information Alias $NameAlias$ of manufacturer $Existing Manuf Name$ has been successfully created. 105062 Error Offline product cannot be made Alias of another product. Description An alias name for the manufacturer has been successfully created. Description The product you modified has been successfully saved. 105061 Error Product having status "Enabled" cannot be deleted. Description You are attempting to create an alias for a product that is currently unavailable.BMC Atrium Core 7. Description The product name that you specified does not exist. Solution Make sure that the specified manufacturer exists in the BMC Atrium Product Catalog. Solution Create an alias for the product with the new name. description. Appendix E Product Catalog error messages 183 . 105065 Error User $z1D_LoggedInUser$ does not have permissions for company $z2TF Company (PDA)$.Product Catalog error messages Table E-1: Product Catalog error messages (Sheet 7 of 7) Error number 105063 Message type Error Message. 105064 Error An entry with the manufacturer name does not exist. Enter a different manufacturer name. Description You do not have the required permission to access the given company. Create an alias of existing product. and solution An entry with the product name does not exist. Description The manufacturer name that you specified does not exist. Solution Contact your system administrator to request access to the given company. 04 184 Troubleshooting Guide .6.BMC Atrium Core 7. The following topics are provided: AR System plug-in error messages (page 186) JDBC plug-in error messages (page 188) Appendix F Federation plug-in error messages 185 .Appendix F Federation plug-in error messages This section provides information about troubleshooting AR System and JDBC plug-in federation errors. Table F-1: AR System plug-in error messages (Sheet 1 of 2) Error number 140100 Message type Error Message. Form Name=<{0}>.04 AR System plug-in error messages Table F-1 lists the error number. Solution Make sure that you define the plug-in configuration in the Federation Manager. message text. 140104 Error Form Name cannot be null when filter type is filter on specific form name. 140101 Error Error loading plug-in configuration for plug-in <{0}> <{1}>. 140103 Error Plug-in configuration for plug-in <{0}> not defined. and solution for the AR System plug-in errors. 140102 Error No entry found with entry id <{0}> from table <{1}>. Solution Make sure that the plug-in configuration that you specified in the Federation Manager is correct. filter type: <{1}> Description You selected the Specified Forms option for the retrieve method of the plug-in but did not specify an AR System form name for the filter. Solution Make sure that you specify an AR System server form name for the filter. 186 Troubleshooting Guide .6. Description You are attempting to use a method that is not supported for the specified class. Check the plug-in configuration. Description An internal error occurred when querying the specified table for the given entry ID. and solution Method <{0}> not supported. description. Solution Make sure that the entry ID is correct for the table that you specified and execute the query again. Solution Make sure that the method that you are attempting to use on the specified class is available for the class type.BMC Atrium Core 7. Description An internal occurred when loading the plug-in for the configuration. message type. description. Description You did not specify the plug-in configuration for the given plug-in. 140106 Error Data Type Conversion failed for value <{0}> with sql type <{1}>. Description A data type mismatch error occurred because you provided a noninteger value for the plug-in. This does not match with the type of plugin you selected. Solution Make sure that you specify integer values for the given input parameters. description.AR System plug-in error messages Table F-1: AR System plug-in error messages (Sheet 2 of 2) Error number 140105 Message type Error Message. filterFormType = <{1}>. Appendix F Federation plug-in error messages 187 . Server Port = <{0}>. 140107 Error Number format exception occurred while data type conversion for plug-in <{0}> : <{1}>. Solution Make sure that: The data type of the value and the SQL table column specified in the qualification match. Description The data type of a value that you specified in the qualification does not match the data type of the SQL table column. and solution Number format exception while processing user input. lastChangedSince filter = <{2}> Description A data type mismatch error occurred because you provided a noninteger value for the given input parameters. Solution Make sure that: The data type matches the plug-in type that you specified The integer value that you specified is correct for the plug-in. The value that you specified for the table column does not exceed its data limit. and solution Method <{0}> not supported. 130103 Error No entry found with entry id <{0}> from table <{1}>. Description The entry ID that you specified for the table does not exist. Table F-2: JDBC plug-in error messages (Sheet 1 of 2) Error number 130100 Message type Error Message. 130102 Error Error fetching entry with entry id <{0}> from table <{1}> . description. Solution Make sure that the plug-in configuration that you specified in the Federation Manager is correct.6. Description You are attempting to use a method that is not supported for the specified class.<{2}>. Solution Make sure that the: The data type of the table columns and the values match The value does not exceed the maximum limit of the table column The table columns that you specify in the query exist The table name that you specify in the query exists 188 Troubleshooting Guide . and solution for the JDBC plug-in errors. 130104 Error Error fetching entries for given qualification from table <{0}> . description.<{1}>. Check the plug-in configuration. Solution Make sure that the entry ID is correct for the table that you specified and execute the query again. message text. Description The qualifications you specified in the query are incorrect. 130101 Error Error loading plug-in configuration for plug-in <{0}> <{1}>. Description An internal occurred when loading the plug-in for the configuration. Solution Modify the entry ID to the one that exists in the table.04 JDBC plug-in error messages Table F-2 lists the error number. message type. Description An internal error occurred when querying the specified table for the given entry ID. Solution Make sure that the method that you are attempting to use on the specified class is available for the class type.BMC Atrium Core 7. Description The data that you are attempting to query is not found in the specified table. and solution No entries found in the table <{0}>. 130109 Error Data Type Conversion failed for value <{0}> with sql type <{1}>. Appendix F Federation plug-in error messages 189 . Solution Make sure that the column that you specified in the qualification exists. Description You are attempting to use an incorrect value in the qualification for a field of Number format. Description The column name that you specified in the query is incorrect. Solution Make sure that you define the plug-in configuration in the Federation Manager.<{0}> Description The table name that you specified in the query is incorrect. Solution Make sure that the value that you specify for the numeric field is of Number format. Description You did not specify the plug-in configuration for the given plug-in. The value that you specified for the table column does not exceed its data limit.AR System plug-in error messages Table F-2: JDBC plug-in error messages (Sheet 2 of 2) Error number 130105 Message type Error Message. 130110 Error Number format exception occurred while data type conversion for plug-in <{0}> : <{1}>. description. Solution Make sure that: The data type of the value and the SQL table column specified in the qualification match. Solution Make sure that the table that you specified in the qualification exists. 130106 Error Error fetching table names from data source . 130108 Error Plug-in configuration for plug-in <{0}> not defined. Description The data type of a value that you specified in the qualification does not match the data type of the SQL table column. 130107 Error Error fetching column names from table <{0}> .<{1}>. Solution Make sure that the data you are attempting to query exists in the table for the given qualification. 04 190 Troubleshooting Guide .BMC Atrium Core 7.6. and solution Error retrieving DatasetIds for the selected target data store. Table G-1: Atrium Integrator error messages (Sheet 1 of 5) Error number NGIE000001 Message type Error Message. and solution for each Atrium Integrator error. NGIE000004 Error Job Creation failed. NGIE000002 Error Error retrieving CI Types for the selected target data store. Chapter G Atrium Integrator Error messages 191 . Solution Verify the BMC Remedy AR System server details specified in the target data store connection. message text. description. Also confirm that a relationship has been selected for the selected CIs on the CI TypeRelationships page of the Integration Job Builder wizard.G Chapter Atrium Integrator Error messages Table G-1 lists the error number. Also confirm that one or more some target attributes have been mapped to the source column on the CI Mapping page of the Integration Job Builder wizard. Solution Verify the data entered in the Integration Job Builder wizard pages and check your connection to the Pentaho server. Solution Verify the BMC Remedy AR System server details specified in the target data store connection. description. Solution Verify the BMC Remedy AR System server details specified in the target data store connection. message type. NGIE000003 Error Error retrieving CI Relationships for the selected CI Types. NGIE000008 Error Error retrieving Views for the schema. NGIE000010 Error Error retrieving Columns for the source. NGIE000009 Error Error retrieving Files for the source. and solution Error retrieving CI attributes for the selected CI Type. NGIE000006 Error Error retrieving Schemas for the source.BMC Atrium Core 7. Also check whether the schema has any view defined. NGIE000007 Error Error retrieving Tables for the schema.6. 192 Troubleshooting Guide .04 Table G-1: Atrium Integrator error messages (Sheet 2 of 5) Error number NGIE000005 Message type Error Message. Solution Confirm connectivity to BMC Remedy AR System by clicking the Test Connection button in the Manage Data Store tool. Also verify that the CI Class is defined correctly for the selected CI Type. description. Solution Check your connection to the Pentaho server and verify that the table or view is defined correctly in the source database. Check whether an entry has been created in the NGIE: FileMetaData form. Solution Confirm that the source database table has valid columns. NGIE000011 Error No Columns available for the selected source. Solution Confirm connectivity to BMC Remedy AR System by clicking the Test Connection button in the Manage Data Store tool. Solution Confirm connectivity to BMC Remedy AR System by clicking the Test Connection button in the Manage Data Store tool. Solution Confirm connectivity to BMC Remedy AR System by clicking the Test Connection button in the Manage Data Store tool. Solution Confirm connectivity to BMC Atrium CMDB by clicking the Test Connection button in the Manage Data Store tool. Also check whether the schema has any table defined. The AtriumCoreInstallationDirectory\cmdb \plugins\shared\pluginsvr_config.xml file contains the following entry: BMC.ATRIUM. NGIE000103 Error Failed to delete NGIE job. Solution Confirm connectivity to BMC Atrium CMDB by clicking the Test Connection button in the Manage Data Store tool.ARDBC. Check whether an entry has been created in the NGIE: FileMetaData form. NGIE000106 Error Failed to get list of job runs.NGIE All the .jar files listed in the BMC. Solution Check your connection to the Pentaho server. Solution Confirm that the Carte server is running. Chapter G Atrium Integrator Error messages 193 . Solution Check your connection to Atrium Integrator. Also confirm that the Carte server is running. NGIE000102 Error Failed to get list of NGIE Jobs. Also check whether there is an entry in the NGIE: JOBLOG form.ARDBC.NGIE section exist at the specified locations. NGIE000105 Error Failed to stop NGIE job. NGIE000101 Error Failed to connect to Atrium Integrator. Solution Check the following: Your connection to the Pentaho server. and solution Error retrieving fields from the selected file. Solution Check your connection to the Pentaho server. Also confirm that the Carte server is running.ATRIUM. description.Table G-1: Atrium Integrator error messages (Sheet 3 of 5) Error number NGIE000012 Message type Error Message. Solution Check your connection to the Pentaho server. NGIE000107 Error Failed to get list of job runs. Also check whether there is an entry in the NGIE: JOBLOG form. NGIE000104 Error Failed to start NGIE job. Solution Check your connection to Atrium Integrator. Solution Check the data store connection details. NGIE000205 Error Error getting data store types. you can copy the job and transformation files saved in the user profile on the mid tier (C:\Documents and Settings\Administrator\jobName\) to the Spoon repository. Solution Check your connection to the Pentaho server. NGIE000203 Error Error deleting data store. Solution Check your connection to the Pentaho server. NGIEA000304 Error Error occurred while trying to connect to the data store. Solution Check the data store connection details.6. Solution Check your connection to the Pentaho server. NGIEA000303 Error Error occurred while trying to connect to the data store.04 Table G-1: Atrium Integrator error messages (Sheet 4 of 5) Error number NGIE000201 Message type Error Message. and solution Error creating data store. 194 Troubleshooting Guide .BMC Atrium Core 7. NGIE000204 Error Error getting data stores. description. NGIEA000310 Error Error publishing the job to the repository. Solution Check your connection to the Pentaho server. NGIEA000305 Error Please check the name and path details. Solution Verify the directory path and check whether the folder specified in the path exists on the Atrium Integrator server. Solution Check your connection to the Pentaho server. Solution Check your connection to the repository database server. NGIE000202 Error Error updating data store. After you fix the connection. Solution Check your connection to the repository database server. description. and solution Error publishing the transformation to the repository. Chapter G Atrium Integrator Error messages 195 .Table G-1: Atrium Integrator error messages (Sheet 5 of 5) Error number NGIEA000311 Message type Error Message. you can copy the job and transformation files saved in the user profile on the mid tier (C:\Documents and Settings\Administrator\jobName\) to the Spoon repository. Solution Check whether the source column to be updated has been specified for the Response area in the Transformation Options tab for the CI Mapping and Relationship Mappings pages of the Integration Job Builder wizard. NGIEA000315 Response column in Transformation Options for one or more CI Types is not set. After you fix the connection. NGIEA000316 Delta column in Transformation Options for one or more CI Types is not set. Solution Check whether the source column to be used for Delta has been specified for the Delta area in the Transformation Options tab for the CI Mapping and Relationship Mappings pages of the Integration Job Builder wizard. 6.04 196 Troubleshooting Guide .BMC Atrium Core 7. 113 AIE. 16.log file 117 arrecond. See BMC Atrium Integration Engine Atrium Integrator error messages 191 log files 41 troubleshooting console issues 41 troubleshooting Spoon errors 41 Atrium widget error messages 38 mid tier and 37 troubleshooting 34 attributes. logs 96 Application Pending form 18 application server logs. Merge missing endpoints 30 multiple Configuration Items (CIs) merges 30 Administrative Information tab 15. See BMC Atrium Integration Engine Apache Tomcat 37 APIs. troubleshooting 39 arerror. 18 Advanced Settings tab 50.sh script file 23 Atrium Console error messages 38 filter error messages 157 troubleshooting 33 Atrium Integration Engine. web services 102 arapi. class definition 68 Audit tab 68 B BMC Asset dataset. missing in Data Field Mapping window 62 audit history.A B C D E F G H I J K L M N O P Q R S T U V W X Y Z Index A aborted Reconciliation Engine jobs 15 access.log file 117 ARERR 6230.cfg file 104 eieEventCleanup.dbg file 110 eieEventMgr. troubleshooting 38 ARERR 9280. troubleshooting 38 ARERR 9391.dbg file 110 enabling debug logging 105 instance management issues 57 log messages 106 logs 104 managing instances 57 missing attributes 62 RPC port error 62 Index 197 .dbg file 110 eieEventListener. 112. duplicate CIs in 26 BMC Atrium CMDB Engine log 96 BMC Atrium CMDB Java API log 97 BMC Atrium Configuration Management Database (BMC Atrium CMDB) API logs 104 C API error messages 119 cleaning up data 84 Java API logs 97 logs 96 permission issues 79 Server-side API logs 96 BMC Atrium Core configuration issues 75 BMC Atrium Core Console active link error messages 153 client-side logging 94 server-side logging 95 BMC Atrium Integration Engine AIE service fatal error 56 AIE service stopped 55 data exchange issues 50 data exchange statistics 113 Data Field Mapping window 62 data mapping issues 54 debug messages 110 debugging 104 debugging initialization phase 112 debugging processing phase 113 eie.dbg file 110 eiemain. federation 69 active link error messages 153 activities. cmdbdriver 73 federated class validation errors 71 searching for invalid 82 Data Exchange application 113 data exchanges debug file 110.log file 96. 113 Data Field Mapping tab 107 Data Field Mapping window 62 Data Integrity Checker 82 data mapping issues 54 Data Mappings tab 50 data models checking class definitions 90 correcting 81 viewing 81 Data Visualization Form modules 72 database settings. 28 Configuration Items (CIs) and Relationship Correction Tool 84 Connection Settings tab 52 consoles BMC Atrium Core 33 BMC Atrium Core. 97 configuration issues BMC Atrium Core 75 Reconciliation Engine 14 Configuration Items (CIs) duplicate 26. starting 82 cmdbdriver data decompression 73 cmdbengdebug. Reconciliation Engine and 32 datasets deleting instances 85 duplicate Configuration Items (CIs) in source 28 finding invalid IDs 83 normalization 76 debug messages. server-side logging 95 Job History 18 correcting Rule Helper issues. 28 C C API error messages 119 cardinality deleting relationships that violate 87 finding relationships that violate 83 Carte server 44 Characteristics tab 154 classes cardinality violations 83 cleaning up 87 data model definitions 90 definition audit history 68 deleting instances 87 federation validation errors 71 client-side logging.A B C D E F G H I J K L M N O P Q R S T U V W X Y Z BMC Atrium Integration Engine (continued) Rule Helper issues 61 service issues 55 SQL adapter issues 57 troubleshooting 49 BMC Atrium Product Catalog error messages 177. active link errors 153 BMC Atrium Core. 26. in cmdbdriver 73 definitions class audit history 68 configuring data exchange 50 data model class 90 exporting Reconciliation Engine 24 deleting class instances 87 instances in datasets 85 orphan relationships 86 relationships that violate cardinality 87 DETAILS entries in RE job log 21 duplicate Configuration Items (CIs) 26. 28 multiple merges 30 unidentified 20. data. BMC Atrium Core Console 94 CMDB Engine library loading errors 117 cmdbdiag. contacting 2 bundling log files 118 Create button. 185 BMC Remedy Action Request System Server (BMC Remedy AR Server) AIE service accidentally stops 55 error logs 117 BMC Software. AIE 110 debugging AIE log settings 105 BMC Atrium Integration Engine 104 data exchanges 110. Product Catalog Setup form 75 customer support 3 D data cleaning up in BMC Atrium CMDB 84 decompression. 111 issues 50 statistics 113 Data Exchanges Information window 50. client-side logging 94 BMC Atrium Core. 111 Reconciliation Engine 102 decompression. BMC Atrium Integration Engine 61 198 Troubleshooting Guide . 105. 112. dbg file 110 endpoints.dbg file 110 eieEventMgr. 116 BMC Atrium CMDB Java logs 97 BMC Atrium Core Console. 111 EIE:CMDBRelMapping form 111 EIE:DataExchange form 111 EIE:DataMapping form 54. Reconciliation Engine job 99 exchanges. 39 I IDs finding invalid dataset 83 resetting reconciliation 84 initialization phase. 28 J Java APIs logs 97 Job Event Information window 100 Job History Console 18 jobs. client side 94 BMC Atrium Core Console. active. 111 EIE:CMDBRelMapping 111 EIE:DataExchange 111 EIE:DataMapping 54. Atrium Console error messages 157 forms Application Pending 18 Data Visualization 72 Index 199 . 34. 111 EIE:Log 106 EIE:MappingInfo 54 Product Catalog Setup 75 RE:Precedence 17 Server Information 31.cfg file 104 EIE:ARMappingInfo form 107 EIE:CMDBDataMapping form 54. 185 Reconciliation Engine 163 errors AIE RPC port 62 fatal AIE service 56 fatal Reconciliation Engine job 15 federation plugin RPC 70 multiple Configuration Items (CIs) match issues 26 events. CMDB Engine library 117 log files bundle 118 zip up 118 Log Files tab 67. 68. server side 95 F fatal errors AIE service 56 Reconciliation Engine job 15 federation access 69 data class validation errors 71 plugins. See Reconciliation Engine jobs L links.dbg file 110 eiemain. missing 30 error messages Atrium Console 38 Atrium Console filter 157 Atrium Integrator 191 Atrium widget 38 BMC Atrium CMDB C API 119 BMC Atrium Core Console active link 153 BMC Atrium Integration Engine 106 BMC Remedy Action Request System Server (BMC Remedy AR Server) 117 CMDB Engine library loading 117 Product Catalog 177.dbg file 110 eieEventListener. RPC errors 70 filters. 111 EIE:Log form 106 EIE:MappingInfo form 54 eieEventCleanup. 26. AIE debug logging 112 instances correcting invalid relationships 85 deleting 87 deleting in datasets 85 finding cardinality violations 83 finding invalid dataset IDs 83 unidentified 20. data 50 exporting Reconciliation Engine definitions 24 forms (continued) EIE:ARMappingInfo 107 EIE:CMDBDataMapping 54.A B C D E F G H I J K L M N O P Q R S T U V W X Y Z E eie. error messages 153 loading. 38. 117 logs API 96 application server 102 BMC Atrium CMDB 96 BMC Atrium CMDB API 104 BMC Atrium CMDB Engine 96. Data Visualization Form 72 multiple threads. Reconciliation Engine log file 99 normalization dataset issues 76 plugin issues 76 Normalization Engine log 116 O orphans. 28 error messages 26. data 54 matching CIs 26 matching Configuration Items (CIs) 28 Merge activity missing endpoints 30 multiple Configuration Items (CIs) merges 30 messages. AIE and 57 mid tier Apache Tomcat and 37 ServletExec and 37 troubleshooting 37 missing attributes 62 endpoints 30 models. deleting relationship 86 M managing instances 57 Mapping Information window 113 mapping. BMC Atrium CMDB 79 plugins federation RPC errors 70 normalization issues 76 polling interval. error Atrium Console 38 Atrium Console filter 157 Atrium widget 38 BMC Atrium CMDB C API 119 BMC Atrium Core Console active link 153 BMC Atrium Integration Engine 106 BMC Remedy Action Request System Server (BMC Remedy AR Server) 117 CMDB Engine library loading 117 Product Catalog 177. debug 105 BMC Atrium Integration Engine.A B C D E F G H I J K L M N O P Q R S T U V W X Y Z logs (continued) BMC Atrium Integration Engine 104 BMC Atrium Integration Engine. 163 exporting definitions 24 log file entries 100 log issues 21 log naming conventions 99 logs 99 missing endpoints 30 multiple Configuration Items (CIs) merges 30 multiple threads 31 200 Troubleshooting Guide . 185 Reconciliation Engine 26. 32 permissions. See Reconciliation Engine RE:Precedence form 17 Reconciliation Engine configuration changes 14 database settings and 32 debugging 102 duplicate Configuration Items (CIs) 26. reducing RE job queue 19 port errors. 99 Systinet 102 TRACE entries 21 web services 102 N names. 163 Microsoft SQL server. AIE RPC 62 Primary Key Mapping tab 54 processes checking status 18 verifying completion 19 processing phase. messages 106 BMC Remedy Action Request System Server (BMC Remedy AR Server) 117 DETAILS entries 21 Java API 97 Reconciliation Engine 21. changing AIE stops service 55 paused Reconciliation Engine jobs 15 performance. AIE debug 110 log 106 messages. Reconciliation Engine and 31 P passwords. AIE debug logging 113 Product Catalog Setup form Create button 75 viewing records 76 product support 3 R RE. Reconciliation Engine 31. See data models Modify Server Configuration window 14 modules. 38. 100 technical support 3 TRACE entries in RE job log 21 U unidentified Configuration Items (CIs) 20. resetting 84 Reconciliation Manager tab 14. 112. BMC Atrium CMDB 73 viewing arrecond. 34. data exchange 113 support. 100 relationships deleting cardinality violations 87 deleting orphans 86 finding cardinality violations 83 fixing invalid 85 reports invalid dataset IDs 83 relationship cardinality violations 83 resetting reconciliation IDs 84 RPC AIE port errors 62 federation plugin errors 70 cmdbdiag program 82 Reconciliation Engine 14 Reconciliation Engine jobs 18 web services 75 statistics. customer 3 Systinet logs. 16. web 102 starting web 75 ServletExec 37 source datasets. web services 102 T tabs Administrative Information 15. federated data class 71 version information. 113 Audit 68 Characteristics 154 Connection Settings 52 Data Field Mapping 107 Data Mappings 50 Log Files 67. See Atrium Widget Index 201 . 32 starting 14 troubleshooting 13 unidentified instances 20 Reconciliation Engine jobs aborted 15 AR System server restarted 16 classId does not exist 17 events for log file 99 failed 15 failing to start 18 fatal errors 15 incomplete 19 insufficient memory 17 paused 15 polling interval 19 Reconciliation Engine restarted 16 troubleshooting 15 viewing records 18 reconciliation IDs. 117 Primary Key Mapping 54 Reconciliation Manager 14. 26. duplicate Configuration Items (CIs) in 28 SQL adapter. AIE and 57 starting AIE debug logging 105 W web services API logs and 104 application server logs 102 logs 102 starting 75 Systinet logs 102 widgets. 28 V validation errors.sh file 23 BMC Atrium CMDB version information 73 data models 81 Reconciliation Engine job records 18 Reconciliation Engine log file events 100 records in Product Catalog Setup form 76 S Server Information form 31. 18 Advanced Settings 50. 68.A B C D E F G H I J K L M N O P Q R S T U V W X Y Z Reconciliation Engine (continued) performance problems 31. 39 server-side logging. BMC Atrium Core Console 95 services AIE fatal error 56 AIE stopped after password change 55 AIE stops AR System server on UNIX 55 BMC Atrium Integration Engine 55 logs. A B C D E F G H I J K L M N O P Q R S T U V W X Y Z windows Data Exchanges Information 50. 113 Data Field Mapping 62 Job Event Information 100 Mapping Information 113 Z zipping log files 118 202 Troubleshooting Guide . 105. 112. . *877671* *877671* *877671* *877671* *176778* .
Copyright © 2024 DOKUMEN.SITE Inc.