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 | .... | 98 | 99 | (Page 100) | 101 | 102 | .... | 181 | newer

    0 0
  • 08/29/13--07:34: Snapshot will not run
  • I am trying to create a new publication on a SQL 2008R2 instance that already has two publications running successfully. When the snapshot agent kicks in it is failing. The job created has the following in the history:

    Step 2:

    The replication agent encountered a failure. See the previous job step history message or Replication Monitor for more information.  The step failed.

    Step 3:

    Executed as user: domain\user. Agent shutdown. For more information, see the SQL Server Agent job history for job 'instance-publication-20'. [SQLSTATE 01000] (Message 20557)  Replication-Replication Snapshot Subsystem: agentinstance-publication-20 failed. The replication agent encountered a failure. See the previous job step history message or Replication Monitor for more information.  The step failed. [SQLSTATE 42000] (Error 14151).  The step failed.

    I have tried turning on logging by adding the relevant params to the job step, running from the command line, switching the NT user to myself (a sysadmin), changing snapshot from network path back to default path and publishing other databases. None of this has made any difference, the folder/files for the snapshot do not get created and I can't get any useful output.

    I also switched the owner of the database to be my own account and ran checkdb (no errors). It's compatibility level is 90.


    0 0

     

    HI everybody,

    i am using transactional replication, Publisher+Distributor - SQL2005 EntEd + SP2+CU11, Subscribers - SQL2005 ExpressEditionSP2. 

    What is the meaning of value 3 in the column "synchronization type" in a result set of procedure "sp_helpsubscription"? The BOL describes only the values 1 and 2.

    0 0
  • 08/14/14--04:50: Log Reader Agent Errors
  • On a server with 4 merge publications I'm getting errors from a Log Reader Agent.

    From documentations it seems to me that Log Reader Agent must be present only if there are some transactional publication, so I think that errors depends on this.

    Probably the Log Reader Agent was created some time ago with a transactional publication that no longer exists.

    So my question is: can I remove the Log Reader Agent?

    To remove it can I simply remove the associated job?

    The error are all like this:

    The process could not execute 'sp_repldone/sp_replcounters' on 'GEREONTK'. (Source: MSSQL_REPL, Error number: MSSQL_REPL20011)
    Get help: http://help/MSSQL_REPL20011

    Unable to execute procedure. The database is not published. Execute the procedure in a database that is published for replication. (Source: MSSQLServer, Error number: 18757)
    Get help: http://help/18757

    The process could not set the last distributed transaction. (Source: MSSQL_REPL, Error number: MSSQL_REPL22017)
    Get help: http://help/MSSQL_REPL22017

    Thanks,

    Roberto


    0 0

    I have a database with CDC enabled. I added transactional replication. SQL does what it should (remove the CDC capture job when it creates the log reader job). Replication is running without issues and so is CDC. The oldest non-distributed lsn (from DBCC Opentran) isn't changing though.

    Has anyone used CDC and replication together and encountered this issue?

    Thanks,

    Kim


    0 0

    I am trying to copy over SQL Server 2005 databases which currently in Windows Server 2003 to SQL Server 2005 which currently newly installed in new server.

    Is that anyway to copy all DB over at the same time, instead of copy individually one by one to save time. Or is there anyway to duplicate the whole SQL Server 2005 over.

    Thanks


    0 0

    I have this error and I am stuck so I have some questions

    I don't know if any of this is relevant
    The error followed the addition of 2 new SP's and a reinitialisation of the subscriptions new snapshot
    I am synchronising direct to the sever
    The table I expect to be causing the problem has only 26,000 rows but it is my biggest and could easily receive 1,000 changes between syncs
    The publisher range was set to 10,000 and the subscriber range to 1,000
    Automatically manage Identity ranges is set to automatic
    The id column is an INT
    The next Starting Value is 2147479395 (6,252 from the Max)

    I have reduced publisher changes to 1,000 and it appears to have worked OK

    It looks to me that by reducing the publisher range to 1,000 (within the scope of the next starting value) seems to have been sorted.
    But
    I would have expected the identity range to be managed to use up unused numbers with only 26,000 rows in the table there would be plenty of scope or is there something I should do?


    jnc


    0 0

    I have C# project that I use to create a pull merge replication subscription. This project generates a DLL that has COM interop support. Our main application is not written in a .Net language.  Having the COM support on my subscription assembly allows me to call into the .Net world from our main program.

    I have been using this methodology successfully since SQL Server 2005 through 2012.

    However, in SQL 2014 some of the assemblies are now version .Net 4 but others are still .Net 2.

    Specifically, my project framework target is .Net 4 and it references:

    • Microsoft.SqlServer.ConnectionInfo - .Net 2.x
    • Microsoft.SqlServer.Management.Sdk.Sfc - .Net 2.x
    • Microsoft.SqlServer.Replication - .Net 4
    • Microsoft.SqlServer.Rmo - .Net 4
    • Microsoft.SqlServer.Smo - .Net 2

    When I call into my assembly I'm receiving this error:

    Mixed mode assembly is built against version 'v2.0.50727' of the runtime and cannot be loaded in the 4.0 runtime without additional configuration information.

    I found the following link which discuss this error:

    http://social.msdn.microsoft.com/Forums/vstudio/en-US/1f60a379-e2e3-46b9-b343-0235486fc746/mixed-mode-assembly-is-built-against-version-v2050727-of-the-runtime-and-cannot-be-loaded-in-the?forum=clr

    The link in that forum to stack overflow talks about adding

    <startupuseLegacyV2RuntimeActivationPolicy="true"><supportedRuntimeversion="v4.0"/></startup>

    to my application .config file, but my assembly does not have a app.config file.

    If anyone can point me in the right direction I would appreciate it.

    This link mentions an AdventureWorks example for 2014 replication but I cannot find the source. That might be enough to get me going in the right direction.

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

    Thanks, Rick


    0 0

    Hi,

    We have SQL 2012 and have configure P2P replication between servers and now our P2P replication is failing with below error:

    Procedure or function sp_MSupd_<> has too many arguments specified.

    Could you please help !


    Rahul


    0 0

    Hi All!

    I am facing issues with Merge Replication in SQL Server 2012. The replication type is push-based with both the publisher and the distributor on the same server. Currently I have 5 subscribers which were replicating perfectly till end last week but today I'm facing metadata cleanup issues with all of them. Here is the error :-

    -------------------------------------------------------------------------------------------------------------------

    Source:  Merge Replication Provider
    Number:  -2147199466
    Message: The merge process could not perform retention-based metadata cleanup in database 'XYZ'. If this failure continues, try increasing the query timeout for this process, or try reducing the retention period. When troubleshooting, restart the synchronization with verbose history logging and specify an output file to which to write.
    2014-06-30 01:23:59.322 Percent Complete: 0
    2014-06-30 01:23:59.322 Category:SQLSERVER
    Source:  XYZ-SQL2012
    Number:  206
    Message: Operand type clash: bigint is incompatible with uniqueidentifier
    2014-06-30 01:23:59.385 Percent Complete: 0
    2014-06-30 01:23:59.385 Category:SQLSERVER
    Source:  XYZ-SQL2012
    Number:  206

    --------------------------------------------------------------------------------------------------------------------

    I can see that all the subscribers are replicating perfectly every 15 mins with the server yet they are showing the above error. For all the subscribers, the subscription expiration is set for an interval of 14 days. I have tried checking the logs but just couldn't get any clues and don't know where to start looking.

    Any help would be highly appreciated.

    Thanks


    0 0

    If table is a part of replication and want to add column in a table, is it necessary to remove table form replication and added it back when Alter operation done? What happened internally if I add/remove column from replication meaning will that flush data from distribution database?


    Rahul


    0 0

    Hi, I have successfully setup replication with Allow Initialization From Backup Files option enable.

    By normal replication setup, if I need add new article into replication. I can just adding through management studio and run snapshot agent.

    But since it is setup without snapshot agent how can I do if I need add new articles?

    Cheers

    Ken



    0 0

    Hi All,

    Am doing a testing on replication migration from 2008 R2(SP2) to sql server 2014. I have some of the database in 2005 compatibility, I tried creating using 'initiate from backup of option' for which I tried to restore the database  it throws compatibility error. When I try to replicate 2005 compatibility database to 2014 instance, data base compatibility automatically changes to 2008. Though we have a drop down to create a database in 2005 it throws compatibility error.

    Is there any way to avoid this, or will this affect the performance? as we are planning to implement the same in Prod server in near future.




    Best Regards Moug


    0 0

    Hi Brandon

    I've  posted the problem below also on the forum http://www.sqlservercentral.com/Forums/Topic1601162-1549-1.aspx
    but till now we had no respons, Is it possible to have a short look at our problem and provide us some advice how to proceed?

    thanks in advance

    for test purposes we used the example program from Brandon Williams on this url: http://code.msdn.microsoft.com/SQL-Server-Express-Merge-4e01e119
    with as parameters for our testlab servers:
            // Define the server, subscription, publication, and database names.
            string subscriberName = "MORSWV447";
            string subscriptionDbName = "TicketOrdersSub";
            string publisherName = "MORSWV558";
            string publisherFailoverPartnerName = "MORSWV559";
            string publicationName = "TicketOrders";
            string publicationDbName = "TicketOrdersPub";
            //string distributorName = "MORSWV560";

    to evaluate DRP scenarios we added the parameter agent.PublisherFailoverPartner = (Mirror server name)

    If we do the failover while the program is running (but not replicating) it is working.   

    Initializing
    Connecting to Publisher 'MORSWV558'
    Connecting to mirrored instance of Publisher 'MORSWV559'
    Retrieving publication information
    Retrieving subscription information.
    Uploading data changes to the Publisher
    No data needed to be merged.
    Downloading data changes to the Subscriber
    No data needed to be merged.
    Merge completed with no data changes processed.
    Done!


    If we close and restart the program it can't find the failoverpartner anymore.      

    Initializing
    Connecting to Publisher 'MORSWV558'
    The merge process could not connect to the Publisher 'MORSWV558:TicketOrdersPub'. Check to ensure that the server is running.
    The merge process could not connect to the Publisher 'MORSWV558:TicketOrdersPub'. Check to ensure that the server is running.
    The process could not access database 'TicketOrdersPub' on server 'MORSWV558'.
    Cannot open database "TicketOrdersPub" requested by the login. The login failed.
    Login failed for user 'xxx'.
    Error: The subscription could not be synchronized. Verify that the subscription has been defined correctly.

    InnerException = {"The merge process could not connect to the Publisher '(Primary Principal)PublicationDBName)'. Check to ensure that the server is running."}

    What did we do wrong here? or is this a bug in the RMO MergePullSubscription.SynchronizationAgent?

    We used for all server Microsoft SQL Server standard Edition 2008 R2 SP2 CU3 on Windows Server 2008 R2 Sp2 - 64 Bit.
    By using the cmd line executable replmerge.exe we can use this parameter as expected.

    thanks in advance for sorting this out.
    Paul


    0 0

    I am working on a Merge Replication. Server is SQL 2012, Clients are 2012 Express. I am able to initialize from a snaphost. As well, any changes made at the main server, come down to the client fine, however if I make a change to a table on the Client, I get the error when I try to run the subscription to update.

    Interestingly, I tested exactly the same setup, on a PC running a full version of SQL 2012, and it worked fine. 

    The clients are not members of the server domain, and are connected via a VPN.

    This is the relevant log info

    TRAVERSESVR2\TRAVERSE11 is the main server

    SDLLC13\TRAVTABLE is the Client

    2014-08-19 00:08:03.425 OLE DB Subscriber 'SDLLC13\TRAVTABLET': {call sys.sp_MSadd_merge_history90 (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
    2014-08-19 00:08:03.440 The merge process could not enumerate changes at the 'Subscriber'. When troubleshooting, restart the synchronization with verbose history logging and specify an output file to which to write.
    2014-08-19 00:08:03.440 OLE DB Distributor 'TRAVERSESVR2\TRAVERSE11': {call sys.sp_MSadd_merge_history90 (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
    2014-08-19 00:08:03.534 OLE DB Subscriber 'SDLLC13\TRAVTABLET': {call sp_MSmergeupdatelastsyncinfo (?,?,?)}
    2014-08-19 00:08:03.597 OLE DB Subscriber 'SDLLC13\TRAVTABLET': {call sp_MSmergeupdatelastsyncinfo (?,?,?)}
    2014-08-19 00:08:03.597 The Merge Agent was unable to update information about the last synchronization at the Subscriber. Ensure that the subscription exists at the Subscriber, and restart the Merge Agent. 
    2014-08-19 00:08:03.597 OLE DB Publisher 'TRAVERSESVR2\TRAVERSE11': {call sp_MSmergeupdatelastsyncinfo (?,?,?)}
    2014-08-19 00:08:03.597 The merge process was unable to update last synchronization information at the Publisher.

    What should I be looking for here?


    0 0

    Dear all,

    I'm facing problem with subscribtion creation:

    use [LPR] exec sp_addsubscription

    @publication = N'UV Publication',

    @subscriber = N'DWH_X',

    @destination_db = N'LPR',

    @sync_type = N'initialize with backup',

    @subscription_type = N'pull',

    @update_mode = N'read only',

    @backupdevicetype='DISK',

    @backupdevicename='\\Source\SQLBACKUP\uv\LPR.bak' GO

    I'm running it on SQL server 2012 Pro and getting error:

    Msg 8115, Level 16, State 2, Procedure sp_MSsetupnosyncsubscriptionwithlsn, Line 237 Arithmetic overflow error converting expression to data type nvarchar.

    Problem appeared when we changed source database from SQL server 2005 to SQL Server 2008 R2 (SP2 is installed as well).

    Could you please advise, how I can solve this problem. I can't find any solution.

    Thank you






    0 0
  • 08/19/14--05:48: Snap-shot replication
  • Hi Team,

    Last Thursday i have configured snapshot replication at that time it was showing successfully but today i have checked it was failing. below error:

    Replication-Replication Transaction-Log Reader Subsystem: agent trans-1 failed. The process could not execute 'sp_replcmds' on 'ggg2'. and

    Executed as user: NT AUTHORITY\SYSTEM. Replication-Replication Snapshot Subsystem: agent xxxx failed. Unable to start execution of step 2 (reason: Error authenticating proxy sds\subb2, system error: Logon failure: unknown user name or bad password.).  The step failed. [SQLSTATE 42000] (Error 14151).  The step failed.

    Now i got the correct credentials please suggest me where can i have change.

    Greatly appreciate anybody help on this.


    subu




    0 0

    I have got a SQL application which needs to be merged with a new CRM applicaiton. so data coming into the source tables, then triggers push certain fields into the Staging table with a flag '0' and then CRM application job picks up from staging table and sets the flag to '1'.

    same is true if the data for the same field is initiated from the CRM and needs to go into my application.

    All well and good.

    Now considering 100s of transactions per minute is the above solution workable. i can think of other alternatives like

    SIS data replication service broker (limited knowledge) etc


    0 0

    Hello,

    I have configured Transnational replication on Moss 2007 content DB over WAN, ?But it works well with small dbs of size 10-12 GB but with 40-60GB database sites are running in error like 404 Site not found....Checked in logs not luck found there also..

    Any help guys.....

    Regards,

    Ashish




    0 0

    Hello,

    Can someone please tell me the exact difference between is_published and is_replicated columns of sys.tables? I know is_published is inherited from sys.objects table , but purpose of both the columns are same. However sometimes for some replicated tables i have seen is_published = 1 and is_replicated = 0 and for another published database tables value of both columns are 1.

    It is bit confusing. Can you please explain?

    Thanks in Advance.

    -Malkesh


    0 0

    Hello

    We have a nightly snapshot replication installed since a few month now.

    2 days ago I got this error for the first time, last night it went fine again, and then this night I got the error again:

    Error messages:

    <dir>

    Message: The replication agent had encountered a file compression (cabinet) library error while calling 'FCIAddFile(pszSourceFile = "D:\Fenevision\repl\unc\REPLICATION NAME\20140821010018\TableName_2#20.bcp")'.
    Stack:    at Microsoft.SqlServer.Replication.CabCreator.ThrowWrappedFciException(String strFormattedFCIAPIString)
       at Microsoft.SqlServer.Replication.CabCreator.AddFileToCabinet(String strFileToAdd)
       at Microsoft.SqlServer.Replication.Snapshot.SnapshotFileProcessor.DoAddFileToCabinet(String strSourceFile)
       at Microsoft.SqlServer.Replication.Snapshot.SnapshotFileProcessor.AgentThreadProc()
       at Microsoft.SqlServer.Replication.AgentCore.BaseAgentThread.AgentThreadProcWrapper() (Source: MSSQL_UNKNOWN, Error number: 9)
    Get help: http://help/9

    </dir>

    The really wierd part is that it worked last night, so I can't really explain it.

    I checked if others had this error, and the only case I could find were:
    - Strange characters in the name of the file (Greek)
    - CAB File more than 2 GB (my file is 400 MB)
    - CAB File with more than 64k files (my CAB contains 2300 files)

    I also checked the harddrive and it has 120 GB of free space.

    Thanks in advante for all help you could provide

    Regards


older | 1 | .... | 98 | 99 | (Page 100) | 101 | 102 | .... | 181 | newer