PI 7.11 sp6 system copy Exchange Profile error code: 399

[Former Member]

Experts,

We have a PI 7.1 (EHP1, sp6) PI system based on AIX 6.1 OS and Oracle 11g.

I recently did the standard PI system copy from a prod source (PIP) to a training target (PIT).

I used the most recenty PI system copy guide that is specific for PI 7.1 EHP1

I did not run into any major problems doing the steps of the copy itself.

I did the usual "post" steps, documented in the guide that really are done on any NW system.

Then I got into the specific "PI" post steps and that's where I now have a problem.

I followed all the steps, fixing my RFCs, JCos, Destinations, cleaning up SLD, SLDAPICUST, creating new business systems...etc.

My big problem is with the exchange profile. Yes, it's easy to change all the SIDs and hostnames using the search tool for all the parameters in the exchange profile, but the one I COULD NOT CHANGE was the "ABAP Connection". In there right after the copy was the hostname of the prod system, the client, and the user PILDUSER. I attempted to put the hostname of my target (PIT) system, but I would get the error:

com.sap.rprof.dbprofiles.DBException: RFC call returned an error code: 399

I'm certain the user is NOT locked and the password is correct for PILDUSER. It'll give me a different error if I put the wrong password in, so I know it's hitting my system.

Worse yet, If I left the hostname in there that was set to "prod", then when I changed all the other values in the "parameters" section of the XI profile, then it actually changed my PROD system!!

If I keep the ABAP connection to PIT, then the entire exchange profile disappears for PIT.

I see these errors in the default trace and application log:

Caused by: com.sap.lcr.api.cimclient.LcrException: CIM_ERR_NOT_FOUND:

No such instance: SAP_J2EEEngineCluster.CreationClassName="SAP_J2EEEngineCluster",

Name="PIT.SystemHome.<traininghostname>"

Caused by: com.sap.lcr.api.cimclient.LcrException: CIM_ERR_NOT_FOUND: No such instance: SAP_J2EEEngineCluster.CreationClassName="SAP_J2EEEngineCluster",Name="PIT.SystemHome.<traininghostname>"

at com.sap.lcr.api.cimclient.SimpleResponseAnalyser.raiseExceptionOnError(SimpleResponseAnalyser.java:120)

#2.#2011 11 03 13:49:47:008#0-500#Error#com.sap.aii.af.service.sld.SLDRegistrationJob#

#BC-XI-CON-AFW#com.sap.aii.af.lib#7E3832DEA80F002B00000000008700C6#4804850000001902##com.sap.aii.af.service.sld.SLDRegistrationJob.SLDRegistrationJob.invoke()#J2EE_GUEST#0##0AFD01D4064C11E1CB5E7E3832DEA80F#0afd01d4064c11e1cb5e7e3832dea80f#0afd01d4064c11e1cb5e7e3832dea80f#0#Application [24]#Plain##

SLD Registration Job: No access to SLD. Waiting for next retry. Error: com.sap.aii.af.lib.sld.SLDException: Failed to initialize ExchangeProfile properties. Reason: Unable to read configuration data (ExchangeProfile/aii.properties)#

#2.#2011 11 03 14:51:18:096#0-500#Error#com.sap.esi.esp.service.server.ESPServiceInterfaceAbstract#

#BC-ESI-WS-JAV#tc_esiesp_{srv#7E3832DEA80F001100000000009A004C#4804850000001385##com.sap.esi.esp.service.server.ESPServiceInterfaceAbstract####109F6812065511E1BF9C7E3832DEA80F#109f6812065511e1bf9c7e3832dea80f#109f6812065511e1bf9c7e3832dea80f#0#Service Runner [tc}esi_espsrv]#Plain##

+There is problem reading the hostname from the ClusterManager. This could lead to improper wsdl links.#

SLDCHECK shows this:

Function call returned exception code 3

Access to the XI Profile is currently disrupted.

I can't be the first person to run into this.

SO strange that I can actually plug in either my dev/QA or PROD hostname in the "ABAP connection" box and it WILL ACCEPT IT...but then, it registered my training system as a "non central adapter engine". I don't want that.

Any ideas?

