Database error: [Data Federator Driver] Cannot reach server.

[sunsethill]

We've been having all kinds of problems getting our multi-source Universe to work successfully on a consistent basis. Unfortunately, SAP has not been able to assist us in pinpointing the root cause of the problem. We’re running 4.1 SP2.

We have a multi-source Universe pulling in data from two SQL Server 2008 databases and one Sybase 15 database.

On a random, but frequent basis, when we refresh the reports based on this Multi-source Universe, we get the following error:

Database error: [Data Federator Driver] Cannot reach server. Reason: attempt to establish connection failed: java.net.ConnectException: Connection refused: connect. (IES 10901)

Please note that we are able to use Information Design Tool without any issues/errors and all the connections test successfully. It's just when we run the Webi reports that we get the error.

We do not get these errors from our “legacy” Universes (i.e. Single source Universes created with Designer in 3x) running Webi reports in BO4.1

Has anyone else come across this issue? If so, any assistance would be appreciated.

[calleT74]

Hi all gurus,

We are experiencing the same error on our 4.1 sp1 prod version here. The exact error we are getting is as follows;

"Database error: [Data Federator Driver] Cannot reach server. Reason: attempt to establish connection failed. java.net.ConnectException: Connection refused: connect (IES 10901) (WIS 10901)"

Anyone who can shed any light please? In the mean time I will follow up with SAP support (again)

Cheers

[iguanasterix]

Hi,

We are having the same problem with Data Federator. The reason why the error message is being thrown is because the Data Federator service is crashing and it is then closing all active connections.

(Check the date modified for your data federator services and you will notice the timestamp is updated to the time of failure due to the service restart)

Have you had any luck with SAP?

Regards,

Alejandro Serrano

[nandos999]

We have recently been getting the same error on a intimintent basis.
We are on 4.1 sp3 . Anyone know what is the reason behind this
When we get the error it causes the federator service to stop and start again.