Enqueue replication service in Netweaver 7.1 (HA setup)

Hi,
I've setup a ERS instance along with an ASCS on my new Netweaver 7.1 installation for HA. I have a remote app server running on host B with the ASCS, Database and ERS on host A.
When I shutdown the ASCS, the ERS no longer works (ensmon crashes), but before everything was ok:
get replinfo request executed successfully
Replication is enabled in server, repl. server is connected
Replication is active
I also tested with enqt and I am not seeing the behavior describe by the documentation (enqt hangs when the ASCS is shutdown and recovers when ASCS is back up).
What I don't understand, is that nothing in the applications servers seems to indication that another enqueue server exists; other than the 3 parameters:
enque/process_location = REMOTESA
DEFAULT.PFL:enque/serverhost = hostA
DEFAULT.PFL:enque/serverinst = 81 (system number of the ASCS)
DEFAULT.PFL:enque/deque_wait_answer = TRUE
Any ideas?
Thanks
-Cyril

Hello,
What do your logs say ?
Has any configuration been changed ?
Regards,
Siddhesh

Similar Messages

Enqueue replication service is not starting

Hello Everyone,
We are running SAP Netweaver Portal NW7.2 SP6 on windows 2003 sp2 , microsoft cluster with two app servers.
We just did the upgrade from Nw 7.1 sp6 7.2 SP6 a month ago , and everything was ok :
Then yesterday , I realised the SAPSTARTSRV.exe file on these locations c:\windows\system32 & c:\windows\SAPcluster are old , then I copy this file from the O:\usr\sap\PIQ\SYS\exe\uc\NTAMD64 and remove the old files and replace them with these two files: SAPSTARTSRV.exe & SAPSTARTSRV.EXE.NEW
but after that SAPSID_XX service "enqueue replication service" that's located at D:\usr\sap\PIQ\ERS21\exe\sapstartsrv.exe" pf="D:\usr\sap\PIQ\ERS21\profile\START_ERS21_alfjepqon01a" is not start again
If I run it as a command in command line, I don't get any error but everytime I try to start the service , this is the error:
"The SAPSID_XX service terminated unexpectedly. It has done this 1 time(s)."
I try to create different service name with the same properties, but I've got the same error .
When I restart the server , I see below error:
"The SAPSID_XX service hung on starting"
meanwhile I see this warnimg in Application log , as well:
"Windows saved user Domain\SAPServiceSID registry while an application or service was still using the registry during log off. The memory used by the user's registry has not been freed. The registry will be unloaded when it is no longer in use.
This is often caused by services running as a user account, try configuring the services to run in either the LocalService or NetworkService account."
the User "Domain\SAPServiceSID" it's the user we are using to run the SAPSID_XX service.
Please let me know if you have any idea or suggestion.
Thanks

Hi Sunny,
Thanks for your reply,I just check this SAP note and follow their procedure to uninstall and install the service, but I've got the same error when I try to start the service
Any suggestion?
Thanks

MSCS H/A enqueue, replication and message servers services

Hi,
I'm looking at the documentation about "Installation of multiple SAP Systems in MSCS: MSSQL Server" but I have a few questions about the SCS and ASCS process.
Are the process setup as generic cluster service? Or are they SAP provided cluster services?
What monitoring is done with the the enqueue, replication and message server services in the cluster?

Mike,
The SAPINST installer will install SCS and ASCS services into MSCS for you. They are installed inside the SAP group in cluster.
The message servers, controlled by either SCS is HA with MSCS. The enqueue services is HA with installation of ERS locally on both nodes. SCS + ERS + ERS provides a triangular HA that means the services is always on and can withstand an cluster failover. The cluster only controls the SCS service. The ERS services are local to each server.
Let me know if I did not answer the question.
jwise

DAG - Backup failing on 1 DB only with error - The Microsoft Exchange Replication service VSS Writer instance ID failed with error code 80070020 when preparing for a backup of database 'DB012'

