This documentation supports the 9.1 to 9.1 Service Pack 3 version and its patches of BMC Atrium Core. The documentation for version 9.1.04 and its patches is available here.

To view the latest version, select the version from the Product version menu.

Extension loader not responding

The extension loader might not successfully copy data to your data model due to issues with the BMC Remedy AR System server. Use the following procedure if the extension loader stops responding or fails to run.

To troubleshoot extension loader process issues

  1. In the AR System Administration Console, log on to the BMC Atrium CMDB server to verify that you can connect to the AR System server.
  2. To verify that you can access the BMC Atrium CMDB server, log on to the cmdbdriver program and issue the glc command.
    For more information about using cmdbdriver, see cmdbdriver program.
  3. Make sure that the database server has at least 15 percent of space available and can grow the transaction log as needed during the installation.


    Set the auto-extend option in the database to make sure that the space on the database server automatically extends.

  4. If the extension loader stops responding, check the arerror.log or armonitor.log files to make sure that the arserver.exe (Microsoft Windows) or arserverd (UNIX) server process did not restart or stop responding.
    During the installation, the Admin thread 390600 is busy, Therefore, you might receive timeout messages when you try to access the AR System Administration Console.
  5. If the AR System server stops responding during the extensions installation, abort the installation and troubleshoot the AR System issue.
  6. If you are installing the extensions as a non-root user, make sure that you use the same user ID that you used to install the AR System server and BMC Atrium CMDB.
  7. To verify that your system has sufficient space (at least 600 MB of free space and 1 GB of temp space), perform the following steps:
    1. Check the %TEMP% directory (Windows) or /tmp (UNIX) for space.
    2. On Windows, check hard disk space using Explorer. On UNIX, use the df- k command to verify that you have a reasonable amount of swap space on the system.
  8. On UNIX, type ulimit -a from the console to verify that the ulimit settings are set high.
    The following output is from a system that is functional. A default system has a process size limit of 64 KB, which is not large enough for the BMC Remedy installer.
    • time (seconds) unlimited
    • file (blocks) unlimited
    • data (kbytes) unlimited
    • stack (kbytes) 8192
    • coredump (blocks) unlimited
    • nofiles (descriptors) 64
    • vmemory (kbytes) unlimited
  9. On IBM AIX, perform the following steps:
    • Enter lsattr -E -l sys0 -a ncargs to make a note of the value from ncargs.
    • Enter chdev -l sys0 -a ncargs=128 to temporarily change ncargs to its maximum for the system.
  10. If any processes on AIX stopped responding, use the procstack -F ProcessID AIX command to troubleshoot the issue.
  11. On Windows, set the VM parameter in the boot.ini file to allow 32-bit programs to use 3 GB of random access memory (RAM).
Was this page helpful? Yes No Submitting... Thank you