Replication Failure

I have noticed a lot of this going on this group - with no definitive
          answers but here goes...
          This is my set-up - 2 Alteon Load Balancers (configured as per docs)
          2 Apache 2.0.39 with relevant Apache Bridge
          2 BEA WL702 Servers in a cluster, Admin & Managed1
          on one machine, managed2 on it's own machine.
          Here is my problem... A request goes to (say) managed1 and a session
          is created, the next request (same session - I know this because I'm
          the only one using the cluster) goes to managed2 and starts a new
          session, which envitably leads to a Java stream dump, or other error
          because information that should be in the session isn't there any
          more. Originally I thought it was due to the fact that replication
          was set to in-memory rather than replicated - so I fixed that, now i'm
          getting an equally incomprehensible stream dump:
          ####<Apr 28, 2003 11:54:23 AM BST> <Warning> <rmi> <jsps302p>
          <managed2> <ExecuteThread: '1' for queue: 'Replication'> <kernel
          identity> <> <080003> <RuntimeException thrown by rmi server:
          weblogic.cluster.replication.ReplicationManager.update(Lweblogic.cluster.replication.ROID;ILjava.io.Serializable;)
          java.lang.NullPointerException>
          While I guess this is down to something in the session being
          non-serialized, I wouldn't expect the application to jump from server
          to server.
          Also I'm getting a lot of :
          <HttpServer(2890001,null default ctx,managed2) found no context for
          "/WLDummyInitJVMIDs". This request does not match the context path for
          any installed web applications and there is no default web application
          configured.>
          turning up in my logs (even if it is not related - any ideas what it
          is?)...
          This is my weblogic.xml :
          <weblogic-web-app>
          <session-descriptor>
          <session-param>
          <param-name>PersistentStoreType</param-name>
          <param-value>replicated</param-value>
          </session-param>
          </session-descriptor>
          </weblogic-web-app>
          Any help would be gratefully accepted.
          Regards
          matthew
          

Can you post the complete stack trace for the exceptions? The NPE might be a
          known problem.
          sree
          "matty" <[email protected]> wrote in message
          news:[email protected]...
          > I have noticed a lot of this going on this group - with no definitive
          > answers but here goes...
          >
          > This is my set-up - 2 Alteon Load Balancers (configured as per docs)
          > 2 Apache 2.0.39 with relevant Apache Bridge
          > 2 BEA WL702 Servers in a cluster, Admin & Managed1
          > on one machine, managed2 on it's own machine.
          >
          > Here is my problem... A request goes to (say) managed1 and a session
          > is created, the next request (same session - I know this because I'm
          > the only one using the cluster) goes to managed2 and starts a new
          > session, which envitably leads to a Java stream dump, or other error
          > because information that should be in the session isn't there any
          > more. Originally I thought it was due to the fact that replication
          > was set to in-memory rather than replicated - so I fixed that, now i'm
          > getting an equally incomprehensible stream dump:
          >
          > ####<Apr 28, 2003 11:54:23 AM BST> <Warning> <rmi> <jsps302p>
          > <managed2> <ExecuteThread: '1' for queue: 'Replication'> <kernel
          > identity> <> <080003> <RuntimeException thrown by rmi server:
          >
          weblogic.cluster.replication.ReplicationManager.update(Lweblogic.cluster.rep
          lication.ROID;ILjava.io.Serializable;)
          > java.lang.NullPointerException>
          >
          >
          > While I guess this is down to something in the session being
          > non-serialized, I wouldn't expect the application to jump from server
          > to server.
          >
          > Also I'm getting a lot of :
          >
          > <HttpServer(2890001,null default ctx,managed2) found no context for
          > "/WLDummyInitJVMIDs". This request does not match the context path for
          > any installed web applications and there is no default web application
          > configured.>
          >
          > turning up in my logs (even if it is not related - any ideas what it
          > is?)...
          >
          > This is my weblogic.xml :
          >
          > <weblogic-web-app>
          >
          > <session-descriptor>
          > <session-param>
          > <param-name>PersistentStoreType</param-name>
          > <param-value>replicated</param-value>
          > </session-param>
          > </session-descriptor>
          >
          > </weblogic-web-app>
          >
          >
          >
          > Any help would be gratefully accepted.
          >
          > Regards
          >
          >
          > matthew
          

