Skip to Content
0
May 26, 2010 at 01:40 PM

BEx Web still using Prod msg server after systemcopy

28 Views

We are still working out all the aspects of doing a Java+ABAP systemcopy for a BI 7.0 system.

Following the systemcopy, if we launch a query from BI, the portal page comes up for logon. We enter our credentials but it fails to logon with the following error. (this is w/out SSO, which is still in the works)

Connect to message server host failed

Connect_PM TYPE=B MSHOST=prdserver.gp.com GROUP=PUBLIC R3NAME=PRD MSSERV=sapmsPRD PCS=1

ERROR service 'sapmsPRD' unknown

The URL that launches for the query uses the QA server and QA port correctly to display the logon of the QA Portal. But after I logon, it fails because it's trying to use the production MSHOST and the production MSSERV. This is obviously cleanup that needs to be done after the systemcopy but I can't find where that is.

The systemcopy was a standard sapinst Export of PRD's Java, followed by the sapinst reinstall of QA using that Export.