cancel
Showing results for 
Search instead for 
Did you mean: 

LANDSCAPE FETCH jobs not running

Former Member
0 Kudos

Hello SAPGurus,

I tried to run LANDSCAPE FETCH job but it throws error in  SOLMAN7.0 system. Following is the logs

The SLD server connection is inactive

Note:- It is to note that I have maintained J2EE_ADMIN user in SLDAPICUST but when I try to login to SLD portal J2EE_ADMIN is not active only SAP* is active.

Following is the output when I fire SLDCHECK tcode

Exchange Infrastructure: Test LCR Connection

Properties of RFC destination SAPSLDAPI
  RFC host:
%%RFCSERVER%%
  program id:      SAPSLDAPI_QCM
  gateway host:
qerossm
  gateway service: sapgw00

Testing the RFC connection to the SLD java client...
RFC ping was successful

Found obsolete SLD server address!
=> Only use transaction SLDAPICUST to maintain the SLD access data.
=> Delete all entries from the obsolete transaction LCRSERVADDR.

Summary: Connection to SLD does not work
=> Check SLD function and configurations

Now checking access to the XI Profile

Properties of RFC destination LCRSAPRFC
  RFC host:
%%RFCSERVER%%
  program id:      LCRSAPRFC_QCM
  gateway host:
qerossm
  gateway service: sapgw00

Testing the RFC connection to the SLD java client...
RFC ping was successful

Calling function EXCHANGE_PROFILE_GET_PARAMETER
Retrieving data from the XI Profile...
Function call returned exception code     3
Access to the XI Profile is currently disrupted.

=> Check whether you can access the XI Profile using a web browser!

Please suggest.

Regards,

Abhishek Paritosh

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Kudos

HI,

  Do you mean that you are able to login to portal only using SAP* user...

If yes, it seems that emergency user is activated .. Only SAP* user will be able to login when emergency user is activated.

So you must deactivate it first. Follow the below points.

  1. Start the config tool for editing UME properties.
  2. Set the property ume.superadmin.activated to false.
  3. Restart the AS Java.

Once done, please try to check whether it resolves your issue.

Thanks and Regards,

Vimal

Former Member
0 Kudos

Maria, I already tried this but it doesnt work. SAP* is still active.

Regards,

Abhishek Paritosh

Former Member
0 Kudos

Till SAP* is active , no other user will be active...

Or you can try this way.

Please login to config tool and perform the below steps.

  1. Start the config tool for editing UME properties.
  2. Set the property ume.superadmin.activated to false.
  3. Save the changes in the config tool
  4. Stop the JAVA system
  5. Navigate to /usr/sap/SID/JC*/j2ee/cluster
  6. You can see a file instance.properties.vmprop .. Rename or move that file to other location.
  7. The file instance.properties.vmprop shouldnt be available there.
  8. Restart the AS Java.


Try this way and see whether SAP* is deactivated.

Thanks and Regards,

Vimal

Former Member
0 Kudos

Vimal, I tried to move the file instance.properties.vmprop and restarted the cluster but still no response

I still get the following while trying to login through J2EE_ADMIN

User SAP* is active. No other users can log on

Regards,

Abhishek Paritosh

Former Member
0 Kudos

Please try to make the changes as said above and try to restart the DB too.

It seems that changes are not in the DB.


Did you notice that new instance.properties_vmprop file has been created newly??

Former Member
0 Kudos

Vimal, I restarted the database and I see that the new instance.properties_vmprop file is created. When I tried to log in to the SLD portal using J2EE_ADMIN it says Authentication failed. Password locked. I unlocked the J2EE_ADMIN user from SAP and tried to log in again but again it fires the same. Also when I try to log in through SAP* it still allows me to log in in the SLD.

Regards,

Abhishek Paritosh

Former Member
0 Kudos

Vimal, every now and then I try to login to SLD through J2EE_ADMIN I guess it locks the user and when I try to unlock it and then try to login it does the same again. What may be the reason behind.

Regards,

Abhishek Paritosh

Former Member
0 Kudos

Hi ,

  As long as SAP* is active, even when you try to unlock the user, it will get locked automatically.

We need to find out a way to stop it .

Thanks and Regards,

Vimal

Former Member
0 Kudos

Hi,

Please refer the two below notes and see whether it helps.

Note 669848 - Unlocking the Administrator User on the J2EE Engine/AS Java

1659382 - After entering correct user ID and password the logon page is displayed without an error message


Thanks and Regards,

Vimal

Former Member
0 Kudos

Vimal, it is to note that I use to login to the Visual admnistrator using SAP* only.Is this correct.

Regards,

Abhishek Paritosh

Former Member
0 Kudos

Hello

Vimal,

I was able to deactivate SAP* user. I did it in Visual administrator but the same should be performed in Config tool also. I went into configtool and did the following

Disable "SAP*" 

1.Start the Config Tool C:\usr\sap\<SID>\<engine-instance>\j2ee\configtool\configtool.bat

Ex: D:\usr\sap\F02\JC00\j2ee\configtool --> configtool.bat

2.Goto cluster-data --> Global server configuration --> services --> com.sap.security.core.ume.service

3.Double-click on the property "ume.superadmin.activated = FALSE"

4.Save.

5. Restart the engine.

