Analysis Application Service doesn't start after DS Addon Install

[Former Member]

Hi all,

I have developed a simple Design Studio google maps addon based on the SAP tutorials. The addon works great on my own machine (local mode) as well as on our internal test server (deployed on our BI 4.1 Server)

I plan now to use this addon at a customer site and after moving the same addon package across to the customer design studio application I could successfully install it locally -where it works fine- and on their BI server.

After installing an addon on the server we need to restart the Analysis Application Service manually, and it never manages to restart fully at the customer site. In the CMC it states "Running with errors" and looking at the Server properties the Analysis Service states "Unable to initialize service. LogID: "

The only way to restart the Server successfully (and process DS applications) is to uninstall the addon from the server (via the DS Studio client).

Looking at the traces, the Adaptive Processing Server throws the following when trying to start:

|AB062C91491A442CBCB0D8B5A8A2069411|2014 05 09 15:29:18.219|+1000|Debug| |<<| | |aps_BOXIDEV.APS.DesignStudio_NEW|15404|  20|ManagedService Update Queue| ||||||||||||||||||||com.sap.security.saml2.lib.common.SAML2ServicesManagerBase||Trying to instantiate service: interface com.sap.security.saml2.cfg.interfaces.services.SAML2CfgKeystoreService from addapter class: com.sap.security.saml2.cfg.nwadapters.SAML2CfgKeystoreServiceNWAdapter 
|AB062C91491A442CBCB0D8B5A8A2069412|2014 05 09 15:29:18.219|+1000|Debug| |<<| | |aps_BOXIDEV.APS.DesignStudio_NEW|15404|  20|ManagedService Update Queue| ||||||||||||||||||||com.sap.security.saml2.lib.common.SAML2ServicesManagerBase||Could not instantiate service: interface com.sap.security.saml2.cfg.interfaces.services.SAML2CfgKeystoreService from adapter class: com.sap.security.saml2.cfg.nwadapters.SAML2CfgKeystoreServiceNWAdapter, because the adapter class is not found. 
|AB062C91491A442CBCB0D8B5A8A2069413|2014 05 09 15:29:18.219|+1000|Debug| |<<| | |aps_BOXIDEV.APS.DesignStudio_NEW|15404|  20|ManagedService Update Queue| ||||||||||||||||||||com.sap.security.saml2.lib.common.SAML2ServicesManagerBase||Trying to instantiate service: interface com.sap.security.saml2.cfg.interfaces.services.SAML2CfgKeystoreService from addapter class: com.sap.security.saml2.cfg.ljsadapters.SAML2CfgKeystoreServiceLJSAdapter 
|AB062C91491A442CBCB0D8B5A8A2069414|2014 05 09 15:29:18.250|+1000|Debug| |<<| | |aps_BOXIDEV.APS.DesignStudio_NEW|15404|  20|ManagedService Update Queue| ||||||||||||||||||||com.sap.security.saml2.cfg.ljsadapters.SAML2CfgKeystoreServiceLJSAdapter||Could not open system keystore!
java.security.KeyStoreException: LJSKS not found
    at java.security.KeyStore.getInstance(KeyStore.java:587)
    at com.sap.security.saml2.cfg.ljsadapters.SAML2CfgKeystoreServiceLJSAdapter.getKeystorePassword(SAML2CfgKeystoreServiceLJSAdapter.java:237)
    at com.sap.security.saml2.cfg.ljsadapters.SAML2CfgKeystoreServiceLJSAdapter.<init>(SAML2CfgKeystoreServiceLJSAdapter.java:76)
    at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
    at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
    at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
    at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
    at java.lang.Class.newInstance0(Class.java:355)
    at java.lang.Class.newInstance(Class.java:308)
    at com.sap.security.saml2.cfg.util.SAML2CfgServicesManager.instantiateClass(SAML2CfgServicesManager.java:50)
    at com.sap.security.saml2.lib.common.SAML2ServicesManagerBase.instantiateService(SAML2ServicesManagerBase.java:62)
    at com.sap.security.saml2.cfg.util.SAML2CfgServicesManager.getCfgKeystoreServiceInstance(SAML2CfgServicesManager.java:58)
    at com.sap.security.saml2.cfg.ljs.SAML2LJSConfiguration.updated(SAML2LJSConfiguration.java:63)
    at org.eclipse.equinox.internal.cm.ManagedServiceTracker$1.run(ManagedServiceTracker.java:181)
    at org.eclipse.equinox.internal.cm.SerializedTaskQueue$1.run(SerializedTaskQueue.java:36)
