Latency in replication

Hi I have new problem with SGD and windows applications.
2 SGD servers on the same VLAN form an array. However when I start a Windows application, kill it and start it again it gives the error;
Application: .../_ens/o=organization/cn=MS Word
Fault Code: Server.LaunchFailed
Fault String: Launch failed
if I kill the application and wait for a little more than a minute the application is launched correctly.
If I remove the replication, making every server a standalone primary the applications work fine as well.
Any help on this would be much appreciated.
Zainab

Possibly thier 2 load balancing is the problem.
This could be if
a) the time between both server differs more the 15s
b) the VLAN is slow.

Similar Messages

Chatty replication protocol (2.6 messages per transaction): bad settings?

Hi,
I'm trying to determine why for a two-site replication setup (Linux, BDB 4.6.21 with the latest patch) it seems like a single transaction can take up to 100 ms to be replicated under heavy load when the non-replicated transaction takes 5 ms.
The transaction in question is a fully-synchronized update (ie: a commit at site R1 should not return until R2 has also committed and flushed the transaction to disk), and there are only two sites in the replication group, the master and the replica.
Here are the statistics I gathered from my application, at the replica after it was promoted to the master (the master having been killed):
Replication: txnsApplied=3584, repMsgsProcessed=9390, repMsgsSent=17, repMsgsSendFailures=4, nextLSN=1/1162804, nextPages=0, pagesRecords=6, pagesRequested=0, status=3, waitingLSN=0/0, waitingPages=0
Replication Manager: connectionAttemptsFailed=0, connectionsDropped=1, repMessagesDropped=0, repMessagesQueued=0, permFailed=4
It seems like the replication protocol is quite chatty (2.6 messages per transaction), which may explain some of the latency.
I use 2048-byte pages, and the typical transaction size is no more than 1024 bytes; I experimented with relaxing the transactional guarantees (setTxnNoSync et al) but had a similar experience.
Does anyone have any suggestions for this environment configuration to increase the throughput of this kind of replication setup? Your help would be kindly appreciated.

Replication: txnsApplied=3584, repMsgsProcessed=9390,
repMsgsSent=17, repMsgsSendFailures=4,
nextLSN=1/1162804, nextPages=0, pagesRecords=6,
pagesRequested=0, status=3, waitingLSN=0/0,
waitingPages=0
Replication Manager: connectionAttemptsFailed=0,
connectionsDropped=1, repMessagesDropped=0,
repMessagesQueued=0, permFailed=4
It seems like the replication protocol is quite
chatty (2.6 messages per transaction), which may
explain some of the latency.The replication protocol is that each log record written to the
log is also transmitted to the client. Therefore, if your transaction
has a lot of operations, or if even a single update results in several
log records written (splitting a page, for example), each of those
log records will be transmitted to the client.
Does anyone have any suggestions for this environment
configuration to increase the throughput of this kind
of replication setup? Your help would be kindly
appreciated.You can try the bulk message configuration option. Look at
the dbenv->rep_set_config method with the DB_REP_CONF_BULK
flag. That option collects the log records locally in memory and
then sends them all either on a txn_commit operation or if the
buffer fills up. That should result in fewer messages.
However, it is also interesting that there were 4 message send failures
as well as 4 permFailed counts in your statistics. It is likely whatever
caused those resulted in some messages to rerequest the missing
records.
Sue LoVerso
Oracle

Replication Error between DC and PDC after a reboot.

