on 01-28-2010 2:48 PM
We have updated PI 7.1 to eHP1.
after the update, we are unable to use RWB.
It throws the following stack error when we click on Component Monitoring and Message Monitoring:
Error during communication with System Landscape Directory: HTTP response code: 403 (Forbidden)
com.sap.aii.rwb.exceptions.BuildLandscapeException: Error during communication with System Landscape Directory: HTTP response code: 403 (Forbidden)
at com.sap.aii.rwb.agent.server.SLDAgentBean.convertException(SLDAgentBean.java:1535)
at com.sap.aii.rwb.agent.server.SLDAgentBean.buildSLD(SLDAgentBean.java:779)
......
Caused by: com.sap.lcr.api.cimclient.CIMClientException: HTTP response code: 403 (Forbidden)
at com.sap.lcr.api.cimclient.HttpRequestSender.newClientException(HttpRequestSender.java:721)
at com.sap.lcr.api.cimclient.HttpRequestSender.processResponse(HttpRequestSender.java:610)
at com.sap.lcr.api.cimclient.HttpRequestSender.send(HttpRequestSender.java:353)
at com.sap.lcr.api.cimclient.CIMOMClient.send(CIMOMClient.java:287)
......
If we trigger a data transfer using RZ70, we get the following error:
0: <hostname)_<SID>_<NR> : RFC data prepared
0: <hostname)_<SID>_<NR> : Used RFC destination: SLD_UC
0: <hostname)_<SID>_<NR> : RFC call failed: JCO.Server could not find server function 'SET_SLD_DATA'
0: <hostname)_<SID>_<NR> : Batch job not scheduled
When we click on SLD Registration link in RWB, we get the following error:
Error retrieving list of registered XI components from SLD; details: com.sap.aii.rwb.exceptions.BuildLandscapeException: Error during communication with System Landscape Directory: HTTP response code: 403 (Forbidden)
Can anyone help me fix the problem
regards,
Roshni
Roshni,
I am running into exactly same issue after upgrading to PI 7.1 EHP1. Can you elaborate more on the problem and fix.
We had an incorrect profile entry for ASCS
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The authentication problem was due to unstable message server. We had an incorrect profile entry for ASCS.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Roshni,
I would rather start isolating the issue by following the below sequence:
1. Check if INTEGRATION_DIRECTORY_HMI rfc works fine? If it's NOT, then delete this rfc and re-create using correct input values (port, host etc)
2. Check SLDAPICUST, Test works fine? If not, then remove it and enter correct credentials
3. Ensure, the Program ID (SAPSLDAPI_<SID>)being used in SAPSLDAPI existing in SLD.
4. Ensure, the program ID (SLD_UC) being used in rfc SLD_UC existing in SLD and rfc configured to use correct Gateway Host/Service
In general, you need to ensure all SLD integration infrastructure related configuration is in place
-Sekhar
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Quick checklist:
Evaluate the settings in Rz70, SLDAPICUST, SM59 (SLD_UC, SAPSLDAPI) (I'm pretty sure your SLD_UC won't work based on your errors), execute SLDCHECK
Verify correct user and password in VA (SLD Data Supplier), also redo the Assign Appliction Roles to User Groups button (top of screen in SLD_DATA_SUPPLIER
Verify SAPSLDAPI JcoRFC is correct in VA
Log on to SLD go to Administration-->Data and visit the last tab to see if SLD RFCs are "UP" or "DOWN" if down, restart the SLD Server from Administration.
Check SLD logs for errors.
Check your RFC user in the UME for the lcrInstanceWriterAll role.
If it still doesn't work, try going to VA Security Provider > sap.com/com.sap.lcr*sld> Security Roles and explicitly assign the LcrInstanceWriterAll role (or lcrAdministrator) is assigned to your RFC user.
Hope this helps,
Phil
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The problem, unfortunately, remains unsolved. Any new thoughts?
regards,
Roshni
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Srinivas,
Thanks for the reply.
We have checked the users. The passwords are correctly maintained and none of the users are locked.
regards,
Roshni
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Roshni,
Mostly we get http 403 forbidden error only in case of user authentication fails.Pls see [this|http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/bd5950ff-0701-0010-a5bc-86d45fd52283?quicklink=index&overridelayout=true] trouble shooting guide its for XI 3.0 but still see if it helps.
Regards,
Srinvas
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
93 | |
10 | |
10 | |
9 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.