Hi Board,
i´ve search across the board, technet and symantec sites but did not found a hint about my problem.
we drive a 2 node DAG (Location1-Ex1-mb1
Location2-exc1-mb1), on SP2 RU4 patchlevel with 40 Databases.
Since some time the backup of one - and only one DB - is failing with these events, logged on the Mailboxserver on which the passive DB is hosted.
Log Name:      Application
Source:        MSExchangeRepl
Date:          28.09.2012 00:37:17
Event ID:      2112
Task Category: Exchange VSS Writer
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      Location1-Exc1-MB1
Description: The Microsoft Exchange Replication service VSS Writer instance 1ab7d204-609a-4aea-b0a7-70afb0db38de failed with error code 80070020 when preparing for a backup of database 'DB012'.
Followed by
Log Name:      Application
Source:        MSExchangeRepl
Date:
01.10.2012 03:33:06
Event ID:      2024
Task Category: Exchange VSS Writer
Level:         Error
Keywords:      Classic
User:
N/A
Computer:      Location1-Exc1-MB1
Description:
The Microsoft Exchange Replication service VSS Writer (Instance 42916d80-36c1-4f73-86d0-596d30226349) failed with error 80070020 when preparing for a backup.
The backup Application - Symantec Backup Exec 2010 R3 – states, this error
Snapshot provider error (0xE000FED1): A failure occurred querying the Writer status.
Check the Windows Event Viewer for details.
Writer Name: Exchange Server, Writer ID: {76FE1AC4-15F7-4BCD-987E-8E1ACB462FB7}, Last error: The VSS Writer failed, but the operation can be retried (0x800423f3), State: Stable (1).
Symatec suggests within http://www.symantec.com/business/support/index?page=content&id=TECH184095
to restart the MS Exchange Replication Service – BUT the mentioned eventID
8229 isn´t present on any of the both Mailboxservers.
The affected Database is active on Location2-Exc1-Mb1 Server and in an overall healthy state. I found during my research, that below Location2-Exc1-Mb1 Server, there are not removed shadow copies present!
This confuses me, since all Backups are normally taken from the passive copy of a Database.
So my questions to the board are:
* Does anyone is facing similar issues?
* Can someone explain why snapshots are present on the Mailboxserver hosting the Active Database, whilst the errors are logged on the passive one?
-          * Does someone know the conditions, why shadows copies remain and
aren´t removed in a proper manner?
What can cause the circumstance, that only 1 DB is facing such issues?
Any suggestion is welcome!
BR
Markus

Hi Lenora,
I´ve encreases VSS / Exchange Backup Log levels to expert, before starting
those things i´ve all tried now:
- Backup from passive DB (forced within Symantec Backup Exec)
- Backup from active DB (forced within Symantec Backup Exec)
- Backup from passive DB without GRT enabled (forced within Symantec Backup Exec)
- Backup from active DB without GRT enabled(forced within Symantec Backup Exec)
All those attempts failed.
But brought some more details - the backup against the active DB states, that there is still a backup in progress and therefore this backup is cancelled by VSS.
The Solution was, that i´ve needed to restart the Exchange Replication Service on the Mailbox Server hosting the passive DB.
Backups are working again on all DBs!
THX for your replys.
Best regards
Markus

Get-mailboxdatabasecopystatus -identity DBNAME | fl gives errors "The Microsoft Exchange Replication service encountered an error while attempting to start a replication instance for". DB is mounted and the DB copies are in healthy status.

We are getting a SCOM alert " Database copy isn''''t keeping up with the changes on the active database copy and has failed."
When we go to the mailbox server and check we found all the Mailbox DB's are mounted properly and their copies are in healthy state. Further digging to this problem we found that there are no critical events to this DB in the eventviewer.
When we runt he get-mailboxdatabasecopystatus -identity DBNAME | Fl then in the ErrorMessage section we get error "The Microsoft Exchange Replication service encountered an error while attempting to start a replication instance for . If the copy doesn't
recover automatically, administrator intervention may be necessary. Error: The directory is not empty."
ErrorEventID : 4126
In the event viewer we get a Information event 4114 saying the DB redundancy health check passed and in the details section we get the same error message mentioned above.
Also we observed that the "MSExchange Replication" counter "Failed" is set to 1 for this perticular DB but is is set to 0 for the other DB's. Tried restarting the MSEXChange replication service but still the "Failed" counter
is 1 and the SCOM alert is still active.
The version is Exchange 2010 SP3 UR5
Any clues???

Hi,
From your description, this issue only affect one mailbox datatabase.
Please use the Update-MailboxDatabaseCopy command to check result.
If it doesn't work, please dismount your active database copy and check if this is Clean Shutdown, if it's dirty shutdown, please bring to clean shutdown and mount this database copy. Then run the Update-MailboxDatabaseCopy command again to check result.
Best regards,
Belinda Ma
TechNet Community Support

Microsoft Exchange Mailbox Replication service was unable to process jobs in a mailbox database 1006.