Hi,
We have a very small server environment and having one DC and one ADC. Last week ADC got a sudden restart. After booting it shown one service failed error. Since then the ADC is not replicating with DC. Giving below the diagnosis
results of Dcdiag and FSMO check.
Domain Controller Diagnosis
Performing initial setup:
Done gathering initial info.
Doing initial required tests
Testing server: Default-First-Site-Name\DC
Starting test: Connectivity
......................... DC passed test Connectivity
Doing primary tests
Testing server: Default-First-Site-Name\DC
DNS Tests are running and not hung. Please wait a few minutes...
Running partition tests on : ForestDnsZones
Running partition tests on : DomainDnsZones
Running partition tests on : Schema
Running partition tests on : Configuration
Running partition tests on : bannaridc
Running enterprise tests on : bannaridc.com
Starting test: DNS
......................... bannaridc.com passed test DNS
Domain Controller Diagnosis
Performing initial setup:
* Verifying that the local machine backupdc, is a DC.
* Connecting to directory service on server backupdc.
* Collecting site info.
* Identifying all servers.
* Identifying all NC cross-refs.
* Found 2 DC(s). Testing 1 of them.
Done gathering initial info.
Doing initial required tests
Testing server: Default-First-Site-Name\BACKUPDC
Starting test: Connectivity
* Active Directory LDAP Services Check
* Active Directory RPC Services Check
......................... BACKUPDC passed test Connectivity
Doing primary tests
Testing server: Default-First-Site-Name\BACKUPDC
Starting test: Replications
* Replications Check
[Replications Check,BACKUPDC] A recent replication attempt failed:
From DC to BACKUPDC
Naming Context: DC=ForestDnsZones,DC=bannaridc,DC=com
The replication generated an error (1256):
The remote system is not available. For information about network troubleshooting, see Windows Help.
The failure occurred at 2014-05-15 12:29:41.
The last success occurred at 2014-05-12 09:23:27.
76 failures have occurred since the last success.
REPLICATION LATENCY WARNING
ERROR: Expected notification link is missing.
Source DC
Replication of new changes along this path will be delayed.
This problem should self-correct on the next periodic sync.
[Replications Check,BACKUPDC] A recent replication attempt failed:
From DC to BACKUPDC
Naming Context: DC=DomainDnsZones,DC=bannaridc,DC=com
The replication generated an error (1256):
The remote system is not available. For information about network troubleshooting, see Windows Help.
The failure occurred at 2014-05-15 12:29:41.
The last success occurred at 2014-05-12 09:33:40.
76 failures have occurred since the last success.
REPLICATION LATENCY WARNING
ERROR: Expected notification link is missing.
Source DC
Replication of new changes along this path will be delayed.
This problem should self-correct on the next periodic sync.
[Replications Check,BACKUPDC] A recent replication attempt failed:
From DC to BACKUPDC
Naming Context: CN=Schema,CN=Configuration,DC=bannaridc,DC=com
The replication generated an error (5):
Access is denied.
The failure occurred at 2014-05-15 12:29:41.
The last success occurred at 2014-05-12 09:23:26.
76 failures have occurred since the last success.
[Replications Check,BACKUPDC] A recent replication attempt failed:
From DC to BACKUPDC
Naming Context: CN=Configuration,DC=bannaridc,DC=com
The replication generated an error (5):
Access is denied.
The failure occurred at 2014-05-15 12:29:41.
The last success occurred at 2014-05-12 09:23:26.
76 failures have occurred since the last success.
REPLICATION LATENCY WARNING
ERROR: Expected notification link is missing.
Source DC
Replication of new changes along this path will be delayed.
This problem should self-correct on the next periodic sync.
[Replications Check,BACKUPDC] A recent replication attempt failed:
From DC to BACKUPDC
Naming Context: DC=bannaridc,DC=com
The replication generated an error (5):
Access is denied.
The failure occurred at 2014-05-15 12:29:42.
The last success occurred at 2014-05-12 09:42:25.
95 failures have occurred since the last success.
REPLICATION LATENCY WARNING
ERROR: Expected notification link is missing.
Source DC
Replication of new changes along this path will be delayed.
This problem should self-correct on the next periodic sync.
* Replication Latency Check
REPLICATION-RECEIVED LATENCY WARNING
BACKUPDC: Current time is 2014-05-15 13:24:11.
DC=ForestDnsZones,DC=bannaridc,DC=com
Last replication recieved from DC at 2014-05-12 09:23:27.
Latency information for 2 entries in the vector were ignored.
2 were retired Invocations. 0 were either: read-only replicas and are not verifiably latent, or dc's no longer replicating this nc. 0 had no latency information (Win2K DC).
DC=DomainDnsZones,DC=bannaridc,DC=com
Last replication recieved from DC at 2014-05-12 09:33:40.
Latency information for 2 entries in the vector were ignored.
2 were retired Invocations. 0 were either: read-only replicas and are not verifiably latent, or dc's no longer replicating this nc. 0 had no latency information (Win2K DC).
CN=Schema,CN=Configuration,DC=bannaridc,DC=com
Last replication recieved from DC at 2014-05-12 09:23:26.
Latency information for 2 entries in the vector were ignored.
2 were retired Invocations. 0 were either: read-only replicas and are not verifiably latent, or dc's no longer replicating this nc. 0 had no latency information (Win2K DC).
CN=Configuration,DC=bannaridc,DC=com
Last replication recieved from DC at 2014-05-12 09:23:26.
Latency information for 2 entries in the vector were ignored.
2 were retired Invocations. 0 were either: read-only replicas and are not verifiably latent, or dc's no longer replicating this nc. 0 had no latency information (Win2K DC).
DC=bannaridc,DC=com
Last replication recieved from DC at 2014-05-12 09:42:25.
Latency information for 2 entries in the vector were ignored.
2 were retired Invocations. 0 were either: read-only replicas and are not verifiably latent, or dc's no longer replicating this nc. 0 had no latency information (Win2K DC).
* Replication Site Latency Check
......................... BACKUPDC passed test Replications
Test omitted by user request: Topology
Test omitted by user request: CutoffServers
Starting test: NCSecDesc
* Security Permissions check for all NC's on DC BACKUPDC.
* Security Permissions Check for
DC=ForestDnsZones,DC=bannaridc,DC=com
(NDNC,Version 2)
* Security Permissions Check for
DC=DomainDnsZones,DC=bannaridc,DC=com
(NDNC,Version 2)
* Security Permissions Check for
CN=Schema,CN=Configuration,DC=bannaridc,DC=com
(Schema,Version 2)
* Security Permissions Check for
CN=Configuration,DC=bannaridc,DC=com
(Configuration,Version 2)
* Security Permissions Check for
DC=bannaridc,DC=com
(Domain,Version 2)
......................... BACKUPDC passed test NCSecDesc
Starting test: NetLogons
* Network Logons Privileges Check
Verified share \\BACKUPDC\netlogon
Verified share \\BACKUPDC\sysvol
......................... BACKUPDC passed test NetLogons
Starting test: Advertising
The DC BACKUPDC is advertising itself as a DC and having a DS.
The DC BACKUPDC is advertising as an LDAP server
The DC BACKUPDC is advertising as having a writeable directory
The DC BACKUPDC is advertising as a Key Distribution Center
Warning: BACKUPDC is not advertising as a time server.
......................... BACKUPDC failed test Advertising
Starting test: KnowsOfRoleHolders
Role Schema Owner = CN=NTDS Settings,CN=DC,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=bannaridc,DC=com
Role Domain Owner = CN=NTDS Settings,CN=DC,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=bannaridc,DC=com
Role PDC Owner = CN=NTDS Settings,CN=DC,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=bannaridc,DC=com
Role Rid Owner = CN=NTDS Settings,CN=DC,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=bannaridc,DC=com
Role Infrastructure Update Owner = CN=NTDS Settings,CN=DC,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=bannaridc,DC=com
......................... BACKUPDC passed test KnowsOfRoleHolders
Starting test: RidManager
* Available RID Pool for the Domain is 3107 to 1073741823
* DC.bannaridc.com is the RID Master
* DsBind with RID Master was successful
* rIDAllocationPool is 2607 to 3106
* rIDPreviousAllocationPool is 2607 to 3106
* rIDNextRID: 2771
......................... BACKUPDC passed test RidManager
Starting test: MachineAccount
Checking machine account for DC BACKUPDC on DC BACKUPDC.
* SPN found :LDAP/backupdc.bannaridc.com/bannaridc.com
* SPN found :LDAP/backupdc.bannaridc.com
* SPN found :LDAP/BACKUPDC
* SPN found :LDAP/backupdc.bannaridc.com/BANNARIDC
* SPN found :LDAP/bcbf105f-e755-4c24-b846-01d447834480._msdcs.bannaridc.com
* SPN found :E3514235-4B06-11D1-AB04-00C04FC2DCD2/bcbf105f-e755-4c24-b846-01d447834480/bannaridc.com
* SPN found :HOST/backupdc.bannaridc.com/bannaridc.com
* SPN found :HOST/backupdc.bannaridc.com
* SPN found :HOST/BACKUPDC
* SPN found :HOST/backupdc.bannaridc.com/BANNARIDC
* SPN found :GC/backupdc.bannaridc.com/bannaridc.com
......................... BACKUPDC passed test MachineAccount
Starting test: Services
* Checking Service: Dnscache
* Checking Service: NtFrs
* Checking Service: IsmServ
* Checking Service: kdc
* Checking Service: SamSs
* Checking Service: LanmanServer
* Checking Service: LanmanWorkstation
* Checking Service: RpcSs
* Checking Service: w32time
* Checking Service: NETLOGON
......................... BACKUPDC passed test Services
Test omitted by user request: OutboundSecureChannels
Starting test: ObjectsReplicated
BACKUPDC is in domain DC=bannaridc,DC=com
Checking for CN=BACKUPDC,OU=Domain Controllers,DC=bannaridc,DC=com in domain DC=bannaridc,DC=com on 1 servers
Object is up-to-date on all servers.
Checking for CN=NTDS Settings,CN=BACKUPDC,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=bannaridc,DC=com in domain CN=Configuration,DC=bannaridc,DC=com on 1 servers
Object is up-to-date on all servers.
......................... BACKUPDC passed test ObjectsReplicated
Starting test: frssysvol
* The File Replication Service SYSVOL ready test
File Replication Service's SYSVOL is ready
......................... BACKUPDC passed test frssysvol
Starting test: frsevent
* The File Replication Service Event log test
......................... BACKUPDC passed test frsevent
Starting test: kccevent
* The KCC Event log test
Found no KCC errors in Directory Service Event log in the last 15 minutes.
......................... BACKUPDC passed test kccevent
Starting test: systemlog
* The System Event log test
An Error Event occured. EventID: 0xC25A001D
Time Generated: 05/15/2014 12:30:20
(Event String could not be retrieved)
An Error Event occured. EventID: 0xC25A001D
Time Generated: 05/15/2014 12:49:04
(Event String could not be retrieved)
An Error Event occured. EventID: 0x40000004
Time Generated: 05/15/2014 12:53:20
Event String: The kerberos client received a
KRB_AP_ERR_MODIFIED error from the server
host/backupdc.bannaridc.com. The target name
used was
LDAP/bcbf105f-e755-4c24-b846-01d447834480._msdcs.bannaridc.com.
This indicates that the password used to encrypt
the kerberos service ticket is different than
that on the target server. Commonly, this is due
to identically named machine accounts in the
target realm (BANNARIDC.COM), and the client
realm. Please contact your system
administrator.
An Error Event occured. EventID: 0xC25A001D
Time Generated: 05/15/2014 13:12:19
(Event String could not be retrieved)
......................... BACKUPDC failed test systemlog
Test omitted by user request: VerifyReplicas
Starting test: VerifyReferences
The system object reference (serverReference)
CN=BACKUPDC,OU=Domain Controllers,DC=bannaridc,DC=com and backlink on
CN=BACKUPDC,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=bannaridc,DC=com
are correct.
The system object reference (frsComputerReferenceBL)
CN=BACKUPDC,CN=Domain System Volume (SYSVOL share),CN=File Replication Service,CN=System,DC=bannaridc,DC=com
and backlink on CN=BACKUPDC,OU=Domain Controllers,DC=bannaridc,DC=com
are correct.
The system object reference (serverReferenceBL)
CN=BACKUPDC,CN=Domain System Volume (SYSVOL share),CN=File Replication Service,CN=System,DC=bannaridc,DC=com
and backlink on
CN=NTDS Settings,CN=BACKUPDC,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=bannaridc,DC=com
are correct.
......................... BACKUPDC passed test VerifyReferences
Test omitted by user request: VerifyEnterpriseReferences
Test omitted by user request: CheckSecurityError
Running partition tests on : ForestDnsZones
Starting test: CrossRefValidation
......................... ForestDnsZones passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... ForestDnsZones passed test CheckSDRefDom
Running partition tests on : DomainDnsZones
Starting test: CrossRefValidation
......................... DomainDnsZones passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... DomainDnsZones passed test CheckSDRefDom
Running partition tests on : Schema
Starting test: CrossRefValidation
......................... Schema passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... Schema passed test CheckSDRefDom
Running partition tests on : Configuration
Starting test: CrossRefValidation
......................... Configuration passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... Configuration passed test CheckSDRefDom
Running partition tests on : bannaridc
Starting test: CrossRefValidation
......................... bannaridc passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... bannaridc passed test CheckSDRefDom
Running enterprise tests on : bannaridc.com
Starting test: Intersite
Skipping site Default-First-Site-Name, this site is outside the scope
provided by the command line arguments provided.
......................... bannaridc.com passed test Intersite
Starting test: FsmoCheck
GC Name: \\DC.bannaridc.com
Locator Flags: 0xe00003fd
PDC Name: \\DC.bannaridc.com
Locator Flags: 0xe00003fd
Time Server Name: \\DC.bannaridc.com
Locator Flags: 0xe00003fd
Preferred Time Server Name: \\DC.bannaridc.com
Locator Flags: 0xe00003fd
KDC Name: \\backupdc.bannaridc.com
Locator Flags: 0xe00001b8
......................... bannaridc.com passed test FsmoCheck
Test omitted by user request: DNS
Test omitted by user request: DNS
Please help me to resolve this issue.
Regards,
suren

