Changing Client in BI installation

[Former Member]

Hello all,

I installed an instance of Netweaver 7.0 for BI with ABAP and Java Stack. Everything worked fine with client 001. They wanted the the client 300 for production so I followed the instructions I could find. I changed the client to 300. Now Java will not connect to ABAP. It keeps locking up the user SAPJSF with failed login attempts. I put a case in with SAP, they told me to change the client and password in the Java configtool. The client was already correct, I made sure the password was as well. Still no joy. It will not log in. From the ABAP side I can log in with the user ID and password. Can someone help me please? It seems to me it is not getting the password from where ever the configtool is storing it?

[Former Member · Accepted solution]

HI,

1. In the left frame choose Server → Services → Configuration Adapter

2. In the tab Display Configuration (right frame) choose Switch between view and edit mode to activate the edit mode.

3. Choose cluster_data → server → cfg → services → Propertysheet com.sap.security.core.ume.service

4. Choose Show the detail of the selected node

5. The parameter ume.r3.connection.master.client must be set to your SAP Exchange Infrastructure client. Adapt the value if necessary

REGARDS

AJAI

[Former Member · Accepted solution]

I have alread done this per SAP, still no luck.

> HI,

>

> 1. In the left frame choose Server → Services

> → Configuration Adapter

> 2. In the tab Display Configuration (right frame)

> choose Switch between view and edit mode to activate

> the edit mode.

> 3. Choose cluster_data → server → cfg

> → services → Propertysheet

> com.sap.security.core.ume.service

> 4. Choose Show the detail of the selected node

> 5. The parameter ume.r3.connection.master.client must

> be set to your SAP Exchange Infrastructure client.

> Adapt the value if necessary

>

> REGARDS

> AJAI

[Former Member · Accepted solution]

Hi Mary,

Did you stop and start the system after making the change?

Best Regards,

Matt

[Former Member · Accepted solution]

Yes, many times.

[Former Member · Accepted solution]

Hi Mary,

I have taken a look at your customer message. It looks like you have changed the password correctly and now a new error has been found. The message has been sent to other processors with the new error. I suggest you continue with the message processing until the error is resolved.

Best Regards,

Matt

[Former Member · Accepted solution]

Here is the current dev trace for server0 process that fails to start. My thought is the problem is before the failed login attempts.

"----

---

trc file: "E:\usr\sap\BID\DVEBMGS00\work\dev_server0", trc level: 1, release: "700"

-

---

node name : ID1439550

pid : 4860

system name : BID

system nr. : 00

started at : Mon Oct 29 14:47:11 2007

arguments :

arg[00] : E:\usr\sap\BID\DVEBMGS00\exe\jlaunch.exe

arg[01] : pf=E:\usr\sap\BID\SYS\profile\BID_DVEBMGS00_s010sap35

arg[02] : -DSAPINFO=BID_00_server

arg[03] : pf=E:\usr\sap\BID\SYS\profile\BID_DVEBMGS00_s010sap35

arg[04] : -DSAPSTART=1

arg[05] : -DCONNECT_PORT=3140

arg[06] : -DSAPSYSTEM=00

arg[07] : -DSAPSYSTEMNAME=BID

arg[08] : -DSAPMYNAME=s010sap35_BID_00

arg[09] : -DSAPPROFILE=E:\usr\sap\BID\SYS\profile\BID_DVEBMGS00_s010sap35

arg[10] : -DFRFC_FALLBACK=ON

arg[11] : -DFRFC_FALLBACK_HOST=localhost

[Thr 3164] Mon Oct 29 14:47:11 2007

[Thr 3164] *** WARNING => INFO: Unknown property [instance.box.number=BIDDVEBMGS00s010sap35] [jstartxx.c 841]

[Thr 3164] *** WARNING => INFO: Unknown property [instance.en.host=s010sap35] [jstartxx.c 841]

[Thr 3164] *** WARNING => INFO: Unknown property [instance.en.port=3201] [jstartxx.c 841]

[Thr 3164] *** WARNING => INFO: Unknown property [instance.system.id=0] [jstartxx.c 841]

**********************************************************************

JStartupReadInstanceProperties: read instance properties [E:\usr\sap\BID\DVEBMGS00\j2ee\cluster\instance.properties]

-> ms host : s010sap35

-> ms port : 3901

