Disaster Server Architecture Replication connection error

(imported topic written by suresh.h@techsa.net)

I have done the installation of DSA

when I checking the D:\Program Files (x86)\BigFix Enterprise\BES Server\FillDBData\FillDBlog.txt log

it showing below error.

TEM server Filldb.log

Mon, 25 Feb 2013 15:28:17 +0400 – Replication connection attempt failed for server ‘LMBIGFIXAEDR1.corp.cplmg.local’: Database Error:

Microsoft

ODBC SQL Server Driver

DBNETLIB

SQL Server does not exist or access denied. (08001:17)

Microsoft

ODBC SQL Server Driver

DBNETLIB

ConnectionOpen (Connect()). (01000:5)

Mon, 25 Feb 2013 15:33:57 +0400 – Replication connection attempt failed for server ‘LMBIGFIXAEDR1.corp.cplmg.local’: Database Error:

Microsoft

ODBC SQL Server Driver

DBNETLIB

SQL Server does not exist or access denied. (08001:17)

Microsoft

ODBC SQL Server Driver

DBNETLIB

ConnectionOpen (Connect()). (01000:5)

Mon, 25 Feb 2013 15:39:25 +0400 – Replication connection attempt failed for server ‘LMBIGFIXAEDR1.corp.cplmg.local’: Database Error:

Microsoft

ODBC SQL Server Driver

DBNETLIB

SQL Server does not exist or access denied. (08001:17)

Microsoft

ODBC SQL Server Driver

DBNETLIB

ConnectionOpen (Connect()). (01000:5)

Mon, 25 Feb 2013 15:44:56 +0400 – Replication connection attempt failed for server ‘LMBIGFIXAEDR1.corp.cplmg.local’: Database Error:

Microsoft

ODBC SQL Server Driver

DBNETLIB

SQL Server does not exist or access denied. (08001:17)

Microsoft

ODBC SQL Server Driver

DBNETLIB

ConnectionOpen (Connect()). (01000:5)

Mon, 25 Feb 2013 15:50:27 +0400 – Replication connection attempt failed for server ‘LMBIGFIXAEDR1.corp.cplmg.local’: Database Error:

Microsoft

ODBC SQL Server Driver

DBNETLIB

SQL Server does not exist or access denied. (08001:17)

Microsoft

ODBC SQL Server Driver

DBNETLIB

ConnectionOpen (Connect()). (01000:5)

Mon, 25 Feb 2013 15:55:58 +0400 – Replication connection attempt failed for server ‘LMBIGFIXAEDR1.corp.cplmg.local’: Database Error:

Microsoft

ODBC SQL Server Driver

DBNETLIB

SQL Server does not exist or access denied. (08001:17)

Microsoft

ODBC SQL Server Driver

DBNETLIB

ConnectionOpen (Connect()). (01000:5)

Mon, 25 Feb 2013 16:01:30 +0400 – Replication connection attempt failed for server ‘LMBIGFIXAEDR1.corp.cplmg.local’: Database Error:

Microsoft

ODBC SQL Server Driver

DBNETLIB

SQL Server does not exist or access denied. (08001:17)

Microsoft

ODBC SQL Server Driver

DBNETLIB

ConnectionOpen (Connect()). (01000:5)

Mon, 25 Feb 2013 16:06:51 +0400 – Replication connection attempt failed for server ‘LMBIGFIXAEDR1.corp.cplmg.local’: Database Error:

Microsoft

ODBC SQL Server Driver

DBNETLIB

SQL Server does not exist or access denied. (08001:17)

Microsoft

ODBC SQL Server Driver

DBNETLIB

ConnectionOpen (Connect()). (01000:5)

Mon, 25 Feb 2013 16:12:29 +0400 – Replication connection attempt failed for server ‘LMBIGFIXAEDR1.corp.cplmg.local’: Database Error:

Microsoft

ODBC SQL Server Driver

DBNETLIB

SQL Server does not exist or access denied. (08001:17)

Microsoft

ODBC SQL Server Driver

DBNETLIB

ConnectionOpen (Connect()). (01000:5)

Mon, 25 Feb 2013 16:17:53 +0400 – Replication connection attempt failed for server ‘LMBIGFIXAEDR1.corp.cplmg.local’: Database Error:

Microsoft

ODBC SQL Server Driver

DBNETLIB

c. (08001:17)

Microsoft

ODBC SQL Server Driver

DBNETLIB

ConnectionOpen (Connect()). (01000:5)

Second server DSA Filldb.log

Mon, 25 Feb 2013 14:40:22 +0400 – FillDB version 8.2.1364.0 starting…

Mon, 25 Feb 2013 14:40:22 +0400 – OpenSSL Initialized (Non-FIPS Mode)

Mon, 25 Feb 2013 14:40:22 +0400 – Using OpenSSL crypto library libBEScrypto_1_0_0_4 - OpenSSL 0.9.8x-fips 10 May 2012

Mon, 25 Feb 2013 14:40:23 +0400 – Replication connection attempt failed for server ‘LMGBIGFIXAEHQ1.corp.cplmg.local’: Database Error:

Microsoft

ODBC SQL Server Driver

SQL Server

Login failed for user ‘CPLMG\LMBIGFIXAEDR1$’. (28000:18456)

Mon, 25 Feb 2013 15:03:48 +0400 – Service Manager Stop Requested.

Mon, 25 Feb 2013 15:03:50 +0400 – FillDB version 8.2.1364.0 starting…

Mon, 25 Feb 2013 15:03:50 +0400 – OpenSSL Initialized (Non-FIPS Mode)

Mon, 25 Feb 2013 15:03:50 +0400 – Using OpenSSL crypto library libBEScrypto_1_0_0_4 - OpenSSL 0.9.8x-fips 10 May 2012

Mon, 25 Feb 2013 15:26:26 +0400 – Service Manager Shutdown Requested.

Mon, 25 Feb 2013 15:27:29 +0400 – FillDB version 8.2.1364.0 starting…

Mon, 25 Feb 2013 15:27:43 +0400 – Unable to connect to database: Database Error:

Microsoft

http://SQL Server Native Client 10.0

Named Pipes Provider: Could not open a connection to SQL Server [2]. (08001:2)

Microsoft

http://SQL Server Native Client 10.0

A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online. (08001:2)

Microsoft

http://SQL Server Native Client 10.0

Client unable to establish connection because an error was encountered during handshakes before login. Common causes include client attempting to connect to an unsupported version of SQL Server, server too busy to accept new connections or a resource limitation (memory or maximum allowed connections) on the server. (08001:26)

Microsoft

http://SQL Server Native Client 10.0

Client unable to establish connection (08001:26)

Microsoft

http://SQL Server Native Client 10.0

Shared Memory Provider: No process is on the other end of the pipe.

(08001:233)

Microsoft

http://SQL Server Native Client 10.0

Client unable to establish connection due to prelogin failure (08001:233)

Mon, 25 Feb 2013 15:25:36 +0400 – OpenSSL Initialized (Non-FIPS Mode)

Mon, 25 Feb 2013 15:25:36 +0400 – Using OpenSSL crypto library libBEScrypto_1_0_0_4 - OpenSSL 0.9.8x-fips 10 May 2012

Kindly help to resolved the issue

Regards,

Suresh H

(imported comment written by r.kelly)

I would check:

That the network account running FILLDB on the second server is the same as the account on the primary server

That you can telnet via port 1433 from the second server back to the SQL server

(imported comment written by suresh.h@techsa.net)

Hi

Thanks for your replay,

Plz tell me SQL DSA server communicating with windows authentication mode or sa authentication

you have any installation document.

Regards

Suresh,