Hi suren,
Error 1256 is logged as the replication status per partition as a result of the destination DC cancelling the sync request from the source DC due to a connectivity failure previously encountered.
Please refer to the articles below to troubleshoot the issue:
Troubleshooting AD Replication error 1256: The remote system is not available.
http://support.microsoft.com/kb/2200187
Troubleshooting AD Replication error 5: Access is denied
http://support.microsoft.com/kb/2002013
Regards,
Mandy
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.

GP Preference Items Throwing "Could not find a part of the path" Error in GP Management Console

Hello,
For background, I recovered two Server 2008 R2 Domain Controllers in the same domain from a JRNL_WRAP_ERROR
using the BurFlags registry key as outlined in KB290762. The non-authoritative restore seemed to resolve NtFrs/replication challenges, as now the FRS and System logs are free from any major errors and "repadmin /showreps" output looks clean.
As part of the cleanup process I am going through and checking all the policy objects. Policy objects that leverage group policy preferences are
throwing an error when the settings are viewed in the management console:
The following errors were encountered:
An unknown error occurred while data was gathered for this extension. Details: Could not find a part of the path 'C:\Users\administrator.YOURDOMAIN\AppData\Local\Temp\2\ny0ho1ht.tmp'.
This occurs for existing Group Policy Preference objects and those that are newly created. It is important note if I go to edit the policy in question
the preference settings are available, it is viewing them in the management console that seems to be the issue. What concerns me here is that the file it is looking for is stored in the local temp directory and not the SYSVOL directory. With replication issues
behind me I am not sure how to address this last piece of the puzzle.
Any assistance in getting this squared away you be appreciated.
Thanks!
Jordan

