Are you the publisher? Claim or contact us about this channel


Embed this content in your HTML

Search

Report adult content:

click to rate:

Account: (login)

More Channels


Showcase


Channel Catalog


Channel Description:

Discussions on SQL Server Replication

older | 1 | .... | 93 | 94 | (Page 95) | 96 | 97 | .... | 181 | newer

    0 0

    SQL 2008 R2 Enterprise edition.

    Server A--publisher and principal

    Server B--distributor (Push subscription)and subscriber

    Server C--mirror

    The issue I have is:

    When the replication failsover to the mirror server(I have set the publisherfailover partner to mirror server) replication works fine but when I want to see the replication monitor I register the distributor and publishers.

    I see the publication under the new principal(former mirror).when I click on subscription watch list window to view details of the subscription it throws error'The start context provided for this detail window is incomplete.the following input is missing LogReaderAgentName(replication Monitor)'.

    Cannot  access a disposed object.

    objectname:DWForm

    When I right click on the replication publication in SSMS to view the log reader agent status and synchronization status it throws error'unable to display agent status'.

    When I try to look into the publication properties on my new principal Subscription option 'only functions and extended stored procedures can be executed from within function error 557'

    When I look into the Publication Access list property 'could not find the distributor or the distribution database on local server.it may not be installed or not configured as publisher at distributor.error 14071'.

    I have registered the mirror server which is my nerw principal as publisher when I configured remote distributor wondering why this error?

    When I look into the agent security property ''error 20036 distributor is not installed properly'

    IS this the expected behavior of the replication when it failsover to the mirror server(which becomes the new principal) or something is wrong here?

    Appreciate your quick response on this.

    Regards

    Shwetha


    0 0

    Hello all,

    I am trying to set up merge replication. The merge agent does not run and gives the following error message:

    The schema script 'TableName_3.sch' could not be propagated to the subscriber.

    The snapshot folder has maximum permissions, but the agent still fails.

    What on earth could the trouble be?

    Cheers...


    BI Consultant, MCP

    0 0

    Hi,

    We have Windows Server 2008 R2 and use transactional replication. Early this week the replication started failing which could be because we ran an index rebuild on the Publisher.

    I tried adding verbose output using -Output C:\LogFile.txt -Outputverboselevel 2 to the log reader agent to get more information on the issue. I restarted the log reader agent. But the log file didnt get created at all.

    Can someone please tell me why this could happen? Where else can I find additional data on the reason for replication errors?


    0 0

    Hi All,

    We are receiving replication alerts with the following messages.

    TCP Provider: An existing connection was forcibly closed by the remote host.

    The process could not connect to Subscriber ''

    TCP Provider: The semaphore timeout period has expired.

    These set of errors comes daily at least once. I was doubting if it is network issue. To track the network we used Solar Wind tool and configured alert on ping request timing out and on packet loss.But the network alert and replication alert comes at different times.

    I wanted to know is there any setting in replication due to which these errors arise.

    In the Mege agent parameter listing, there is logintimeout and -querytimeout. Can some one point out the difference between two?

    Thanks!


     


    0 0

    Hi,

    We have transactional replication Setup in our company , a set of tables involved in replication needed to be reloaded on prod say about 12-13 Million rows .

    We decided to drop the articles and add it back to replication so that a new snapshot for the specific articles can be generated and the transfer of data is fast and no breakage in the replication.

    But what is the best practice or a threshold point for taking this route i.e dropping an article and adding it back ?

    I mean 

    when Is it good to go this route  i.e when the load is more than 10, 000 rows or 50.000 rows  100,000 or at what number do we start this process?

    Thanks,

    Jack


    0 0

    We are using filtered merge replication between server and clients. Previously all the clients used to update local database and then replication used to relay those to server to other clients. Recently to reduce traffic, since 99% of the time clients are connected, we decided to change the architecture so that the clients update the server directly and changes are downloaded and local db is kept up to date in case it goes offline. The problem is that since we changed this, we are getting lots of deadlocks.
    The filter table is the bottleneck and is involved in most the deadlocks. This table is queried by all the merge objects and is directly modified by the code as well.


    Regards Mayur, MCTS Windows,Web and Distributed applications


    0 0

    Hi all

    I noticed that after cheking the database relation in the suscribers after installing the merge replication.

    the relations in tables that I have in my Publisher database do not appear in the suscribers database.

    Is this normal ? Do I have to define again the tables relations in the suscribers ?

    Thanks in advance

    James


    0 0
  • 06/23/14--04:06: Merge replication
  • Hi all,

      I'm using Microsoft SQL Server Business Intelligence (64-bit) for the Merge Replication for both Publisher & Subscriber.

    After configuring Bi-directional Merge replication i'm getting the below error Message for some tables As Conflicted Rows.

    A row update at 'Server A' could not be propagated to 'Server B' . This failure can be caused by a constraint violation. Explicit value must be specified for identity column in table 'Table A' either when IDENTITY_INSERT is set to ON or when a replication user is inserting into a NOT FOR REPLICATION identity column.

    Note ; There is a trigger on  'Table A'  both side at Publisher & subscriber. which is dependent on other tables too.

     I'm new to Merge Replication Can u plz help for this error.

    Thanks in advance.


    Pavicoolman


    0 0
  • 06/16/13--06:24: Errors in Replication
  • Hi,

    we are facing 'out of syncs' in our Replication (transactional with updateable Subscribers)

    I checked MSrepl_errors and did a join to MSREPL_Commands over command ID - hope this is a valid one. In Comnands I found the  table (as article) which isn't updated.
    I run the sp_browsereplcmds on the xact_seqno ofMSREPL_Commandsand found statements that should update the table  - but they didn't. (the column in subscriber is not changed)

    The strange thing is, that in the errors table  an other table is named as causing an error (a constraint violation of a primary key) - thats confusing for me.

    For example:
    In errors an error on table A is writen. If a join command_id to commands table. Here TableB as article is listed. Running browserepcmds shows statements updating  tableB (which is the subscriber running out of sync)

    Sorry, I'm new in replication, so a perhaps silly question:
    Behind a seq_no there may be several statements, right?
    What happens if the first statement fails? Will the other statements be run on subscriber or will the process just stop?

    This issue is realy urgent for us, so I would be realy happy for some advice.

    Thanks

    Christian



    0 0

    I have a standalone sql 2008 28 GB  remote distributor on windows 2003 that we would like to migrate to a windows 2008 clustered sql 2008 server.  We do not have the distributor_admin password for publishers to connect to the distributor as previous dbas have left the company.  We have a 24x7 environment and we would like a small as possible downtime.  Is there any way without having to detach the db and recreate the publications that we could move the distributor?  Can we use log shipping?

    0 0

    Hi,

    We running a mobile sales - application, where users capture data through mobile devices into an SQLSERVER server db(s). We then have a REPORTSERVER server that maintains our 'working database(s)', for report development purposes. 

    Transactional replication has been setup between the 2 servers. Problem we encounter is replication failing on numerous occassions for some of the dbs, hence the need to restart / rebuild replication. 

    Do you perhaps have a quick fix or some suggestions to reolve this automatically without user intervention. It is affecting normal daily activities as reports need to be pulled from the REPORTSERVER on a daily basis.

    some common errors:

     - 'cannot DROP TABLE 'XXXXXXX' BECAUSE it is being referenced by object 'yyyyy'. error number: 3729
     - 'The subscription(s) have been marked inactive and must be reinitialized. NoSync subscriptions will need to be dropped and recreated.'Error number: 21074
     - 'Agent 'xxxx' is retrying after an error. 1 retries attempted. See agent job history in the Jobs folder for more details.'
     - 'The concurrent snapshot for publication 'xxxxx' is not available because it has not been fully generated or the Log Reader Agent is not running to activate it. 
        If generation of the concurrent snapshot was interrupted, the Snapshot Agent fo...'
    Rgards,

    Zimiso.


    0 0

    Hi all,

      Am experiencing this error in Microsoft SQL Server 2014 - 12.0.2000.8 (X64) Enterprise Edition (Build 7601: Service Pack 1).

    Error messages:
    Message: Failed to read BLOB column
    Stack:    at Microsoft.SqlServer.Replication.Snapshot.SqlServer.NativeBcpOutProvider.ThrowNativeBcpOutException(CConnection* pNativeConnectionWrapper)
       at Microsoft.SqlServer.Replication.Snapshot.SqlServer.NativeBcpOutProvider.BcpOut(String strBcpObjectName, String strBcpObjectOwner, String strBaseBcpObjectName, Boolean fUnicodeConversion, String strDataFile, String strLoadOrderingHint, String strWhereClause, Boolean useTableLockHint, Int32 bcpFileFormatVersion)
       at Microsoft.SqlServer.Replication.Snapshot.SqlServer.BcpOutThreadProvider.DoWork(WorkItem workItem)
       at Microsoft.SqlServer.Replication.WorkerThread.NonExceptionBasedAgentThreadProc()
       at Microsoft.SqlServer.Replication.AgentCore.BaseAgentThread.AgentThreadProcWrapper() (Source: MSSQLServer, Error number: 0)
    Get help: http://help/0
    Message: Shared Memory Provider: No process is on the other end of the pipe.
    Stack:  (Source: MSSQLServer, Error number: 233)
    Get help: http://help/233
    Message: Communication link failure
    Stack:  (Source: MSSQLServer, Error number: 233)
    Get help: http://help/233
    Message: Shared Memory Provider: No process is on the other end of the pipe.
    Stack:  (Source: MSSQLServer, Error number: 233)
    Get help: http://help/233
    Message: Communication link failure
    Stack:  (Source: MSSQLServer, Error number: 233)
    Get help: http://help/233


    Please can you assist me on this issue.



    0 0

    Good morning,

    I have a problem now that a client is using merge replication.

    there are 2 servers where people create products at the same time but the replication send conflict errors and some products does not replicate to the other server.

    the error says some like:

    A row insert at 'Server A' could not be propagated to 'Server B' . This failure can be caused by a constraint violation. Explicit value must be specified for identity column in table 'Table products' with unique key productsID.

    how can this be resolved ?. I thought replication managed this automatically.

    thank you

    James


    0 0

    As per the document in 'Configure IIS 7 for Web Synchronization' (http://technet.microsoft.com/en-us/library/ff714039(v=sql.110).aspx),

    The account used for the SQL Server Replication Listener must be a member of the PAL and be mapped to a login in the Publisher/Distributor database.

    Is this possible to do this if the Publisher/Distributor server and IIS server are on separate servers and separate workgroups. If not are there any workarounds? or should these server belong to the same domain?

    Thanks,


    0 0

    Good morning! I was reading the following article - http://msdn.microsoft.com/en-us/library/hh213151.aspx - which says to configure AlwaysOn, we need a Quorum for the cluster group. So I read the article for that, but I'm confused with the wording.

    Suppose I have this scenario: I have S1 (primary) and S2 (secondary) with the Synchronous, AlwaysOn configuration. And this... 'quorum' (I'm extremely unfamiliar with this terminology; sorry....). If I understand right, S1 and S2 will vote every XXX time saying "I'm healthy!" or "I'm not healthy!" and they have to remain voting or else "the cluster will turn offline for safety" <-- So the article for the quorum said. 

    What actually happens if I turn off / unplug S1 (essentially simulating a catastrophic hardware failure)? It can no longer vote in the quorum, so will the cluster turn off S2 for safety? Or will AlwaysOn kick in & pick up the information where S1 left off? Thank you for any advice :)



    0 0

    When I run the Vanilla Snapshot  agent that was created with the publication I get multiple parallel threads in 2012.  I did not get this when we ran R2 even though I was running concurrent.  This was the best method to avoid blocking on our production DB even though the Snapshot did take a lot longer to prepare.  Avoiding blocking is important in our case.

    So today in 2012, I had to add a MaxBcpThreads 1 to the params of the Snapshot agent job to get it back down to 1 BCP thread.

    Anyone else found this problem?  Or is it something else I'm missing

    Thanks

    ...Ray


    ...Ray


    0 0

    Hello,

    I'm querying the table dbo.MSmerge_conflicts_info on the publisher and the conflicts shown in that query are the real ones I can see on the View conflicts dialog within Microsoft Sql Server Management Studio. In the subscriber, I also see the conflicts in that table.

    The problem is the following: If I resolve one conflict with the View Conflicts dialog, this table is updated on the publisher and the number of entries for this conflict table dbo.MSmerge_conflicts_info is reduced. However, after the sinchronization between the publisher and the subscriber, the query in the subscriber is still returnning the old conflict and new ones are added (never is updated deleting the solved ones), this table is not refreshed and I cannot see the real pending conflicts on the subscriber as I can see on the same table in the publisher.

    Is there any way to obtain the real pending conflicts on the subscriber that were not solved in the publisher?

    Thanks in advance!


    0 0

    Hello,


    I have 2 SQL Server 2014 instances running on different servers.  I am testing replication services by using one instance as the publisher and the other as the subscriber.  I have created a publication on the push service and subscribe to it on the subscription server.  I have proper permissions define and I am only pushing one table.  Whenever I run the Snapshot agent from the publisher server it starts and then stops immediately.  The error I receive is "can't find path to c:\program files\Microsoft SQL Server\MSSQL\<instance>\repldata\unc".  Any Idea what this can mean?  I'm logged in as Administrator a nd still get this message.  Any help would be appreciated.

    Thx

    John G


    John Grace


    0 0
  • 06/26/14--12:39: No Sync
  • Is there a way with transactional immediate replication (SS 2012) to sync up two tables manually and then tell SQL Server to accept these with a "nosync" option or something similar?

    I've got a large table (400+ million rows) that I want to never reinitialize because it is so large.  I can figure out which rows are out of sync if replication gets "hung" or loses its mind and then manually sync up the tables.

    So, for example, let's say I get one of these warning messages that this table needs to be reinitialized.  Can I sync them up manually and then tell SQL Server to take them as is?  (So I'd really just like to use replication as a day-to-day feed.)

    Hope that makes sense.  Is there a way to tell Sql Server that the pub and sub are in sync?  


    0 0

    I am running SQL Server 2005 SP2 CU3, and have noticed this from time to time.  We periodically restore production databases back to our test environment and do so by first disabling publishing and distribution on the test publication servers.  We then restore the databases from production, and then re-run the replication script created from "Generate Scripts".  After this, we restart the Snapshot agents on all our publications which uses one distribution database and server to distribute to various subscriber servers, all of which are not updateable subscriptions.

     

    Every once in a while I notice that although Publisher To Distributor History and Distributor To Subscriber History have caught-up and report "No replicated transactions are available", the Undistributed Commands shows a number of commands still in the distribution database waiting to be applied to one or more subscriptions.  Sometimes 1 subscription will show 0 commands waiting, while another subscription to the same publication shows more.  Even if I wait it out, I notice no movement on the commands.

     

    If I run sp_browsereplcmds I can see a few updates, index creation commands, and a bunch of snapshot scripts waiting to be applied.  However, if I check these out, I notice that the tables involved are in synch with the publisher with no need of these commands to run.

     

    What is then happening?  I've tried to run the distribution agent clean-up job but this accomplishes nothing.  Usually, only after 3 days will the clean-up expired subscriptions job run and remove these "bad commands".

     

    How can I ensure that the undistributed commands are "clean" so that after re-establishing replication, I can ensure a zero value?

     

    Any help would be appreciated.


older | 1 | .... | 93 | 94 | (Page 95) | 96 | 97 | .... | 181 | newer