HI all,
I ran into a problem with one of the servers in my DAG. Due to a backup failure, the log partition filled up and the Exchange database went offline on this particular server. The DAG continued to function on the other server. So this particular
DB01 had only some test accounts in it so I removed the database copy. Unfortunately the removal must not have completed correctly.
After recovering the needed space in the partition, I tried to recopy the database and it failed. So I deleted the entire database from the active server and it successfully removed it from the active server. Now on both the servers the database
is not showing, however I'm receiving the error below which indicates to me that the service still thinks the database exists. I am also getting event 4113 Database redundancy health check failed for the database copy as it shows there is only one copy
of the database (failed redundancy) but there should be zero copies.
This database no longer exists in AD as I have verified this with ADSI so it must have something on the exchange server that is still telling the service the database exists.
Can you point me to the location to clean this up?
Log Name:      Application
Source:        MSExchange Mailbox Replication
Date:          02/25/2011 2:00:07 PM
Event ID:      1006
Task Category: Service
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      email1.domain.com
Description:
The Microsoft Exchange Mailbox Replication service was unable to process jobs in a mailbox database.
Database: DB01
Error: MapiExceptionUnknownUser: Unable to open message store. (hr=0x80004005, ec=1003)
Diagnostic context:
    Lid: 55847   EMSMDBPOOL.EcPoolSessionDoRpc called [length=243]
    Lid: 43559   EMSMDBPOOL.EcPoolSessionDoRpc returned [ec=0x0][length=200][latency=0]
    Lid: 23226   --- ROP Parse Start ---
    Lid: 27962   ROP: ropLogon [254]
    Lid: 17082   ROP Error: 0x3EB
    Lid: 26937
    Lid: 21921   StoreEc: 0x3EB
    Lid: 27962   ROP: ropExtendedError [250]
    Lid: 1494    ---- Remote Context Beg ----
    Lid: 26426   ROP: ropLogon [254]
    Lid: 22086
    Lid: 27206
    Lid: 17990
    Lid: 16966   StoreEc: 0x8004010F
    Lid: 31433   StoreEc: 0x8004010F
    Lid: 8620    StoreEc: 0x3EB
    Lid: 1750    ---- Remote Context End ----
    Lid: 26849
    Lid: 21817   ROP Failure: 0x3EB
    Lid: 26297
    Lid: 16585   StoreEc: 0x3EB
    Lid: 32441
    Lid: 1706    StoreEc: 0x3EB
    Lid: 24761
    Lid: 20665   StoreEc: 0x3EB
    Lid: 25785
    Lid: 29881   StoreEc: 0x3EB
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
    <Provider Name="MSExchange Mailbox Replication" />
    <EventID Qualifiers="32772">1006</EventID>
    <Level>3</Level>
    <Task>1</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2011-02-25T22:00:07.000000000Z" />
    <EventRecordID>181576</EventRecordID>
    <Channel>Application</Channel>
    <Computer>email1.domain.com</Computer>
    <Security />
</System>
<EventData>
    <Data>DB01</Data>
    <Data>MapiExceptionUnknownUser: Unable to open message store. (hr=0x80004005, ec=1003)
Diagnostic context:
    Lid: 55847   EMSMDBPOOL.EcPoolSessionDoRpc called [length=243]
    Lid: 43559   EMSMDBPOOL.EcPoolSessionDoRpc returned [ec=0x0][length=200][latency=0]
    Lid: 23226   --- ROP Parse Start ---
    Lid: 27962   ROP: ropLogon [254]
    Lid: 17082   ROP Error: 0x3EB
    Lid: 26937
    Lid: 21921   StoreEc: 0x3EB
    Lid: 27962   ROP: ropExtendedError [250]
    Lid: 1494    ---- Remote Context Beg ----
    Lid: 26426   ROP: ropLogon [254]
    Lid: 22086
    Lid: 27206
    Lid: 17990
    Lid: 16966   StoreEc: 0x8004010F
    Lid: 31433   StoreEc: 0x8004010F
    Lid: 8620    StoreEc: 0x3EB
    Lid: 1750    ---- Remote Context End ----
    Lid: 26849
    Lid: 21817   ROP Failure: 0x3EB
    Lid: 26297
    Lid: 16585   StoreEc: 0x3EB
    Lid: 32441
    Lid: 1706    StoreEc: 0x3EB
    Lid: 24761
    Lid: 20665   StoreEc: 0x3EB
    Lid: 25785
    Lid: 29881   StoreEc: 0x3EB     </Data>
</EventData>
</Event>

Hi
This error occurs because the MailboxReplicationService (MRS) currently caches Mailbox Database information past the lifetime of some databases.
Restarting the service will clear the cache.
Maybe it is the simplest way to solve it.
If it doesn’t work, you can try cmd to check it.
Get-MailboxDatabase : Can you find the database which you delete?
Remove-MailboxDatabase -Identity "MyDatabase": You can try to delete database if you can see the database.

The Microsoft Exchange Mailbox Replication service was unable to process a request due to an unexpected error. Event 1121

