SQL 2008 R2 replication error: The process could not connect to DistributorSQL 2008 Replication over InternetSQL Transactional Replication snapshot not applyingReplication between SQL 2008 & SQL 2000 - Across network (DMZ) - process could not connect to SubscriberTable modifications while running db replication (MS SQL 2008)Adding new article to transactional replication gives error at subscriberSQL Server 2008 - Performance impact of transactional replication?SQL Server 2008 Chaining Merge ReplicationUsing a subscriber database as a backupHow to move the files of a replicated database (SQL Server 2008 R2) to a different driveIf a SQL Server Replication Distributor and Subscriber are on the same server, should a PUSH or PULL subsciption be used?

Multi tool use
Multi tool use

Why did the Apollo 13 crew extend the LM landing gear?

Is there an idiom that support the idea that "inflation is bad"?

On which topic did Indiana Jones write his doctoral thesis?

Why is B♯ higher than C♭ in 31-ET?

How do I tell my manager that his code review comment is wrong?

How can I close a gap between my fence and my neighbor's that's on his side of the property line?

Should I mention being denied entry to UK due to a confusion in my Visa and Ticket bookings?

Can Infinity Stones be retrieved more than once?

BOOM! Perfect Clear for Mr. T

Independent, post-Brexit Scotland - would there be a hard border with England?

Make some Prime Squares!

Can my company stop me from working overtime?

Will 700 more planes a day fly because of the Heathrow expansion?

Why do money exchangers give different rates to different bills?

Why is Arya visibly scared in the library in S8E3?

What was the first instance of a "planet eater" in sci-fi?

What to use instead of cling film to wrap pastry

Getting a W on your transcript for grad school applications

How do LIGO and VIRGO know that a gravitational wave has its origin in a neutron star or a black hole?

Would glacier 'trees' be plausible?

Are there any Final Fantasy Spirits in Super Smash Bros Ultimate?

Verb "geeitet" in an old scientific text

How do I make a function that generates nth natural number that isn't a perfect square?

Why do people keep telling me that I am a bad photographer?



SQL 2008 R2 replication error: The process could not connect to Distributor


SQL 2008 Replication over InternetSQL Transactional Replication snapshot not applyingReplication between SQL 2008 & SQL 2000 - Across network (DMZ) - process could not connect to SubscriberTable modifications while running db replication (MS SQL 2008)Adding new article to transactional replication gives error at subscriberSQL Server 2008 - Performance impact of transactional replication?SQL Server 2008 Chaining Merge ReplicationUsing a subscriber database as a backupHow to move the files of a replicated database (SQL Server 2008 R2) to a different driveIf a SQL Server Replication Distributor and Subscriber are on the same server, should a PUSH or PULL subsciption be used?






.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty height:90px;width:728px;box-sizing:border-box;








1