Caused by: java.security.NoSuchAlgorithmException: LJSKS KeyStore not available
    at sun.security.jca.GetInstance.getInstance(GetInstance.java:142)
    at java.security.Security.getImpl(Security.java:659)
    at java.security.KeyStore.getInstance(KeyStore.java:584)
    ... 14 more

|AB062C91491A442CBCB0D8B5A8A2069415|2014 05 09 15:29:18.250|+1000|Debug| |<<| | |aps_BOXIDEV.APS.DesignStudio_NEW|15404|  20|ManagedService Update Queue| ||||||||||||||||||||com.sap.security.saml2.lib.common.SAML2ServicesManagerBase||Successfully instantiated service: interface com.sap.security.saml2.cfg.interfaces.services.SAML2CfgKeystoreService from addapter class: com.sap.security.saml2.cfg.ljsadapters.SAML2CfgKeystoreServiceLJSAdapter 
|AB062C91491A442CBCB0D8B5A8A2069416|2014 05 09 15:29:18.313|+1000|Error| |==|E| |aps_BOXIDEV.APS.DesignStudio_NEW|15404|  20|ManagedService Update Queue| ||||||||||||||||||||com.sap.security.saml2.cfg.SAML2GlobalConfigImpl||Could not initialize SAML2 global configuration
com.sap.security.saml2.cfg.exceptions.SAML2ConfigurationException: Could not load trusted Identity Providers
    at com.sap.security.saml2.cfg.SAML2TrustedIdPsConfigImpl.loadAllTrustedIdPs(SAML2TrustedIdPsConfigImpl.java:151)
    at com.sap.security.saml2.cfg.SAML2TrustedIdPsConfigImpl.<init>(SAML2TrustedIdPsConfigImpl.java:73)
    at com.sap.security.saml2.cfg.SAML2ConfigImpl.initConfigurationObjects(SAML2ConfigImpl.java:79)
    at com.sap.security.saml2.cfg.SAML2ConfigImpl.<init>(SAML2ConfigImpl.java:55)
    at com.sap.security.saml2.cfg.SAML2GlobalConfigImpl.initGlobalConfiguration(SAML2GlobalConfigImpl.java:98)
    at com.sap.security.saml2.cfg.SAML2GlobalConfigImpl.<init>(SAML2GlobalConfigImpl.java:69)
    at com.sap.security.saml2.cfg.SAML2GlobalConfigImpl.createInstance(SAML2GlobalConfigImpl.java:85)
    at com.sap.security.saml2.cfg.SAML2GlobalConfigImpl.getInstance(SAML2GlobalConfigImpl.java:78)
    at com.sap.security.saml2.cfg.SAML2CfgFactory.getSAML2GlobalConfig(SAML2CfgFactory.java:24)
    at com.sap.security.saml2.cfg.ljs.SAML2LJSConfiguration.updated(SAML2LJSConfiguration.java:64)
    at org.eclipse.equinox.internal.cm.ManagedServiceTracker$1.run(ManagedServiceTracker.java:181)
    at org.eclipse.equinox.internal.cm.SerializedTaskQueue$1.run(SerializedTaskQueue.java:36)
Caused by: com.sap.security.saml2.cfg.storage.CfgStorageException: Could not obtain sub configurations for cfg path: default/trusted_providers/trusted_idps
    at com.sap.security.saml2.cfg.ljsadapters.filestorage.CfgFileStorage.getSubCfgNames(CfgFileStorage.java:307)
    at com.sap.security.saml2.cfg.storage.CfgObject.getSubCfgPaths(CfgObject.java:136)
    at com.sap.security.saml2.cfg.SAML2TrustedIdPsConfigImpl.loadAllTrustedIdPs(SAML2TrustedIdPsConfigImpl.java:121)
    ... 11 more