Hello all,
We migrated our Exchange server from 2003 to 2010. After the mailbox move requests were finished we had one that was stuck. We basically skipped it as we had a lot of other things to finish over the weekend. Here we are a year later, the old exchange server
is gone and so is an old DC. I am receiving an error every four minutes in event viewer.
The Microsoft Exchange Mailbox Replication service was unable to process a request due to an unexpected error.
Request GUID: '3e46b7cb-2ac0-42c1-98e8-57517a19ee40'
Database GUID: '5c6c573b-4f45-4ce3-b296-11cf69c2e2b6'
Error: Unable to find 'OLD Domain Controller' computer information in domain controller 'OLD Domain Controller' to perform the suitability check. Verify the fully qualified domain name..
I have checked in EMC for move requests. None are listed. I have checked the DCs listed in EMC properties. Old DC is not listed.
I also ran these commands in shell to attempt to cancel the stuck request.
Get-MoveRequest -MoveStatus Completed;Pending;InProgress;Failed;CompletedWithWarning;Suspended;Queued;CompletionWithProgress : Remove-MoveRequest
NO changes. Still throwing error. Any suggestions? I also tried using the guid and shell to look at the move request. Systems replies no such request.

Hello,
Please try to restart iis services to check the result.
If the issue persists, I recommend you ping you DC server on your exchange server to check if your exchange server can communicate with your DC server.
If there are other DCs, please try to use set-adserversettings cmdlet to specify a DC for your exchange server.
Set-AdServerSettings
http://technet.microsoft.com/en-us/library/dd298063(v=exchg.150).aspx
Besides, please install the lasted rollup to check the result.
Cara Chen
TechNet Community Support

The Microsoft Exchange Mailbox Replication service was unable to process a request due to an unexpected error. : Error: An Active Directory Constraint Violation error occurred

Hello,
We have a multi domain parent child AD domain infrastructure and now we upgraded our exchange from Exchange 2007 to Exchange 2013. Since last few days, we see the below error on the mailbox server event viewer.
EVENT ID : 1121
The Microsoft Exchange Mailbox Replication service was unable to process a request due to an unexpected error.
Request GUID: '93a7d1ca-68a1-4cd9-9edb-a4ce2f7bb4cd'
Database GUID: '83d028ec-439d-4904-a0e4-1d3bc0f58809'
Error: An Active Directory Constraint Violation error occurred on <domain controller FQDN>. Additional information: The name reference is invalid.
This may be caused by replication latency between Active Directory domain controllers.
Active directory response: 000020B5: AtrErr: DSID-0315286E, #1:
Our Exchange setup is in parent domain, but we keep on getting this error for various domain controllers in each child domain in the same site. We then configured one of the parent domain domain controller on Exchange. Still we are getting this error for
the configured parent domain DC.
Verified the AD replication and there is no latency or pending stuffs.
Any support to resolve this issue will be highly appreciated. Thank you in advance.
Regards,
Jnana R Dash

Hi,
In addition to Ed's suggestion, I would like to clarify the following things for troubleshooting:
1. Please restart IIS at first.
2. If the issue persists, please ping your DC on your Exchange server to check if Exchange can communicate with DC.
Hope it helps.
Best regards,
Amy Wang
TechNet Community Support

The Microsoft Exchange Mailbox Replication service was unable to process a request due to an unexpected error

Since demoting a child domain a few days ago, Exchange 2013 is still trying to contact it and as a result generating errors in the application event logs. I had a similar problem which I solved by removing some old migration batches, now I have a problem
with the Microsoft Exchange Mailbox Replication service.
The event logged is:
The Microsoft Exchange Mailbox Replication service was unable to process a request due to an unexpected error.
Request GUID: '0b6c0f5a-0563-48e2-8b97-e0781c6cc69a'
Database GUID: '23258311-ad29-41c2-a842-522f48baa267'
Error: Unable to read from Active Directory. --> The call to Microsoft Exchange Active Directory Topology service on server 'TopologyClientTcpEndpoint (localhost)' returned an error. Error details Unable to find a suitable directory server for
domain 'admin.riddlesdown.local'.. --> Unable to find a suitable directory server for domain 'admin.riddlesdown.local'..
Process Microsoft.Exchange.Directory.TopologyService.exe (PID=2280). Exchange Active Directory Provider could not find an available domain controller in domain admin.riddlesdown.local. This event may be caused by network connectivity issues or
configured incorrectly DNS server.
The domain doesn't exist in AD Sites and Services, I have removed all traces from DNS but this is still occurring. When I run Get-ADServerSettings | fl it reports no trace of the domain or a DC that was previously in it.
How can I stop these events occurring and is it likely to be causing something else not to work correctly.
We are running Exchange 2013 CU1