-> OS libs : E:\usr\sap\BID\DVEBMGS00\j2ee\os_libs

-> Admin URL :

-> run mode : normal

-> run action : NONE

-> enabled : yes

**********************************************************************

**********************************************************************

Used property files

-> files [00] : E:\usr\sap\BID\DVEBMGS00\j2ee\cluster\instance.properties

**********************************************************************

**********************************************************************

Instance properties

-> ms host : s010sap35

-> ms port : 3901

-> os libs : E:\usr\sap\BID\DVEBMGS00\j2ee\os_libs

-> admin URL :

-> run mode : normal

-> run action : NONE

-> enabled : yes

**********************************************************************

**********************************************************************

Bootstrap nodes

-> [00] bootstrap : E:\usr\sap\BID\DVEBMGS00\j2ee\cluster\instance.properties

-> [01] bootstrap_ID1439500 : E:\usr\sap\BID\DVEBMGS00\j2ee\cluster\instance.properties

-> [02] bootstrap_ID1439550 : E:\usr\sap\BID\DVEBMGS00\j2ee\cluster\instance.properties

**********************************************************************

**********************************************************************

Worker nodes

-> [00] ID1439500 : E:\usr\sap\BID\DVEBMGS00\j2ee\cluster\instance.properties

-> [01] ID1439550 : E:\usr\sap\BID\DVEBMGS00\j2ee\cluster\instance.properties

**********************************************************************

[Thr 3164] JLaunchRequestQueueInit: create named pipe for ipc

[Thr 3164] JLaunchRequestQueueInit: create pipe listener thread

[Thr 2724] JLaunchRequestFunc: Thread 2724 started as listener thread for np messages.

[Thr 720] WaitSyncSemThread: Thread 720 started as semaphore monitor thread.

[Thr 3164] NiInit3: NI already initialized; param 'maxHandles' ignored (1;202)

[Thr 3164] CPIC (version=700.2006.09.13)

[Thr 3164] [Node: server0] java home is set by profile parameter

Java Home: E:\JavaJDK

[Thr 3164] JStartupICheckFrameworkPackage: can't find framework package E:\usr\sap\BID\DVEBMGS00\exe\jvmx.jar

**********************************************************************

JStartupIReadSection: read node properties [ID1439550]

-> node name : server0

-> node type : server

-> node execute : yes

-> jlaunch parameters :

-> java path : E:\JavaJDK

-> java parameters : -Djco.jarm=1 -XX:MaxPermSize=512M -XX:PermSize=512M -XX:NewSize=320M -XX:MaxNewSize=320M -XX:DisableExplicitGC -verbose:gc -Xloggc:GC.log -XX:PrintGCDetails -XX:+PrintGCTimeStamps -Djava.awt.headless=true -Dsun.io.useCanonCaches=false -XX:SoftRefLRUPolicyMSPerMB=1 -XX:SurvivorRatio=2 -XX:TargetSurvivorRatio=90 -Djava.security.policy=./java.policy -Djava.security.egd=file:/dev/urandom -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy

-> java vm version : 1.4.2_15-b02

-> java vm vendor : Java HotSpot(TM) 64-Bit Server VM (Sun Microsystems Inc.)

-> java vm type : server

-> java vm cpu : amd64

-> heap size : 2048M

-> init heap size : 2048M

-> root path : E:\usr\sap\BID\DVEBMGS00\j2ee\cluster\server0

-> class path : .\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.

-> OS libs path : E:\usr\sap\BID\DVEBMGS00\j2ee\os_libs

-> main class : com.sap.engine.boot.Start

-> framework class : com.sap.bc.proj.jstartup.JStartupFramework

-> registr. class : com.sap.bc.proj.jstartup.JStartupNatives

-> framework path : E:\usr\sap\BID\DVEBMGS00\exe\jstartup.jar;E:\usr\sap\BID\DVEBMGS00\exe\jvmx.jar

-> shutdown class : com.sap.engine.boot.Start

-> parameters : -Xss2m -Xmx2048m -verbose:gc -XX:UseParNewGC -XX:UseTLAB -XX:HandlePromotionFailure -XX:PrintClassHistogram -XX:SoftRefLRUPolicyMSPerMB=1 -XX:+PrintTenuringDistribution

-> debuggable : no

-> debug mode : no

-> debug port : 50021

-> shutdown timeout : 120000

**********************************************************************