DCDIAG /C outputs the following error in relation to the VerifyEnterpriseRefrences test:
Starting test: VerifyEnterpriseReferences
The following problems were found while verifying various important DN
references. Note, that these problems can be reported because of
latency in replication. So follow up to resolve the following
problems, only if the same problem is reported on all DCs for a given
domain or if the problem persists after replication has had
reasonable time to replicate changes.
[1] Problem: Missing Expected Value
Base Object:
CN=DC04,OU=Domain Controllers,DC=YOURDOMAIN,DC=local
Base Object Description: "DC Account Object"
Value Object Attribute Name: msDFSR-ComputerReferenceBL
Value Object Description: "SYSVOL FRS Member Object"
Recommended Action: See Knowledge Base Article: Q312862
[2] Problem: Missing Expected Value
Base Object:
CN=DC03,OU=Domain Controllers,DC=YOURDOMAIN,DC=local
Base Object Description: "DC Account Object"
Value Object Attribute Name: msDFSR-ComputerReferenceBL
Value Object Description: "SYSVOL FRS Member Object"
Recommended Action: See Knowledge Base Article: Q312862
LDAP Error 0x20 (32) - No Such Object.
I am evaluating the suggested KB now but am not sure it is related to the issue at hand but posted it for completeness.
All other tests pass.

Setting Overrides on all relevant Rules and Monitors

Can someone please help me with the following question? I was reading the post below (I believe written by
Cameron
Fuller) detailing some best practice around overrides. It stated if you override a ‘parameter’ for one rule/monitor (e.g. let’s say a parameter
dealing with a threshold) you should override the parameter for ‘all’ rules and monitors 'that use this parameter'. More information from the post below
Make sure that an overridden parameter is set for every rule and for every monitor that uses the parameter
When you override a parameter, make sure that the parameter is configured for each rule that uses the parameter and for each monitor that uses the parameter. There may be more than
one rule or monitor that uses the particular parameter. For example, the following rules and monitors use the
Intersite Expected Max Latency parameter: Monitors
AD Replication Monitoring
Rules
AD Replication Performance Collection - Metric Replication Latency
AD Replication Performance Collection - Metric Replication Latency: Maximum
AD Replication Performance Collection - Metric Replication Latency: Minimum
AD Replication Performance Collection - Metric Replication Latency: Average
Now my question is:
How do I discovery all the rules/monitors that are using this particular ‘parameter’?
For example using either PowerShell or SQL query. If PowerShell I assume you would have to
use Get-Rule or Get-SCOMRule with the –Criteria filter. Does anyone have an example please?
As a side note I could do the following in PowerShell as one way to find all cmdlets what use the –path parameter as one of their parameters
Get-Command -CommandType cmdlet | where {$_.parameters.keys -eq "path"}
So to recap: As above if I want to set an override on ‘Intersite Expected Max Latency’
for a given rule or monitor how do I find all other rules/monitors also use ‘Intersite Expected Max Latency’
as I can override these too?
Thanks All
AAnotherUser__
AAnotherUser__

Hi,
We may use the specific word to filter out those proper rules and monitors， to filter out all monitors that which name contains latency:
get-scommonitor -name “*latency*”
Please refer to the below links to find more details about the get-scomrule and get-scommonitor command:
Get-SCOMRule
http://technet.microsoft.com/en-us/library/hh918556(v=sc.20).aspx
Get-SCOMMonitor
http://technet.microsoft.com/en-us/library/hh918469(v=sc.20).aspx
Regards,
Yan Li
Regards, Yan Li