No, that didn't work. Here are more details:
Source: MSExchange ADAccess (EventID: 2130)
Process Microsoft.Exchange.Directory.TopologyService.exe (PID=2280). Exchange Active Directory Provider could not find an available domain controller in domain admin.riddlesdown.local. This event may be caused by network connectivity issues or configured
incorrectly DNS server.
Source: MSExchange ADAccess (EventID: 2119)
Process Microsoft.Exchange.Directory.TopologyService.exe (PID=2280). Error DNS_ERROR_RCODE_NAME_ERROR (0x8007232B) occurred when DNS was queried for the service location (SRV) resource record used to locate a domain controller for domain admin.riddlesdown.local
The query was for the SRV record for _ldap._tcp.dc._msdcs.admin.riddlesdown.local
Common causes of this error include the following:
- The DNS SRV records required to locate a domain controller for the domain are not registered in DNS. These records are registered with a DNS server automatically when a domain controller is added to a domain. They are updated by the domain controller
at set intervals. This computer is configured to use DNS servers with following IP addresses:
10.59.100.7
10.59.100.8
fec0:0:0:ffff::1Microsoft.Exchange.Directory.TopologyService.exe
fec0:0:0:ffff::2Microsoft.Exchange.Directory.TopologyService.exe
fec0:0:0:ffff::3Microsoft.Exchange.Directory.TopologyService.exe
- One or more of the following zones do not include delegation to its child zone:
admin.riddlesdown.local
riddlesdown.local
local
. (the root zone)
Source: MSExchange Mailbox Replication Service (EventID: 1121)
The Microsoft Exchange Mailbox Replication service was unable to process a request due to an unexpected error.
Request GUID: '87f4b926-0621-43d3-afeb-fe475ee6d850'
Database GUID: '23258311-ad29-41c2-a842-522f48baa267'
Error: Unable to read from Active Directory. --> The call to Microsoft Exchange Active Directory Topology service on server 'TopologyClientTcpEndpoint (localhost)' returned an error. Error details Unable to find a suitable directory server for domain 'admin.riddlesdown.local'..
--> Unable to find a suitable directory server for domain 'admin.riddlesdown.local'..
Something is cause the Exchange server to go looking for our old domain, but what and why?

Issue in Consuming Rest/JSON Service from Netweaver gateway system

Hello Experts,
We are trying to consume the Rest/JSON web service from NetWeaver Gateway System.
But we are getting HTTP Communication failure error.
URL: 'http://sgpvmc0031.apac.bosch.com/ActivityManager2/rest/v1/query/employees/amh1sgp/workItems/pending'
The Host system of Serve is a Non-SAP System.
In web browser, it ask for user id and password, by passing them, it provide the response.
Please find my code details.
DATA: lo_http_client TYPE REF TO if_http_client,
         lv_service TYPE string,
         lv_result TYPE string,
         lo_ixml TYPE REF TO if_ixml,
         lo_streamfactory TYPE REF TO if_ixml_stream_factory,
         lo_istream TYPE REF TO if_ixml_istream,
         lo_document TYPE REF TO if_ixml_document,
         lo_parser TYPE REF TO if_ixml_parser,
         lo_weather_element TYPE REF TO if_ixml_element,
         lo_weather_nodes TYPE REF TO if_ixml_node_list,
         lo_curr_node TYPE REF TO if_ixml_node,
         lv_value TYPE string,
         lv_node_length TYPE i,
         lv_node_index TYPE i,
*        ls_weather TYPE zweather,
         lv_node_name TYPE string,
         lv_bin            type xstring,
         lv_node_value TYPE string,
         lo_conv           type ref to cl_abap_conv_in_ce,
         lv_response       type string,
         l_client type string.
DATA: result_tab TYPE TABLE OF string,
          w_result TYPE string .
   lv_service = 'http://sgpvmc0031.apac.bosch.com/ActivityManager2/rest/v1/query/employees/amh1sgp/workItems/pending'.
* lv_service = 'https://rb-wam-q.bosch.com/ActivityManager2/rest/v1/query/employees/amh1sgp/workItems/pending'.
*BREAK-POINT.
CALL METHOD CL_HTTP_CLIENT=>CREATE
   EXPORTING
     HOST               = 'sgpvmc0031.apac.bosch.com'
     SERVICE            = '80'
