Error FWM 00001 Transport error: Communication failure.

Environment BO XI R 3.1 SP 4

On logging on Desktop Intelligence, the following error occurs:


 SessionFacade::openSessionLogon with user info has failed(Transport error: Communication failure.(FWM 00001)


Cause
The client could not talk to the Server.


This is the main  reason. 

1)SYSTEM:6400(J2EE) means you are using 3 tier Desktop Intelligence which happens through web works fine as there is no firewall in between. 

2)SYSTEM:6400 is 2 tier login and your firewall is blocking the connection. 

The first one is a key that gets created when you modify or create a new Desktop Intelligence document from Infoview, that is 3-tier.
The second one is you entering manually the information for 2-tier.



Others Possible causes of the problem are:
The server may be down.
There may have been a network communication problem.
The request my have timed out.



Could be also a database connectivity issue between the CMS server and the Repository database.
In order to check this issue:
double click your Server Intelligence Agent in the Central Configuration Manager to open the SIA properties and view the Configuration tab. Check to be sure that the data sources you created contain the correct credentials and that communication exists between your server and the database.




Action
Verify that the server is up, that network communication is working correctly, and check if a request time out has been set.
If one has been set, lengthen the amount of time before the request times out.

Also check the Firewall of  windows and antivirus.

If the server BO is multi-homed, the right solution could be to add an entry in the SERVERS HOST file under your pc path:
C:\WINDOWS\system32\drivers\etc

In other cases the issue eas due to  permissions. 
The permission was not set to the Universe connection.
In this cases try using the CMC to check the permissions to the Universe, the Universe Connection, and also check the permissions set for the DB you are using.

Check also:

FWM 00001 - openSessionLogon with user info has failed - [repo_proxy 13]
BUSINESS OBJECTS ERRORS LIST

Comments

  1. This looks like thoroughly perfect. Every one of these bit of material happen to be fabricated in conjunction with loads of past material. I prefer the fact that considerably. O'hare

    ReplyDelete
  2. I like your post. It is good to see you verbalize from the heart and clarity on this important subject can be easily observed... O'hare

    ReplyDelete

Post a Comment

Popular posts from this blog

SAP Dashboard Error - Cannot find the BusinessObjects Enterprise report source. (LO 26608)

SAP HANA Introduction

SAP BusinessObjects 4.0 - Suite Presentation