Caused by: com.sap.security.saml2.cfg.storage.CfgStorageException: SAML 2 configuration directory (set to "null") is incorrect! Use system property "sys.global.dir" to specify it the correct one!
    at com.sap.security.saml2.cfg.ljsadapters.SAML2LJSAdapters.getConfigurationRoot(SAML2LJSAdapters.java:46)
    at com.sap.security.saml2.cfg.ljsadapters.filestorage.CfgFileStorageAccessor.getReadableConfiguration(CfgFileStorageAccessor.java:38)
    at com.sap.security.saml2.cfg.ljsadapters.filestorage.CfgFileStorage.obtainReadableConfiguration(CfgFileStorage.java:408)
    at com.sap.security.saml2.cfg.ljsadapters.filestorage.CfgFileStorage.getSubCfgNames(CfgFileStorage.java:287)
    ... 13 more

|AB062C91491A442CBCB0D8B5A8A2069417|2014 05 09 15:29:18.313|+1000| |Warning|  | | |aps_BOXIDEV.APS.DesignStudio_NEW|15404|  20|ManagedService Update Queue| ||||||||||||||||||||com.sap.security.saml2.cfg.ljs.SAML2LJSConfiguration||Could not refresh SAML2 configuration
com.sap.security.saml2.cfg.exceptions.SAML2ConfigurationException: Could not initialize SAML2 global configuration
    at com.sap.security.saml2.cfg.SAML2GlobalConfigImpl.<init>(SAML2GlobalConfigImpl.java:72)
    at com.sap.security.saml2.cfg.SAML2GlobalConfigImpl.createInstance(SAML2GlobalConfigImpl.java:85)
    at com.sap.security.saml2.cfg.SAML2GlobalConfigImpl.getInstance(SAML2GlobalConfigImpl.java:78)
    at com.sap.security.saml2.cfg.SAML2CfgFactory.getSAML2GlobalConfig(SAML2CfgFactory.java:24)
    at com.sap.security.saml2.cfg.ljs.SAML2LJSConfiguration.updated(SAML2LJSConfiguration.java:64)
    at org.eclipse.equinox.internal.cm.ManagedServiceTracker$1.run(ManagedServiceTracker.java:181)
    at org.eclipse.equinox.internal.cm.SerializedTaskQueue$1.run(SerializedTaskQueue.java:36)
Caused by: com.sap.security.saml2.cfg.exceptions.SAML2ConfigurationException: Could not load trusted Identity Providers
    at com.sap.security.saml2.cfg.SAML2TrustedIdPsConfigImpl.loadAllTrustedIdPs(SAML2TrustedIdPsConfigImpl.java:151)
    at com.sap.security.saml2.cfg.SAML2TrustedIdPsConfigImpl.<init>(SAML2TrustedIdPsConfigImpl.java:73)
    at com.sap.security.saml2.cfg.SAML2ConfigImpl.initConfigurationObjects(SAML2ConfigImpl.java:79)
    at com.sap.security.saml2.cfg.SAML2ConfigImpl.<init>(SAML2ConfigImpl.java:55)
    at com.sap.security.saml2.cfg.SAML2GlobalConfigImpl.initGlobalConfiguration(SAML2GlobalConfigImpl.java:98)
    at com.sap.security.saml2.cfg.SAML2GlobalConfigImpl.<init>(SAML2GlobalConfigImpl.java:69)
    ... 6 more

The main messages that I get from this are:

     - Could not open system keystore!

     - LJSKS Not Found

     - SAML 2 configuration directory (set to "null") is incorrect! Use system property "sys.global.dir" to specify it the correct one!

     - Could not refresh SAML2 configuration

It seems some kind of authentication error, but I don't understand what could trigger it.

As a reminder, this addon works fine on our internal BI4 server installation and there isn't much different with our customer's.

They do have AD authentication enabled, but I can't see how this would be related.

All the post I have found seem to related to HANA or a SAP BW system, which our customer don't have.

Any help is appreciated.

Best regards,

Antoine

[mhf · Accepted solution]

Hello Antoine,

try the following SAP Note 1942899.

That fixed it for us.

Regards,

Michael

[Former Member · Accepted solution]

Absolutely nailed it! and within 30min of posting!

Thanks Michael, that worked a charm.

[hans_segers · Accepted solution]

I had the same issue ("Unable to initialize service. LogID" in the APS running the Analysis Application Service) after having installed an SDK Extension on the Platform.

Before the APS was running fine.

I could fix it as well by following SAP KB 1942899

Thanks

Hans