Could not start the app due to a configuration problem

Question

Hi Gurus,
I have an issue to be resolved asap, need your assistance.
I have implemented SAP Fiori apps (Approve Purchase Order, Approve Purchase Contract, My Leave Request and Approve Leave Request)
We have only one Gateway system and 3 back end ECC systems.
Gateway Client 220 is integrated with ECC Dev and performed all the configurations and tested successfully.
We have created a new client 320 with a copy of client 220, Integrated 320 client to ECC quality system and performed necessary configurations and while testing Approve Purchase order and Approve Purchase Contract tiles are loading the count from ECC Quality system but when I click on the tile it throws an error "could not start the app due to a configuration problem" and when I click the error ot is being redirected to Client 220.
From the inspect element I found below error
2015-04-13 12:22:13 INTEROP service's ResolveLink operation returned 2 targets for hash '#PurchaseOrder-approve', first one is used. - used target: {"id":"PurchaseOrder-approve~652","shellType":"FLP","postParameters":"","text":"Approve Purchase Orders","applicationData":"SAPUI5.Component=ui.s2p.mm.purchorder.approve","applicationAlias":"ApprovePurchaseOrders","applicationType":"URL","url":"/sap/bc/ui5_ui5/sap/mm_po_apv"}
ignored target: {"id":"PurchaseOrder-approve~65k","shellType":"FLP","postParameters":"","text":"Approve Purchase Orders","applicationData":"SAPUI5.Component=ui.s2p.mm.purchorder.approve","applicationAlias":"ApprovePurchaseOrders","applicationType":"URL","url":"/sap/bc/ui5_ui5/sap/mm_po_apv"} sap.ushell_abap.adapters.abap.NavTargetResolutionAdapter
I did not found any duplicate # key entries in table USOBHASH.
Any response is highly appreciated, thanks in advance
Regards,
Srujan

Answer 1

Hi Michael,
Thanks for that, I have raised an OSS message to SAP, to seek their assistance on the solution I followed to fix the issue. I have reverted back the changes and reproduced the issue for SAP guys to investigate further, at last they concluded me there is an external alias defined for /sap/bc/ui5_ui5/sap in transaction SICF in GP1/320, which contains a hard-coded client 220.
This is responsible for the fact that the services are redirected/opened in client 220
After removing the client hard-coded in system alaises under /sap/bc/ui5_ui5/ in transaction SICF, I have reverted back the change from "Alternative Logon Procedure" to "standard" in logon procedure of each service and tested, now the issue got resolved.
This could help someone to resolve the similar issue.
Thanks everyone
Regards,
Srujan