How many sites can a DAG belong?

Hi all,
How many sites/data centres can a DAG belong? I am quite familiar using 2 data centres to implement a DAG however I have a scenario where adding an additional data centre may be an option. The DAG would have a single primary DC hosting active
databases (plus FSW) whilst the other 2 DCs would be for passive copies.
Is this a scenario supported by Microsoft?
Any help/links to definitive info would be great.
paul.

I dont think there is set number.
If you are looking for "official" guidance:
http://blogs.technet.com/b/exchange/archive/2014/04/21/the-preferred-architecture.aspx
To achieve a highly available and site resilient architecture, you must have two or more datacenters that are well-connected (ideally, you want a low round-trip network latency, otherwise replication and the client experience are adversely affected).
In addition, the datacenters should be connected via redundant network paths supplied by different operating carriers.
Note the reference to "two or more datacenters"
Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

Error in GP archiving

Hi Experts.
I'm having an error while trying to do the Guided Procedures Archiving.
The error is:
Operation could not be completed
com.sap.caf.eu.gp.model.arch.exception.ArchException: Operation could not be completed
     at com.sap.caf.eu.gp.model.arch.logging.ExceptionHandler.throwArchException(ExceptionHandler.java:53)
     at com.sap.caf.eu.gp.model.arch.impl.ArchOperationPerformer.invokeArchivingAPI(ArchOperationPerformer.java:222)
     at com.sap.caf.eu.gp.model.arch.impl.ArchOperationPerformer.archiveProcessInstance(ArchOperationPerformer.java:117)
     at com.sap.caf.eu.gp.model.arch.impl.ArchOperationPerformer.archive(ArchOperationPerformer.java:63)
     at com.sap.caf.eu.gp.model.arch.ArchiveBeanBean.onMessage(ArchiveBeanBean.java:32)
     at com.sap.caf.eu.gp.model.arch.ArchiveBeanBean0_0Extension.onMessage(ArchiveBeanBean0_0Extension.java:137)
     at com.sap.jms.client.session.Session.run(Session.java:619)
     at com.sap.engine.services.ejb.message.RunnableObject.run(RunnableObject.java:49)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
Caused by: java.lang.IllegalArgumentException: Invalid or empty URI!
     at com.sap.caf.eu.gp.model.arch.impl.ArchOperationPerformer.invokeArchivingAPI(ArchOperationPerformer.java:217)
     ... 10 more
It says something about an "Invalid or empty URI".
On step 4 of manual archiving (Select Instances), on the "Process Instance" table, every instance has empty values on columns: "Instance Name" and "Template Name" (the rest of the columns have valid values: template version, complete date, initiator and status).
is this the cause of the error?
how can I solve this problem?
Regards.

DCDIAG /C outputs the following error in relation to the VerifyEnterpriseRefrences test:
Starting test: VerifyEnterpriseReferences
The following problems were found while verifying various important DN
references. Note, that these problems can be reported because of
latency in replication. So follow up to resolve the following
problems, only if the same problem is reported on all DCs for a given
domain or if the problem persists after replication has had
reasonable time to replicate changes.
[1] Problem: Missing Expected Value
Base Object:
CN=DC04,OU=Domain Controllers,DC=YOURDOMAIN,DC=local
Base Object Description: "DC Account Object"
Value Object Attribute Name: msDFSR-ComputerReferenceBL
Value Object Description: "SYSVOL FRS Member Object"
Recommended Action: See Knowledge Base Article: Q312862
[2] Problem: Missing Expected Value
Base Object:
CN=DC03,OU=Domain Controllers,DC=YOURDOMAIN,DC=local
Base Object Description: "DC Account Object"
Value Object Attribute Name: msDFSR-ComputerReferenceBL
Value Object Description: "SYSVOL FRS Member Object"
Recommended Action: See Knowledge Base Article: Q312862
LDAP Error 0x20 (32) - No Such Object.
I am evaluating the suggested KB now but am not sure it is related to the issue at hand but posted it for completeness.
All other tests pass.

Failed test VerifyEnterpriseReferences

Hello,
DCDiag is failing at "VerifyEnterpriseReferences". Any assistance on this would be greatly appreciated, thanks!
Please see full details of error below:
      Starting test: VerifyEnterpriseReferences
         The following problems were found while verifying various important DN
         references. Note, that these problems can be reported because of
         latency in replication. So follow up to resolve the following
         problems, only if the same problem is reported on all DCs for a given
         domain or if the problem persists after replication has had
         reasonable time to replicate changes.
           [1] Problem: Missing Expected Value
             Base Object:
            CN=AUCHMAIL1,CN=Domain System Volume (SYSVOL share),CN=File Replication Service,CN=System,DC=auchconstruction,DC=com
             Base Object Description: "SYSVOL FRS Member Object"
             Value Object Attribute Name: frsComputerReference
             Value Object Description: "DC Account Object"
             Recommended Action: Check if this server is deleted, and if so
            clean up this DCs SYSVOL FRS Member Object. Also see Knowledge
            Base Article: Q312862
           [2] Problem: Missing Expected Value
             Base Object:
            CN=AUCHMAIL1,CN=Domain System Volume (SYSVOL share),CN=File Replication Service,CN=System,DC=auchconstruction,DC=com
             Base Object Description: "SYSVOL FRS Member Object"
             Value Object Attribute Name: serverReference
             Value Object Description: "DSA Object"
             Recommended Action: Check if this server is deleted, and if so
            clean up this DCs SYSVOL FRS Member Object. Also see Knowledge
            Base Article Q312862
         ......................... AUCHFILE01 failed test VerifyEnterpriseReferences

