Replication Log

Hi,
Where can I see log of replication. I need to find out who ( User name) actually has performed the replication in the system. Can you please let me know where can I see it.
Thanks.

Check this blog -
http://blogs.msdn.com/b/sqlqueryprocessing/archive/2006/11/14/query-execution-timeouts-in-sql-server-part-1-of-2.aspx
Check your SQL Server error logs to see if you find any Memory related errors or Memory dumps. It looks like there was a memory crunch during the time forcing log reader to stop.
Also make sure that you have configured your memory settings properly.
Regards, Ashwin Menon My Blog - http:\\sqllearnings.com

Similar Messages

  • Replication Log, PC Shutdown

    If a computer is shutdown before replication has completed, does it show up in the replication log? If so, how does it show in the replication log?

    Hi Jonathan,
    No, a system shutdown won't be explicitly recorded in the dbremote output / console log. dbremote entries typically look like this between dbremote runs (shut down / start-up):
         I. 2014-04-24 16:41:06. Execution completed
         I. 2014-04-24 16:41:09. SQL Remote Message Agent Version 16.0.0.1824
    System Shutdowns / Start-ups are recorded in the "System" Event log on Microsoft Windows:
         Control Panel > Administrative Tools > Event Viewer > System
    Look for 'Kernel-General' entries:
         ===========================================
         Log Name:      System
         Source:        Microsoft-Windows-Kernel-General
         Date:          23/4/2014 5:08:31 PM
         Event ID:      13
         Task Category: None
         Level:         Information
         Keywords:     
         User:          N/A
         Computer:      hostname
         Description:
         The operating system is shutting down at system time 2014-04-23T21:08:31.001823500Z.
         ===========================================
    Regards,
    Jeff Albion
    SAP Active Global Support

  • Replication Log Reader stopped unexpectedly

    This morning our websites stopped serving pages.  Whilst investigating I notice that the Replication Sql LogReader had stopped running and was reporting the error:
    "SubSystem Message - Job 'XXX582060-XXXXX-1' (0x6D6877EFE4F8EA4D930F8C967FE49BE5), step
    2 - A time out occurred while waiting for memory resources to execute the query. Rerun the query."
    I have restarted the LogReader and it seems to be working fine but I'd really like to get to the bottom of why it stopped in the first place so I can prevent happening in the future.
    Any help would be great.
    Thanks
    Mike

    Check this blog -
    http://blogs.msdn.com/b/sqlqueryprocessing/archive/2006/11/14/query-execution-timeouts-in-sql-server-part-1-of-2.aspx
    Check your SQL Server error logs to see if you find any Memory related errors or Memory dumps. It looks like there was a memory crunch during the time forcing log reader to stop.
    Also make sure that you have configured your memory settings properly.
    Regards, Ashwin Menon My Blog - http:\\sqllearnings.com

  • Transaction log usage grows due to replication even if I don't use replication at all

    Hi
    The transaction log usage keeps growing a lot on my user database since few days back. the database is in full recovery model and I do transaction log backups every 10 minutes. The DB was part of Database Mirroring but I removed it. The usage was controlled
    for many years by the backups but something happened that is messing up the transaction log
    this is DBCC OPENTRAN
    Transaction information for database 'MyDB'.
    Replicated Transaction Information:
            Oldest distributed LSN     : (0:0:0)
            Oldest non-distributed LSN : (1450911:6823:1)
    DBCC execution completed. If DBCC printed error messages, contact your system administrator.
    log_reuse_wait_desc reports REPLICATION
    the funny thing is that I am not using replication at all. I am using CDC.
    To reduce the transaction log usage I run below statement every day since the problem started
    EXEC sp_repldone @xactid = NULL, @xact_segno = NULL, 
        @numtrans = 0, @time = 0, @reset = 1
    Any idea what should I do to solve this problem and be back on a normal situation?
    BTW, The server is SQL 2012 (11.0.2383)
    Thanks
    Javier Villegas |
    @javier_vill | http://sql-javier-villegas.blogspot.com/
    Please click "Propose As Answer" if a post solves your problem or "Vote As Helpful" if a post has been useful to you

    CDC uses the replication log reader agent and if you manually ran sp_repldone like that you lost information in your CDC capture.  If the capture job can't keep up with the workload or is not running for CDC, you would have the exact problems you describe.
     If you execute sp_repldone like that, you might as well disable CDC.
    http://technet.microsoft.com/en-us/library/dd266396(v=sql.100).aspx
    Jonathan Kehayias | Principal Consultant | MCM: SQL Server 2008
    My Blog |
    Twitter |
    MVP Profile
    Training |
    Consulting |
    Become a SQLskills Insider
    Troubleshooting SQL Server

  • Event ID: 5014, 5004 The DFS Replication Service is stopping communication with partner / Error 1726 (The remote procedure call failed.)

    I'm replicating between two servers in two sites (Server A - Server 2012 R2 STD, Server B - Server 2008 R2) over a VPN (Sonicwall Firewall).  Though the initial replication seems to be
    happening it is very slow (the folder in question is less than 3GB).  I'm seeing these in the event viewer every few minutes:
    The DFS Replication service is stopping communication with partner PPIFTC for replication group FTC due to an error. The service will retry the connection periodically.
    Additional Information:
    Error: 1726 (The remote procedure call failed.)
    and then....
    The DFS Replication service successfully established an inbound connection with partner PPIFTC for replication group FTC.
    Here are all my troubleshooting steps (keep in mind that our VPN is going through a SonicWall <--I increased the TCP timeout to 24 hours):
    -Increased TCP Timeout to 24 hours 
    -Added the following values on both sending and receiving members and rebooted server
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
    Value =DisableTaskOffload
    Type = DWORD
    Data = 1
    Value =EnableTCPChimney
    Type = DWORD
    Data = 0
    Value =EnableTCPA
    Type = DWORD
    Data = 0
    Value =EnableRSS
    Type = DWORD
    Data = 0
    ---------------------------------more troubleshooting--------------------------
    -Disabled AntiVirus on both members
    -Made sure DFSR TCP ports 135 & 5722 are open
    -Installed all hotfixes for 2008 R2 (http://support.microsoft.com/kb/968429) and rebooted
    -Ran NETSTAT –ANOBP TCP and the DFS executable results are listed below:
    Sending Member:
    [DFSRs.exe]
      TCP    10.x.x.x:53            0.0.0.0:0             
    LISTENING       1692
    [DFSRs.exe]
      TCP    10.x.x.x:54669        
    10.x.x.x:5722          TIME_WAIT       0
      TCP    10.x.x.x:54673        
    10.x.x.x:5722          ESTABLISHED     1656
     [DFSRs.exe]
      TCP    10.x.x.x:64773        
    10.x.x.x:389           ESTABLISHED     1692
    [DFSRs.exe]
      TCP    10.x.x.x:64787        
    10.x.x.x:389           ESTABLISHED     1656
     [DFSRs.exe]
      TCP    10.x.x.x:64795        
    10.x.x.x:389           ESTABLISHED     2104
    Receiving Member:
    [DFSRs.exe]
      TCP    10.x.x.x:56683        
    10.x.x.x:389           ESTABLISHED     7472
     [DFSRs.exe]
      TCP    10.x.x.x:57625        
    10.x.x.x:54886         ESTABLISHED     2808
    [DFSRs.exe]
      TCP    10.x.x.x:61759        
    10.x.x.x:57625         TIME_WAIT       0
      TCP    10.x.x.x:61760        
    10.x.x.x:57625         TIME_WAIT       0
      TCP    10.x.x.x:61763        
    10.x.x.x:57625         TIME_WAIT       0
      TCP    10.x.x.x:61764        
    10.x.x.x:57625         TIME_WAIT       0
      TCP    10.x.x.x:61770        
    10.x.x.x:57625         TIME_WAIT       0
      TCP    10.x.x.x:61771        
    10.x.x.x:57625         TIME_WAIT       0
      TCP    10.x.x.x:61774        
    10.x.x.x:57625         TIME_WAIT       0
      TCP    10.x.x.x:61775        
    10.x.x.x:57625         TIME_WAIT       0
      TCP    10.x.x.x:61776        
    10.x.x.x:57625         TIME_WAIT       0
      TCP    10.x.x.x:61777        
    10.x.x.x:57625         TIME_WAIT       0
      TCP    10.x.x.x:61778        
    10.x.x.x:57625         TIME_WAIT       0
      TCP    10.x.x.x:61779        
    10.x.x.x:57625         TIME_WAIT       0
      TCP    10.x.x.x:61784        
    10.x.x.x:52757         ESTABLISHED     7472
    [DFSRs.exe]
      TCP    10.x.x.x:63661        
    10.x.x.x:63781         ESTABLISHED     4880
    ------------------------------more troubleshooting--------------------------
    -Increased Staging to 32GB
    -Opened the ADSIedit.msc console to verify the "Authenticated Users" is set with the default READ permission on the following object:
    a. The computer object of the DFS server
    b. The DFSR-LocalSettings object under the DFS server computer object
    -Ran
    ping <var>10.x.x.x</var> -f -l 1472 and got replies back from both servers
    -AD replication is successful on all partners
    -Nslookup is working so DNS is working
    -Updated NIC drivers on both servers
    - I ran the following to set the Primary Member:
    dfsradmin Membership Set /RGName:<replication group name> /RFName:<replicated folder name> /MemName:<primary member> /IsPrimary:True
    Then Dfsrdiag Pollad /Member:<member name>
    I'm seeing these errors in the dfsr logs:
    20141014 19:28:17.746 9116 SRTR   957 [WARN] SERVER_EstablishSession Failed to establish a replicated folder session. connId:{45C8C309-4EDD-459A-A0BB-4C5FACD97D44} csId:{7AC7917F-F96F-411B-A4D8-6BB303B3C813}
    Error:
    + [Error:9051(0x235b) UpstreamTransport::EstablishSession upstreamtransport.cpp:808 9116 C The content set is not ready]
    + [Error:9051(0x235b) OutConnection::EstablishSession outconnection.cpp:532 9116 C The content set is not ready]
    + [Error:9051(0x235b) OutConnection::EstablishSession outconnection.cpp:471 9116 C The content set is not ready]
    ---------------------------------------more troubleshooting-----------------------------
    I've done a lot of research on the Internet and most of it is pointing to the same stuff I've tried.  Does anyone have any other suggestions?  Maybe I need to look somewhere
    else on the server side or firewall side? 
    I tried replicating from a 2012 R2 server to another 2012 server and am getting the same events in the event log so maybe it's not a server issue. 
    Some other things I'm wondering:
    -Could it be the speed of the NICs?  Server A is a 2012 Server that has Hyper-V installed.  NIC teaming was initially setup and since Hyper-V is installed the NIC is a "vEthernet
    (Microsoft Network Adapter Multiplexor Driver Virtual Switch) running at a speed of 10.0Gbps whereas Server B is running a single NIC at 1.0Gbps
    -Could occasional ping timeout's cause the issue?  From time to time I get a timeout but it's not as often as the events I'm seeing.  I'm getting 53ms pings.  The folder
    is only 3 GB so it shouldn't take that long to replicate but it's been days.  The schedule I have set for replication is mostly all day except for our backup times which start at 11pm-5am.  Throughout the rest of the time I have it set anywhere from
    4Mbps to 64 Kbps.  Server A is on a 5mb circuit and Server B is on a 10mb circuit. 

    I'm seeing the same errors, all servers are running 2008 R2 x64. Across multiple sites, VPN is steady and reliably.
    185 events from 12:28:21 to 12:49:25
    Events are for all five servers (one per office, five total offices, no two in the same city, across three states).
    Events are not limited to one replication group. I have quite a few replication groups, so I don't know for sure but I'm running under the reasonable assumption that none are spared.
    Reminder from original post (and also, yes, same for me), the error is: Error: 1726 (The remote procedure call failed.)
    Some way to figure out what code triggers an Event ID 5014, and what code therein specifies an Error 1726, would extremely helpful. Trying random command line/registry changes on live servers is exceptionally unappealing.
    Side note, 1726 is referenced here:
    https://support.microsoft.com/kb/976442?wa=wsignin1.0
    But it says, "This RPC connection problem may be caused by an unstable WAN connection." I don't believe this is the case for my system.
    It also says...
    For most RPC connection problems, the DFS Replication service will try to obtain the files again without logging a warning or an error in the DFS Replication log. You can capture the network trace to determine whether the cause of the problem is at the network
    layer. To examine the TCP ports that the DFS Replication service is using on replication partners, run the following command in a
    Command Prompt window:
    NETSTAT –ANOBP TCP
    This returns all open TCP connections. The connections in question are "DFSRs.exe", which the command won't let you filter for.
    Instead, I used the NETSTAT command as advertised, dumping output to info.txt:
    NETSTAT -ANOBP TCP >> X:\info.txt
    Then I opened Excel and manually opened the .TXT for the open wizard. I chose fixed-width fields based on the first row for each result, and then added a column:
    =IF(A3="Can not", "Can not obtain ownership information", IF(LEFT(A3,1) = "[", A3&B3&C3, ""))
    Dragging this down through the entire file let me see that row (Row F) as the file name. Some anomalies were present but none impacted DFSrs.exe results.
    Finally, you can sort/filter (I sorted because I like being able to see everything, should I choose to) to get just the results you need, with the partial rows removed from the result set, or bumped to the end.
    My server had 125 connections open.
    That is a staggering number of connections to review, and I feel like I'm looking for a needle in a haystack.
    I'll see if I can find anything useful out, but a better solution would be most wonderful.

  • Transactional replication very slow with indexes on Subscriber table

    I have setup Transactional Replication for one of our databases where one table with about 5mln records is replicated to a Subsriber database. With every replication about 500-600.000 changed records are send to the Subscriber.
    Since one month I see very strange behaviour when I add about 10 indexes to the Subscriber table. As soon as I have added the indexes replication speed becomes extremely slow (almost 3 hours for 600k records). As soon as I remove the indexes the replication
    is again very fast, about 3 minutes for the same amount of records.
    I've searched a lot on the internet to solve this issue but can't find any explaination for this strange behaviour after adding the indexes. As far as I know it doesn't have to be a problem to add indexes to a Subscriber table, and it hasn't been before on
    another replication configuration we use.
    Some information from the Replication Log:
    With indexes on the Subscriber table
    Total Run Time (ms) : 9589938 Total Work Time : 9586782
    Total Num Trans : 3 Num Trans/Sec : 0.00
    Total Num Cmds : 616245 Num Cmds/Sec : 64.28
    Total Idle Time : 0 
    Writer Thread Stats
    Total Number of Retries : 0 
    Time Spent on Exec : 9580752 
    Time Spent on Commits (ms): 2687 Commits/Sec : 0.00
    Time to Apply Cmds (ms) : 9586782 Cmds/Sec : 64.28
    Time Cmd Queue Empty (ms) : 5499 Empty Q Waits > 10ms: 172
    Total Time Request Blk(ms): 5499 
    P2P Work Time (ms) : 0 P2P Cmds Skipped : 0
    Reader Thread Stats
    Calls to Retrieve Cmds : 2 
    Time to Retrieve Cmds (ms): 10378 Cmds/Sec : 59379.94
    Time Cmd Queue Full (ms) : 9577919 Full Q Waits > 10ms : 6072
    Without indexes on the Subscriber table
    Total Run Time (ms) : 89282 Total Work Time : 88891
    Total Num Trans : 3 Num Trans/Sec : 0.03
    Total Num Cmds : 437324 Num Cmds/Sec : 4919.78
    Total Idle Time : 0 
    Writer Thread Stats
    Total Number of Retries : 0 
    Time Spent on Exec : 86298 
    Time Spent on Commits (ms): 282 Commits/Sec : 0.03
    Time to Apply Cmds (ms) : 88891 Cmds/Sec : 4919.78
    Time Cmd Queue Empty (ms) : 1827 Empty Q Waits > 10ms: 113
    Total Time Request Blk(ms): 1827 
    P2P Work Time (ms) : 0 P2P Cmds Skipped : 0
    Reader Thread Stats
    Calls to Retrieve Cmds : 2 
    Time to Retrieve Cmds (ms): 2812 Cmds/Sec : 155520.63
    Time Cmd Queue Full (ms) : 86032 Full Q Waits > 10ms : 4026
    Can someone please help me with this issue? Any ideas? 
    Pim 

    Hi Megens:
    Insert statement might be slow with not only indexes and few others things too
    0) SQL DB Blocking during inserts
    1) If any insert triggers are existed
    2) Constraints - if any
    3) Index fragmentation
    4) Page splits / fill factor
    Without indexes inserts will be fast because, each time when new row going to insert to the table, SQL Server will do
    1) it will check for the room, if no room page splits will happen and record will placed at right place
    2) Once the record updated all the index should be update
    3) all these extra update work will cause can make insert statement bit slow
    Its better to have index maintenance jobs frequently to avoid fragmentation.
    If every thing is clear on SQL Server Side, you need look up on DISK IO, N/W Latency between the servers and so on
    Thanks,
    Thanks, Satish Kumar. Please mark as this post as answered if my anser helps you to resolves your issue :)

  • ACS replication issue on VMware ESX 3.5

    I have just installed ACS 4.2 on two VMware hosts. I've configured database replication but it won't work. The error message is "shared secret mismatch". This error message occurs if a NAT device is in the path (which it isn't in this case) or if the tcp header is otherwise changed during transmission. I'm wondering if VMware is adding something to the TCP header. Has anyone come across this problem before or has anyone successfully implemented ACS replication when both hosts are on VMware?
    Thanks.

    Hi,
    I see that you are getting "shared secret mismatch error" under database replication logs. Just wanted to inform you that this is not because of nat'ed device. This happens when we have different keys for AAA servers on primary and secondary ACS.
    The primary server must be configured as an AAA server and must have a key.
    The secondary server must have the primary server configured as an AAA
    server and its key for the primary server must match the primary servers own
    key. The shared secret key should be same on the both the ACS's.
    I am sending you one link for Setting Up Replication for Cisco Secure ACS, I
    am sure this example with screen shots gives you better understanding.
    Please visit the below suggested ULR:
    http://www.cisco.com/en/US/products/sw/secursw/ps2086/products_configuration
    _example09186a00800e518a.shtml
    If that doesn't resolve the issue, please let me know if you see any server with this ip address 127.0.0.1.
    HTH
    JK
    -Plz rate helpful posts-

  • ACS 4.2 Database replication issue

    Hello Experts,
    Hope you are all doing well. I need your help in ACS database replication, I want to do replication between ACS servers. The issue i am facing is that there is no error in ACS replication log. It just says outbound replication started. and sits there no other error message is shown. I can successfully telnet secondary server's destination port 2000. But when i hit the replication button from primary server, i do not observe any hit count on my ASA ACL on which i allowed tcp 2000 for destination secondary server.I also checked my syslog server if there is any traffic denied between these 2 ACS servers but found nothing. I also did wireshark captures on the interfaces but no traffic is initiated when i press replicate now button. Initially i thought its a machine issue, but same behavior is shown when i swapped primary----to secondary. There are other applications running on both the servers which requires JAVA. Like Cisco IME etc. Can it be JAVA issue? Please help me out. i am using Release 4.2(0) Build 124 on both servers.Attached below is the Replication LOG snapshot,
    Regards,
    Rizwan.

    https://supportforums.cisco.com/discussion/11382366/problems-witch-acs-42-replication
    https://supportforums.cisco.com/discussion/11363046/replication-problem-acs-ver-42

  • DAG Replication Network Isolation from MAPI

    Hi,
    Recently We have implemented Exchange 2010 SP2 DR setup.
    We have two sites Prod and DR. We are facing some issue in DAG replication Network (Replication Adapter).
    We are using 10.10.10.x for Mapi Networks and 192.168.1.x for Replication Network for Prod and 10.11.10.x for MAPI and 192.168.2.x for Replications.
    As per Microsoft recommended, We configured replication adapters and added static routes for Replication Network.
    We understand, Replicarion adapter is used for DAG Replication (Log Shipping and Seeding) and configured forewall to allow tonly  DAG port 64327 for replication Vlans between sites.
    Now, When we check the replication network hit in firewall. Its still using MAPI Network (MAPI Nic) to communication with DR sites. Replication Nics is not working properly.
    Please let me know, How to isolate the MAPI and Replication Networks. Do we need configure Replication Port in DAG properties.
    How to check whether Replication Network is working between the sites.
    Regards
    M
     

    My Problem is, While seeding is happening between Primary Site to DR Site. Connections are going only via MAPI Networks. It is not using Replication Netowork. I have added the static route in all the prod and DR Mailbox Servers. But I have not
    configured Replication Port in DAG properties. And also, I allowed only Port 64327 for Replication Vlan in both Primary and DR. Please let me know if you have any solutions. Regards M
    That's expected if you are just using the EMC, or using standard options via EMS
    What happens if you use
    http://technet.microsoft.com/en-us/library/dd335201(v=exchg.141).aspx
    Update-MailboxDatabaseCopy -Network
    and
    http://technet.microsoft.com/en-us/library/dd335158.aspx
    Managing Mailbox Database Copies
    To specify the networks you want to use for seeding, use the Network parameter when running the
    Update-MailboxDatabaseCopy cmdlet and specify the DAG networks that you want to use. If you don't use the
    Network parameter, the system uses the following default behavior for selecting a network to use for the seeding operation:
    If the source server and target server are on the same subnet and a replication network has been configured that includes the subnet, the replication network will be used.
    If the source server and target server are on different subnets, even if a replication network that contains those subnets has been configured, the client (MAPI) network will be used for seeding.
    If the source server and target server are in different datacenters, the client (MAPI) network will be used for seeding.
    Cheers,
    Rhoderick
    Microsoft Premier Field Engineer, Exchange
    Blog:
    http://blogs.technet.com/rmilne  Twitter:
       LinkedIn:
       Facebook:
    Note: My posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

  • ACS SE Database replication fails

    Hello, I recently upgraded our ACS SEs from 4.0 to 4.1. All appeared to go OK but I checked the logs recently and saw the the database replication is failing with the message:
    ACS '[hostname]'is running a different version of ACS - aborting.
    All ACS SE were upgraded at the same time and display the same versions when examining the Appliance Upgrade page. Does anyone have any ideas what the problem is?
    Thanks in advance.

    Hi, I am having a related problem but in my case I am using ACS for Windows ver.4.0. I am replicating from one primary ACS to three other ACS using scheduled nightly replication.
    The problem is that the data is being updated on all three ACS servers, but in the database replication logs on the primary I get messages stating that "ACS-server-name replication failed possibly due to short time-out or dead". Moreover, not all three servers timeout. Sometimes one server timeout, and other times two servers timeout, etc.
    On the replicated servers logs, the only log, in case server times out, shows that "replication cycle starting....". while when replication is successfull, it also shows Replication cycle completed successfully.
    I have played around with the timeouts but the result is random. I have also checked if there are any bandwidth issues, but replication is scheduled at night with minimal network traffic and the servers are also not being used for authentications.
    Don't understand why I don't see successful messages all the time, specially when the data does get updated on the replica ACS.
    Thanks.
    MAG

  • Language specific replication of material group description not working SRM

    Hi All,
    We have backend R/3 MM system from which we replicate our materials,material groups. For Italian language the replication of the material groups description is not working. Though the description is available in backend R/3 system when i run the DNL_CUST_PROD1object in R3AS tcode, there is no replication log in SMQ2 but still the Italian language is not replicated into SRM.
    There are no logs in SMW01 tcode also.
    Please suggest.
    Best regards,
    Sam

    Hi,
    As david explained,you need to set the filter for the LANGUAGE field  in trascn R3AC3 before replicating the product categories.
    In R3AC3 select DNL_CUST_PROD1. Go to table structures tab . Click on the filter next to T023T table. This will take you to the filter tab. Select source site name and filter options. In the field put "SPRAS", in op put "EQ" and in low value the value 'IT"(for italian) . You can also describe a range here instead of individual material group numbers.
    BR,
    Disha.
    Do reward points for  useful answers.

  • Reverse replication not implemented for action:

    Hi, we see a persistent error reported in our replication log:
    Reverse replication not implemented for action: TEST. Remote outbox path: /var/replication/outbox/1338320761214
    The node mentioned has cq:repActionType = TEST.
    The consequence is that this aborts the replication of nodes in the publisher node and our author and publisher seem out of sync because of that. Is this something anyone has come across before. How to prevent this?
    If I delete that node in the outbox it seems to resolve the issue, but I'd like to know what caused it to appear in the first place to make sure we don't end up seeing this issue in our production environment.
    Any help is greatly appreciated.

    I don't remember exactly when the TEST nodes are created but they are only when some tests are run.
    When it happened to me I had to delete once and then it never happened.
    D.

  • Object Replication Manager - Errors 6004

    Hello everyone.
    I'm seeing these errors in SMS_OBJECT_REPLICATION_MANAGER component.
    I have seen many posts with the same issue reported, but none with answer that would help me correct this in my environment, like here:
    http://social.technet.microsoft.com/Forums/en-US/3f0cc0ed-5fd9-4860-aabd-e40e8f62053f/sms-object-replication-manager-failed-to-process-sms-object-changes?forum=configmgradminconsole
    These errors do not go away. Instead, they keep piling up.
    I looked at replication logs for more details but there is really nothing relevant there.
    Does anyone have any suggestions where else could be the issue?
    Thanks you for your help.

    Hi,
    My fault, the steps in the blog below should work.
    "SCCM and components:
    HKEY_LOCAL_MACHINE \ SOFTWARE \ Microsoft \ SMS \ Tracing \ ENABLED = 1 – (REG_DWORD – General SCCM turn on Logging)
    HKEY_LOCAL_MACHINE \ SOFTWARE \ Microsoft \ SMS \ Tracing \ xxxxxxx \ Enabled = 1 – (REG_DWORD – The Role SCCM’de If you change the compositions according to him)
    HKEY_LOCAL_MACHINE \ SOFTWARE \ Microsoft \ SMS \ Tracing \ xxxxxxx \ MaxFileSize = 3000000 – (REG_DWORD – 3 MB large – NAL and Debug Logging for growth with more than it is worth)
    Important components to be linked to SQL for SQL logging, open the key: HKEY_LOCAL_MACHINE \ SOFTWARE \ Microsoft \ SMS \ Tracing \ Sqlenabled = 1 – (REG_DWORD) "
    SCCM ConfigMgr 2012 How to Turn On Verbose SQL NAL logging
    (Note: Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice.
    Microsoft does not guarantee the accuracy of this third-party contact information.)
    Best Regards,
    Joyce Li
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • DS 5.1 "half" multi-master replication

    I realize the situation described below is not the best method, but those decisions were out of my hands.
    I have two servers in two datacenters (serverA and serverB). Both servers are set as multi-masters within the console. However, due to replication over WAN restrictions, there is only one replication agreement from serverA to serverB (no agreement from serverB to serverA). All writes are directed to serverA and serverB is not used by any clients for queries. ServerB is intended as a hot failover should we need it (again, don't ask, not my decision).
    We have been experiencing the second host (serverB) randomly crashing. There are no indications within the logs (of course minimal error logging is on).
    My bet is the crashing is due to the "half" nature of this multi-master set up. Has anyone else seen or can confirm this? Again, yes I know this is not the ideal way to go...sometimes you just have to do what you're told.
    Thanks

    One thing to check would be the replication logs of
    the master1 server to see if it is having
    difficulties prior to the crash of master2.
    Will have to check the logs. The logging level is usually turned fairly low due to the number of changes and utilization on the server (master1 not master2).
    Is master2 used for anything else (application
    queries or other read-transactions)? The thinking
    being that system utilization or excessive
    connections could be causing issues ...Master2 is not used for anything. No queries other than regular monitoring queries ("Can you hear me?") We have had one of our dedicated consumers crash similar to this, but only once not the number of times (up to about 6+ over the past month) the secondary master has crashed.
    The server is a Sun 480R running Solaris 8. The servers in the farm are supposed to be near-identical. It has come to the point where I am debating whether it is a replication problem (as I noted in my original post) or the system just needs to be rebuilt.

  • Issue with CDC and Replication enabled

    Hello,
    We have this strange issue with CDC and replication. Let me explain
    1. We have a database on write server and we replicate some tables to the read server. There are 15 tables that we replication and 8 of them have computed columns that are persisted.
    2. We also have CDC enabled on the same database where we have transactional replication enabled. I know that both CDC and replication uses replication log reader. Some how, all the time we see the log_reuse_wait says replication
    3. If I add around 100-200 MB into these tables, with these persisted columns, it will be around 500 MB of data. But the replication is queuing up 10-15 GB of data.
    4. I checked CDC tables, and the updates are in cdc tables. Also, I don't see CDC capture job. Is this because there is already replication enabled?
    What might be the issue that's causing the log to hold for a very long extended periods of time? We don't see any issue with log reader and CDC.

    2. Log_reuse_wait will show replication status both for CDC and replication.
    4. Yes as you are using transaction replication, Log Reader Agent is created for the database and the capture job won’t exist.
    When the Log Reader Agent is used for both change data capture and transactional replication, replicated changes are first written to the distribution database.
    Then, captured changes are written to the change tables. Both operations are committed together. If there is any latency in writing to the distribution database, there will be a corresponding latency before changes appear in the change tables.
    https://msdn.microsoft.com/en-us/library/cc645938.aspx?f=255&MSPPError=-2147217396
    As you said CDC updates are in cdc table I don’t see any issue.
    You could run DBCC OPENTRAN to see the old active transaction? It will give you more info.

Maybe you are looking for