*    PROXY_HOST         =
*    PROXY_SERVICE      =
*     SCHEME             = SCHEMETYPE_HTTP
*    SSL_ID             =
*    SAP_USERNAME       =
*    SAP_CLIENT         =
   IMPORTING
     CLIENT             = lo_http_client
   EXCEPTIONS
     ARGUMENT_NOT_FOUND = 1
     PLUGIN_NOT_ACTIVE = 2
     INTERNAL_ERROR     = 3
     others             = 4
IF SY-SUBRC <> 0.
* Implement suitable error handling here
ENDIF.
    lo_http_client->request->set_method( if_http_request=>co_request_method_get ).
    lo_http_client->authenticate( username = 'portal' password = 'portal' ).
    cl_http_utility=>set_request_uri(
        request = lo_http_client->request
        uri = '/ActivityManager2/rest/v1/query/employees/amh1sgp/workItems/pending'
    call method lo_http_client->request->set_header_field
       EXPORTING
         name = 'content-type'
         value = 'text/plain'.
    call method lo_http_client->send( ).
    call method lo_http_client->receive( ).
Kindly help us to understand where to check.
Regards,
Nitin

Hi,
Try to test the url in the standard report RSHTTP20.
Regards,
Felipe

The File Replication Service has detected that the replica set "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)" is in JRNL_WRAP_ERROR.

Hi!
I recently took over management of a Windows 2003 domain that had only one domain controller. I was building a second DC for redundancy and discovered that the SYSVOL share on the original DC is in "JRNL_WRAP_ERROR" after the SYSVOL and NETLOGON
share would not create on the new DC. This error goes back as far as the log goes back so I don't know how long it has been in this state.
The message in the event log states to enable "Enable Journal Wrap Automatic Restore" but I found a KB article that says to use the BurFlags key instead. http://support.microsoft.com/kb/290762
Should I run an authoritative restore since I don't have another domain controller with a good SYSVOL?
The File Replication Service has detected that the replica set "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)" is in JRNL_WRAP_ERROR.
Replica set name is    : "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)"
Replica root path is   : "c:\windows\sysvol\domain"
Replica root volume is : "\\.\C:"
A Replica set hits JRNL_WRAP_ERROR when the record that it is trying to read from the NTFS USN journal is not found. This can occur because of one of the following reasons.
[1] Volume "\\.\C:" has been formatted.
[2] The NTFS USN journal on volume "\\.\C:" has been deleted.
[3] The NTFS USN journal on volume "\\.\C:" has been truncated. Chkdsk can truncate the journal if it finds corrupt entries at the end of the journal.
[4] File Replication Service was not running on this computer for a long time.
[5] File Replication Service could not keep up with the rate of Disk IO activity on "\\.\C:".
Setting the "Enable Journal Wrap Automatic Restore" registry parameter to 1 will cause the following recovery steps to be taken to automatically recover from this error state.
[1] At the first poll, which will occur in 5 minutes, this computer will be deleted from the replica set. If you do not want to wait 5 minutes, then run "net stop ntfrs" followed by "net start ntfrs" to restart the File Replication
Service.
[2] At the poll following the deletion this computer will be re-added to the replica set. The re-addition will trigger a full tree sync for the replica set.
WARNING: During the recovery process data in the replica tree may be unavailable. You should reset the registry parameter described above to 0 to prevent automatic recovery from making the data unexpectedly unavailable if this error condition occurs again.
To change this registry parameter, run regedit.
Click on Start, Run and type regedit.
Expand HKEY_LOCAL_MACHINE.
Click down the key path:
   "System\CurrentControlSet\Services\NtFrs\Parameters"
Double click on the value name
   "Enable Journal Wrap Automatic Restore"
and update the value.
If the value name is not present you may add it with the New->DWORD Value function under the Edit Menu item. Type the value name exactly as shown above.

> The message in the event log states to enable "Enable Journal Wrap
> Automatic Restore" but I found a KB article that says to use the
> BurFlags key instead.
http://support.microsoft.com/kb/290762
>
> Should I run an authoritative restore since I don't have another domain
> controller with a good SYSVOL?
The automatic restore process AFAIK will initiate a D2 restore. And if
there's no other DC, sysvol might be gone.
I really would prefer to have control - this means I would do a D4.
Absolutely I would :)
Martin
Mal ein
GUTES Buch über GPOs lesen?
NO THEY ARE NOT EVIL, if you know what you are doing:
Good or bad GPOs?
And if IT bothers me - coke bottle design refreshment :))

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

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

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

VSS timeouts on Hyper-V guest, Exchange Replication Service, CU5

