DLO console hangs when trying to add a dedupe server - or gives error dedupe server s not running
Article ID: 100010579
Updated On:
Description
Error Message
The dedupe details you have entered is invalid or there is not dedupe server running at the specified location.
C:\Program Files\Symantec\Symantec DLO\Dedupe\Tomcat\logs\dedupserver.log shows:
Cannot create PoolableConnectionFactory (The connection to the host DLO75, named instance DEDUPE failed. Error: "java.net.SocketTimeoutException: Receive timed out". Verify the server and instance names and check that no firewall is blocking UDP traffic to port 1434. For SQL Server 2005 or later, verify that the SQL Server Browser Service is running on the host.)
Resolution
The SQL browser service must be running on the SQL server to broker the connection on port 1434
Applies To
By default SQL uses port 1433 to connect to unnamed instances. SQL uses port 1434 to connect to the SQL browser service which then redirects connection requests to the correct port that is assigned to a named instance. DLO dedupe services always assumes a named instance is used and thus always tries to connect using port 1434, therefore the browser service must be running for proper dedupe functionality.
Issue/Introduction