I have found the solution.
The server (AUCHMAIL1) was removed awhile back, but the reference to the server still remained in ADSI. I deleted the old server entry via ADSIedit.msc (Domain -> DC -> CN=System -> CN=File Replication Service -> CN=Domain System Volume (SYSVOL
share) -> CN=AUCHMAIL1) and confirmed no further errors thrown against 'VerifyEnterpriseReferences' during a DCDIAG.

DCDIAG

Hello -
I ran a simple DCDIAG with no switches and the errors below came back, I'm not sure how to fix these errors. Please help, I'd sure appreciate any guidance as to what the errors mean and how to go about fixing them.
See errors below:
Starting test: SystemLog
         An Warning Event occurred. EventID: 0x80001795
            Time Generated: 04/10/2014   12:52:35
            Event String:
            The program w3wp.exe, with the assigned process ID 7684, could not authenticate locally by using the target name HTTP/remote.legacyhc.com. The target name used is not valid. A target
name should refer to one of the local computer names, for example, the DNS host name.
         An Warning Event occurred. EventID: 0x0000043D
            Time Generated: 04/10/2014   12:53:17
            Event String:
            Windows failed to apply the Group Policy Registry settings. Group Policy Registry settings might have its own log file. Please click on the "More information" link.
         An Warning Event occurred. EventID: 0x0000043D
            Time Generated: 04/10/2014   12:58:22
            Event String:
            Windows failed to apply the Group Policy Registry settings. Group Policy Registry settings might have its own log file. Please click on the "More information" link.
         An Warning Event occurred. EventID: 0x0000043D
            Time Generated: 04/10/2014   13:03:27
            Event String:
            Windows failed to apply the Group Policy Registry settings. Group Policy Registry settings might have its own log file. Please click on the "More information" link.
         An Warning Event occurred. EventID: 0x0000043D
            Time Generated: 04/10/2014   13:08:31
            Event String:
            Windows failed to apply the Group Policy Registry settings. Group Policy Registry settings might have its own log file. Please click on the "More information" link.
         An Warning Event occurred. EventID: 0x0000043D
            Time Generated: 04/10/2014   13:13:37
            Event String:
            Windows failed to apply the Group Policy Registry settings. Group Policy Registry settings might have its own log file. Please click on the "More information" link.
         An Warning Event occurred. EventID: 0x0000043D
            Time Generated: 04/10/2014   13:18:41
            Event String:
            Windows failed to apply the Group Policy Registry settings. Group Policy Registry settings might have its own log file. Please click on the "More information" link.
         An Warning Event occurred. EventID: 0x0000043D
            Time Generated: 04/10/2014   13:23:45
            Event String:
            Windows failed to apply the Group Policy Registry settings. Group Policy Registry settings might have its own log file. Please click on the "More information" link.
         An Warning Event occurred. EventID: 0x0000043D
            Time Generated: 04/10/2014   13:28:51
            Event String:
            Windows failed to apply the Group Policy Registry settings. Group Policy Registry settings might have its own log file. Please click on the "More information" link.
         An Warning Event occurred. EventID: 0x0000043D
            Time Generated: 04/10/2014   13:33:55
            Event String:
            Windows failed to apply the Group Policy Registry settings. Group Policy Registry settings might have its own log file. Please click on the "More information" link.
         An Warning Event occurred. EventID: 0x0000043D
            Time Generated: 04/10/2014   13:38:59
            Event String:
            Windows failed to apply the Group Policy Registry settings. Group Policy Registry settings might have its own log file. Please click on the "More information" link.
         An Error Event occurred. EventID: 0xC0002719
            Time Generated: 04/10/2014   13:42:34
            Event String:
            DCOM was unable to communicate with the computer 208.67.220.220 using any of the configured protocols.
         An Error Event occurred. EventID: 0xC0002719
            Time Generated: 04/10/2014   13:42:56
            Event String:
            DCOM was unable to communicate with the computer 208.67.222.222 using any of the configured protocols.
         An Error Event occurred. EventID: 0xC0002719
            Time Generated: 04/10/2014   13:43:17
            Event String:
            DCOM was unable to communicate with the computer 8.8.4.4 using any of the configured protocols.
         An Error Event occurred. EventID: 0xC0002719
            Time Generated: 04/10/2014   13:43:38
            Event String:
            DCOM was unable to communicate with the computer 8.8.8.8 using any of the configured protocols.
         An Warning Event occurred. EventID: 0x0000043D
            Time Generated: 04/10/2014   13:44:05
            Event String:
            Windows failed to apply the Group Policy Registry settings. Group Policy Registry settings might have its own log file. Please click on the "More information" link.
         ......................... LEGACYDC failed test SystemLog
      Starting test: Topology
         ......................... LEGACYDC passed test Topology
      Starting test: VerifyEnterpriseReferences
         The following problems were found while verifying various important DN
         references. Note, that these problems can be reported because of
         latency in replication. So follow up to resolve the following
         problems, only if the same problem is reported on all DCs for a given
         domain or if the problem persists after replication has had
         reasonable time to replicate changes.
            [1] Problem: Missing Expected Value
             Base Object:
            CN=PETERSONDC1,OU=Domain Controllers,DC=legacyhc,DC=local
             Base Object Description: "DC Account Object"
             Value Object Attribute Name: msDFSR-ComputerReferenceBL
             Value Object Description: "SYSVOL FRS Member Object"
             Recommended Action: See Knowledge Base Article: Q312862
            [2] Problem: Missing Expected Value
             Base Object:
            CN=EVANSTONDC,OU=Domain Controllers,DC=legacyhc,DC=local
             Base Object Description: "DC Account Object"
             Value Object Attribute Name: msDFSR-ComputerReferenceBL
             Value Object Description: "SYSVOL FRS Member Object"
             Recommended Action: See Knowledge Base Article: Q312862
            [3] Problem: Missing Expected Value
             Base Object:
            CN=LAGRANGE-VDC,OU=Domain Controllers,DC=legacyhc,DC=local
             Base Object Description: "DC Account Object"
             Value Object Attribute Name: msDFSR-ComputerReferenceBL
             Value Object Description: "SYSVOL FRS Member Object"
             Recommended Action: See Knowledge Base Article: Q312862
            [4] Problem: Missing Expected Value
             Base Object:
            CN=ARLINGTON-VDC,OU=Domain Controllers,DC=legacyhc,DC=local
             Base Object Description: "DC Account Object"
             Value Object Attribute Name: msDFSR-ComputerReferenceBL
             Value Object Description: "SYSVOL FRS Member Object"
             Recommended Action: See Knowledge Base Article: Q312862
            [5] Problem: Missing Expected Value
             Base Object:
            CN=AURORA-VDC,OU=Domain Controllers,DC=legacyhc,DC=local
             Base Object Description: "DC Account Object"
             Value Object Attribute Name: msDFSR-ComputerReferenceBL
             Value Object Description: "SYSVOL FRS Member Object"
             Recommended Action: See Knowledge Base Article: Q312862
            LDAP Error 0x5e (94) - No result present in message.
         ......................... LEGACYDC failed test

