I have been trying to connect SAP BusinessObjects Xcelsius 2008 Sp3(Client Machine) using BICS with SAP NW(Server Machine) but I am facing an Error for which details are as follows.
While creating a SAP NW BW connection in Xcelsius, when I select a BW query for import, after a successful BW connection, I recieve Error 2032.
I have tried checking the workflow with a network traffic monitoring tool called Fiddler and it shows that when i select a BW query, after the connection, Xcelsius looks for bicsremotecrossdomain.xml as a host instead of http:/<host>:8000/bicsremotecrossdomain.xml where <host> is our SAP NW Server. It is not looking for the host systems IP and Port and goes directly looking for the bicsremotecrossdomain.xml file which is actually located on http://<host>:8000/bicsremotecrossdomain.xml.We have SAP NW 7.01 EHP1 SPS 7 for for both Java and ABAP. Additionally I have SAP GUI 7.2 and flash 10.1 installed on the the client machine.
Any help in resolving this issue will be greatly appreciated.
Thanks and Regards,
Edited by: Abdul Mughni on Oct 2, 2010 11:44 AM
Edited by: Abdul Mughni on Oct 2, 2010 11:45 AM
I have encountered the 2032 issue at multiple customer projects.
It is a "stubborn" issue that is quite difficult to pinpoint since the same error code is raised for a whole range of different root causes (missing crossdomain policies, inactive BICS webservice , correct HTTP server entries in Portal tables, firewall/port blocking, etc, etc)
Currently the endusers at a specific customer are encountering the issue in a seamingly "random"way: some users can execute the dashboard and some users cannot due to the 2032 issue, though if they execute the same dashboard on the test system instead of the production system the dashboard is running without issues. And sometimes the next day the users can access the dashboard without any issues (without restarting the SAP Portal in between).
So it seems that possible root causes like missing crossdomain policies, inactive BICS webservice , correct HTTP server entries in Portal tables, firewall/port blocking can be ruled out.
It looks more like a JAVA stack issue: at some times the JAVA stack can process the BICS request and sometimes it can not.
Maybe caused by JAVA memory settings?
Note: we have currently a very limited dashboard user group (only a few users) and a relatively simple dashboard (max 2 active BICS connections).
Does anybody recognize/have experience with this type of behaviour of the BICS 2032 issue?
(note: we are running Xcelsius 2008 Sp4 with SAP NW 7.01 EHP1 SP 7)