11/26/2009 2748 views

Hi Friends,
Has anybody faced such error message while log-in to business object application? As per Install instructions, I am following guest login, with no password.

There are 4 options which are by default selected:

System: emssboss04:6400 (j2ee portal)
Username: guest
Authentication: Enterprise

I am getting internal error, and when I am clicking on details tab, it shows following message.

Error: [repo_proxy 13] HttpSessionFacade::opensearch - unable to proceed to the handleshake : HTTP communication problem

My problem is:
In Authentication mode, If I am selecting Standalone(no cms) then I am able to log-in in to the application. I have to capture some post installation configurations. So if I capture those logging with "Standalone(no cms)" will it be applied to whole application? or for different login details settings will be changed?

0 Comments   [ + ] Show comments


Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

All Answers

Some points:

- what has this got to with 'Package Development'?
- a Google for [BusinessObjects + "HTTP communication problem"] turned up a couple of forum posts above issues which the posters solved by removing files left behind by older versions of the app in question.
- BO apps are adept at filling the event log with messages. At least one of them will point to the cause.
Answered 11/26/2009 by: VBScab
Red Belt

I am installing this application on clean vmware built.......does that error means, It requires some authentication from server?
Answered 11/26/2009 by: abking99
Second Degree Blue Belt

Obviously BO needs access to servers successfully for launch.

Yes, you can can capture post install settings by launching application in Standalone mode, these settings will be applied to application for different logins.
Answered 11/26/2009 by: mekaywe
Brown Belt