I have two servers running SQL 2008 R2 Standard, each with an instance named "MAIN". I have a small test database on my primary server (one table, 13 rows) that I want to replicate to a second server as a proof-of-concept for some larger databases that I want to replicate. I set up the primary server to be a publisher and distributor, and set the database to do transactional replication. I copied the data to the second server via a backup/restore, not via a snapshot (which I'll have to do with the larger databases due to database size and limited bandwidth). I followed the instructions here:
http://gnawgnu.blogspot.com/2009/11/sql-2008-transactional-replication-and.html



Now on the subscriber, I go under Replication / Local Subscriptions / Right click / Properties on my subscription to the DB. The status of the last synchronization shows a status of: "The process could not connect to Distributor 'PRIMARYSERVERMAIN'."



Data IS replicating from the primary to the secondary. Any record I add on the primary shows up on the secondary server within seconds.



Is the Distributor part of the Snapshot system that I'm not using, or is it part of the transaction replication stuff?



Thanks,
Lance










share|improve this question






























    1















    I have two servers running SQL 2008 R2 Standard, each with an instance named "MAIN". I have a small test database on my primary server (one table, 13 rows) that I want to replicate to a second server as a proof-of-concept for some larger databases that I want to replicate. I set up the primary server to be a publisher and distributor, and set the database to do transactional replication. I copied the data to the second server via a backup/restore, not via a snapshot (which I'll have to do with the larger databases due to database size and limited bandwidth). I followed the instructions here:
    http://gnawgnu.blogspot.com/2009/11/sql-2008-transactional-replication-and.html



    Now on the subscriber, I go under Replication / Local Subscriptions / Right click / Properties on my subscription to the DB. The status of the last synchronization shows a status of: "The process could not connect to Distributor 'PRIMARYSERVERMAIN'."



    Data IS replicating from the primary to the secondary. Any record I add on the primary shows up on the secondary server within seconds.



    Is the Distributor part of the Snapshot system that I'm not using, or is it part of the transaction replication stuff?



    Thanks,
    Lance










    share|improve this question


























      1












      1








      1








      I have two servers running SQL 2008 R2 Standard, each with an instance named "MAIN". I have a small test database on my primary server (one table, 13 rows) that I want to replicate to a second server as a proof-of-concept for some larger databases that I want to replicate. I set up the primary server to be a publisher and distributor, and set the database to do transactional replication. I copied the data to the second server via a backup/restore, not via a snapshot (which I'll have to do with the larger databases due to database size and limited bandwidth). I followed the instructions here:
      http://gnawgnu.blogspot.com/2009/11/sql-2008-transactional-replication-and.html



      Now on the subscriber, I go under Replication / Local Subscriptions / Right click / Properties on my subscription to the DB. The status of the last synchronization shows a status of: "The process could not connect to Distributor 'PRIMARYSERVERMAIN'."



      Data IS replicating from the primary to the secondary. Any record I add on the primary shows up on the secondary server within seconds.



      Is the Distributor part of the Snapshot system that I'm not using, or is it part of the transaction replication stuff?



      Thanks,
      Lance










      share|improve this question
















      I have two servers running SQL 2008 R2 Standard, each with an instance named "MAIN". I have a small test database on my primary server (one table, 13 rows) that I want to replicate to a second server as a proof-of-concept for some larger databases that I want to replicate. I set up the primary server to be a publisher and distributor, and set the database to do transactional replication. I copied the data to the second server via a backup/restore, not via a snapshot (which I'll have to do with the larger databases due to database size and limited bandwidth). I followed the instructions here:
      http://gnawgnu.blogspot.com/2009/11/sql-2008-transactional-replication-and.html



      Now on the subscriber, I go under Replication / Local Subscriptions / Right click / Properties on my subscription to the DB. The status of the last synchronization shows a status of: "The process could not connect to Distributor 'PRIMARYSERVERMAIN'."



      Data IS replicating from the primary to the secondary. Any record I add on the primary shows up on the secondary server within seconds.



      Is the Distributor part of the Snapshot system that I'm not using, or is it part of the transaction replication stuff?



      Thanks,
      Lance







      sql-server-2008 replication transactional-replication






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Mar 11 '11 at 1:22







      Lance Lefebure

















      asked Feb 14 '11 at 21:13









      Lance LefebureLance Lefebure

      11326




      11326




















          2 Answers
          2






          active

          oldest

          votes


















          0














          Check whether Browser services is running all SQL instance.
          Are you using a named instance?
          Also see if there are an resource jobs are running.






          share|improve this answer






























            0














            The distributor is what is recording the changes from the publisher and queueing them before they are sent to the subscriber.



            The default is to do a push subscription where no connectivity is needed from the subscriber to the distributor as the connection goes from the distributor to the subscriber. That being the case I'm guessing that there's a firewall blocking either UDP port 1434 on the publisher, or there's a firewall blocking the TCP port that the named instance on PRIMARYSERVER is listening on.






            share|improve this answer























              Your Answer








              StackExchange.ready(function()
              var channelOptions =
              tags: "".split(" "),
              id: "2"
              ;
              initTagRenderer("".split(" "), "".split(" "), channelOptions);

              StackExchange.using("externalEditor", function()
              // Have to fire editor after snippets, if snippets enabled
              if (StackExchange.settings.snippets.snippetsEnabled)
              StackExchange.using("snippets", function()
              createEditor();
              );

              else
              createEditor();

              );

              function createEditor()
              StackExchange.prepareEditor(
              heartbeatType: 'answer',
              autoActivateHeartbeat: false,
              convertImagesToLinks: true,
              noModals: true,
              showLowRepImageUploadWarning: true,
              reputationToPostImages: 10,
              bindNavPrevention: true,
              postfix: "",
              imageUploader:
              brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
              contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
              allowUrls: true
              ,
              onDemand: true,
              discardSelector: ".discard-answer"
              ,immediatelyShowMarkdownHelp:true
              );



              );













              draft saved

              draft discarded


















              StackExchange.ready(
              function ()
              StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f235444%2fsql-2008-r2-replication-error-the-process-could-not-connect-to-distributor%23new-answer', 'question_page');

              );

              Post as a guest















              Required, but never shown

























              2 Answers
              2






              active

              oldest

              votes








              2 Answers
              2






              active

              oldest

              votes









              active

              oldest

              votes






              active

              oldest

              votes









              0














              Check whether Browser services is running all SQL instance.
              Are you using a named instance?
              Also see if there are an resource jobs are running.






              share|improve this answer



























                0














                Check whether Browser services is running all SQL instance.
                Are you using a named instance?
                Also see if there are an resource jobs are running.






                share|improve this answer

























                  0












                  0








                  0







                  Check whether Browser services is running all SQL instance.
                  Are you using a named instance?
                  Also see if there are an resource jobs are running.






                  share|improve this answer













                  Check whether Browser services is running all SQL instance.
                  Are you using a named instance?
                  Also see if there are an resource jobs are running.







                  share|improve this answer












                  share|improve this answer



                  share|improve this answer










                  answered May 12 '11 at 14:33









                  Satya SKJSatya SKJ

                  393




                  393























                      0














                      The distributor is what is recording the changes from the publisher and queueing them before they are sent to the subscriber.



                      The default is to do a push subscription where no connectivity is needed from the subscriber to the distributor as the connection goes from the distributor to the subscriber. That being the case I'm guessing that there's a firewall blocking either UDP port 1434 on the publisher, or there's a firewall blocking the TCP port that the named instance on PRIMARYSERVER is listening on.






                      share|improve this answer



























                        0














                        The distributor is what is recording the changes from the publisher and queueing them before they are sent to the subscriber.



                        The default is to do a push subscription where no connectivity is needed from the subscriber to the distributor as the connection goes from the distributor to the subscriber. That being the case I'm guessing that there's a firewall blocking either UDP port 1434 on the publisher, or there's a firewall blocking the TCP port that the named instance on PRIMARYSERVER is listening on.






                        share|improve this answer

























                          0












                          0








                          0







                          The distributor is what is recording the changes from the publisher and queueing them before they are sent to the subscriber.



                          The default is to do a push subscription where no connectivity is needed from the subscriber to the distributor as the connection goes from the distributor to the subscriber. That being the case I'm guessing that there's a firewall blocking either UDP port 1434 on the publisher, or there's a firewall blocking the TCP port that the named instance on PRIMARYSERVER is listening on.






                          share|improve this answer













                          The distributor is what is recording the changes from the publisher and queueing them before they are sent to the subscriber.



                          The default is to do a push subscription where no connectivity is needed from the subscriber to the distributor as the connection goes from the distributor to the subscriber. That being the case I'm guessing that there's a firewall blocking either UDP port 1434 on the publisher, or there's a firewall blocking the TCP port that the named instance on PRIMARYSERVER is listening on.







                          share|improve this answer












                          share|improve this answer



                          share|improve this answer










                          answered Mar 4 '13 at 20:58









                          mrdennymrdenny

                          26.4k43466




                          26.4k43466



























                              draft saved

                              draft discarded
















































                              Thanks for contributing an answer to Server Fault!


                              • Please be sure to answer the question. Provide details and share your research!

                              But avoid


                              • Asking for help, clarification, or responding to other answers.

                              • Making statements based on opinion; back them up with references or personal experience.

                              To learn more, see our tips on writing great answers.




                              draft saved


                              draft discarded














                              StackExchange.ready(
                              function ()
                              StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f235444%2fsql-2008-r2-replication-error-the-process-could-not-connect-to-distributor%23new-answer', 'question_page');

                              );

                              Post as a guest















                              Required, but never shown





















































                              Required, but never shown














                              Required, but never shown












                              Required, but never shown







                              Required, but never shown

































                              Required, but never shown














                              Required, but never shown












                              Required, but never shown







                              Required, but never shown







                              ve h3 kvhAsurmwLMCd4 VD9XdP3,iTeIxkl WEpkDR W QjuqnsP QLWTC4XyziNthxHRQrNn1,KZ,rlnFnA7oFkNXQ,TY,3jSBHo0
                              D QvH,CyplMxzyDH0oAFMIfQ,DKDkiDf jUA 1cqR,inA9sPt8CglJJDMCmWO9 CEAvU deDHoyGvdYxB,Tpdwt

                              Popular posts from this blog

                              RemoteApp sporadic failureWindows 2008 RemoteAPP client disconnects within a matter of minutesWhat is the minimum version of RDP supported by Server 2012 RDS?How to configure a Remoteapp server to increase stabilityMicrosoft RemoteApp Active SessionRDWeb TS connection broken for some users post RemoteApp certificate changeRemote Desktop Licensing, RemoteAPPRDS 2012 R2 some users are not able to logon after changed date and time on Connection BrokersWhat happens during Remote Desktop logon, and is there any logging?After installing RDS on WinServer 2016 I still can only connect with two users?RD Connection via RDGW to Session host is not connecting

                              Vilaño, A Laracha Índice Patrimonio | Lugares e parroquias | Véxase tamén | Menú de navegación43°14′52″N 8°36′03″O / 43.24775, -8.60070

                              Cegueira Índice Epidemioloxía | Deficiencia visual | Tipos de cegueira | Principais causas de cegueira | Tratamento | Técnicas de adaptación e axudas | Vida dos cegos | Primeiros auxilios | Crenzas respecto das persoas cegas | Crenzas das persoas cegas | O neno deficiente visual | Aspectos psicolóxicos da cegueira | Notas | Véxase tamén | Menú de navegación54.054.154.436928256blindnessDicionario da Real Academia GalegaPortal das Palabras"International Standards: Visual Standards — Aspects and Ranges of Vision Loss with Emphasis on Population Surveys.""Visual impairment and blindness""Presentan un plan para previr a cegueira"o orixinalACCDV Associació Catalana de Cecs i Disminuïts Visuals - PMFTrachoma"Effect of gene therapy on visual function in Leber's congenital amaurosis"1844137110.1056/NEJMoa0802268Cans guía - os mellores amigos dos cegosArquivadoEscola de cans guía para cegos en Mortágua, PortugalArquivado"Tecnología para ciegos y deficientes visuales. Recopilación de recursos gratuitos en la Red""Colorino""‘COL.diesis’, escuchar los sonidos del color""COL.diesis: Transforming Colour into Melody and Implementing the Result in a Colour Sensor Device"o orixinal"Sistema de desarrollo de sinestesia color-sonido para invidentes utilizando un protocolo de audio""Enseñanza táctil - geometría y color. Juegos didácticos para niños ciegos y videntes""Sistema Constanz"L'ocupació laboral dels cecs a l'Estat espanyol està pràcticament equiparada a la de les persones amb visió, entrevista amb Pedro ZuritaONCE (Organización Nacional de Cegos de España)Prevención da cegueiraDescrición de deficiencias visuais (Disc@pnet)Braillín, un boneco atractivo para calquera neno, con ou sen discapacidade, que permite familiarizarse co sistema de escritura e lectura brailleAxudas Técnicas36838ID00897494007150-90057129528256DOID:1432HP:0000618D001766C10.597.751.941.162C97109C0155020