The note above is correct, the IPs in your DCDIAG are all public DNS servers:
208.67.220.220 and 208.67.222.222 are OpenDNS
8.8.8.8 and 8.8.4.4 are Google's DNS servers
The KB article that is referenced is calling out deleted FRS objects, so you may have some corruption in your AD environment.
I would take a look at the DNS, FRS, and other AD related logs and see what is there. Hopefully you have a recent backup that you can recover with if needed.
Although it is possible the issue is that your account does not have the rights to run the dcdiag. The event logs should have additional details that help.

Sccm 2012 hierachy consideration

The system consists of 10 data-centers, 200+ remote (geology) sites and has about 50,000 clients in total, with a single forest.
Now, when come into the plan/design a sccm2012 hierarchy for this system, I have some questions regarding site systems placement in data-centers:
1. Do I need to place a primary site in each of the data-centers? This will result in 10 primary sites with a CAS.
2. Can I place only one primary site in one (the largest) data-center, and place a MP/DP in each of the rest data-centers? This may lead to a stand-alone primary site.
3. Can I place two primary sites in two major data-centers with a CAS, and place a MP/DP in each of the rest data-centers?
4. In case placing one or two primary sites, can I place just a DP instead of MP/DP in each of the rest of the data-centers?
For remote sites with 50+ clients I will consider place a DP over there.
Thanks in advance for your help.

I concur with Narcoticoo (lots of folks agreeing on this thread :-) ) that the consultant didn't know what he was talking about -- I'd even go so far as saying you should ask for your money back.
For the question of "is a secondary preferable for higher bandwidth or a low/narrow bandwidth?", low bandwidth or high client count is where secondary sites are best used. This is because they compress, throttle, and schedule most client
to MP traffic destined for the primary site including state and status messages and hw and sw inventory. The overhead caused by this traffic is quite small though in normal scenarios which is why they aren't strictly required/recommended unless the bandwidth
between the clients at a location and the MP will be over-utilized. This is a subjective standard though because it truly depends on the network involved as well as the client count.
For the question "As a secondary in sccm2012 also has a database (express though), does it cause latency of replication when bandwidth is not good enough?" the answer is not black and white. If the links are truly terrible, volatile, and/or have
extreme latency, like say VSAT connections to roaming ships, then yes, the replication between the secondary site and primary site is an issue. In these extreme cases, the use of third-party, complementary tools is a valid option. Generally though, the trade-off
of less client chattiness combined with the scheduling, throttling, and compression of upward client traffic is beneficial where bandwidth is a concern.
Jason | http://blog.configmgrftw.com | @jasonsandys

DCDIAG " VerifyEnterpriseReferences" Failed

From last few days we are observing that our ROOT DC is giving very slow response when anybody is trying to log in. Post running all the command, we have got the below error. It's basically DCDIAG command for testing all the key services in the Domain Controller.
     Starting test: VerifyEnterpriseReferences
         The following problems were found while verifying various important DN
         references. Note, that these problems can be reported because of
         latency in replication. So follow up to resolve the following
         problems, only if the same problem is reported on all DCs for a given
         domain or if the problem persists after replication has had
         reasonable time to replicate changes.
            [1] Problem: Missing Expected Value
             Base Object: CN=LostAndFoundConfig,CN=Configuration,DC=CONTOSO,DC=COM
             Base Object Description: "Server Object"
             Value Object Attribute: serverReference
             Value Object Description: "DC Account Object"
             Recommended Action: This could hamper authentication (and thus
            replication, etc). Check if this server is deleted, and if so
            clean up this DCs Account Object. If the problem persists and
            this is not a deleted DC, authoratively restore the DSA object from
            a good copy, for example the DSA on the DSA's home server.
         ......................... FORESTROOTDC failed test

Connect to the "Configuration" partition using ADSIEdit and browse to "CN=LostAndFoundConfig,CN=Configuration,DC=CONTOSO,DC=COM" verify that the ntdsa object belongs to a demoted/deleted DC - if so delete the object(s)
Open the ADSI Edit MMC snap-in.
On the Action menu, click Connect to.
In the Connection Settings dialog box, in the Name field, enter a name for the ADSI connection. Under
Connection Point, select Select a well known Naming Context, and then select
Configuration in the drop-down menu. Click OK.
In the left pane, double-click the Configuration object, and then double-click
LostAndFoundConfig.
In the right pane, delete all objects and containers. Right-click the object or container, click
Delete, and then click Yes.
Exit ADSI Edit.
Enfo Zipper
Christoffer Andersson – Principal Advisor
http://blogs.chrisse.se - Directory Services Blog

