on 09-01-2014 7:18 PM
Hi All,
We recently completed Oracle to DB2 migration on DEV EP instance.
Post migration,we cannot login with "j2ee_admin" user,thus we cannot apply "Java login" dependent support patches.
Currently S/W components are on different versions and Application team is not able to deploy new application ,error faced is "SDM Error "Connection between SDM client and server is broken"
We have carried out same activity on Sandbox where patch application went smooth,but here even after updating the j2ee_admin username and password in secure-store using config-tool it doesn't help.
Login to visual admin is also not possible with any user.
I am able to access EP front-end with "administrator" user but while applying support upgrade patches like SAPJTECHS it cannot login and connect using j2ee_admin user.
Please advice..
In default trace below error is being faced:
#1.5^H#001A64760122005E000000790000532F0005020054EEF817#1409575331755#com.sap.tc.cbs.server.rt.bs.BSAdmin##com.sap.tc.cbs.server.rt.bs.BSAdmin####n/a##dabf750a31d311e4845d0000001cbae2#Thread[CBS BSA Orc,10,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error##Java###{0}
{1}
[EXCEPTION]
{2}#3#Unable to instantiate a Build Space administrator!
Build Space "EPD_MYGPTR_C" [bsID: 6, version: 1] [in-queue: on, out-queue: "on", processing: on]#Server error [503 Service Unavailable]#com.sap.tc.cbs.api.CommunicationException: Server error [503 Service Unavailable]
at com.sap.tc.cbs.comm.Repository.execute(Repository.java:64)
at com.sap.tc.cbs.api.impl.BSFacade.getOwnerBuildspace(BSFacade.java:510)
at com.sap.tc.cbs.server.rt.bs._BuildSpaceValidator.checkWorkspace(_BuildSpaceValidator.java:87)
at com.sap.tc.cbs.server.rt.bs._BuildSpaceValidator.validateWSs(_BuildSpaceValidator.java:57)
at com.sap.tc.cbs.server.rt.bs.BSAdmin.validate(BSAdmin.java:183)
at com.sap.tc.cbs.server.rt.bs.BSAdmin.updateState(BSAdmin.java:251)
at com.sap.tc.cbs.server.rt.bs.BSAdminOrc.determineChanges(BSAdminOrc.java:437)
at com.sap.tc.cbs.server.rt.bs.BSAdminOrc.validateBuildSpaceData(BSAdminOrc.java:217)
at com.sap.tc.cbs.server.rt.bs.BSAdminOrc.act(BSAdminOrc.java:339)
at com.sap.tc.cbs.server.rt.impl.CourteousTimer.run(CourteousTimer.java:139)
at java.lang.Thread.run(Thread.java:708)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Pati
could you refer the SAP Note Error msg "com.sap.tc.cbs.api.CommunicationException: Server error"
1175019 - Unable to instantiate a Build Space administrator!
1239613 - CommunicationException: Unexpected response status [200 OK]
Regards
Ram
Hi Vinnet,
1st complete the post configuration of your migration.
Adjust RFC configuration of java connector.
If you are using NWDI in you landscape, check on that
Check SLD connection.
The above error is related to Design Time Repository and Component Build Service - i.e you NWDI and SLD portal - if you can work on this refer:
1175019 - Unable to instantiate a Build Space administrator!
Hi Vinnet,
This is your Portal system. Why are you using J2EE_Admin ?
You have just migrated your system - you need to adjust you UME setting.
Goto configtool and correct the UME setting to point to ABAP source, then only you can logon with J2ee_admin.
Otherwise, only Administrator user will work.
Also, don't have to update J2EE_admin password in secure store. Update password of administrator.
Check with : 1144877 - Connection between SDM client and server is broken
Configuration of User Management in the Portal - Portal - SAP Library
Regards
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Pati
1. Check the user id J2EE_admin user id locked?
2. Could you check this SAP Notes for Visual admin logon issue
957355 - Cannot log on to the Visual Administrator or deploy via SDM
BR
SS
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
If the UME is configured to an existing ABAP stack then you will be using J2EE_ADMIN user. If this portal is configured to use it's own database as the UME then you should use the Administrator user.
Regards
RB
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
84 | |
10 | |
10 | |
10 | |
7 | |
6 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.