Note:- But the question is when I try to login through J2EE_ADMIN it says Authentication failed. Password locked. For this when I unlock it from ABAP and login again it throws the same. Any suggestions.

Regards,

Abhishek Paritosh

Former Member
0 Kudos

Hi,

Please go through the below two links and see whether you can any idea on your issue.

http://scn.sap.com/thread/3151047

http://scn.sap.com/thread/91267

Please check whether any RFC's is using J2ee_admin user

Thanks and Regards,

Vimal

Former Member
0 Kudos

Hello Vimal,

Thanks for your reply. I am trying to change the password for J2EE_ADMIN in configtool in ume.superadmin.password and also in admin/password/SID and jdbc/pool/SID/password in Securestore but it is not allowing me to change the password in admin/password/SID which in turn doesnt change in ume.superadmin.password. Please suggest because I am trying to put the same password which I have placed in SU01 for J2EE_ADMIN in ABAP.

Note:- I am not able to login in Visual Administrator also as it was taking SAP* which is now deactivated by me

Regards,

Abhishek Paritosh

Former Member
0 Kudos

If the user j2ee_admin is unable to logon to SLD, that's what you should fix to get the LANDSCAPE_FETCH job running again.

Logon to ABAP-stack, tx SU01

enter j2ee_admin, make sure it's not locked, and has the role SAP_J2EE_ADMIN.

Now try logging on again.

Regards,

David

Former Member
0 Kudos

David, I already checked the lock and role for J2EE_ADMIN. Still it doesn't work.

Regards,

Abhishek Paritosh

shyam_dontamsetty
Active Participant
0 Kudos

hi abhishek,

It is advisable to use communication user type for the destination instead of J2EE_admin user id.any way 1. have you checked the user j2ee_admin user id locked or not? 2. give server address as fully qualified domain address and try now.

Best Regards,

Shyam

Former Member
0 Kudos

Hello Shyam,

1. J2EE_ADMIN is not locked.

2. Where do you want me to put fqdn

Regards,

Abhishek Paritosh

shyam_dontamsetty
Active Participant
0 Kudos

Hi Abhishek,

- Goto Tcode : LCRSERVADDR and delete all the address details.

- Now maintain correct 1. user id/password 2. Host details  in Tcode:SLDAPICUST

- Now test SLDCHECK

give me feedback once after all above steps are done.

Best Regards,

Shyam

Former Member
0 Kudos

Shyam, following is the content maintained in SLDAPICUST

Alias Name:-SAP_CONFIG

Hostname:- qerossm

Port:- 50000

User:- J2EE_ADMIN

Following is the entry maintained in LCRSERVADDR

Hostname:- qerossm

Port:- 50000

Regards,

Abhishek Paritosh

Former Member
0 Kudos

Shyam, when I tried to test SLDCHECK I got the same result which I have mentioned in my original post.

Regards,

Abhishek Paritosh

shyam_dontamsetty
Active Participant
0 Kudos

hi Abhishek,

Hostname:- qerossm   - Maintain fully qualified host name

Best Regards,

Shyam

shyam_dontamsetty
Active Participant
0 Kudos

hi abhishek,

delete the entires from this tcode LCRSERVADDR and try again.

Best Regards,

Shyam

Former Member
0 Kudos

Shyam, I checked into SE80 tcode

choose the relevant Web Dynpro application from the navigation tree for your Web Dynpro component/interface, and check the URL in the administration data. Checked whether the path details in field URL also contain the full domain and host name. And I found the address as

http://qerosser1.com:8000/sap/bc/webdynpro/sap/demo_selopt_transp_cont

so shall I put http://qerosser1.com:8000

Regards,

Abhishek Paritosh

Former Member
0 Kudos

Shyam, I deleted the entries from LCRSERVADDR and tried SLDCHECK still there are some errors

Exchange Infrastructure: Test LCR Connection

Properties of RFC destination SAPSLDAPI
  RFC host:
%%RFCSERVER%%
  program id:      SAPSLDAPI_QCM
  gateway host:
qerossm
  gateway service: sapgw00

Testing the RFC connection to the SLD java client...
RFC ping was successful

SLD server access settings:
  host name:   qerossm
  port number: 50000
  user       : J2EE_ADMIN
Use transaction SLDAPICUST if you wish to maintain the SLD server access data
Launching the SLD GUI in a separate browser window...
=> Verify in the browser GUI that the SLD is in a healthy running state!

Calling function LCR_LIST_BUSINESS_SYSTEMS
Retrieving data from the SLD server...
Function call returned exception code     4
=> Check whether the SLD is running!

Summary: Connection to SLD does not work
=> Check SLD function and configurations

Now checking access to the XI Profile

Properties of RFC destination LCRSAPRFC
  RFC host:
%%RFCSERVER%%
  program id:      LCRSAPRFC_QCM
  gateway host:
qerossm

gateway service: sapgw00

sting the RFC connection to the SLD java client...
C ping was successful

lling function EXCHANGE_PROFILE_GET_PARAMETER
trieving data from the XI Profile...
nction call returned exception code     3
cess to the XI Profile is currently disrupted.
Check whether you can access the XI Profile using a web browser!

Pls suggest.

Regards,

Abhishek Paritosh

shyam_dontamsetty
Active Participant
0 Kudos

for hostname check this parameter value icm/host_name_full.

Maintain the same in host name.

Best Regards,

Shyam