5 Replies Latest reply on Mar 22, 2019 1:36 PM by Gustavo del Gerbo

    BMC Drift Management 8.1.01 installation issue (it displays a non-existent authentication failure and does not allow to continue the installation process)

    Pedro Guerrero
      Share:|

      Hello everyone

       

      I've been attempting to install BMC Drift Management but everytime I enter the correct data (which I've verified several times with people around here) I got the "Authentication Failed" error

       

      ===============================================================================
      AR System Server Settings
      -------------------------

      Specify your AR System Server settings.
      ENTER THE NUMBER CORRESPONDING TO THE AR SERVER YOU WOULD LIKE TO SELECT.
        ->1- occ1prarsbap01

      Select the AR System server (DEFAULT: occ1prarsbap01): 1
      TCP Port (DEFAULT: 0): 2020
      User Name (DEFAULT: Demo): Demo
      Password:***************

      ===============================================================================
      AR System Server Settings
      -------------------------

      Please correct the following errors.

      Authentication failed. Check to make sure that the user name and password are
      correct.

      I'm unable to use the GUI option for installation also this time (I have no chances to have a graphic environment installed as of now):

       

      Graphical installers are not supported by the VM. The console mode will be used instead…

      Upon further assistance, I got this link: The Adventure of the Drifting Data. A.K.A things you don't know about Drift Management  where I could check some settings that we currently have and I don't see any major problem with it

       

      [root@occ1prarsbap01 /]# cat /app01/remedy01/ARSystem/conf/ar.conf | grep "JOBMGR.FILTERAPI"

      Server-Plugin-Alias: JOBMGR.FILTERAPI JOBMGR.FILTERAPI occ1prarsbap01:9999

       

      [root@occ1prarsbap01 /]# cat /etc/arsystem/occ1prarsbap01/armonitor.conf | grep "Xmx"

      /usr/java/jre1.8.0_121/bin/java -Xmx3072m -classpath /app01/remedy01/ARSystem/pluginsvr:/app01/remedy01/ARSystem/pluginsvr/arpluginsvr91_build002.jar:/app01/remedy01/ARSystem/approval/bin/armaskingImpl91_build002.jar:/app01/remedy01/ARSystem/api/lib/arcmnapp91_build002.jar com.bmc.arsys.pluginsvr.ARPluginServerMain -x occ1prarsbap01 -i /app01/remedy01/ARSystem#/usr/java/jre1.8.0_121/bin/java -Xmx768m -classpath /app01/remedy01/ARSystem/dsoj:/app01/remedy01/ARSystem/dsoj/ardsoj91_build002.jar:/app01/remedy01/ARSystem/api/lib/arapi91_build002.jar:/app01/remedy01/ARSystem/api/lib/arcmnapp91_build002.jar:/app01/remedy01/ARSystem/api/lib/arutil91_build002.jar:/app01/remedy01/ARSystem/dsoj/com.bmc.arsys.messaging.client-9.1.03-SNAPSHOT.jar:/app01/remedy01/ARSystem/dsoj/com.bmc.arsys.companion.client-9.1.03-SNAPSHOT.jar:/app01/remedy01/ARSystem/dsoj/com.bmc.arsys.companion.remote-9.1.03-SNAPSHOT.jar:/app01/remedy01/ARSystem/dsoj/activemq-all-5.10.0.jar com.bmc.arsys.dsoj.DSOServer --unicode -i /app01/remedy01/ARSystem -m

      /usr/java/jre1.8.0_121/bin/java -Xmx3072m -classpath /app01/remedy01/ARSystem/pluginsvr/fts/secondary:/app01/remedy01/ARSystem/pluginsvr/fts/core:/app01/remedy01/ARSystem/pluginsvr:/app01/remedy01/ARSystem/pluginsvr/arpluginsvr91_build002.jar: com.bmc.arsys.pluginsvr.ARPluginServerMain -x occ1prarsbap01 -i /app01/remedy01/ARSystem -m

      /usr/java/jre1.8.0_121/bin/java -Xmx768m -classpath /app01/remedy01/ARSystem/approval/bin:/app01/remedy01/ARSystem/pluginsvr/arpluginsvr91_build002.jar:/app01/remedy01/ARSystem/approval/bin/arasj91_build002.jar:/app01/remedy01/ARSystem/api/lib/arcmnapp91_build002.jar:/app01/remedy01/ARSystem/approval/bin/armaskingImpl91_build002.jar:/app01/remedy01/ARSystem/api/lib/log4j-1.2.14.jar com.bmc.arsys.pluginsvr.ARPluginServerMain -x occ1prarsbap01 -i /app01/remedy01/ARSystem -m

      /usr/java/jre1.8.0_121/bin/java  -Xmx1024m -cp /app01/remedy01/ARSystem/diserver/data-integration:/app01/remedy01/ARSystem/diserver/data-integration/lib/* -Dorg.mortbay.util.URI.charset=UTF-8 -Djava.library.path= -DKETTLE_HOME=/app01/remedy01/ARSystem/diserver -DKETTLE_REPOSITORY= -DKETTLE_USER= -DKETTLE_PASSWORD= -DKETTLE_PLUGIN_PACKAGES= -DKETTLE_LOG_SIZE_LIMIT= -DKETTLE_MAX_LOG_SIZE_IN_LINES=5000 -DKETTLE_DISABLE_CONSOLE_LOGGING=Y -DKETTLE_COMPATIBILITY_MERGE_ROWS_USE_REFERENCE_STREAM_WHEN_IDENTICAL=Y -DKETTLE_LENIENT_STRING_TO_NUMBER_CONVERSION=Y org.pentaho.di.www.Carte occ1prarsbap01 20000 -i /app01/remedy01/ARSystem

      [root@occ1prarsbap01 /]#

       

      I also checked this document: Prerequisites for Installing Drift Management and help as non-root - Linux only - Documentation for BMC Remedy ITSM Depl…

      and gave read,write,execute permissions to all what's needed for a successful installation but I'm still stuck in this loop.

       

      Notice that I also logged into the mid-tiers using the given user and password and it works fine

      It is highly probable that I could be overlooking something but I think I ran out of resources this time which is why I ask for further help on this.

       

      Drift Management versión is 8.1.01

      AR System versión is 9.1.03

      We were told in a previous BMC case that this combination works

       

      Thank you in advance for your assistance

      Best regards

      Pedro.