Date: Fri, 29 Mar 2024 10:32:04 -0500 (CDT) Message-ID: <1757253278.30342.1711726324477@bmc1-rhel-confprod1.managed.contegix.com> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_30341_720713077.1711726324476" ------=_Part_30341_720713077.1711726324476 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Messages that begin with the BMC-IWS
prefix are rel=
ated to BMC Impact Integration Web Services. Each message is preceded by a =
six-digit ID number, followed by one of the following alphabetic characters=
: E, I, or W. The alphabetic character identifies whether the message descr=
ibes an error (E), supplies information (I), or delivers a warning (W).
The following groups of numbered messages are related to the function indi=
cated:
BMC-IWS messages numbered 001001 through 001022 are general exception me= ssages.
Explanation: Attempt to connect to the named ImpactManager fail= ed.
User Response: Check the status of the cell and the network. Al= so, read the exception message for details.
Explanation: The named operation failed.
User Response: Read the exception message for details and possi= ble suggestions.
Explanation: The value provided for cellName in the operation i= s invalid.
User Response: Verify that the value provided for cellName is l= isted in the BMC Impact Integration Web Services mcell.dir= file.
Explanation: Attempt to connect to the named ImpactManager cell= failed.
User Response: Verify that you have a valid mcell.dir= strong> file and that the ImpactManager entered is valid. Also, read the ex= ception message for details.
Explanation: The input connection handle in the SendEvent opera= tion is invalid.
User Response: Verify that the value you provided for connectHa= ndle in the Connect operation is valid.
Explanation: Attempt to create the sending event client for the= named ImpactManager failed, causing the Connect operation to fail.
User Response: Verify that the mcell.dir file = is valid, and that the entry for the cell is valid. For more information, c= heck the IIWS log file.
Explanation: An error was detected in the SendEvent operation.<= /p>
User Response: Read the exception message for details and possi= ble suggestions.
Explanation: The query string entered for the query is invalid<= /p>
User Response: Verify and correct the query string.
Explanation: The operation request failed.
User Response: Read the exception message for details and possi= ble suggestions.
Explanation: The input parameter in the operation request is in= valid.
User Response: Verify that the input parameter is correct for t= he operation.
Explanation: The query operation failed due to no query handle = found.
User Response: Check the IIWS log file for more information.
Explanation: The input query handle is invalid.
User Response: Make sure that the handle you use in the respons= e section of the query operation is valid.
Explanation: The input parameter in the operation request is in= valid.
User Response: Use an input parameter that is correct for the o= peration.
Explanation: The execution of the operation failed.
User Response: Read the exception message for details and possi= ble suggestions.
Explanation: An array type was expected for the slot.
User Response: Check your client input slot value and type.
Explanation: The slot was skipped for the event. The values in = the name and value pair for the named slot were invalid.
User Response: None required.
Explanation: No valid value was entered for where to send the e= vent. The event was dropped.
User Response: Check the input event in the SendEvent operation= .
Explanation: The input componentId
for BMC Impact =
Manager was not found.
User Response: Ensure that the CI that has the mc_udid equal to
componentId
exists in BMC Impact Manager.
Explanation: The input status for MC_SM_COMPONENT_STATUS is not= valid.
User Response: Use the valid MC_SM_COMPONENT_STATUS that is def= ined in BMC Impact Manager.
Explanation: There is no input for className
in th=
e QueryClassDefinitions operation.
User Response: If the classOnly
parameter in the Q=
ueryClassDefinition is true, then the className
value cannot b=
e null.
Explanation: The input for the registrationID
para=
meter in the unregisterStateChange request is invalid.
User Response: You have to use the registrationID
=
returned from the previous RegisterStateChange call.
Explanation: The execution of UnregisterStateChange failed. The= re are no valid RegisterStateChange calls.
User Response: You must use the registrationID
ret=
urned from the preceeding RegisterStateChange call in the Unregiste=
rStateChange call.
BMC-IWS messages numbered 002001 through 001007 are exception messages g= enerated by the subscription function.
Explanation: The attempt to initialize the subscription failed,= and an error message was generated.
User Response: Read the exception message for details and possi= ble suggestions.
Explanation: The client ID and filterName combination uniquely = identifies a subscription from the Subscribe call. The GetEvents, AckEvents= , and Unsubscribe operations have to supply the same ID and filterName as t= he ones that the previous Subscribe used.
User Response: You must call Subscribe before calling GetEvents= , AckEvents, or Unsubscribe. Verify that client ID and filterName are the s= ame.
Explanation: The attempt to run the Subscribe operation failed.=
User Response: Read the exception message for details and possi= ble suggestions.
Explanation: The attempt to run the Unsubscribe operation faile= d.
User Response: Read the exception message for details and possi= ble suggestions.
Explanation: The attempt to run the GetEvents operation failed.=
User Response: Read the exception message for details and possi= ble suggestions.
Explanation: The attempt to run the AckEvents operation failed.=
User Response: Read the exception message for details and possi= ble suggestions.
Explanation: The attempt to run the GetFilternames operation fa= iled.
User Response: Read the exception message for details and possi= ble suggestions.
BMC-IWS messages numbered 003001 through 001004 are exception messages g= enerated during initialization.
Explanation: The attempt to initialize the IIWS process failed.=
User Response: Verify that BMC Impact Integration Web Services = is installed and working correctly. For more information, check the BMC Imp= act Integration Web Services log file.
Explanation: An attempt to read the BMC Impact Manager server <= strong>dir file failed.
User Response: Verify that the mcell.dir file = exists under $IIWS_HOME/Tomcat/webapps/imws/WEB-INF/etc.= strong> Verify that it is correctly formatted.
Explanation: An attempt to find the mcell.dir = file from the BMC Impact Integration Web Services configuration direc= tory failed.
User Response: Verify that the $IIWS_HOME environment = is defined correctly. Then, verify that the mcell.dir file= exists under the $IIWS_HOME/Tomcat/webapps/imws/WEB-INF/e= tc directory.
Explanation: The attempt to load the ImWebServices.conf= configuration file from BMC Impact Integration Web Services confi= guration directory failed.
User Response: Verify that the $IIWS_HOME environment = is defined correctly. Then, verify that the ImWebServices.conf configuration file exists under the $IIWS_HOME/Tomcat= /webapps/imws/WEB-INF/etc directory.