Transport Error: Communication failure FWM 00001

building reports crystal reports
1

I have Crystal Reports 2008(Service Pack 0) installed on my laptop, I am trying to connect to BO XI 3.1 (CMS server) [to build Crystal reports on top of BO XI 3.1 universe] – during the connection process I am constantly running in to error “Transport Error: Communication failure FWM 00001”

Can some one please advice?

Indra.bobj (BOB member since 2009-06-18)

2

I get this same error. I am also not able to connect using the Web Intelligence Rich Client. I have no trouble using CMC or Infoview. I can even use the Webi thin client in Infoview. :hb:

jpeek (BOB member since 2009-08-21)

3

I had a similar problem as Indra.bobj but in my case i am using crystal reports XI R2 version

Any solutions?

krish007 :india: (BOB member since 2006-10-06)

4

The solution to my issue turned out to be permissions. The permission was not set to the Universe connection. Try using the CMC to check the permissions to the Universe, the Universe Connection, and I would also check the permissions set for the DB you are using.

jpeek (BOB member since 2009-08-21)

5

I am loging as an Administrator

krish007 :india: (BOB member since 2006-10-06)

6

In my case, I had to add an entry in the SERVERS HOST file. I believe the reason is, the server is multihomed.

alanhecht :us: (BOB member since 2003-04-24)

7

We are also having the same issue. We are using Crystal 2008 and BOXI r3.1 SP3 FP3.4. The host server build is: Windows 2008 64bit. Appreciate any help.

its_vicky07 :us: (BOB member since 2007-09-02)

8

Were you able to resolve this issue?

di652 (BOB member since 2005-02-24)

9

We faced the same issue and made the following observations:

  1. The problem only arose when we were logged on to client systems. When we logged on to a version of Crystal on the same box where the server was installed, the problem did not come up.

  2. We realized that all ports were in listen state and the client was able to telnet to the server, just fine.

  3. The issue was coming up even before the server tried to authenticate - we got the same error message whether or not we typed the correct password.

  4. It looks like, the BO Enterprise tries to pass on the IP address of the server that hosts the Server, and through the advanced Performance manager utility, we realized that the IP that was being passed on was incorrect. (ours is a complex system and our server shares lot of load and has multiple - IP). BO was randomly picking up the first in the list of network connections and that was the issue. When we changed the priority on the N/w connection, the issue was resolved.

Hope this helps
-Subah

Subah :india: (BOB member since 2005-05-17)

10

My problem was: Saving a CR to the BI40 server from CR client. fwm0001 - workaround: upload the CR file within BI4 Launchpad and then replacing the uploaded version was working well :wink:
Wobi

Wolfgang Bidner :austria: (BOB member since 2002-08-30)

11

THANKS THANKS THANKS

osrootofos :us: (BOB member since 2012-02-10)