2162052 - SMP Server stuck at '120 of 121' tracked bundles have initialized - Agentry hanging - unable to start SMP server (agentry.core <-- Issue)

• Symptom 1: Bundles (and their services) not yet initialized: com.sap.mobile.platform.server.agentry.core <-- Issue
• The following Agentry startup.log was identified to state: Loading agent from ag3.dll..reading config file (Hang here)

• Symptom 2: It can also hang here on SMP 3.0 startup (see SMPServerName-smp-server.log) but after running the startup for at least 4 hours+ (i.e. wait for it), it will successfully start up
  
  ~~~~~~~~~~From log file~~~~~~~~~~~
  
  SMPServerStatusManager: 2017 01 20 12:43:19.587 Bundle initialization will be monitored.  Bundle: com.sap.mobile.platform.server.mobilink.integration
  SMPServerStatusManager: 2017 01 20 12:43:19.620 com.sap.mobile.platform.server.notifications.persistence, state: STARTING, type: START_ACTIVATION, startLevel:7
  SMPServerStatusManager: 2017 01 20 12:43:19.622 com.sap.mobile.platform.server.notifications.persistence, state: ACTIVE, type: END_ACTIVATION, startLevel:7
  ..
  .. Wait for at least 4+ hours (see below and it will startup successfully)
  ..
  SMPServerStatusManager: 2017 01 20 17:19:54.711 com.sap.mobile.platform.server.online.common.persistence, state: STARTING, type: START_ACTIVATION, startLevel:7
  SMPServerStatusManager: 2017 01 20 17:19:54.713 com.sap.mobile.platform.server.online.common.persistence, state: ACTIVE, type: END_ACTIVATION, startLevel:7
  ..
  ..
  SMPServerStatusManager: 2017 01 20 17:22:19.659 Bundles (and their services) not yet initialized: com.sap.mobile.platform.server.agentry.core <-- Issue
  ..
  2017 01 20 17:22:50#0-600#INFO#System.out###Agentry Prod Def Load Loop Thread#########Ex12nManager::begin |
  2017 01 20 17:22:50#0-600#INFO#System.out###Agentry Prod Def Load Loop Thread#########using INI file C:\Users\I834260\Documents\Agentry\SMP\Server\configuration\com.sap.mobile.platform.server.agentry.application.SAPWM\JavaBE.ini |
  2017 01 20 17:22:50#0-600#INFO#System.out###Agentry Prod Def Load Loop Thread#########initServer::begin |
  2017 01 20 17:22:50#0-600#INFO#System.out###Agentry Prod Def Load Loop Thread#########setMobileAppName::begin |
  2017 01 20 17:22:50#0-600#INFO#System.out###Agentry Prod Def Load Loop Thread#########setMobileAppName::Mobile application name from server: null... |
  2017 01 20 17:22:50#0-600#INFO#System.out###Agentry Prod Def Load Loop Thread#########setMobileAppName::Mobile application name from JavaBE.ini: SAP_WORK_MANAGER_63... |
  2017 01 20 17:22:50#0-600#INFO#System.out###Agentry Prod Def Load Loop Thread#########setMobileAppName::Setting the mobile application name to SAP_WORK_MANAGER_63... |
  2017 01 20 17:22:50#0-600#INFO#System.out###Agentry Prod Def Load Loop Thread#########setHost::begin |
  ..
  ..
  2017 01 20 17:23:17#0-600#INFO#System.out###SMPServerStatusManager#########SMPServerStatusManager: The SMP server has initialized and is ready.  <-- started successfully |
  ~~~~~~~~~~End~~~~~~~~~~~~~~~~
• Symptom 3: Unable to Publish an Agentry application to the SMP 3.0 server

SAP Mobile Platform 3.0

"SMP 3.0 Agentry startup hangs", "SAP Mobile Platform 3.0 hangs on startup", "Agentry hangs on startup", "SMP 3.0 hangs for a long time before starting", ".application.lock", "Agentry Publish" , KBA , MOB-SYC-SAP , Syclo Mobility for SAP backend , MOB-SYC-OTH , Syclo Mobility for other backend , MOB-SYC-IBM , Syclo Mobility for IBM backend , Problem