I'm having a problem with a Hyper-V guest that is running Exchange 2013 CU5. I will say I have had issues with this VM since installing CU5.
Note: I am doing a backup from within the VM guest, not from the host.
The scheduled backup takes a long time to complete, an entire weekend to backup 150GB to an ISCSI disk. In addition the CPU time is very high (58%) while this is happening. Attempting to open the backup manager window consistently makes the CPU
time hit 99%. When this happens Outlook clients will fail. When backup manager opens it will continually say "Reading data; please wait..." If the backup manager happened to already been open, the backup job will say "Volume
1 0% of 4 volumes."
The processes taking up the CPU time are Microsoft Volume Shadow Copy Service (24%), Microsoft Block level backup service (62%) and virtual disk service (12%). Memory use always hovers around 65%. If I attempt to kill the processes with
task manager, there is no change. If I use the kill executable it will say the process is not running. I cannot stop the corresponding service either. I cannot stop the backup. I cannot query vss writer status. I cannot restart
the ISCSI service (device in use.) Restarting the NAS that contains the ISCSI target does nothing. The only recourse is to restart the server.
If I restart the server and start a backup fairly soon after, the backup completes normally, in about an hour. During a normal backup CPU usage is at about 30%. The Microsoft Volume Shadow Copy Service runs at 0% CPU time as well as the virtual
disk service. The Microsoft Block Level Backup Engine runs at 10% CPU time. The scheduled backup is set to start at 9:30pm. I have also tried changing backup times. If I restart the server at 4 am and do not run a manual backup, the
scheduled backup performs poorly.
After some digging I find these errors:
Log Name: Application
Source: MSExchangeRepl
Date: 10/14/2014 9:30:41 PM
Event ID: 2112
Task Category: Exchange VSS Writer
Level: Error
Keywords: Classic
User: N/A
Description:
The Microsoft Exchange Replication service VSS Writer instance 7a465f3f-25ba-45b2-952a-870a6ddc2f2b failed with error code 80070020 when preparing for a backup of database 'Mailbox Database 2123847568'.
Log Name: Application
Source: VSS
Date: 10/14/2014 9:30:41 PM
Event ID: 8229
Task Category: None
Level: Warning
Keywords: Classic
User: N/A
Description:
A VSS writer has rejected an event with error 0x00000000, The operation completed successfully.
. Changes that the writer made to the writer components while handling the event will not be available to the requester. Check the event log for related events from the application hosting the VSS writer.
Operation:
PrepareForBackup event
Context:
Execution Context: Writer
Writer Class Id: {7e47b561-971a-46e6-96b9-696eeaa53b2a}
Writer Name: MSMQ Writer (MSMQ)
Writer Instance Name: MSMQ Writer (MSMQ)
Writer Instance ID: {b8ae6140-7fcb-427d-9493-e070221f752f}
Command Line: C:\Windows\system32\mqsvc.exe
Process ID: 1676
Log Name: Application
Source: MSExchangeRepl
Date: 10/14/2014 9:30:41 PM
Event ID: 2024
Task Category: Exchange VSS Writer
Level: Error
Keywords: Classic
User: N/A
Description:
The Microsoft Exchange Replication service VSS Writer (Instance 7a465f3f-25ba-45b2-952a-870a6ddc2f2b) failed with error 80070020 when preparing for a backup.
As you can see the errors happen almost immediately after the backup starts.
In addition the following VSSwriters show a last error "timed out"
Microsoft Exchange Writer
Com+ RegDB Writer
Shadow Copy Optimization Writer
Registry Writer
I will add also the following issues I have been experiencing ever since installing CU5:
1 Version buckets threshold easy reached. Had to modify threshold and set limits on email size. Sometimes still happens.
2 After a restart of the server, the server may have no, or limited connection to the network. It may or may not have an exclamation point on the network icon. If there is no exclamation point, it can ping other network resources, but inbound requests
and pings, will fail. The event log shows that the network should be available while booting, but it's not since it cannot communicate with active directory. The fix for this is to disable/enable the network adapter and then all is well.
I really need some help figuring this out. Again, never had an issue with this server prior to Exchange 2013 CU5 being installed.

Hi,
The reason I think it is Exchange related, is that from the error message it mentioned:
A VSS writer has rejected an event with error 0x00000000
And then it indicated it is "Microsoft Exchange Replication service VSS Writer".
The Microsoft Exchange Replication service VSS Writer (Instance 7a465f3f-25ba-45b2-952a-870a6ddc2f2b) failed with error 80070020 when preparing for a backup
Later I found this article:
How to turn on the Exchange writer for the Volume Shadow Copy service in Windows Small Business Server 2003
http://support2.microsoft.com/kb/838183/en-us
It mentioned that with turned on Exchange writer, we will fail to do system state backup and Exchange backup at a same time:
The Exchange writer may cause conflicts with the information store backup feature of the Backup utility. The information store backup feature uses online streaming to back up the Exchange databases. If the Exchange writer is registered, the Backup utility
may log errors if you try to back up the system state and the Exchange information store at the same time. (For example, the Backup utility may log Event ID 8019.)
In order to confirm if it is the cause, please test to:
1. Create a backup-once task to backup only a simple file - this is a quick test to confirm if Windows Server Backup is fine or not.
2. A second backup-once task to do a system state backup without any exchange related information.
3. If both failed, please test to disable Exchange Writer and redo test 1&2.
It will take us some time on doing these tests. The reason is to figure out if it is Exchange related or not. I'll continue discuss with you if any new clue is found.
If you have any feedback on our support, please send to [email protected]

