Configuration Issues - DSA

[Mayank]

Hello ,

We have configured DSA in our existing environment , but failed to establish the connection between two servers hence replication is not happening.

followed the below steps:
1)Created one user in SQL server with DBO rights in Primary and secondary server.
2)Created the following registry entries under FillDB with same user name and password.
a)ReplicationUser
b)ReplicationPassword
c)ReplicationDatabase
3)Install the server using server installer using existing masthead.

after the successfull installation it is giving the error in replication Tab as"Connection Broken" "Database Error : Actionsite has not been created.

We are clueless , anyone having any idea please share your inputs.

Thanks
Mayank

[sureshhan]

Hi Mayank,

Please run the FillDB and BES Root services on Local system Account provide user name password

SOLVED: DSA Server Database Issue

HI Team, database is a default instance database. We tried to changes in REPLICATION_SERVERS tables: Primary Server REPLICATION_SERVERS tables: 0 TECS\BIGFIXSQL http://TECS:52311 300 0 NULL NULL 1 300 1 NULL NULL 2 DSAIBMbigfix.tech.net http://DSAIBMbigfix.tech.net:52311 300 1 NULL NULL 3 DSAIBMbigfix.tech.net http://DSAIBMbigfix.tech.net:52311 300 1 NULL NULL 4 DSAIBMbigfix.tech.net http://DSAIBMbigfix.tech.net:52311 300 1 NULL NULL 5 DSAIBMbigfix.tech.net http://DSAIBMbigf…

[strawgate]

@Mayank

Database Error : Actionsite has not been created

i have received a similar error message in the past and came to this conclusion.

It’s important to note that the Action Site missing message was because replication was working but in only one direction (my theory at least). the Primary server was trying to get data from the replica and the replica realized it didnt have anything yet – essentially the error occurs when it’s attempting bi-directional replication but the secondary doesnt have any data to share. The reason the secondary didn’t have any data was because it couldn’t resolve the correct ip for the primary. Replication was only working in one direction due to a complex network setup. The secondary couldn’t get data from the primary so it stayed in this uninitialized state.

Are you using Default or Named Instances? SQLSERVER or SQLSERVER\INSTANCE

Login to both servers and verify that you can:

1. Ping the other server
2. TCPing the other server with TCP 1433
3. Open SQL Management Studio and connect to the other server
4. Open SQL Management studio and connect to the other server with your replication user credentials

[Mayank]

Hi Strawgate
Are you using Default or Named Instances? SQLSERVER or SQLSERVER\INSTANCE ---- This one i am not able to understand.

Login to both servers and verify that you can:

Ping the other server-- Happening
TCPing the other server with TCP 1433— Happening
Open SQL Management Studio and connect to the other serverOpen SQL Management studio and connect to the other server with your repplication user credentials-- We are able to connect.

Thanks
Mayank

[strawgate]

When you connect with SQL Management Studio does it look like this:

Or like this:

[Mayank]

Hi Strawgate

while connecting to the SQL server i am putting my server hostname and then user name and password to connect it and it successfully connects.

Thanks
Mayank

[JasonWalker]

You did this on both DSA servers, right? You’ll need to create the SQL Account and registry entries on both.

[Mayank]

hey Jason

While configuring DSA , i have created the SQL account and registry entries on both the servers.

Thanks
Mayank