Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
mpalaparthi
Starting Member
4 Posts |
 Posted - 2011-06-15 : 16:19:13
|
| Hello All,I am trying to setup Pull Transactional replication with publisher and distributer on one server and subscriber on another server.I did:shared the snapshot folder as \\servername\repldata and gave while configuring the distributerrun the log reader and snapshot agents under sql agent accountsgiving the distributer under distributer_admin login and gave that login while configuring the subscriberI am getting the error in log readet agent and the msg is "No replicated transactions are available "I dont know where it went wrong.Please give any suggenstions or ideas, its a kind of urgent and important.Thanks and regards |
|
|
russell
Pyro-ma-ni-yak
5072 Posts |
Posted - 2011-06-15 : 17:01:12
|
| That's not an error, it's an informational message.Did you run the snapshot yet?How often are you pulling? |
 |
|
|
mpalaparthi
Starting Member
4 Posts |
Posted - 2011-06-15 : 17:18:53
|
| Thanks u so much for the replyDid you run the snapshot yet?I update a record in the publisher database and I running the snapshot agent, it is running successfully and when I see the Log reader agent initially it says "2 transaction(s) with 225 command(s) were delivered." and after some time it says "No replicated transactions are available"How often are you pulling?frequentlyAlso when I see the sync proces in the subscriber it gaves me an error msg that " The process could not connect to Distributor 'publisher server name'."Please advice... Thanks |
|
|
|
russell
Pyro-ma-ni-yak
5072 Posts |
Posted - 2011-06-15 : 19:11:24
|
| I don't know why you got the error when you synched, but the snapshot worked and was distributed, so that's a good sign.Why are you pulling instead of pushing? Is the connection not always available? If so, that's why you got the error.Snapshot should only be run once (except when adding articles, or rare fatal errors).I'd update an article at the publisher and just wait for the pull and see if it gets distributed. |
|
|
|
mpalaparthi
Starting Member
4 Posts |
Posted - 2011-06-16 : 10:50:17
|
| Hello All,Thank u so much to all for your valuable replies. I got the solution, this is what I did1. Delete the whole replication including, first delete the subscriber then delete the publisher and then the distributer (make sure u delete the distributer by running select * from sysdatabases and u dont want to see the distribution database (to delete the distributer make the database offline and then delete)2. create a login (Ex: replication_admin) with sysadmin privilages in publiser, subscriber and in ditribution databse and make the that login ad dbo for publisher and subscriber databases3. share the snapshot folder (Ex: \\servername\sharedname\) and gave enough permissions to sql service logins and the login under which u want r going to setup replication4. create the distribter, gave the snaoshot shared folder while configuring the distributer, run the log reader agent and snapshot agnets under sql servive logins5. create the publisher and gave the replication_admin login for CONNECT TO DISTRIBUTER option6. check the replication monitor for any issues7. Configure the subscriber and gave the sql service account login for CONNECT TO PUBLISHER option (if u r using pull subscription)8. My publisher and subscriber servers runs under the same sql service account permissions (login and password is same for both)Hope this helps !!Thanks |
|
|
|
|
|
|
|
|
Replication error: No replicated transactions