When I call transaction sxmb_ifr on my PI system I expect http://<host>:<port>/dir to open, but instead http://<host>:<port>/sap/public/myssocntl?sap-client=001 opens and says "Internet Explorer cannot display the webpage".
Opening http://<host>:<port>/dir manually works fine.
The Exchange Profile (http://<host>:<port>/webdynpro/dispatcher/sap.com/com.sap.xi.exprofui/XIProfileApp) seems to be okay, the fully qualified domain name is maintained for all relevant parameters:
com.sap.aii.ib.server.connect.webas.r3.ashost
com.sap.aii.rwb.server.centralmonitoring.name
com.sap.aii.rwb.server.centralmonitoring.r3.ashost
com.sap.aii.rwb.server.centralmonitoring.r3.mshost
com.sap.aii.connect.repository.name
com.sap.aii.connect.directory.name
com.sap.aii.connect.landscape.name
com.sap.aii.connect.rwb.name
com.sap.aii.connect.cr.name
com.sap.aii.connect.rwb.r3.mshost
com.sap.aii.connect.integrationserver.name
com.sap.aii.connect.repository.mshost
com.sap.aii.connect.integrationserver.sld.name
com.sap.aii.connect.integrationserver.r3.mshost
com.sap.aii.connect.directory.mshost
The SAP instances have been restarted from the SAP console after updating the Exchange Profile. (Is there an easier way to make the system re-read the Exchange Profile?)
Transaction sicf shows that /sap/public/myssocntl is active.
SLDCHECK runs fine.
Another suggestion I found was creating destination SAP_PROXY_ESR, however it appears this should only be done in the connected business systems, but not in the PI system. In sproxy on the PI system the ESR contents are loaded fine (no error message that only offline data is available), so this seems to confirm this information.
What else could be causing this? I found a lot of threads on the topic, but in the end they all seemed to amount to one of the above problems, mostly the exchange profile (and in business systems destination SAP_PROXY_ESR missing).