Hi to all
I have a strange problema with my Exchange 2013, when I try to add a copy of the database, I receive this error:
8864 w3wp#MSExchangeECPAppPool
54
00:00:00.0090058
Ver todo el bosque: ‘True’, Configuración del controlador de dominio: «ADIL01.domain.com.mx», Catálogo global preferido: «ADIL01.domain.com.mx», Controladores de dominio preferidos: «{ ADIL01.domain.com.mx }»
Microsoft.Exchange.Cluster.Replay.SeedInProgressException: Se produjo un error en la operación de propagación: An error occurred while performing the seed operation. Error: Failed to notify source server ‘EXCH-IL03.domain.com.mx’ about the local
truncation point. Hresult: 0xc8000713. Error: Unable to find the file. —> Microsoft.Exchange.Cluster.Replay.FailedToNotifySourceLogTruncException: Failed to notify source server ‘EXCH-IL03.domain.com.mx’ about the local truncation point. Hresult: 0xc8000713.
Error: Unable to find the file. at Microsoft.Exchange.Cluster.Replay.LogShipContextWrapper.Notify(Int64 lgenReplicated, Int64& lgenLowestRequiredGlobally) at Microsoft.Exchange.Cluster.Replay.LogTruncater.RequestGlobalTruncationCoordination(Int64 localTruncationPoint,
String sourceMachineFqdn, String localNodeName, Guid identityGuid, String logPrefix, String destLogPath, Boolean circularLogging, ManualOneShotEvent cancelEvent) at Microsoft.Exchange.Cluster.Replay.DatabaseSeederInstance.ManageLogTruncation() at Microsoft.Exchange.Cluster.Replay.DatabaseSeederInstance.SeedThreadProcInternal()
— End of inner exception stack trace (Microsoft.Exchange.Cluster.Replay.FailedToNotifySourceLogTruncException) — at Microsoft.Exchange.Cluster.Replay.SeederInstanceBase.LogError(Exception ex) at Microsoft.Exchange.Cluster.Replay.DatabaseSeederInstance.SeedThreadProcInternal()
at Microsoft.Exchange.Data.Storage.Cluster.HaRpcExceptionWrapperBase`2.RunRpcServerOperation(String databaseName, RpcServerOperation rpcOperation) — End of stack trace on server (EXCH-IL04.domain.com.mx) — at Microsoft.Exchange.Configuration.Tasks.Task.ThrowError(Exception
exception, ErrorCategory errorCategory, Object target, String helpUrl) at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target) at Microsoft.Exchange.Cluster.Replay.SeedProgressReporter.HandleError()
at Microsoft.Exchange.Cluster.Replay.SeedProgressReporter.MonitorProgress() at Microsoft.Exchange.Management.SystemConfigurationTasks.TaskSeeder.SeedDatabase() at Microsoft.Exchange.Management.SystemConfigurationTasks.AddDatabaseCopyTaskBase`1.SeedDatabase(ReplayConfiguration
config) at Microsoft.Exchange.Management.SystemConfigurationTasks.AddDatabaseCopyTaskBase`1.PerformSeedIfNecessary() at Microsoft.Exchange.Management.SystemConfigurationTasks.AddMailboxDatabaseCopy.InternalProcessRecord() at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)
7
Microsoft.Exchange.Cluster.Replay.FailedToNotifySourceLogTruncException: Failed to notify source server ‘EXCH-IL03.domain.com.mx’ about the local truncation point. Hresult: 0xc8000713. Error: Unable to find the file. at Microsoft.Exchange.Cluster.Replay.LogShipContextWrapper.Notify(Int64
lgenReplicated, Int64& lgenLowestRequiredGlobally) at Microsoft.Exchange.Cluster.Replay.LogTruncater.RequestGlobalTruncationCoordination(Int64 localTruncationPoint, String sourceMachineFqdn, String localNodeName, Guid identityGuid, String logPrefix, String
destLogPath, Boolean circularLogging, ManualOneShotEvent cancelEvent) at Microsoft.Exchange.Cluster.Replay.DatabaseSeederInstance.ManageLogTruncation() at Microsoft.Exchange.Cluster.Replay.DatabaseSeederInstance.SeedThreadProcInternal()
Ex4543D9
False
0 objects execution has been proxied to remote server.
0
ActivityId: 9655c63d-c0aa-410e-b896-55a1fa5540f7
ServicePlan:;IsAdmin:True;
es-MX
I try: http://blog.dargel.at/2014/10/09/error-0xc8000713-unable-to-find-the-file-when-trying-to-replicate-db-in-dag/
but all the database are in clean shutdown.
May be: http://technet.microsoft.com/en-us/library/bb795725.aspx
But I created the «REG_EXPAND_SZ» with»Disable Exchange Writer» value: 0, restarted the «MS Exchange Information Store» and still does not appear ‘Microsoft Exchange Writer’.
The second server has just installed with Windows 2012 R2, Exchange 2013 CU6 and all the last patchs until last week.Any suggestion? thanks in advance
Doc MX
Недавно разворачивал Database Availability Group в Exchange 2016 и столкнулся с проблемой создания пассивной копии одной из баз. А именно: при выполнении командлета Add-MailboxDatabaseCopy появлялась следующая ошибка:
[PS] C:>Get-MailboxDatabase -Identity db-01 | Add-MailboxDatabaseCopy -MailboxServer ex02 -ActivationPreference 2
The seeding operation failed. Error: An error occurred while performing the seed operation. Error: Failed to notify source server
‘EX01.AD.customer.local’ about the local truncation point. Hresult: 0xc8000713. Error: Unable to find the file.
[Database: db-01, Server: EX02.AD.customer.local]
+ CategoryInfo : InvalidOperation: (:) [Add-MailboxDatabaseCopy], SeedInProgressException
+ FullyQualifiedErrorId : [Server=EX01,RequestId=2e434125-4b73-4845-b42c-218aae43caf4,TimeStamp=23.10.2014 15:37:18] [FailureCategory=Cmdlet-SeedInPr
ogressException] 92042DF7,Microsoft.Exchange.Management.SystemConfigurationTasks.AddMailboxDatabaseCopy
+ PSComputerName : ex01.AD.customer.local
В результате поисков выяснилось, что такая проблема решается путем полного бекапирования базы (для «подрезки» логов базы) и повторного создания копии, однако, это решение не помогло.
Зато помог следующий солюшн, предложенный техподдержкой Microsoft:
1. Отключить базу данных
2. Убедиться, что база в состоянии “clean shutdown”:
|
ESEutil /mh X:Databases<span class=«skimlinks-unlinked»>Database.edb |
Если нет, то необходимо починить базу с помощью esutil:
|
Eseutil /r E00 /d: “Database Path” /l: “Log Folder Path” /s: “Log Folder Path” /a /i |
(http://technet.microsoft.com/en-us/library/aa998074(v=exchg.65).aspx)
3. Переместить все файлы из папки с логами базы во временную директорию. В случае когда папки базы и логов совпадают (как и у меня), переместить все файлы (папки не трогать!) кроме .edb.
4. Подключить базу
5. Возобновить создание пассивной копии
|
Update—MailboxDatabaseCopy DB—01EX02 —DeleteExistingFiles |
После этих действий копия базы создалась корректно.
Запись опубликована в рубрике IT с метками DAG, exchange. Добавьте в закладки постоянную ссылку.
I was recently tasked with a project that included migrating an Exchange Server 2010 environment to an Exchange Server 2013 one, fast forward everything was migrated to a single server the second server was setup and configured properly as well and it was time to add the copies of the mailbox databases.
The customer had a requirement to have circular logging enabled, but before adding a mailbox database copy circular logging must be disabled.
While attempting to add one of the databases I got the following error:
The seeding operation failed. Error: An error occurred while performing the seed operation. Error: Failed to notify source server ‘ExchangeServer FQDN’ about the local truncation point. Hresult: 0xc8000713. Error: Unable to find the file. [Database: DATABASE, Server: ExchangeServer FQDN]
And the status of the database copy is failed and suspended
I tried adding another database thinking that this might be related to this single database and the results were the same. I did a quick research on the subject and most of the responses were that you should:
- Dismount the database.
- Run eseutil with the /mh parameters (more info here).
I had a lot of databases and dismounting the databases to run the utility was merely impossible even on a weekend, on the other hand as I was continuing my research I found a thread on Technet which mentions a long side to running the eseutil “moving the logs” to another directory so that they will get recreated and here it hit me!
What if I re-enable circular logging then try to update the database! Because since circular logging was enabled I am already missing on a lot of the transactions that were initially written on the database!
- I tried first hitting the update option but sadly I got the same error
- I tried hitting resume option which resulted again in the failed and suspended status then hit the update option again.
- AND IT WORKED
I was glad that I did not have to go through the eseutil havoc as it would have bumped the project at least 1 week (going through all databases that is), I hope this helps!
(Abdullah)^2
21772 Total Views 11 Views Today
I was working on the issue where someone messed up the database. Only 1st copy was mounted and other copies were not healthy.
Environment:
3 data center expanded DAG
2 Data center has Exchange servers
1 Data Center has FSW
Only one data center is internet facing.
Issue:
While creating a copy of the database on the 2nd server, we got the following errors.
First Error
The seeding operation failed. Error: An error occurred while performing the seed operation. Error: Failed to notify source server “server fqdn ” about the local truncation point. Hresult: 0xc8000713. Error: Unable to find the file.
2nd error
Failed to open a log truncation context to source server. Hresult: 0xc7ff1004. Error: Error returned from an ESE function call (-1305).
Resolution:
This is the issue with the old logs folder which was not in the sync.
For the 1st error.
-Login to the source server
-Remove the 2nd copy of the database
-Dismount the database
-Verify database is clean shutdown by running the command eseutil /mh driveletter:databasedatabase.edb
-Now rename the logs file folder to logs old.
-Mount the database
-Now the 1st issue will be fixed.
For the 2nd error.
-Login to the destination server where we are creating the 2nd copy
-Now rename the logs and database file folder by adding old prefix.
-Add the 2nd database copy.
-Now the 2nd issue will be fixed.
This environment was not backed up so there was a time when circular logging was enabled then disabled. After this one of the administrator messed up the database copies while expanding the C drive.
Conclusion:
This most important thing is to remember the error and its code because error will not clearly tell you the cause of the issue.
Next important thing is to take all precaution even if the environment is not in production.
Prabhat Nigam
Microsoft MVP | Exchange Server
Team@MSExchangeGuru
Posted September 27th, 2015 under DAG, Database Management, Exchange 2013. Tags: 0xc7ff1004, 0xc8000713, An error occurred while performing the seed operation, Failed to open a log truncation context to source server
RSS 2.0 feed.
Leave a response, or trackback.