Similar Messages

  • Server 2012 R2 Domain Controllers stop accepting log in and replication failure.

    We have recently completed a Domain upgrade to 2012 R2 AD DS from native 2003 AD. The issue we are experiencing is that for seemingly no reason the 2012 hosts will randomly stop accepting (RDP) logins and we see replication failures. We also cannot
    otherwise remotely manage the host (remote service management etc...). The only way I've been able to recover from this condition is to restart the affected host, after which (RDP) logins are again accepted and successful replication starts again.
    Logs aren't showing any issues prior to the issue happening and it is not specific to one host. I have been digging around to find a solution to this abnormal behavior but as yet haven't come across anything specific to what I am seeing.
    Domain level is 2008 R2 and our few remaining 2008 R2 hosts never experience this. Only seems to be the 2012 hosts and randomly among all the DCs. Not one specific 2012 host is affected.
    We have 20 DCs total.
    Are there any known issues? Any advice on what I may be able to look at?
    We are otherwise healthy aside from this intermittent replication/login issue.

    This sounds more like a network type issue than AD type problem.
    Are any firewalls in the way? 
    Do the servers respond to a ping when they are not responding to RDP.
    What are you seeing in event logs prior to the change. 
    Are the servers physical or virtual? Are you able to get onto the console - either through your HyperVisor or through ILO type management?
    Thanks
    Regards,
    Denis Cooper
    MCITP EA - MCT
    Help keep the forums tidy, if this has helped please mark it as an answer
    Blog: http://www.windows-support.co.uk 
    Twitter:   LinkedIn:

  • Windows Server 2012 R2 Hyper V on a SBS 2011 Domain replication failure

    I have a SBS 2011 Domain which I am adding two 2012 R2 Standard servers in order to facilitate virtualization and consolidate physical servers. I have the two 2012 R2 servers up and running and a test server running virtually on Hyper-V.   I want
    to test replication from one Hyper-V host to the other, however, I am unable to setup Kerberos delegation in the SBS 2011 AD domain.  Specifically, the Service Type of Microsoft Virtual System Migration Service is not listed.  CIFS is available,
    however, there are no Service Types having to do with Hyper-V available.
    I have upgraded the AD using adprep from the 2012 R2 installation disc, however, this has not added the service types.
    Thank you in advance for the help!

    Hi Justin,
    Thank you for the information.  I had originally reviewed the article you mentioned in your reply, however, this did not work for me.  It accurately described the problem I am having, however, the solution did not work.
    I did a little review of the syntax of the command SETSPN and found that the article referenced above has a "/" instead of a "\" in the command line.  When I modified my syntax to reflect using the forward slash, the command seemed to processed
    correctly, however, when I go back to the delegation steps, the service name is still not there.  I did verify the service was registered properly by listing out all the SPN registrations.
    Clarifying Question:  Based on the command I ran to add this Service, I am wondering if I used the correct servers.  Basically, I have the following:
    Server 1 - SBS 2011 domain controller
    Server 2 - 2012 R2 Hyper-V Server
    Server 3 - 2012 R2 Hyper-V Server
    I want to setup this Kerberos delegation for CIFS and Microsoft Virtual System Migration on Server 2 and 3 and am setting this up using ADUC on Server 1.  I ran the SETSPN command on Server 1 for Server 1 - was this the correct thing to do or should
    I have an SPN entry for Server 2 and/or 3?
    Sorry for what is probably a very basic question.
    Thank you again for your help.

  • BDb replication failure

    Hi
    I ve tried to create a 40 million record database and tried to replicate it with another slave.After around 12 hours we crashed the master to see how far the replication has been completed.When we crashed the master and tried to rejoin the replication evironment but we got the following error
    unable to join the environment.
    We observed that the master database size is abt 1000Mb and the slave size is abt 980 Mb.we tried to check LSN of the master and the slave using the db_stat() utility we get the following error
    db_stat: unable to join the environment
    db_stat: DB_ENV->open: Resource temporarily unavailable
    Is this caused because we crashed the processes? Or is there something else to it.The no of log files are the same but we are not able to check the lsn as we are not even able to open the enviroment again.
    Thanks
    Sandeep

    Could you please clarify a few things?
    1. Did you finish inserting into the database at the master before
    attaching a new client? Or did you have the client attached during
    the time you were inserting?
    2. What do you mean by "tried to rejoin the replication environment"
    after crashing the master? Do you mean that you left the client
    running, and then tried to restart the master and have it connect
    to the client? If so, did you start the restarted master as
    another client, or as master again?
    3. What did the client do in response to the master's crash?
    Alan Bram
    Oracle

  • HttpSession replication failure

    I am using IIS proxy to talk to a Cluster of 2 servers (each run on a
              physical server).
              I am deploying my application(contains a web component and ejb component
              packaged as a ear) using Cluster install. I have also included the
              PersistenceStoreType "replicated" in weblogic.xml. But when I test the fail
              over in my cluster the application fails since the application it does not
              get the context which is in the session.
              I am not sure what is happening or wheather I am missing something. Any help
              which will help be to debug this is greatly appreciated.
              thanks,
              

    are you making sure that your session is persistant ?
              Thanks
              "Mark" <[email protected]> wrote in message
              news:[email protected]...
              > Thanks for replying.
              > I have included the session parameter persistentStoreType=replicated in
              the
              > weblogic.xml.
              > Still I am not able to get the session failover . And I am not sure as to
              > whats happening too. Can you please elaborate on the debug flags, I did
              pass
              > them as command line args but there was no change in the log output
              > generated.
              >
              > thanks,
              >
              > "Kumar Allamraju" <[email protected]> wrote in message
              > news:[email protected]...
              > Use the following to monitor the Replication traffic.
              > <!-- Replication Debug Flags
              > DebugReplication="true"
              > DebugReplicationDetails="true"
              > -->
              >
              1) -Dweblogic.DebugReplication=true -Dweblogic.DebugReplicationDetails=true
              > etc.... weblogic.Server
              > or
              > 2) set the above in ServerDebug MBean in config.xml
              > <ServerDebug Name="MyServer-1" DebugReplication="true"
              > />
              > Hope it helps
              > BTW, have you set the persistenceType=replicated in your weblogic.xml?
              >
              > PS: These debug flags are unsupported and may change in the
              > future releases.
              > --
              > Kumar
              >
              > Mark wrote:
              > I am using Weblogic6.1sp2 on Win2K configured for IIS proxy on another
              > machine.
              > When I test for failover, the application breaks since it does not find
              the
              > session in the other server.
              > And I checked the session ID. I turned the full logging on the proxy, and
              > can see that the web proxy
              > tries to contact the failed app server and then connects to the other
              server
              > thats running.And then the console logs
              > shows that the servlet failed to find the session info.
              > But how will I know (rather where should I look) if the session has indeed
              > been replicated by the appserver.
              > The console or the logs do not say anything about this.
              > thanks,
              > "Cameron Purdy" <[email protected]> wrote in message
              > news:[email protected]...
              > > Sounds like you are using 6.0 or 6.1 ... could you fill in the details?
              > >
              > > What context do you mean in the session? Does the second server claim no
              > > session for that user? Or is something missing from inside that session?
              > > (Use session ID to verify that it is indeed the same session.)
              > >
              > > Peace,
              > >
              > > --
              > > Cameron Purdy
              > > Tangosol, Inc.
              > > Clustering Weblogic? You're either using Coherence, or you should be!
              > > Download a Tangosol Coherence eval today at http://www.tangosol.com/
              > >
              > >
              > >
              > > "Mark" <[email protected]> wrote in message
              > > news:[email protected]...
              > > > I am using IIS proxy to talk to a Cluster of 2 servers (each run on a
              > > > physical server).
              > > > I am deploying my application(contains a web component and ejb
              component
              > > > packaged as a ear) using Cluster install. I have also included the
              > > > PersistenceStoreType "replicated" in weblogic.xml. But when I test the
              > > fail
              > > > over in my cluster the application fails since the application it does
              > not
              > > > get the context which is in the session.
              > > > I am not sure what is happening or wheather I am missing something.
              Any
              > > help
              > > > which will help be to debug this is greatly appreciated.
              > > >
              > > > thanks,
              > > >
              > > >
              > > >
              > >
              > >
              >
              >
              

  • Replication failure "requires administrator action"

    Hello (again),
    We are currently running a two machine (A and B) multi-master setup. Both machines are configured to send updates immediately.
    Yesterday, the following error appeared in the error log on machine B:
    [30/May/2003:09:55:39 -0700] NSMMReplicationPlugin - Replication: Incremental update failed and requires administrator action
    There are no other errors in the error log. Replication from B to A is permantly stopped, but replication from A to B is okay.
    After digging into this a bit, it appears that the error is caused by A failing to return data to B when B first connects:
    [29/May/2003:18:10:16 -0700] conn=1381 op=0 BIND dn="cn=Replication Manager,cn=config" method=128 version=3
    [29/May/2003:18:10:16 -0700] conn=1381 op=0 RESULT err=0 tag=97 nentries=0 etime=0 dn="cn=replication manager,cn=config"
    [29/May/2003:18:10:16 -0700] conn=1381 op=1 SRCH base="" scope=0 filter="(objectClass=*)" attrs="supportedControl supported
    Extension"
    [29/May/2003:18:10:16 -0700] conn=1381 op=1 RESULT err=0 tag=101 nentries=0 etime=0
    The same connection from A to B looks like:
    [29/May/2003:16:36:25 -0700] conn=711 op=0 BIND dn="cn=Replication Manager,cn=config" method=128 version=3
    [29/May/2003:16:36:25 -0700] conn=711 op=0 RESULT err=0 tag=97 nentries=0 etime=0 dn="cn=replication manager,cn=config"
    [29/May/2003:16:36:25 -0700] conn=711 op=1 SRCH base="" scope=0 filter="(objectClass=*)" attrs="supportedControl supportedE
    xtension"
    [29/May/2003:16:36:25 -0700] conn=711 op=1 RESULT err=0 tag=101 nentries=1 etime=0
    Am I on track here?
    What is going on, and how do I fix this?
    Thanks,
    Gil

    Hi there,
    You have not specify the version of Directory used.
    If you use any earlier version of Directory Server than 5.1SP2HF3 or 5.1SP3, then it is strongly recommended to get your servers up to these versions... indeed, there has been several major replication issues fixed there.
    Then, if the beginning of your replication issue is still within the changelog trimmer period, you may try to restart your Server A (the consumer of Server B). Verify then if the replication restart... by checking with the insync command (using Server B on the "-s" argument).
    If this does not work, then I am afraid you will have to reinitialize your Directory Server.
    Hope this would help you.
    Cheers.
    /Damien.

  • Replication Failure - Master - Consumer

    We have a 5.2 Directory Server running as master and a 5.2 Directory Server as a Consumer.
    When setting up replication I followed the steps in the documentation and everything worked fine up until I attempted to intialize the replica - it fails everytime with the following errors:
    On the Consumer in the error log it reports:
    [10/Jun/2004:11:48:14 -0700] - ERROR<8303> - Replication - conn=10 op=3 msgId=4 - Schema replication error [C] Failed with error code 20
    On the Master in the error log it reports:
    [10/Jun/2004:11:51:08 -0700] - WARNING<10303> - Repl. Transport - conn=-1 op=-1 msgId=-1 - [S] Unable to push the schema on the consumer withresponse: Unknown rc (20)
    [10/Jun/2004:11:51:08 -0700] - WARNING<10247> - Total Protocol - conn=-1 op=-1 msgId=-1 - Unable to replicate schema to host ldapconsumer1.xxx.xxx, port 3890. Continuing with replication session.
    [10/Jun/2004:11:51:13 -0700] - WARNING<10303> - Repl. Transport - conn=-1 op=-1 msgId=-1 - [S] Unable to push the schema on the consumer withresponse: Unknown rc (20)
    I found 8303 in the Directory Server error code list and it just says:
    - Failed with error code error
    - Schema replication failed locally on the consumer.
    - Check error code and contact Sun ONE Technical Support.
    Can anyone help?
    Thanks,
    Dan

    I had a similar problem when I first setup replication between two DS5.2 systems. The Master was installed via tarball and the consumer was installed via the Sun packages. Upon investigation, I found that the schema files were different between the two systems. I just manually copied over the schema files from the master to the replica and the errors went away and replication started working.
    Is this a problem that should be reported to Sun? I don't know. I found a quick solution and kept on going.
    HTH,
    Roger S.

  • Replication failure TT16041

    Hi,
    We are trying to get replication to work. The tables are under fairly heavy insert/update/delete load. After running for a couple of days, the subscriber failed and the transactions logs were kept on the master, that eventually ran out of disk space.
    The error message on the subscriber at the start of the problem was:
    2007-03-25 03:20:49 Err : 1258: REP: MTSDB:rephold.c(89): TT16041: Failed to compute a new replication hold LSN in rephold()
    2007-03-25 03:20:49 Err : 1258: REP: MTSDB:rephold.c(89): TT6003: TT6003: Lock request denied because of time-out
    Details: Tran 3.31777 (pid 1258) wants U lock on rowid 0x000000000019a7f8, table TTREP.REPPEERS. But tran 1.383762061 (pid 1258) has it in X (request was X). Holder SQL () -- file "table.c", lineno 24314, procedure "sbTblNextActiveTuple()"
    2007-03-25 03:20:52 Err : 1258: REP: MTSDB:rephold.c(89): TT16041: Failed to compute a new replication hold LSN in rephold()
    2007-03-25 03:20:52 Err : 1258: REP: MTSDB:rephold.c(89): TT6003: TT6003: Lock request denied because of time-out
    Details: Tran 3.31778 (pid 1258) wants U lock on rowid 0x000000000019a7f8, table TTREP.REPPEERS. But tran 1.383762061 (pid 1258) has it in X (request was X).
    Any thoughts on what went wrong here?

    What version of TT is this?6.0.4
    Were there any other messages in the log before after these?I now have all the available log files (30 MB) of both master and subscriber.
    The first message in the log files was TT16041. The 2nd was TT6003. This kept repeating until eventually after 3 days the status was set to FAILED.
    2007-03-22 03:20:29 Err : 1258: REP: MTSDB:rephold.c(89): TT16041: Failed to compute a new replication hold LSN in rephold()
    2007-03-22 03:20:29 Err : 1258: REP: MTSDB:rephold.c(89): TT6003: TT6003: Lock request denied because of time-out
    Details: Tran 3.6156 (pid 1258) wants U lock on rowid 0x000000000019a7f8, table TTREP.REPPEERS. But tran 1.79426805 (pid 1258) has it in X (request was X). Holder SQL () -- file "table.c", lineno 24314, procedure "sbTblNextActiveTuple()"
    2007-03-22 03:20:32 Err : 1258: REP: MTSDB:rephold.c(89): TT16041: Failed to compute a new replication hold LSN in rephold()
    2007-03-22 03:20:32 Err : 1258: REP: MTSDB:rephold.c(89): TT6003: TT6003: Lock request denied because of time-out
    Details: Tran 3.6157 (pid 1258) wants U lock on rowid 0x000000000019a7f8, table TTREP.REPPEERS. But tran 1.79426805 (pid 1258) has it in X (request was X). Holder SQL () -- file "table.c", lineno 24314, procedure "sbTblNextActiveTuple()"
    2007-03-22 03:20:36 Err : 1258: REP: MTSDB:rephold.c(89): TT16041: Failed to compute a new replication hold LSN in rephold()
    2007-03-22 03:20:36 Err : 1258: REP: MTSDB:rephold.c(89): TT6003: TT6003: Lock request denied because of time-out
    Details: Tran 3.6158 (pid 1258) wants U lock on rowid 0x000000000019a7f8, table TTREP.REPPEERS. But tran 1.79426805 (pid 1258) has it in X (request was X). Holder SQL () -- file "table.c", lineno 24314, procedure "sbTblNextActiveTuple()"
    2007-03-22 03:35:29 Err : 1258: REP: MTSDB:rephold.c(89): TT16041: Failed to compute a new replication hold LSN in rephold()
    2007-03-22 03:35:29 Err : 1258: REP: MTSDB:rephold.c(89): TT6003: TT6003: Lock request denied because of time-out
    Details: Tran 3.6247 (pid 1258) wants U lock on rowid 0x000000000019a7f8, table TTREP.REPPEERS. But tran 1.79801525 (pid 1258) has it in X (request was X). Holder SQL () -- file "table.c", lineno 24314, procedure "sbTblNextActiveTuple()"
    2007-03-22 03:35:32 Err : 1258: REP: MTSDB:rephold.c(89): TT16041: Failed to compute a new replication hold LSN in rephold()
    2007-03-22 03:35:32 Err : 1258: REP: MTSDB:rephold.c(89): TT6003: TT6003: Lock request denied because of time-out
    Details: Tran 3.6248 (pid 1258) wants U lock on rowid 0x000000000019a7f8, table TTREP.REPPEERS. But tran 1.79801525 (pid 1258) has it in X (request was X). Holder SQL () -- file "table.c", lineno 24314, procedure "sbTblNextActiveTuple()"
    2007-03-22 03:35:36 Err : 1258: REP: MTSDB:rephold.c(89): TT16041: Failed to compute a new replication hold LSN in rephold()
    2007-03-22 03:35:36 Err : 1258: REP: MTSDB:rephold.c(89): TT6003: TT6003: Lock request denied because of time-out
    Details: Tran 3.6249 (pid 1258) wants U lock on rowid 0x000000000019a7f8, table TTREP.REPPEERS. But tran 1.79801525 (pid 1258) has it in X (request was X). Holder SQL () -- file "table.c", lineno 24314, procedure "sbTblNextActiveTuple()"
    2007-03-22 03:50:29 Err : 1258: REP: MTSDB:rephold.c(89): TT16041: Failed to compute a new replication hold LSN in rephold()
    2007-03-22 03:50:29 Err : 1258: REP: MTSDB:rephold.c(89): TT6003: TT6003: Lock request denied because of time-out
    etc...
    2007-03-25 06:05:36 Err : 1258: REP: MTSDB:rephold.c(89): TT16041: Failed to compute a new replication hold LSN in rephold()
    2007-03-25 06:05:36 Err : 1258: REP: MTSDB:rephold.c(89): TT6003: TT6003: Lock request denied because of time-out
    Details: Tran 3.32768 (pid 1258) wants U lock on rowid 0x000000000019a7f8, table TTREP.REPPEERS. But tran 1.389282609 (pid 1258) has it in X (request was X). Holder SQL () -- file "table.c", lineno 24314, procedure "sbTblNextActiveTuple()"
    2007-03-25 06:05:40 Warn: 1258: REP: MTSDB:transmitter.c(6391): TT16149: Current state is FAILED for peer MTSDB
    2007-03-25 06:05:40 Info: 1217: : maind got #22.181 from 1258, disconnect: name=/var/TimesTen/mts/mtsDB context= 10024ce20 dbdev= panic=N shmKey=%04%02%80%19
    2007-03-25 06:05:40 Info: 1217: : 1258/10024ce20: Disconnect /var/TimesTen/mts/mtsDB
    2007-03-25 06:05:40 Info: 1217: : disco.c:297: Mark in-flux (now reason 3=disconnect pid 1258 nwaiters 0 ds /var/TimesTen/mts/mtsDB) (was reason 0)
    2007-03-25 06:05:40 Info: 1217: : maind: done with request #22.181
    2007-03-25 06:05:40 Info: 1217: : maind got #22.182 from 1258, disconnect complete: name=/var/TimesTen/mts/mtsDB context= 10024ce20 success=Y panic=N
    2007-03-25 06:05:40 Info: 1217: : 1258 10024ce20: DisconnectComplete Y /var/TimesTen/mts/mtsDB
    2007-03-25 06:05:40 Info: 1217: : daDbDisconnectComplete by 1258: decrementing nUsers from 9, panicked=-1, trashed=-1, shmSeq=4
    2007-03-25 06:05:40 Info: 1217: : disco.c:610: Mark not in-flux (was reason 3=disconnect pid 1258 nwaiters 0 ds /var/TimesTen/mts/mtsDB)
    2007-03-25 06:05:40 Info: 1217: : maind: done with request #22.182
    2007-03-25 06:05:40 Info: 1258: REP: MTSDB:repagent.c(1156): TT16026: Thread 'TRANSMITTER' (context 10024ce20; return code 'RESTART_THREAD') exiting
    2007-03-25 06:05:40 Warn: 1258: REP: MTSDB:receiver.c(1574): TT16060: Failed to read data from the network. select() timed out
    2007-03-25 06:05:40 Info: 1217: : maind got #22.183 from 1258, disconnect: name=/var/TimesTen/mts/mtsDB context= 1002bbb40 dbdev= panic=N shmKey=%04%02%80%19
    2007-03-25 06:05:40 Info: 1217: : 1258/1002bbb40: Disconnect /var/TimesTen/mts/mtsDB
    2007-03-25 06:05:40 Info: 1217: : disco.c:297: Mark in-flux (now reason 3=disconnect pid 1258 nwaiters 0 ds /var/TimesTen/mts/mtsDB) (was reason 0)
    2007-03-25 06:05:40 Info: 1217: : maind: done with request #22.183
    2007-03-25 06:05:40 Info: 1217: : maind got #22.184 from 1258, disconnect complete: name=/var/TimesTen/mts/mtsDB context= 1002bbb40 success=Y panic=N
    2007-03-25 06:05:40 Info: 1217: : 1258 1002bbb40: DisconnectComplete Y /var/TimesTen/mts/mtsDB
    2007-03-25 06:05:40 Info: 1217: : daDbDisconnectComplete by 1258: decrementing nUsers from 8, panicked=-1, trashed=-1, shmSeq=4
    2007-03-25 06:05:40 Info: 1217: : disco.c:610: Mark not in-flux (was reason 3=disconnect pid 1258 nwaiters 0 ds /var/TimesTen/mts/mtsDB)
    2007-03-25 06:05:40 Info: 1217: : maind: done with request #22.184
    2007-03-25 06:05:40 Info: 1258: REP: MTSDB:repagent.c(1156): TT16026: Thread 'RECEIVER' (context 1002bbb40; return code 'FAIL') exiting
    2007-03-25 06:05:43 Info: 1217: : maind got #22.185 from 1258, connect: name=/var/TimesTen/mts/mtsDB context= 10024ce20 user=root pass= dbdev= logdev= logdir= grpname= access=%00%00%00%00 persist=%00%00%00%00 flags=%01%00%08@ newpermsz=%00%00%00%00%00%00%00%00 newtempsz=%00%00%00%00%00%00%00%00 newpermthresh=%00%00%00Z newtempthresh=%00%00%00Z newlogbufsz=%00%00%00%00%00%80%00%00 autorefreshType=%ff%ff%ff%ff logflushmethod=%00%00%00%01 connections=%00%00%00@ control1=%00%00%00%00 control2=%00%00%00%00 control3=%00%00%00%00 ckptrate=%00%00%00%00 connflags=%00%00%00%00 newlogfilesz=%00%00%00%00%00%80%00%00 skiprestorecheck=%00%00%00%00 realuser=root conn_name=TRANSMITTER ckptfrequency=%00%00%02X ckptlogvolume=%00%00%00@ recoverythreads=%00%00%00%00 reqid=*
    2007-03-25 06:05:43 Info: 1217: : 1258 10024ce20: Connect /var/TimesTen/mts/mtsDB a=0x0 f=0x1000840
    2007-03-25 06:05:43 Info: 1217: : permsize=0 tempsize=0
    2007-03-25 06:05:43 Info: 1217: : logbuffsize=8388608 logfilesize=8388608
    2007-03-25 06:05:43 Info: 1217: : permwarnthresh=90 tempwarnthresh=90 logflushmethod=1 connections=64
    2007-03-25 06:05:43 Info: 1217: : ckptfrequency=600 ckptlogvolume=64 conn_name=TRANSMITTER
    2007-03-25 06:05:43 Info: 1217: : recoverythreads=0
    2007-03-25 06:05:43 Info: 1217: : control1=0 control2=0 control3=0
    2007-03-25 06:05:43 Info: 1217: : ckptrate=0
    2007-03-25 06:05:43 Info: 1217: : 1217/1258: <wait and mark>: Mark in-flux (now reason 2=connect pid 1258 nwaiters 0 ds /var/TimesTen/mts/mtsDB) (was reason 0)
    2007-03-25 06:05:43 Info: 1217: : marked in flux for connect by 1258 : 0
    2007-03-25 06:05:43 Info: 1217: : daDbConnect returns 0
    2007-03-25 06:05:43 Info: 1217: : maind: done with request #22.185
    2007-03-25 06:05:43 Info: 1217: : maind got #22.186 from 1258, connect complete: name=/var/TimesTen/mts/mtsDB context= 10024ce20 success=Y shmkey=%04%02%80%19 connid=%00%00%00%01 fatal=N
    2007-03-25 06:05:43 Info: 1217: : 1258 10024ce20: ConnectComplete Y N /var/TimesTen/mts/mtsDB
    2007-03-25 06:05:43 Info: 1217: : connect.c:1750: Mark not in-flux (was reason 2=connect pid 1258 nwaiters 0 ds /var/TimesTen/mts/mtsDB)
    2007-03-25 06:05:43 Info: 1217: : Mark NOT in flux for connect by 1258
    2007-03-25 06:05:43 Info: 1217: : daDbConnectComplete for /var/TimesTen/mts/mtsDB: incremented nUsers to 8, trashed=-1, panicked=-1, shmSeq=4
    2007-03-25 06:05:43 Info: 1217: : maind: done with request #22.186
    2007-03-25 06:05:43 Info: 1258: REP: MTSDB:repagent.c(1126): TT16025: Thread 'TRANSMITTER' (context 10024ce20) starting
    2007-03-25 06:05:43 Info: 1258: REP: MTSDB:transmitter.c(946): TT16114: Attempting to connect to MTSDB on MYDB_REP (10.0.0.2); port: 16004
    2007-03-25 06:05:44 Info: 1258: REP: MTSDB:transmitter.c(946): TT16114: Attempting to connect to MTSDB on MYDB_REP (10.0.0.2); port: 16004
    etc...

  • AD Replication Failure Between 2 Server 2008 R2 - LDAP bind failed with error 8341,

    Hi everybody,
    I've having 2 AD Server : GDS and DC1.
    They can't replicate with each other for a long time ( more than 60 days )
    They placed at 2 diffirent subnet, no FW rule.
    I can ping, resolve the DNS by nslookup both Servers
    When i use cmd command : net view \\domain 
    => The error appear : System error 5 has occurred Access is denied in both server
    In the event log i see some error like Event ID 2087, 1864 in the GDS AD Server 
    Please check this link  for more detail http://1drv.ms/1wqmeuf ( Link contact image and log file of repadmin|dcdiag )
    After searching,
    i planning to depromote and rejoin the GDS to the DC1 AD Server, clean metadata. But what about the user account, group data. Is that lost ?
    Server not replicate for more than 60 days, it need to reset Kerberos password right ?
    I'm lost now, Please help me to setting somehow that replicatie this 2 server again.
    If you need any information to resolve this problem, Please tell me.
    Thank you!!

    Hi Datnt,
    If the server is not replicated within the tombstone period, its is always recommended to do a force removal from AD and doing a metadata cleanup to remove the old entries.
    If you still want to do it without demoting, just go through the below link by Ace, it might help you.
    Active Directory Lingering Objects, Journal Wraps, USN Rollbacks, Tombstone 
    Lifetime, and Event IDs 13568, 13508, 1388, 1988, 2042, 2023, 2095, 1113, 1115, 
    2103, and more ...
    http://msmvps.com/blogs/acefekay/archive/2011/12/27/active-directory-lingering-objects-journal-wraps-tombstone-lifetime-and-event-ids-13568-13508-1388-1988-2042-2023.aspx
    Regards,
    Rafic
    If you found this post helpful, please give it a "Helpful" vote.
    If it answered your question, remember to mark it as an "Answer".
    This posting is provided "AS IS" with no warranties and confers no rights! Always test ANY suggestion in a test environment before implementing!

  • Daily Forest replication error

    Hi, let me first give a brief overview of our infra. Our DC is a child domain from AU(Parent Domain/Forest). Our normal operation is at a specific/scheduled time, it is supposed to replicate with the Parent Domain/Forest but for some reason AU is telling
    us that DC replication is failing.
    Thanks
    Jeff

    Hi Jeff,
    Would you please tell us that do you have a contiguous namespace in the forest?
    What’s the error message after you run repadmin/showrepl?
    Here are some links below I suggest you refer to:
    Forest replication is failing
    http://social.technet.microsoft.com/Forums/windowsserver/en-US/bebb9884-8dbd-4e71-aefb-2e78e0ea485a/forest-replication-is-failing?forum=winserverDS
    How To Diagnose Active Directory Replication Failures
    http://support.microsoft.com/kb/2498185/ar
    Troubleshooting Active Directory Replication Problems
    http://technet.microsoft.com/en-us/library/cc738415(v=WS.10).aspx
    Best Regards,
    Amy

  • UCCX 7.01 CTI manager failover

    Hi, I couldn't find any definitive  documentation on the what determines if a CCX server fails over to the  secondary CTI manager.  Is it loss of ping?  Is it CTI service related.
    Env:
    2 CCM servers running 7.0.2
    1 CCX server running 7.0.1
    Our  CCX server is pointed to the subscriber first and publisher second  under AXL provider and CTI manager.  Replication between the 2 servers  failed on Jan 2nd.  When folks tried to log into CCX on the morning of  Jan 3rd, they received an error stating that a CTI manager is not  available.  We logged into CCX and removed the subscriber from the list  of selected AXL and CTIM servers and people were able to log into CCX.   We rebooted the subscriber and after some time, replication was again  restored.
    My  main concern was why did the CTI Manager running on the publisher not  take over?  Was it because the Subscriber was still pingable?  The TAC  engineer stated that the failover was based on pings.  Can anyone verify  this?  He did not seem too confident when he made this statement and it  would make much more sense to have the failover based on service  availability.
    We've  since gone into RTMT and setup e-mail alerts so in the future, we'll at  least be given a heads up if there is a replication failure.
    Thanks in advance!
    -Eric

    This is what I found but it does not seem to contain any useable information.
    503: Nov 11 15:19:46.829 EST %MIVR-CLUSTER_MGR-7-UNK:Post Convergence Event: CONVERGENCE_COMPLETED, name=CRS SQL Server - Repository
    504: Nov 11 15:19:46.844 EST %MIVR-PROMPT_MGR-1-MGR_PARTIAL_SERVICE:Prompt Manager in partial service:
    505: Nov 11 15:19:46.844 EST %MIVR-GRAMMAR_MGR-6-MGR_IN_SERVICE:Grammar Manager in service:
    506: Nov 11 15:19:46.844 EST %MIVR-CLUSTER_MGR-7-UNK:try to process MasterConvergenceCompletedCmdImpl: name CRS SQL Server - Historical, nodeId=1, type=MASTER_ELECTED, uniqueId=99, master=true, updateTick=423, baseTick=422, nodeCurrentTick=423
    /* Style Definitions */
    table.MsoNormalTable
    {mso-style-name:"Table Normal";
    mso-tstyle-rowband-size:0;
    mso-tstyle-colband-size:0;
    mso-style-noshow:yes;
    mso-style-priority:99;
    mso-style-qformat:yes;
    mso-style-parent:"";
    mso-padding-alt:0in 5.4pt 0in 5.4pt;
    mso-para-margin:0in;
    mso-para-margin-bottom:.0001pt;
    mso-pagination:widow-orphan;
    font-size:11.0pt;
    font-family:"Calibri","sans-serif";
    mso-ascii-font-family:Calibri;
    mso-ascii-theme-font:minor-latin;
    mso-fareast-font-family:"Times New Roman";
    mso-fareast-theme-font:minor-fareast;
    mso-hansi-font-family:Calibri;
    mso-hansi-theme-font:minor-latin;}

  • Get-ADReplicationFailure and Get-ADReplicationUpToDatenessVectorTable

    Hi,
    Where does the Get-ADReplicationFailure and Get-ADReplicationUpToDatenessVectorTable cmdlets retrieve it`s data from?
    Lets start with Get-ADReplicationFailure: It shows 2 replication failures which is not current. Running the following in the same environment shows no errors:
    $dclist= get-addomaincontroller-filter *
    foreach($dc in$dclist) {
    repadmin /showrepl /csv | ConvertFrom-Csv
    Get-ADReplicationUpToDatenessVectorTable: This cmdlet returns a lot of Microsoft.ActiveDirectory.Management.ADReplicationUpToDatenessVectorTable objects. Many of them have old timestamps and
     no value for the Partner property:
    LastReplicationSuccess : 26.04.2010 21:01:02
    Partition              : DC=domain,DC=local
    PartitionGuid          : 7ddec540-31db-44d3-9ab5-d5adb479627e
    Partner                :
    PartnerInvocationId    : 0e2fbc85-8d50-4c30-ae65-27648a0888b9
    Server                 : dc01.domain.local
    UsnFilter              : 19853
    These are probably old domain controllers which is decomissioned years ago. Why does these show up? And where is the cmdlet getting this data from?
    The replication topology seems healthy using the legacy tools, but the new cmdlets isn`t giving the same impression.
    Some clarifications would be appreciated.

    Hi scripter42,
    The Get-ADReplicationFailure cmdlet returns all failures currently associated with a given domain controller or Active Directory Lightweight Directory Services (AD LDS) instance. The return object is of type ADReplicationFailure. This cmdlet returns the
    list of failures in the ADReplicationSummary object for a specific server.
    The ADReplicationUpToDatenessVectorTable displays the highest Update Sequence Number (USN) for the specified domain controller(s). This information shows how up-to-date a replica is with its replication partners.
    Regards,
    Lany Zhang

  • RTMT for the Real World

    Hello,
    does anyone have any suggesstions on what alerts to enable on RTMT for CUCM?  I see some listed in Red and other in Black.  We curently seem to be generating an excessive amount of alerts and I would like to pare that back to only relevant alerts.
    Thanks in Advance!.  All replies rated.

    In my opinion, DRF failure, CPU pegging, Code Yellow, DB replication failure, LowAvailableVirtualMemory, ServerDown. There are others in CallManager that you might need to make sure that you are alerted if Gateways go down. 

  • XLA Bookmark Problem - Urgent

    Hi,
    I am using Timesten7 along with java for application development and Xla monitoring. Actually, our xla bookmarks are in sync with our replication bookmarks, whenever we do some updates to the tables corresponding to the Bookmarks.
    But the bookmarks are in the held in the last read position when there are no updates. Due to the other updates, which are not listened, the replication pointers are keep moving forward. This results in our Xla lagging where it got started.Sometimes the log files difference becomes more than 10. Since the Xla is holding onto the logs, the memory gets full , as this leads to disk space full error and replication failure and very bad impact on the application.
    Is it a default behaviour of TimesTen ?? If so how can we move the xla bookmarks, even though if there are no updates, so as to clear the log buffer. Please provide me with a better solution.
    Thanks in advance,
    Bala

    Hi Chris,
    You are right, we are using JMS/XLA with CLIENT_ACKNOWELDGE. But while trying to fix this error, we used AUTO_ACKNOWLEDGE as well. If it help, we get messages Synchronously.
    To further elaborate, we have 4 listeners (bookmarks) listening to changes in 4 Views. The code is based on the XlaLevel3 example in the TT sample codes, with a difference that we create 4 separate listeners for the 4 views (instead of 1 in XlaLevel3). The problem is that 2 of the views belong to tables that do not get updated frequently and hence our program never gets any messages in these two queues! If the listener does not get an event, then it cannot acknowledge as well (auto or client).
    In our tests, we even commented out 3 of the bookmarks and tried to observe the behaviour for only 1 bookmark. Repeatedly we observed that the bookmark does not move unless there is a change in underlying tables that the View is made of.
    Could this behaviour by design?
    Thanks,
    Bala

  • Active Directory - Lingering Objects

    Hello,
    I'm having an issue with replication and I'm hoping someone can point me in the right direction.
    I have the Strict Replication setting enabled on all of my DCs.  I am running into a problem with replication failures due to lingering objects.  I ran repldiag.exe /removelingeringobjects /advisorymode on one of the DCs and it found 52 objects.
     However, the lingering objects are shared printer objects that are still in use in my organization.  What would be the impact of deleting these printer objects?  Would my workstations loose the ability to print to these printers?
    Thank you.

    Have you reviewed the link below?
    Lingering objects prevent Active Directory replication from occurring
    http://support.microsoft.com/kb/317097

Maybe you are looking for