Another issue is that the SLD PI information from the PIT system is missing the "Integration Directory". It has the other 5 entries...Adapter Engine, Domain, Integration Repository, Integration Server, RWB.

Thanks for reading this,

NICK

[Former Member · Accepted solution]

the secure store was messed up. The fix:

Delete the table entry

applname="AIICOMMON"

file="exchange_profile.xml"

in the table aii_profiles via tx se16. Then

go to the ExchangeProfile UI and use the import functionality

to import the Exchange Profile file (extracted from the "source

system") again. Please have in mind, that you have to maintain all

passwords again and adapt the parameters.

In the future, I think the best solution is to use a "migration key" right away for the secure store target system as soon as the copy is done.

[Former Member · Accepted solution]

Hi Nick,

Thanks for sharing the solution.

Thanks,

Siva Kumar

[Former Member · Accepted solution]

Hi Nick, thanks.

It worked for me too.

Do you know what could have caused this?

At.,

Bernardo Braga

[Former Member · Accepted solution]

You need to run tcode Secstore before you start doing any of the post-steps on PI target.

Then, get a migration key.  if you do those steps, you will never see this problem.

--NICK

[Former Member · Accepted solution]

Hello Nick,

Thanks . Your solution , helped after 6 hours of investigation

I had to sacrifice my badmindon game for today.

I missed the obvious, did not have patience to read this thread which is one of the first hit in google for error

code: 399

Deleted secstore entries  and table entry "AIICOMMON" in se16

Thank you Nick:)

Kind Regards,

Jacob

[Former Member · Accepted solution]

Jacob,

Yeah...that error really sucks the first time.  but now you're like me, you'll never forget!

Take care,

nick

[Former Member · Accepted solution]

Hello Jacob,

Thanks for the solution.

I have same situation now, XI system copy on NW 7.3

Any help to follow up with steps for the procedure to export and import of the exchange profile from  Source to Target/

Thanks in advance.

Regards,

Medha D

[Former Member]

Hi Nick,

Thanks a lot

.

It works for me too ( NW 7.31 system copy).

Great.

Eddie Jr

[steven_pelser]

And for me Thanks Very much really helped

[Former Member]

HI all,

Can you  please suggest for PI 7.31 Java stack, can we just do a DB backup restore and run the post steps as per the system copy guide  for system refresh? or we need to do Java export and import also?

We are in process of building new PI system  and need suggestion on this, can we install a newPI systems and copy the DB from  PROD  to have all usage types and components copy thru DB refresh.

Please suggest.

Thanks,

Subhash.G

[Former Member]

Hey Subhash,

You're going to have a very bad day if you ever try to Sys Copy a Java stack or dual-stack using only the DB restore.  The java stuff mostly lives at the OS level and won't come across to the target system if all you do is the DB side.  I highly suggest you go through sapinst to do the copy, but use the "DB specific method" once prompted.

NICK

[Former Member]

Thanks for your reply nick.

As per the doc from SAP it was mentioned if you do DB  specific method which is Db backup/restore no need of Java export from source system.

Any comments on this?

Thanks,

Subhash.G

[Former Member]

Yeah, totally agree!  I guess I thought that you originally meant a pure DB restore without using any SAP tools.  But yeah, you are correct and that's the method I would use and have used.  My only difference is that I've only done this with dual stack PI.  I have yet to split mine up even though we are at 7.40 now.

good luck

NICK

[Former Member]

Thanks Nick.

The below are the steps we are planning to follow.

From SWM ->  731 ->syscopy ->target system

1) Install SCS

2) Install DB instance using  Homogenous backup/restore method [ DB backup available]

3)Install PAS/ASS.

As per SAP this process will get all Usage types and any additional  3rd party components installed in the Java stack.

Please comment.

Thanks,

Subhash.G

[Former Member]

Thanks for the suggestions, we completed the NW 7.2 Java systems homogenous copy with backup/restore method successfully.

[Former Member]

Hello Nick ,

Any inputs.

I have same situation now, XI system copy on NW 7.3

Any help to follow up with steps for the procedure to export and import of the exchange profile from  Source to Target.

Thanks in advance.

Regards,

Medha D

[Former Member]

Medha,

Hey!  look, this issue has already been resolved in this particular thread.  Please....carefully....read everything I wrote!