[Thr 3164] JLaunchISetDebugMode: set debug mode [no]

[Thr 4948] JLaunchIStartFunc: Thread 4948 started as Java VM thread.

[Thr 4948] [JHVM_PrepareVMOptions] use java parameters set by profile parameter

Java Parameters: -Xss2m

**********************************************************************

JHVM_LoadJavaVM: VM Arguments of node [server0]

-> stack : 1048576 Bytes

-> arg[ 0]: exit

-> arg[ 1]: abort

-> arg[ 2]: vfprintf

-> arg[ 3]: -Djco.jarm=1

-> arg[ 4]: -XX:MaxPermSize=512M

-> arg[ 5]: -XX:PermSize=512M

-> arg[ 6]: -XX:NewSize=320M

-> arg[ 7]: -XX:MaxNewSize=320M

-> arg[ 8]: -XX:+DisableExplicitGC

-> arg[ 9]: -verbose:gc

-> arg[ 10]: -Xloggc:GC.log

-> arg[ 11]: -XX:+PrintGCDetails

-> arg[ 12]: -XX:+PrintGCTimeStamps

-> arg[ 13]: -Djava.awt.headless=true

-> arg[ 14]: -Dsun.io.useCanonCaches=false

-> arg[ 15]: -XX:SoftRefLRUPolicyMSPerMB=1

-> arg[ 16]: -XX:SurvivorRatio=2

-> arg[ 17]: -XX:TargetSurvivorRatio=90

-> arg[ 18]: -Djava.security.policy=./java.policy

-> arg[ 19]: -Djava.security.egd=file:/dev/urandom

-> arg[ 20]: -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy

-> arg[ 21]: -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy

-> arg[ 22]: -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy

-> arg[ 23]: -Dsys.global.dir=E:\usr\sap\BID\SYS\global

-> arg[ 24]: -Dapplication.home=E:\usr\sap\BID\DVEBMGS00\exe

-> arg[ 25]: -Djava.class.path=E:\usr\sap\BID\DVEBMGS00\exe\jstartup.jar;E:\usr\sap\BID\DVEBMGS00\exe\jvmx.jar;.\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.

-> arg[ 26]: -Djava.library.path=E:\JavaJDK\jre\bin\server;E:\JavaJDK\jre\bin;E:\JavaJDK\bin;E:\usr\sap\BID\DVEBMGS00\j2ee\os_libs;E:\oracle\BID\102\bin;E:\oracle\BID\102\Opatch;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files (x86)\Dell\SysMgt\RAC5;C:\Program Files (x86)\Dell\SysMgt\oma\bin;C:\Program Files (x86)\Dell\SysMgt\oma\oldiags\bin;E:\usr\sap\BID\SYS\exe\uc\NTAMD64

-> arg[ 27]: -Dmemory.manager=2048M

-> arg[ 28]: -Xmx2048M

-> arg[ 29]: -Xms2048M

-> arg[ 30]: -DLoadBalanceRestricted=no

-> arg[ 31]: -Djstartup.mode=JCONTROL

-> arg[ 32]: -Djstartup.ownProcessId=4860

-> arg[ 33]: -Djstartup.ownHardwareId=W1811314774

-> arg[ 34]: -Djstartup.whoami=server

-> arg[ 35]: -Djstartup.debuggable=no

-> arg[ 36]: -Xss2m

-> arg[ 37]: -DSAPINFO=BID_00_server

-> arg[ 38]: -DSAPSTART=1

-> arg[ 39]: -DCONNECT_PORT=3140

-> arg[ 40]: -DSAPSYSTEM=00

-> arg[ 41]: -DSAPSYSTEMNAME=BID

-> arg[ 42]: -DSAPMYNAME=s010sap35_BID_00

-> arg[ 43]: -DSAPPROFILE=E:\usr\sap\BID\SYS\profile\BID_DVEBMGS00_s010sap35

-> arg[ 44]: -DFRFC_FALLBACK=ON

-> arg[ 45]: -DFRFC_FALLBACK_HOST=localhost

-> arg[ 46]: -DSAPSTARTUP=1

-> arg[ 47]: -DSAPSYSTEM=00

-> arg[ 48]: -DSAPSYSTEMNAME=BID

-> arg[ 49]: -DSAPMYNAME=s010sap35_BID_00

-> arg[ 50]: -DSAPDBHOST=s010sap35

