EvB 3.0.0 RTM, FIM Agent configuration issue with non-local SQL connection for FIMSynchronizationService database.

Mark Southwell 13 years ago updated by anonymous 9 years ago 8

Issue hit with Event Broker 3.0.0 RTM. When configuring the FIM Agent in EvB when EvB resides on a FIM synchronisation server and the FIMSynchronizationServer database resides on a separate SQL server, the server name entered in the Database Connection details dialogue must be fully qualified otherwise the error below occurs. Recommend documentation update to include this requirement.

The FIM agent test is failing with the message: "A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: TCP Provider, error: 0 - The requested name is valid, but no data of the requested type was found.)". Ensure the agent is configured correctly and the target system is running.


Hi Mark,

I've successfully connected to a remote FIM instance from a local EventBroker installation, and only the hostname was supplied.

Is there any reason why, particular to your network, that the FQDN would be required?


Reassigned to check.

Hi Tony,

The FIM instance is local however the FIM database is remote. Screen shot attached.

Is that the scenario you tested? There does not appear to be any other issues with name resolution for the solution.



Screen shot of FIM EvB config

Hi Mark,

I misunderstood the requirements - currently testing the described behaviour.



Hi Mark,

When you've got some time on your hands, could you check whether the problem is exclusive to the FIM Agent? e.g. Can you connect to the FIM database with the SQL Server agent?


Additionally - if you get a chance - could you try pinging the hostname and the FQDN to see whether both are definitely visible?

Issue seems to be local to ACG CEO. Unable to reproduce at ACt Government.