Solved

SQL SERVER Peer to Peer Transitional Replication Error

Posted on 2010-11-11
8
642 Views
Last Modified: 2012-05-10
I am trying to Setup a Peer to Peer Transitional Replication between 2 SQl SERVER 2008 EE Servers.

Servers : PRTRWEBSERVER and PRTRESCRMSERVER

I followed the steps as described in the Microsoft article :

http://technet.microsoft.com/en-us/library/ms152536.aspx

I have never setup replication before and so i am stumped on the errors I am getting right now.

Agent and Publisher Security setting I gave as the Domain Administrator (PRTR\Administrator)

Please see attached Error Logs.
 PRTRWEBSERVER Error Logs PRTRESCRMSERVER Error Logs
0
Comment
Question by:isaackhazi
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 4
  • 4
8 Comments
 
LVL 12

Expert Comment

by:NormanMaina
ID: 34118363
can you break it down further...am just trying to understand it.

Between PRTRWEBSERVER and PRTRESCRMSERVER

1.did you configure both servers as distributors?
2.did you configure both serves as publishers?
3.did you configure a topology and added the two nodes?
4.do all databases that participate in peer-to-peer replication contain identical schema and data?
5.Publications must allow schema changes to be replicated. (This is a setting of 1 for the publication property replicate_ddl, which is the default setting.)- have you done that?
6.Have you ensured that there are no Row and column filtering?

Cross check with the below guide which is easier to understand:
http://msdn.microsoft.com/en-us/library/ms152536.aspx

0
 
LVL 8

Author Comment

by:isaackhazi
ID: 34118461
these are the steps I followed.

Say PRTRWEBSERVER - S1 and PRTRESCRMSERVER - S2


Created Dist. in S1
Created Dist in S2
Created A new Publication in S1 (Selected the table/Articles to be Published)
Enabled S1 for Peer to Peer Replication and set Conflict Detection to true
Backed Up S1
Restored it to S2
Configured Peer to Peer topology on S1 and added S2 to the topology.

I basically followed the Microsoft article.


0
 
LVL 8

Author Comment

by:isaackhazi
ID: 34118466
The Link you provided to me was the guide I followed to set up the replication.
0
How Do You Stack Up Against Your Peers?

With today’s modern enterprise so dependent on digital infrastructures, the impact of major incidents has increased dramatically. Grab the report now to gain insight into how your organization ranks against your peers and learn best-in-class strategies to resolve incidents.

 
LVL 8

Author Comment

by:isaackhazi
ID: 34118476
The Questions I have is:

when I setup S1 as Dist. should I proceed and Setup S2 as dist. aswell...

Or should I Setup S1 as dist, setup a pulication in S1, enable S1 for peer to peer rep. and then backup, restore to S2
THEN setup Dist on S2?
0
 
LVL 12

Expert Comment

by:NormanMaina
ID: 34119800
yes you have to set up S@ as a distributor as well.

This link has a more straightforward guide than the technet link you used.
http://msdn.microsoft.com/en-us/library/ms152536.aspx
0
 
LVL 12

Expert Comment

by:NormanMaina
ID: 34126407
did it work?
0
 
LVL 8

Author Comment

by:isaackhazi
ID: 34129705
No,

I followed that and tried everything.
I keep getting the "The process could not execute 'sp_replcmds' on 'PRTRESCRMSERVER'."

on bother replicaTION SERVER ERrOR LOGS
0
 
LVL 12

Accepted Solution

by:
NormanMaina earned 500 total points
ID: 34130045
This problem occurs because the Windows Service Control Manager cannot grant the required permissions to run agent jobs to the new domain account.

To resolve this problem, use SQL Server Configuration Manager to change the domain account back to a startup account.

follow these steps:

   1. Set the SQL Server Agent service account in SQL Server Configuration Manager to the LocalSystem account.
   2. Stop and then start the SQL Server Agent service.
   3. Reset the SQL Server Agent service account in SQL Server Configuration Manager back to the original account.
   4. Stop and then start the SQL Server Agent service.

You can also reset the password of the SQL Server Agent service account in SQL Server Configuration Manager.

To avoid this problem in the future, its recommended that you use SQL Server Configuration Manager instead of the Windows Service Control Manager to modify startup accounts.
0

Featured Post

Best Practices: Disaster Recovery Testing

Besides backup, any IT division should have a disaster recovery plan. You will find a few tips below relating to the development of such a plan and to what issues one should pay special attention in the course of backup planning.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

How to leverage one TLS certificate to encrypt Microsoft SQL traffic and Remote Desktop Services, versus creating multiple tickets for the same server.
Ever needed a SQL 2008 Database replicated/mirrored/log shipped on another server but you can't take the downtime inflicted by initial snapshot or disconnect while T-logs are restored or mirror applied? You can use SQL Server Initialize from Backup…
Via a live example combined with referencing Books Online, show some of the information that can be extracted from the Catalog Views in SQL Server.
Viewers will learn how to use the UPDATE and DELETE statements to change or remove existing data from their tables. Make a table: Update a specific column given a specific row using the UPDATE statement: Remove a set of values using the DELETE s…

729 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question