CCR Replication error Event ID 2147
Hi
I have a Windows 2003 CCR on Exchange 2007 SP3 R6.
On one of the 3 Storage groups I have a failed copy status.
And the following events are logged
Log file action LogCopy failed for storage group MailSrv\MailStore4. Reason: Access to the path '\\cms1\30ecd310-0116-4031-b730-2fc8b28dcd8d$' is denied.
There was a problem with 'cms1', which is an alternate name for 'CMS1'. The list of aliases is now 'cms1', and the alias 'was' removed from the list. The specific problem is 'Access to the path '\\cms1\30ecd310-0116-4031-b730-2fc8b28dcd8d$' is denied.'.
The other storage groups are fine.
I have tried to stop the replication service - delete the logs and the mail stores for the passive node and reseed the database.
This has not fixed the issue.
I have seen a lot of suggested fixes which should be fixed in SP2 and SP3 - also relatd articles in Windows 2008.
Can somebody suggest a fix for this?
Is this applicable to Windows 2003?
http://problemgone.blogspot.com/2010/12/msexchange-repl-2104-logcopy-failed.html
May 24th, 2012 4:03am
did we had full backup on active-node
i would suggest
have a full back-up on active wait for the log files to get purged dismount the passive db move or remove the database,log files, etc (on passive node)delete the search index folder by running
ResetSearchIndex.ps1 (on passive node)mount it re-seed it
Free Windows Admin Tool Kit Click here and download it now
May 24th, 2012 2:33pm
Hi Horesebox,
Above gave a good suggestion, please make a test.
Regards!Gavin
TechNet Community Support
May 25th, 2012 6:04am
Hi Horesebox,
Above gave a good suggestion, please make a test.
Regards!Gavin
TechNet Community Support
Free Windows Admin Tool Kit Click here and download it now
May 25th, 2012 6:07am
Yeah I did that and it didn't work.
I just ran an analysis of the mailstore and got the following error back -
Analysis results: MailStore4
Database status is 'Clean Shutdown'
Details:
This database is in a 'Clean Shutdown' state. Therefore, you do not have to apply transaction log files to the database before it can be mounted. However, you may be able to apply additional transaction log files to this database to bring it more up-to-date.
Database information:
Domain controller you selected is: Domain Controller
Server that you selected is: mail06
Storage group that you selected is: MailStore4
Database that you selected is: MailStore4
Database signature is: 10/26/2007 12:33:28 3959484
Log signature is: 10/26/2007 12:33:28 3984734
Solution:
If you cannot mount this database even though it is in a 'Clean Shutdown' state, the cause may be that another database in the same storage group requires recovery. Run this tool against each database in the storage group to ensure that each database is
in a 'Clean Shutdown' state. If all databases are in a 'Clean Shutdown' state and you are experiencing Error -1216, refer to Microsoft Knowledge Base article 296843 at http://go.microsoft.com/fwlink/?linkid=3052&kbid=296843.
-------------
I then ran an integrity check against the MailStore and got the following error -
Checking database integrity.
The database is not up-to-date. This operation may find that
this database is corrupt because data from the log files has
yet to be placed in the database.
To ensure the database is up-to-date please use the 'Recovery' operation.
The database is not up-to-date. Intergrity check may find that this databse is corrupt because data from the log files has yet to be placed in the database. It is strongly recommended the database is brought up-to-date before continuing! Do you wish to abort
this operation?
Running eseutil against a live DB is not something that I have done before.
Any thoughts?
May 28th, 2012 4:44am