-> arg[ 51]: -Dj2ee.dbhost=s010sap35

**********************************************************************

CompilerOracle: exclude com/sapportals/portal/pb/layout/taglib/ContainerTag addIviewResources

CompilerOracle: exclude com/sap/engine/services/keystore/impl/security/CodeBasedSecurityConnector getApplicationDomain

CompilerOracle: exclude com/sap/engine/services/rmi_p4/P4StubSkeletonGenerator generateStub

CompilerOracle: exclude com/sapportals/portal/prt/util/StringUtils escapeToJS

CompilerOracle: exclude com/sapportals/portal/prt/core/broker/PortalServiceItem startServices

CompilerOracle: exclude com/sap/engine/services/webservices/server/deploy/WSConfigurationHandler downloadFile

CompilerOracle: exclude com/sapportals/portal/prt/jndisupport/util/AbstractHierarchicalContext lookup

CompilerOracle: exclude com/sapportals/portal/navigation/cache/CacheNavigationNode getAttributeValue

CompilerOracle: exclude com/sapportals/portal/navigation/TopLevelNavigationiView PrintNode

CompilerOracle: exclude com/sapportals/wcm/service/ice/wcm/ICEPropertiesCoder encode

CompilerOracle: exclude com/sap/lcr/pers/delta/importing/ObjectLoader loadObjects

CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/InstanceBuilder readElement

CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/InstanceBuilder readSequence

CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/TypeMappingImpl initializeRelations

CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/GeneratedComplexType _loadInto

[Thr 4948] JHVM_LoadJavaVM: Java VM created OK.

**********************************************************************

JHVM_BuildArgumentList: main method arguments of node [server0]

-> arg[ 0]: -Xss2m

-> arg[ 1]: -Xmx2048m

-> arg[ 2]: -verbose:gc

-> arg[ 3]: -XX:+UseParNewGC

-> arg[ 4]: -XX:+UseTLAB

-> arg[ 5]: -XX:+HandlePromotionFailure

-> arg[ 6]: -XX:+PrintClassHistogram

-> arg[ 7]: -XX:SoftRefLRUPolicyMSPerMB=1

-> arg[ 8]: -XX:+PrintTenuringDistribution

**********************************************************************

[Thr 1072] Mon Oct 29 14:47:12 2007

[Thr 1072] JHVM_RegisterNatives: registering methods in com.sap.bc.krn.perf.PerfTimes

[Thr 1072] JHVM_RegisterNatives: registering methods in com.sap.bc.proj.jstartup.JStartupFramework

[Thr 1072] JLaunchISetClusterId: set cluster id 1439550

[Thr 1072] JLaunchISetState: change state from [Initial (0)] to [Waiting for start (1)]

[Thr 1072] JLaunchISetState: change state from [Waiting for start (1)] to [Starting (2)]

[Thr 4072] Mon Oct 29 14:47:22 2007

[Thr 4072] JHVM_RegisterNatives: registering methods in com.sap.mw.rfc.driver.CpicDriver

[Thr 4072] JHVM_RegisterNatives: registering methods in com.sap.i18n.cp.ConverterJNI

[Thr 2652] Mon Oct 29 14:47:23 2007

[Thr 2652] JLaunchIExitJava: exit hook is called (rc = -11113)

[Thr 2652] **********************************************************************

• ERROR => The Java VM terminated with a non-zero exit code.

• Please see SAP Note 943602 , section 'J2EE Engine exit codes'

• for additional information and trouble shooting.

**********************************************************************

[Thr 2652] JLaunchCloseProgram: good bye (exitcode = -11113)"

[Former Member · Accepted solution]

The solution turned out to be that I needed to change the global parameters in the java configtool and create the proper users in the new ABAP client. The locking of the user was just a symtom of the data being incorrect where ever it was coming from.

[Former Member]

hi,

did u copied all users from 001 client to 300?.client is copied from 001 or 000?.

client 300copy from 001 it will work properly

regards

ajai

[Former Member]

hi,

in j2ee visula admin u can chenge the property of this

ume.r3.connection.master.client to 300.

then u can try.it will work.

regards

ajai

[Former Member]

> hi,

>

> in j2ee visula admin u can chenge the property of

> this

> ume.r3.connection.master.client to 300.

>

> then u can try.it will work.

> regards

> ajai

I have already done this step per SAP. Still no luck.