I'll sum it up for you....

if you do a sys copy for NW PI, make EXTRA SURE to run tcode secstore, and get a migration key.  that ought to be the very first thing you do once you get the lic key there and you can log in to the system.

after that, you can follow the documented sys copy post steps.  You can find those by searching the service.sap.com website. 

that's the best I can do for you.  that resolved my issue as I documented in this thread.  if you have a different issue, then open a new thread.  If what I wrote isn't clear enough, I suggest you get with a more senior basis person on your team to help you resolve your issue.  Also, you can always open an OSS message with SAP support.

Please don't "wait" on me, or expect any inputs to help you with your issue.  the point of this thread was an issue I brought up...and I resolved it and I was kind enough to put the resolution here in the thread. 

NICK

[Former Member]

Hi Nick,

Did you get chance to follow note 999962? Please go through PI Readiness check document. Hope it will solve your problem.

Thanks,

Siva Kumar

[Former Member]

Siva,

This is a good note that I was already aware of. I have confirmed all that is correct as far as the username and passwords of these users is concerned.

Yes, I have also read the PI readiness check. But if your Exchange profile is in the state that mine is in, there isn't much you can do for the 'readiness" check.

But thank you for the reply,

NICK

[Former Member]

Nick,

Seeing the SLD error in default trace, Firstly logon to NWA and check the destinations. Check SLD data supplier detination and SLD and Jco destinations.

Regarding the domain, You have change these values in Exchange profiler. After changing the hostnames and domain name here restart j2ee engine. This will re-register components in SLD with new domain.

Regards,

Vamshi.

[Former Member]

Vamshi,

I wish it was that simple of a solution. I checked all that and it is correct. I have restarted many times....

To me, the real problem is the Exchange Profile and why I cannot change the "abap connection" to match the hostname of the PI target system?

I can put any other hostname in there and it gets accepted. I can put my prod/qa or dev hostname in there and it will work...but NOT the PI training hostname which is the target PI system.

--NICK

[Former Member]

Here is the error I get when I try to change the "abap connection" to the correct hostname:

RFC call returned an error code: 399

Stack Trace class com.sap.rprof.dbprofiles.DBException:<br><pre>at com.sap.rprof.dbprofiles.DBProfiles.checkReturn(DBProfiles.java:184) at com.sap.rprof.dbprofiles.DBProfiles.getProfile(DBProfiles.java:105) at com.sap.rprof.dbprofiles.RemoteProfile.readRemoteProfileFromMedia(RemoteProfile.java:1378) at com.sap.rprof.dbprofiles.RemoteProfile.getRemoteProfileFromFactory(RemoteProfile.java:204) at com.sap.rprof.dbprofiles.RemoteProfile.getRemoteProfile(RemoteProfile.java:154) at com.sap.rprof.dbprofiles.ExchangeProfile.getExchangeProfile(ExchangeProfile.java:46) at com.sap.rprof.remoteProfile.webui.ProfileWebTree.<init>(ProfileWebTree.java:24) at com.sap.rprof.remoteProfile.webui.Edit.getWebTree(Edit.java:322) at JEE_jsp_treeexprof_4804850_1319481176000_1319565151782._jspService(JEE_jsp_treeexprof_4804850_1319481176000_1319565151782.java:59) at com.sap.engine.services.servlets_jsp.lib.jspruntime.JspBase.service(JspBase.java:102) at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:140) at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:436) at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:240) at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:140) at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:37) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:493) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:298) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:399) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:388) at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:48) at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78) at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:84) at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78) at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:244) at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78) at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:78) at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9) at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78) at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60) at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9) at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78) at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27) at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12) at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78) at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29) at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12) at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78) at com.sap.engine.services.httpserver.filters.MemoryStatisticFilter.process(MemoryStatisticFilter.java:43) at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12) at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78) at com.sap.engine.services.httpserver.filters.DSRHttpFilter.process(DSRHttpFilter.java:42) at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12) at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78) at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:428) at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:247) at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:45) at com.sap.engine.core.thread.execution.Executable.run(Executable.java:122) at com.sap.engine.core.thread.execution.Executable.run(Executable.java:101) at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:327) </pre>