Exchange Server 2013 SP1 CU5 - The Microsoft Exchange Replication service VSS Writer encountered an exception

We have 2 server DAG with a witness all servers are Server 2012 R2. Both members of the DAG are Exchange 2013 SP1 CU5.
We haven't seen this until recently, but during a VSS enabled storage snapshot the following errors occur. All of which are related to MSExchangeRepl and the Exchange VSS Writer.
Event IDs 2140, 2026, 2028, 2030.
The errors start with the 2140 seen here:
The Microsoft Exchange Replication service VSS Writer encountered an exception in function Microsoft::Exchange::Cluster::ReplicaVssWriter::CReplicaVssWriterInterop::PrepareSnapshot. HResult -2147467259. Exception Microsoft.Mapi.MapiExceptionDatabaseError: MapiExceptionDatabaseError:
Unable execute Prepare on snapshot. (hr=0x80004005, ec=1108)
Diagnostic context:
Lid: 1494 ---- Remote Context Beg ----
Lid: 56264 StoreEc: 0x1388
Lid: 46280 StoreEc: 0x454
Lid: 1750 ---- Remote Context End ----
Lid: 59216
Lid: 34640 StoreEc: 0x454
Lid: 52264
Lid: 46120 StoreEc: 0x454
at Microsoft.Mapi.MapiExceptionHelper.InternalThrowIfErrorOrWarning(String message, Int32 hresult, Boolean allowWarnings, Int32 ec, DiagnosticContext diagCtx, Exception innerException)
at Microsoft.Mapi.MapiExceptionHelper.ThrowIfError(String message, Int32 hresult, IExInterface iUnknown, Exception innerException)
at Microsoft.Mapi.ExRpcAdmin.ProcessSnapshotOperation(Guid mdbGuid, SnapshotOperationCode operationCode, UInt32 flags)
at Microsoft.Exchange.Cluster.Replay.StoreRpcController.<>c__DisplayClass1c.<SnapshotPrepare>b__1b()
at Microsoft.Exchange.Cluster.Replay.SafeRefCountedTimeoutWrapper.<>c__DisplayClass2.<ProtectedCallWithTimeout>b__0()
at Microsoft.Exchange.Data.HA.InvokeWithTimeout.Invoke(Action invokableAction, Action foregroundAction, TimeSpan invokeTimeout, Boolean sendWatsonReportNoThrow, Object cancelEvent)
at Microsoft.Exchange.Cluster.Replay.SafeRefCountedTimeoutWrapper.ProtectedCallWithTimeout(String operationName, TimeSpan timeout, Action operation)
at Microsoft.Exchange.Cluster.ReplicaVssWriter.CReplicaVssWriterInterop.SnapshotPrepare(Guid dbGuid, UInt32 flags)
at Microsoft.Exchange.Cluster.ReplicaVssWriter.CReplicaVssWriterInterop.PrepareSnapshot().

Hi Julez K,
According to your description, you could try upgrading to CU6.
In addition, you could review the Exchange Application (App) Event log and the Exchange System (Sys) Event log for errors , and some related resolutions for your reference.
http://www.symantec.com/business/support/index?page=content&id=TECH209938
Note: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety,
or suitability of any software or information found there. Please make sure that you completely understand the risk before retrieving any suggestions from the above link.
Hope it can be helpful.
Best regards,
Eric

The File Replication Service cannot replicate d:\sysvol\domain

i am getting a error in my evetn viewer that says...
The File Replication Service cannot replicate d:\sysvol\domain because the pathname of the customer designated staging directory:
d:\sysvol\staging\domain
is not the fully qualified pathname of an existing, accessible local directory

Is d:\sysvol\staging\domain a path to an existing accessible directory on that system? You might consider running "net share" from a command line to see where sysvol and netlogon are pointing on that particular system to get the ball rolling.

Enqueue replication service in Netweaver 7.1 (HA setup)

Similar Messages

Maybe you are looking for