Error FWM 00001 - USR0013 - openSessionLogon with user info has failed - Cannot access the repository
Let see another case of the error:
related to the error :
Using Rich Client (or Desktop Intelligence) in a Business Objects XI R3.1 with Enterprise authentication on the System
NOT USING J2EE system.
As I wrote before SYSTEM:6400(J2EE) means you are using 3 tier Deski
which happens through web works fine as there is no firewall in between.
while using SYSTEM:6400 we are in case of
2 tier login and your firewall is blocking the connection.
In order to solve the problem you need to open some ports in the firewall
for detail please read FWM 00001 - openSessionLogon with user info has failed
If this operation does not solve the problem
you can edit the REGEDIT - Registry Editor (after making a copy of it in order to recover it in case of problem)
then go to:
HKEY_LOCAL_MACHINE KEY
SOFTWARE
BUSINESS OBJECTS
Suite 11.5
Enterprise
At this point you should see CMSClusterMembers, in your business objects cluster names (according to the name on CMS configuration tab) with @ sign ahead.
For example @BOCLUSTER where BOCLUSTER is the name on CMS.
In this name you don't need to digit the port number.
Read also related post:
http://businessobjectsbi4.blogspot.it/2013/01/fwm-00001-transport-error-communication.html
[repo_proxy 13] SessionFacade:openSessionLogon with user info has failed(Transport error: Communication failure.(FWM 00001) (hr=#0x80042a01)
related to the error :
Cannot access the repository (USR0013)
Using Rich Client (or Desktop Intelligence) in a Business Objects XI R3.1 with Enterprise authentication on the System
NOT USING J2EE system.
As I wrote before SYSTEM:6400(J2EE) means you are using 3 tier Deski
which happens through web works fine as there is no firewall in between.
while using SYSTEM:6400 we are in case of
2 tier login and your firewall is blocking the connection.
In order to solve the problem you need to open some ports in the firewall
for detail please read FWM 00001 - openSessionLogon with user info has failed
If this operation does not solve the problem
you can edit the REGEDIT - Registry Editor (after making a copy of it in order to recover it in case of problem)
then go to:
HKEY_LOCAL_MACHINE KEY
SOFTWARE
BUSINESS OBJECTS
Suite 11.5
Enterprise
At this point you should see CMSClusterMembers, in your business objects cluster names (according to the name on CMS configuration tab) with @ sign ahead.
For example @BOCLUSTER where BOCLUSTER is the name on CMS.
In this name you don't need to digit the port number.
Read also related post:
http://businessobjectsbi4.blogspot.it/2013/01/fwm-00001-transport-error-communication.html
Comments
Post a Comment