FYI: Testing Active Directory Replication Latency/Convergence Through PowerShell (Update 2)

see:
(2014-02-01) Testing Active Directory Replication Latency/Convergence Through PowerShell (Update
2)
Jorge de Almeida Pinto [MVP-DS] | Principal Consultant | BLOG: http://jorgequestforknowledge.wordpress.com/

Might that link has been been broken.Here is the link
http://jorgequestforknowledge.wordpress.com/2014/02/01/testing-active-directory-replication-latencyconvergence-through-powershell-update-2/
Nice Jorge. Thanks for sharing.
Regards~Biswajit
Disclaimer: This posting is provided & with no warranties or guarantees and confers no rights.
MCP 2003,MCSA 2003, MCSA:M 2003, CCNA, MCTS, Enterprise Admin
MY BLOG
Domain Controllers inventory-Quest Powershell
Generate Report for Bulk Servers-LastBootUpTime,SerialNumber,InstallDate
Generate a Report for installed Hotfix for Bulk Servers

Latency at the apply side in multi master replication

Hi Gurus,
We are facing some multi master replication latency always at one side . Ex: Site1 -> Site 3 . Transactions from site 1 always gets applied on Site 3 with some latency though the latency doesnt happen while applying from Site 1 - Site 2 for the same transaction originating at site 1 in 3 site(3 way) multi master replication environment.
We have investigated into it and now looking to check the system replication tables which would be involved at the apply side (ex:- Site 3).
Could someone pls let me know all the system replication tables that would be involved at the apply side which can impact the latency .I know few of them but dont know the all of them.
System.def$_AQERROR
System.def$_ERROR
System.def$_ORIGIN
Thanks

I would say that 50, 50 and 75 are a Very Large number of Job Queue processes. Do you really have that many jobs that need to run concurrently ?
Since Advanced Replication Queues are maintained in only a small set of tables you might end up having "buffer busy waits" or "read by other session" waits or latch waits.
BTW, what other factors did you eliminate before deciding to look at the Replication tables ?
See the documentation on monitoring performance in replication :
http://download.oracle.com/docs/cd/B10501_01/server.920/a96568/rarmonit.htm#35535
If you want to look at the "tables" start with the Replication Data Dictionary Reference at
http://download.oracle.com/docs/cd/B10501_01/server.920/a96568/rarpart4.htm#435986
and then drill down through the View definitions to the underlying base tables.

Help needed on Fixing replication latency issues

Hi Team,
Good day!!!
I am new to replication setup and I am working on the issues with replication latency.
Can you please provide us your experience and expertise on fixing and troubleshooting replication issues.
Below are some queries on that,
1) How to check the replication errors?
2) how to find out the replication latency?
3) What are the steps to fix the replication latency?
4) how to teoubleshoot the issues coming on replication latency?
Awaiting your valuable response and replies.
Thanks in advance,
Sarvan.N

Hi Sarvan,
Firstly, usually, we check replication errors via the Replication Monitor or by viewing replication agent job history. Besides the two methods, we can also check replication errors from the SQL Server error log and so on. For more details,
please review this
article.
Secondly, based on my research, the latency issues always occur in Transactional Replication. We can check that if there are latency issues by using Replication Monitor as well as Transact-SQL commands. Below is an example that posts a tracer token
record and uses the returned ID of the posted tracer token to view latency information. Refer to :
Measure Latency and Validate Connections for Transactional Replication.
DECLARE @publication AS sysname;
DECLARE @tokenID AS int;
SET @publication = N'AdvWorksProductTran';
USE [AdventureWorks2012]
-- Insert a new tracer token in the publication database.
EXEC sys.sp_posttracertoken
@publication = @publication,
@tracer_token_id = @tokenID OUTPUT;
SELECT 'The ID of the new tracer token is ''' +
CONVERT(varchar,@tokenID) + '''.'
GO
-- Wait 10 seconds for the token to make it to the Subscriber.
WAITFOR DELAY '00:00:10';
GO
-- Get latency information for the last inserted token.
DECLARE @publication AS sysname;
DECLARE @tokenID AS int;
SET @publication = N'AdvWorksProductTran';
CREATE TABLE #tokens (tracer_id int, publisher_commit datetime)
-- Return tracer token information to a temp table.
INSERT #tokens (tracer_id, publisher_commit)
EXEC sys.sp_helptracertokens @publication = @publication;
SET @tokenID = (SELECT TOP 1 tracer_id FROM #tokens
ORDER BY publisher_commit DESC)
DROP TABLE #tokens
-- Get history for the tracer token.
EXEC sys.sp_helptracertokenhistory
@publication = @publication,
@tracer_id = @tokenID;
GO
Thirdly, transactional replication latency issues could be caused by many factors, such as network traffic or bandwidth constraints, transactional load on the publisher, system resources, blocking/locking issues and so on. I recommend you troubleshoot latency
issues referring to the following blog.
http://blogs.msdn.com/b/repltalk/archive/2010/02/21/transactional-replication-conversations.aspx
Thanks,
Lydia Zhang

FYI: Testing SYSVOL Replication Latency/Convergence Through PowerShell (Update 2)

see:
(2014-02-02)
Testing SYSVOL Replication Latency/Convergence Through PowerShell (Update 2)
Jorge de Almeida Pinto [MVP-DS] | Principal Consultant | BLOG: http://jorgequestforknowledge.wordpress.com/

see:
http://jorgequestforknowledge.wordpress.com/2014/02/16/testing-active-directory-replication-latencyconvergence-through-powershell-update-3/
Jorge de Almeida Pinto [MVP-DS] | Principal Consultant | BLOG: http://jorgequestforknowledge.wordpress.com/

Latency in replication

Similar Messages

Maybe you are looking for