This documentation supports the 21.05 version of BMC Service Level Management. To view an earlier version, select the version from the product version menu.

Troubleshooting ARX file generation issues

When you import or export service targets, the ARX file may not be generated.

Issue symptom

A message for successful completion is displayed, but the data is not imported.


Issue scope

While importing an ARX file to BMC Service Level Management.

Resolution

Run the following command:

cd /<SLM Installed Directory>
/BMCSLMInstallJVM/bin./java
-DisRik=1 -cp "/
<AR Installed directory>/
api/lib/arapi91_build004.jar:
/<AR Installed directory>
/api/lib/arapiext91_build004.jar:
/<AR Installed directory>
/api/lib/log4j-1.2.14.jar:/
<AR Installed directory>
/pluginsvr/activation.jar"
com.bmc.arsys.apiext.
data.DataImport
-h 1 -g 1 -x "nonrootuser
name@machine_Name"
-u "AR Admin User"
– p  “AR Admin Password”
-a AR_ TCP Port  -o
"SLM arx file path" -l "SLM arx log file path"
For example:
[nonroot@machine_Name
bin]#
./java -DisRik=1 -cp
"/opt/bmc/ARSystem
/api/lib/arapi91_build004.jar:
/opt/bmc/ARSystem
/api/lib
/arapiext91_build004.jar
:/opt/bmc/ARSystem
/api/lib/log4j-1.2.14.jar:
/opt/bmc/ARSystem
/pluginsvr/activation.jar"
com.bmc.arsys.apiext.data.
DataImport -h 1 -g 1 -x
"servername" -u "Demo" -o
"/opt/SLM/SLM_importfile.arx"
-l "/opt/SLM/SLM_arximport.log" -a 0


Issue symptom

ARX file is not generated when you export service target.

Issue scope

In a Server Group environment, this could affect one or more servers.

Resolution

Perform the following steps to troubleshoot the ARX file generation issues:

StepTaskDescription
1Check SLM preferences

Perform the following steps:

  1. Select Administration Console > Application Administration Console > Custom Configuration > Service Level Management > Configure Application Settings > Preferences.
  2. In the AR Install Path area, select No.
  3. Ensure that the AR Install Path for Multi AR Server box is empty.
    If the AR Install Path for Multi AR Server field is not empty, copy the content for future reference.
  4. In the SLM Import area, select No.
  5. Ensure Path for arimportcmd.exe box is empty.
    If the Path for arimportcmd.exe box is not empty, copy the content for future reference.
  6. Click Save.
2Check the AR export/import process

Perform the following steps:

  1. Open the command prompt and change the working directory to the following locations:
    • (Microsoft Windows) ARSystemServerInstallDir
    • (Linux) ARSystemInstallDir/bin 

  2. Type the following command at the command prompt and press Enter:
    • (Microsoft Windows)

      runmacro -o BMC_Test -x localhost -a <Port Number> -U <arsystem admin user> -P <password> -s SLM:Association -t arx -q "('associationName' =\"Reference Form\")"

      If you get the following error:
      The program can't start because MFC71.dll is missing from your computer. Try reinstalling the program to fix this problem
      Ensure the following files exist at location c:\Windows and try again.

      • mfc71.dll
      • msvcp71.dll
    • (Linux)

      ./runmacro -o BMC_Test -x localhost -a <Port Number> -U <arsystem admin user> -P <password> -s SLM:Association -t arx -q "('associationName' =\"Reference Form\")"

      If you get the following error, install the required libraries:
      ./runmacro: error while loading shared libraries: library_name: cannot open shared object file: No such file or directory

      Example

      runmacro -o BMC_Test -x localhost -a 0 -U Demo -P password -s SLM:Association -t arx -q "('associationName' =\"Reference Form\")"

3Import or export service targetsIf you get plug-in errors, see Troubleshooting plug-in errors in Service Level Management.
4Check if the imported service targets exist in Service Level Management.
  1. In a browser, enter the following URL to open the SLM:Association form:
    http://<midTierServer>/arsys/forms/<ARSystemServer>/<formName>
    For example, http://vw-us-rem-qa:8080/arsys/forms/vw-us-rem-qa/SLM:Associationform.
  2. In the instanceName1 field, enter the required value, and click Search.
  3. In the search results pane, select the required record, and click Delete.
  4. Open the SLM:GoalSchedule form.
  5. In the Name field, enter the required value, and click Search.
  6. In the search results pane, select the required record, and click Delete
  7. Repeat the steps d-f for the following forms:
    1. SLM:RuleAction
    2. SLM:RuleActionSequence
    3. SLM:RuleActionSetValueItem
    4. SLM:RuleCondition
    5. SLM:RuleDefinition
    6. SLM:RuleEventData
  8. Open the SLM:RuleFilterRegistration form.

  9. In the actionName field, enter the required value, and click Search.

  10. In the search results pane, select the required record, and click Delete.
  11. Open the SLM:Milestone form.
  12. In the ParentSLMId field, enter the required value, and click Search.

  13. In the search results pane, select the required record, and click Delete.

5Import service targets If the Milestone or Action information is missing from the imported service target, contact BMC Support and request for SW00381675_hotfix. Apply the hotfix on the source server and perform the Export/Import of service targets.

If none of the above procedures work for exporting or importing service targets, contact BMC support and provide the following log information:

  • From the client side:
    • Active Links
    • Filter
    • SQL
  • From the server side:
    • API
    • Filter
    • SQL
Was this page helpful? Yes No Submitting... Thank you

Comments