Last post Apr 05, 2008 08:13 PM by The IT Guys
Mar 23, 2008 01:04 PM|The IT Guys|LINK
Exchange 2007 SP1
Can't get the CCR to replicate. Our system was working fine until we ran out of storage space on our log volume. Now that the storage issue is resolved, CCR wont replicate.
[PS] C:\>update-storagegroupcopy -identity "EXMBX01\BusinessSG2" -DeleteExistingFiles -Verbose
VERBOSE: Update-StorageGroupCopy : Beginning processing.
VERBOSE: Update-StorageGroupCopy : Searching objects "EXMBX01\BusinessSG2" of type "StorageGroup" under the root "$null".
VERBOSE: Update-StorageGroupCopy : Previous operation run on domain controller 'AD02.XXXXX.local'.
VERBOSE: Update-StorageGroupCopy : Processing object "EXMBX01\BusinessSG2".
Update-StorageGroupCopy : This task can only be performed locally on the source or target computer.
At line:1 char:24
+ update-storagegroupcopy <<<< -identity "EXMBX01\BusinessSG2" -DeleteExistingFiles -Verbose
VERBOSE: Update-StorageGroupCopy : Ending processing.
Event log errors
Warning 2601, Error 2501 and 2604 every 15 minutes
2601 - Process MSEXCHANGEADTOPOLOGY (PID=1280). When initializing a remote procedure call (RPC) to the Microsoft Exchange Active Directory Topology service, Exchange could not retrieve the SID for account <WKGUID=DC1301662F547445B9C490A52961F8FC,CN=Microsoft
Exchange,CN=Services,CN=Configuration,...> - Error code=8007077f.
The Microsoft Exchange Active Directory Topology service will continue starting with limited permissions.
2501 - Process MSEXCHANGEADTOPOLOGY (PID=1280). The site monitor API was unable to verify the site name for this Exchange computer - Call=DsctxGetContext Error code=8007077f. Make sure that Exchange server is correctly registered on the
2604 - Process MSEXCHANGEADTOPOLOGY (PID=1280). When updating security for a remote procedure call (RPC) access for the Exchange Active Directory Topology service, Exchange could not retrieve the security descriptor
for Exchange server object EXMBX01 - Error code=8007077f.
The Exchange Active Directory Topology service will continue with limited permissions.
From what we can tell, the AD and DNS are configured correctly.
Anyone know a solution?
Mar 24, 2008 07:50 AM|PowerK6|LINK
please check this post
Mar 24, 2008 11:16 PM|The IT Guys|LINK
I shut all exchange services and restarted netlogon, I also shutdown and reboot the cluster.
Issue still exists.
Any other ideas?
Mar 25, 2008 09:18 AM|DmitriG|LINK
The IT Guys
Any other ideas?
Mar 26, 2008 01:11 PM|The IT Guys|LINK
Ya, MS PSS is an option, they are terrible with there call routing, and last time we called them took them two weeks to call us back. Frustrating...
I think I will delete the role from Node2 and reinstall and see if that resolves the issue(s)
Mar 26, 2008 01:46 PM|DmitriG|LINK
The IT Guys
Another issue, not sure if related, but started happening at the same time...The backup's are not clearing out the log files, I am having to manually delete them.
The backup logs state the backup was successful.
It is the same issue. As I understand, in CCR case, log file will not be deleted until it been copied and applied to passive DB copy.
Apr 05, 2008 08:13 PM|The IT Guys|LINK
Delete database and log files on passive node
Preform a soft recovery of the logs to database
Delete Log files on primary
Copy database to passive node
Resume storage group copy