Hello everyone,
I have Exchange 2010 SP3 set up on a Windows Server 2008 R2 64-bit server. Checking backup status through the event logs(backup is being done through Windows Server Backup) has yielded a 9782 Exchange VSS Writer error for each of four mailbox databses and a public folder database, as well as a 2007 ESE Shadow Copy error, which I have researched and am formulating a plan for (I will check on those separately).
However, I also noticed Warning ID 1007 MailboxReplication service messages occurring every 10 minutes or so. Below is a sample of one message:
Level Date and Time Source Event ID Task Category
Warning 1/30/2015 7:59:33 AM MSExchange Mailbox Replication 1007 Service "The Mailbox Replication service was unable to determine the set of active mailbox databases on a mailbox server.
Mailbox server: SR203EB.XXX.COM
Error: MapiExceptionNetworkError: Unable to make admin interface connection to server. (hr=0x80040115, ec=-2147221227)
Diagnostic context:
......
Lid: 15000 dwParam: 0x6BA Msg: EEInfo: prm[1]: Pointer val: 0x0000000000000000
Lid: 15000 dwParam: 0x6BA Msg: EEInfo: prm[2]: Pointer val: 0x4CFDA8C000000000
Lid: 16280 dwParam: 0x6BA Msg: EEInfo: ComputerName: n/a
Lid: 8600 dwParam: 0x6BA Msg: EEInfo: ProcessID: 2452
Lid: 12696 dwParam: 0x6BA Msg: EEInfo: Generation Time: 2015-01-30 12:59:33:348
Lid: 10648 dwParam: 0x6BA Msg: EEInfo: Generating component: 18
Lid: 14744 dwParam: 0x6BA Msg: EEInfo: Status: 10060
Lid: 9624 dwParam: 0x6BA Msg: EEInfo: Detection location: 318
Lid: 13720 dwParam: 0x6BA Msg: EEInfo: Flags: 0
Lid: 11672 dwParam: 0x6BA Msg: EEInfo: NumberOfParameters: 0
Lid: 24060 StoreEc: 0x80040115
Lid: 23746
Lid: 31938 StoreEc: 0x80040115
Lid: 19650
Lid: 27842 StoreEc: 0x80040115
Lid: 20866
Lid: 29058 StoreEc: 0x80040115"
The server mentioned was a server that was intended to be set up as a backup to our Exchange Server, even though it is a smaller and less-powerful unit. Research on that issue had yielded that the desired setup (install WS 2008 R2 x64 and Exchange, but no data) was not recommended (setting up a DAG with multiple servers was not possible due to budget constraints). However, Exchange setup had been started (up to Mailbox Server role install), and was abandoned after persuading the powers-that-be that it was unworkable. The server in the error report is not online at this point, nor are there plans to bring it online again unless the worst happens.
My question is how concerned do I need to be about this error? My research leads me to believe that this could indicate that the regular Exchange server thinks there is a DAG in existence and is trying to replicate the mailboxes to the server in the report. This, in turn, is causing the Exchange VSS Writer to fail, leading the backups to fail in turn. Therefore I'm inclined to boot up SR203EB and uninstall Exchange completely, then un-join it from the domain. Could it be that simple to remove these 1007 Warnings, or am I completely off-track? I would appreciate any advice on this matter.
Thank you in advance.
I have Exchange 2010 SP3 set up on a Windows Server 2008 R2 64-bit server. Checking backup status through the event logs(backup is being done through Windows Server Backup) has yielded a 9782 Exchange VSS Writer error for each of four mailbox databses and a public folder database, as well as a 2007 ESE Shadow Copy error, which I have researched and am formulating a plan for (I will check on those separately).
However, I also noticed Warning ID 1007 MailboxReplication service messages occurring every 10 minutes or so. Below is a sample of one message:
Level Date and Time Source Event ID Task Category
Warning 1/30/2015 7:59:33 AM MSExchange Mailbox Replication 1007 Service "The Mailbox Replication service was unable to determine the set of active mailbox databases on a mailbox server.
Mailbox server: SR203EB.XXX.COM
Error: MapiExceptionNetworkError: Unable to make admin interface connection to server. (hr=0x80040115, ec=-2147221227)
Diagnostic context:
......
Lid: 15000 dwParam: 0x6BA Msg: EEInfo: prm[1]: Pointer val: 0x0000000000000000
Lid: 15000 dwParam: 0x6BA Msg: EEInfo: prm[2]: Pointer val: 0x4CFDA8C000000000
Lid: 16280 dwParam: 0x6BA Msg: EEInfo: ComputerName: n/a
Lid: 8600 dwParam: 0x6BA Msg: EEInfo: ProcessID: 2452
Lid: 12696 dwParam: 0x6BA Msg: EEInfo: Generation Time: 2015-01-30 12:59:33:348
Lid: 10648 dwParam: 0x6BA Msg: EEInfo: Generating component: 18
Lid: 14744 dwParam: 0x6BA Msg: EEInfo: Status: 10060
Lid: 9624 dwParam: 0x6BA Msg: EEInfo: Detection location: 318
Lid: 13720 dwParam: 0x6BA Msg: EEInfo: Flags: 0
Lid: 11672 dwParam: 0x6BA Msg: EEInfo: NumberOfParameters: 0
Lid: 24060 StoreEc: 0x80040115
Lid: 23746
Lid: 31938 StoreEc: 0x80040115
Lid: 19650
Lid: 27842 StoreEc: 0x80040115
Lid: 20866
Lid: 29058 StoreEc: 0x80040115"
The server mentioned was a server that was intended to be set up as a backup to our Exchange Server, even though it is a smaller and less-powerful unit. Research on that issue had yielded that the desired setup (install WS 2008 R2 x64 and Exchange, but no data) was not recommended (setting up a DAG with multiple servers was not possible due to budget constraints). However, Exchange setup had been started (up to Mailbox Server role install), and was abandoned after persuading the powers-that-be that it was unworkable. The server in the error report is not online at this point, nor are there plans to bring it online again unless the worst happens.
My question is how concerned do I need to be about this error? My research leads me to believe that this could indicate that the regular Exchange server thinks there is a DAG in existence and is trying to replicate the mailboxes to the server in the report. This, in turn, is causing the Exchange VSS Writer to fail, leading the backups to fail in turn. Therefore I'm inclined to boot up SR203EB and uninstall Exchange completely, then un-join it from the domain. Could it be that simple to remove these 1007 Warnings, or am I completely off-track? I would appreciate any advice on this matter.
Thank you in advance.
