The Microsoft Exchange Mailbox Transport Submission service terminated unexpectedly

Hi, I get following error on my new Exchange 2013 server:
It has done this 1 time(s). The following corrective action will be taken in 5000 milliseconds: Restart the service.
Mailbox database is mounted and contains mailboxes (also system mailbox), ipv6 is enabled on the exchange server.
Is there any logging I can find to see what's going on actually? The transport service won't start either.

Hello,
Could you please check the application log and let us know the related event ID and its details?
Thanks,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Simon Wu
TechNet Community Support

Similar Messages

Exchange 2013 The Microsoft Exchange Search Host Controller service terminates

Hi Folks,
at our Exchange Server ( Version 15.0 (Build 775.38 / 0.1 (8.0.535.0 ) we found over 200k entrys / day saying that:
The Microsoft Exchange Search Host Controller service terminated unexpectedly. It has done this 193270 time(s). The following corrective action will be taken in 30 milliseconds: Restart the service.
The Command:
Get-MailboxDatabaseCopyStatus | fl 'Content*'
shows the following:
ContentIndexState            : Failed
ContentIndexErrorMessage     : An internal error occurred for the database or its index
ContentIndexVersion          :
ContentIndexBacklog          :
ContentIndexRetryQueueSize   :
ContentIndexMailboxesToCrawl :
ContentIndexSeedingPercent   :
ContentIndexSeedingSource    :
i investigated a bit further:
RunspaceId                            : 06d7b8f6-969f-47f8-89ba-87b2fed639bb
Identity                              : db_1\exch1
Id                                    : db_1\exch1
Name                                  : db_1\exch1
DatabaseName                          : db_1
Status                                : Healthy
InstanceStartTime                     : 14.10.2014 21:03:38
LastStatusTransitionTime              : 14.10.2014 21:03:45
MailboxServer                         : exch1
ActiveDatabaseCopy                    : exch2
ActiveCopy                            : False
ActivationPreference                  : 1
StatusRetrievedTime                   : 15.10.2014 13:36:52
WorkerProcessId                       : 2076
ActivationSuspended                   : False
ActionInitiator                       : Unknown
ErrorMessage                          :
ErrorEventId                          :
ExtendedErrorInfo                     :
SuspendComment                        :
RequiredLogsPresent                   :
SinglePageRestore                     : 0
ContentIndexState                     : Failed
ContentIndexErrorMessage              : An internal error occurred for the database or its index
ContentIndexVersion                   :
ContentIndexBacklog                   :
ContentIndexRetryQueueSize            :
ContentIndexMailboxesToCrawl          :
ContentIndexSeedingPercent            :
ContentIndexSeedingSource             :
CopyQueueLength                       : 0
ReplayQueueLength                     : 0
ReplaySuspended                       : False
ResumeBlocked                         : False
ReseedBlocked                         : False
MinimumSupportedDatabaseSchemaVersion : 0.121
MaximumSupportedDatabaseSchemaVersion : 0.126
So i read that the Database is OK, but the Index is broken somewhow ?
I`ve read somewhere that i should delete the GUID Folder and restart the Hostcontroller service, can somebody explain HOW to do this ? where can i Find the GUID Folder ? Is it the correct way to solve this problem ?
thx in advance!

Hi,
after i removed the suggested Folder, i disabled both "Microsoft Exchange Search service and Microsoft Exchange Search Host Controller service, than i restarted the Exchange Server.
After that i restarted both services.
Sadly nothing has changed, hostcontroller.exe is still crashing:
The Microsoft Exchange Search Host Controller service terminated unexpectedly. It has done this 153 time(s). The following corrective action will be taken in 30 milliseconds: Restart the service.
The sequence is like this:
First the Search controller starts:
Search HostController Starts: Service started successfully.
After that the hostcontroller crashes:
.NET Runtime: Application: hostcontrollerservice.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: Microsoft.Ceres.HostController.Controller.HostControllerException
Stack:
   at Microsoft.Ceres.HostController.WcfServer.WcfService.StartService()
   at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
   at System.Threading.ThreadHelper.ThreadStart()
Than we get this Application Error:
Application Error:
Faulting application name: hostcontrollerservice.exe, version: 16.0.775.0, time stamp: 0x5211bea8
Faulting module name: KERNELBASE.dll, version: 6.2.9200.16864, time stamp: 0x531d34d8
Exception code: 0xe0434352
Fault offset: 0x0000000000047b8c
Faulting process id: 0x2a08
Faulting application start time: 0x01cfe90eb249f511
Faulting application path: C:\Program Files\Microsoft\Exchange Server\V15\Bin\Search\Ceres\HostController\hostcontrollerservice.exe
Faulting module path: C:\Windows\system32\KERNELBASE.dll
Report Id: f2351e08-5501-11e4-940b-00155d203202
Faulting package full name:
Faulting package-relative application ID:
So if anybody can help - feel free!

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?

PST Import to archive mailbox - Stays in queue until i restart the microsoft exchange mailbox replication service

Good Day all,
Stretched dag between site a and site b. Cas array at each site. Mailboxes primarily are located in site a unless there is a major outage then the dag flips to site b. setup two archive databases, one in site A on a non replicated partition
of the dag server and one in site B on a separate mailbox only server.
All exchange servers are patched to the latest sp and rollup.
site a has no issues at all, everything i import queues up and processes with no problems
at site b two imports will process and then stop until i restart the microsoft exchange mailbox replication service on the cas server. No errors no nothing just lots of move request sitting in the queue.
considering i have an insane amount of psts to import there does anyone have any suggestions besides setting up a task to restart the imicrosoft exchange mailbox replication service every 15 minutes?
thanks for your help in advance

Yeah I know from my research when I was setting up the dag you were not a fan of the stretched DAG but it works for us really well and passed all fail over tests that we ran on it <knocking on wood>.
Yes its running but it stops working after one session. I have had success in raising the transfer count from 2 to 5 but I can't really go much higher without taking down the server. the problem is when I am transferring someone with hundreds
of PSTs I have to babysit it...which sucks..
anyway, thanks for your help and have a great day :)

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.

Cisco Unified CCX Node Manager service terminated unexpectedly

"Windows must now restart because the Cisco Unified CCX Node Manager service terminated unexpectedly."
After I installed my CCX os and software. The os reminded me like above. I guessed I need to upgrade the patch of my OS. And I also installed McAfee ver 8.5i at my OS. But that doesn't work. I noticed that the status of cisco unified ccx node manager was starting.

On a new install, this can occur if you start patching the OS before you get UCCX installed. This is especially a problem in an HA environment. Some of the patches set values to things they should not be if they are applied before the software is installed.
When installing UCCX on a new system, you should build the OS on the box (DO NOT PATCH at this time), Install the UCCX software and integrate with CCM, get your second server (if you are doing HA) on line with OS and UCCX and integrated. Once all the above are done, then you can start installing OS patches and UCCX patches.
You should NEVER start installing things like AV software before you have the system completely up and working. If you do, and they cause issues, you cannot tell if it's a system issue, or something caused by your a/v software.

Event ID 7031 followed by 7032 The Microsoft Exchange Transport service terminated unexpectedly.

Hello
Have a strange problem that reoccurs every day. The following are recorded in the log.
7031
The Microsoft Exchange Transport service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 5000 milliseconds: Restart the service.7032The Service Control Manager tried to take a corrective action (Restart the service) after the unexpected termination of the Microsoft Exchange Transport service, but this action failed with the following error:
An instance of the service is already running.Any suggestions are welcome./Deland
/Andreas

Here are the result from the level 5 logging. I Havent disabled the TransportAgent yet.
Log Name:      Application
Source:        MSExchangeTransport
Date:          2013-07-19 10:13:25
Event ID:      12025
Task Category: TransportService
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      XXXX
Description:
Transport service is disconnecting performance counters with process lifetime from their old process.
Followed by 32 events of 12028
Log Name:      Application
Source:        MSExchangeTransport
Date:          2013-07-19 10:13:25
Event ID:      12028
Task Category: TransportService
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      XXXX
Description:
The process with process ID 1100 is holding the performance counter configuration cache total requests Value=0 SpinLock=0 Lifetime=Type: 1 ProcessId: 1100 StartupTime: 130186827159405062 from instance transportrules(B1D082BB) RefCount=0 SpinLock=0 Offset=3936
and category MSExchangeTransport Configuration Cache while running processes are: Processes running are:
6300 UMWorkerProcess
5312 Microsoft.Exchange.ServiceHost
1568 Microsoft.Exchange.Diagnostics.Service
2212 WMSvc
776 svchost
1760 MSExchangeHMHost
9808 MSExchangeDelivery
376 explorer
2252 Microsoft.Exchange.Directory.TopologyService
9436 rundll32
1752 nscp
2932 noderunner
6076 MSExchangeSubmission
7056 scanningprocess
1736 PccNtMon
1340 fms
4688 MSExchangeTransport
1732 Ntrtscan
2716 MSExchangeMailboxAssistants
548 winlogon
9016 TmProxy
348 svchost
2904 SMSvcHost
1524 inetinfo
8376 TMBMSRV
5264 MSExchangeThrottling
12552 powershell
4080 w3wp
1124 svchost
7688 svchost
12744 w3wp
332 smss
1316 svchost
13188 mmc
5772 ForefrontActiveDirectoryConnector
3080 HostedAgent
11364 conhost
3268 w3wp
1060 svchost
2924 noderunner
904 dwm
3856 w3wp
504 wininit
7200 Microsoft.Exchange.Store.Worker
1668 SMSvcHost
4832 MSExchangeFrontendTransport
2072 sftracing
4932 MSExchangeMailboxReplication
7192 Microsoft.Exchange.Store.Worker
6992 Microsoft.Exchange.UM.CallRouter
9640 w3wp
9204 svchost
3244 svcGenericHost
1200 Microsoft.Exchange.Store.Service
876 svchost
10724 rundll32
3040 conhost
2480 w3wp
5992 MSExchangeTransportLogSearch
596 services
12508 w3wp
2636 MSExchangeHMWorker
11892 taskhostex
4796 Microsoft.Exchange.Search.Service
3568 WmiPrvSE
12532 ServerManager
9564 msdtc
4352 Microsoft.Exchange.EdgeSyncSvc
2032 mqsvc
6560 scanningprocess
3404 TmListen
4384 updateservice
3004 scanningprocess
6744 umservice
1424 hostcontrollerservice
828 svchost
432 csrss
696 svchost
1284 spoolsv
8152 w3wp
3576 w3wp
1264 svchost
496 csrss
5928 Microsoft.Exchange.RpcClientAccess.Service
2972 noderunner
2380 conhost
604 lsass
6884 Microsoft.Exchange.Store.Worker
10056 WmiPrvSE
992 svchost
2764 noderunner
5324 msexchangerepl
4 System
3548 Microsoft.Exchange.AntispamUpdateSvc
2168 svchost
0 Idle
And 28 events on 106
Log Name:      Application
Source:        MSExchange Common
Date:          2013-07-19 10:13:29
Event ID:      106
Task Category: General
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      XXXX
Description:
Performance counter updating error. Counter name is DataRow seeks total, category name is MSExchangeTransport Database. Optional code: 2. Exception: The exception thrown is : System.InvalidOperationException: Instance '_total' already exists with a lifetime
of Process. It cannot be recreated or reused until it has been removed or until the process using it has exited.
   at System.Diagnostics.SharedPerformanceCounter.FindInstance(Int32 instanceNameHashCode, String instanceName, CategoryEntry* categoryPointer, InstanceEntry** returnInstancePointerReference, Boolean activateUnusedInstances, PerformanceCounterInstanceLifetime
lifetime, Boolean& foundFreeInstance)
   at System.Diagnostics.SharedPerformanceCounter.GetCounter(String counterName, String instanceName, Boolean enableReuse, PerformanceCounterInstanceLifetime lifetime)
   at System.Diagnostics.SharedPerformanceCounter..ctor(String catName, String counterName, String instanceName, PerformanceCounterInstanceLifetime lifetime)
   at System.Diagnostics.PerformanceCounter.InitializeImpl()
   at System.Diagnostics.PerformanceCounter.get_RawValue()
   at Microsoft.Exchange.Diagnostics.ExPerformanceCounter.get_RawValue()
Last worker process info : System.ArgumentException: Process with an Id of 14868 is not running.
   at System.Diagnostics.Process.GetProcessById(Int32 processId)
   at Microsoft.Exchange.Diagnostics.ExPerformanceCounter.GetLastWorkerProcessInfo()
Processes running while Performance counter failed to update:
6300 UMWorkerProcess
5312 Microsoft.Exchange.ServiceHost
1568 Microsoft.Exchange.Diagnostics.Service
2212 WMSvc
776 svchost
1760 MSExchangeHMHost
9808 MSExchangeDelivery
376 explorer
2252 Microsoft.Exchange.Directory.TopologyService
9436 rundll32
1752 nscp
2932 noderunner
10416 EdgeTransport
6076 MSExchangeSubmission
7056 scanningprocess
1736 PccNtMon
1340 fms
4688 MSExchangeTransport
1732 Ntrtscan
2716 MSExchangeMailboxAssistants
548 winlogon
9016 TmProxy
348 svchost
2904 SMSvcHost
1524 inetinfo
15116 conhost
8376 TMBMSRV
5264 MSExchangeThrottling
12552 powershell
4080 w3wp
1124 svchost
7688 svchost
12744 w3wp
332 smss
1316 svchost
13188 mmc
5772 ForefrontActiveDirectoryConnector
3080 HostedAgent
11364 conhost
3268 w3wp
1060 svchost
2924 noderunner
904 dwm
3856 w3wp
504 wininit
7200 Microsoft.Exchange.Store.Worker
1668 SMSvcHost
4832 MSExchangeFrontendTransport
2072 sftracing
4932 MSExchangeMailboxReplication
7192 Microsoft.Exchange.Store.Worker
6992 Microsoft.Exchange.UM.CallRouter
9640 w3wp
9204 svchost
3244 svcGenericHost
1200 Microsoft.Exchange.Store.Service
876 svchost
10724 rundll32
3040 conhost
2480 w3wp
5992 MSExchangeTransportLogSearch
596 services
12508 w3wp
2636 MSExchangeHMWorker
11892 taskhostex
4796 Microsoft.Exchange.Search.Service
3568 WmiPrvSE
12532 ServerManager
9564 msdtc
4352 Microsoft.Exchange.EdgeSyncSvc
2032 mqsvc
6560 scanningprocess
3404 TmListen
4384 updateservice
3004 scanningprocess
6744 umservice
1424 hostcontrollerservice
828 svchost
432 csrss
696 svchost
1284 spoolsv
8152 w3wp
3576 w3wp
1264 svchost
496 csrss
5928 Microsoft.Exchange.RpcClientAccess.Service
2972 noderunner
2380 conhost
604 lsass
6884 Microsoft.Exchange.Store.Worker
10056 WmiPrvSE
992 svchost
2764 noderunner
5324 msexchangerepl
4 System
3548 Microsoft.Exchange.AntispamUpdateSvc
2168 svchost
0 Idle
Performance Counters Layout information: A process is holding onto a transport performance counter. processId : 1100, counter : datarow seeks total Value=59 SpinLock=0 Lifetime=Type: 1 ProcessId: 1100 StartupTime: 130186827159405062, currentInstance : queue(B351294)
RefCount=0 SpinLock=0 Offset=48552, categoryName: MSExchangeTransport Database
A process is holding onto a transport performance counter. processId : 1100, counter : datarow seeks total Value=0 SpinLock=0 Lifetime=Type: 1 ProcessId: 1100 StartupTime: 130186827159405062, currentInstance : cat event 8(ED0419E7) RefCount=0 SpinLock=0 Offset=44384,
categoryName: MSExchangeTransport Database
A process is holding onto a transport performance counter. processId : 1100, counter : datarow seeks total Value=0 SpinLock=0 Lifetime=Type: 1 ProcessId: 1100 StartupTime: 130186827159405062, currentInstance : cat event 6(ED0419E9) RefCount=0 SpinLock=0 Offset=40216,
categoryName: MSExchangeTransport Database
A process is holding onto a transport performance counter. processId : 1100, counter : datarow seeks total Value=4 SpinLock=0 Lifetime=Type: 1 ProcessId: 1100 StartupTime: 130186827159405062, currentInstance : cat event 3(ED0419EC) RefCount=0 SpinLock=0 Offset=36048,
categoryName: MSExchangeTransport Database
A process is holding onto a transport performance counter. processId : 1100, counter : datarow seeks total Value=3 SpinLock=0 Lifetime=Type: 1 ProcessId: 1100 StartupTime: 130186827159405062, currentInstance : cat event 1(ED0419EE) RefCount=0 SpinLock=0 Offset=31880,
categoryName: MSExchangeTransport Database
A process is holding onto a transport performance counter. processId : 1100, counter : datarow seeks total Value=18 SpinLock=0 Lifetime=Type: 1 ProcessId: 1100 StartupTime: 130186827159405062, currentInstance : cat(B874BB3) RefCount=0 SpinLock=0 Offset=27712,
categoryName: MSExchangeTransport Database
A process is holding onto a transport performance counter. processId : 1100, counter : datarow seeks total Value=0 SpinLock=0 Lifetime=Type: 1 ProcessId: 1100 StartupTime: 130186827159405062, currentInstance : inqueue(56145953) RefCount=0 SpinLock=0 Offset=23544,
categoryName: MSExchangeTransport Database
A process is holding onto a transport performance counter. processId : 1100, counter : datarow seeks total Value=17 SpinLock=0 Lifetime=Type: 1 ProcessId: 1100 StartupTime: 130186827159405062, currentInstance : smtpin(81392C98) RefCount=0 SpinLock=0 Offset=19376,
categoryName: MSExchangeTransport Database
A process is holding onto a transport performance counter. processId : 1100, counter : datarow seeks total Value=0 SpinLock=0 Lifetime=Type: 1 ProcessId: 1100 StartupTime: 130186827159405062, currentInstance : mail(7C6FB7CC) RefCount=0 SpinLock=0 Offset=15208,
categoryName: MSExchangeTransport Database
A process is holding onto a transport performance counter. processId : 1100, counter : datarow seeks total Value=68 SpinLock=0 Lifetime=Type: 1 ProcessId: 1100 StartupTime: 130186827159405062, currentInstance : other(ADC98A1) RefCount=0 SpinLock=0 Offset=11040,
categoryName: MSExchangeTransport Database
A process is holding onto a transport performance counter. processId : 4832, counter : datarow seeks total Value=0 SpinLock=0 Lifetime=Type: 1 ProcessId: 4832 StartupTime: 130183498009738545, currentInstance : _total(CFBEE918) RefCount=1 SpinLock=0 Offset=32,
categoryName: MSExchangeTransport Database
Log Name:      Application
Source:        MSExchange Common
Date:          2013-07-19 10:13:31
Event ID:      106
Task Category: General
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      XXXX
Description:
Performance counter updating error. Counter name is Transaction Durable Callback Count/sec, category name is MSExchangeTransport Database. Optional code: 1. Exception: The exception thrown is : System.InvalidOperationException: Instance '_total' already exists
with a lifetime of Process. It cannot be recreated or reused until it has been removed or until the process using it has exited.
   at System.Diagnostics.SharedPerformanceCounter.FindInstance(Int32 instanceNameHashCode, String instanceName, CategoryEntry* categoryPointer, InstanceEntry** returnInstancePointerReference, Boolean activateUnusedInstances, PerformanceCounterInstanceLifetime
lifetime, Boolean& foundFreeInstance)
   at System.Diagnostics.SharedPerformanceCounter.GetCounter(String counterName, String instanceName, Boolean enableReuse, PerformanceCounterInstanceLifetime lifetime)
   at System.Diagnostics.SharedPerformanceCounter..ctor(String catName, String counterName, String instanceName, PerformanceCounterInstanceLifetime lifetime)
   at System.Diagnostics.PerformanceCounter.InitializeImpl()
   at System.Diagnostics.PerformanceCounter.IncrementBy(Int64 value)
   at Microsoft.Exchange.Diagnostics.ExPerformanceCounter.IncrementBy(Int64 incrementValue)
Last worker process info : System.ArgumentException: Process with an Id of 14868 is not running.
   at System.Diagnostics.Process.GetProcessById(Int32 processId)
   at Microsoft.Exchange.Diagnostics.ExPerformanceCounter.GetLastWorkerProcessInfo()
Processes running while Performance counter failed to update:
6300 UMWorkerProcess
5312 Microsoft.Exchange.ServiceHost
1568 Microsoft.Exchange.Diagnostics.Service
2212 WMSvc
776 svchost
1760 MSExchangeHMHost
9808 MSExchangeDelivery
376 explorer
2252 Microsoft.Exchange.Directory.TopologyService
9436 rundll32
1752 nscp
2932 noderunner
10416 EdgeTransport
6076 MSExchangeSubmission
7056 scanningprocess
1736 PccNtMon
1340 fms
4688 MSExchangeTransport
1732 Ntrtscan
2716 MSExchangeMailboxAssistants
548 winlogon
9016 TmProxy
348 svchost
2904 SMSvcHost
1524 inetinfo
15116 conhost
8376 TMBMSRV
5264 MSExchangeThrottling
12552 powershell
4080 w3wp
1124 svchost
7688 svchost
12744 w3wp
332 smss
1316 svchost
13188 mmc
5772 ForefrontActiveDirectoryConnector
3080 HostedAgent
11364 conhost
3268 w3wp
1060 svchost
2924 noderunner
904 dwm
3856 w3wp
504 wininit
7200 Microsoft.Exchange.Store.Worker
1668 SMSvcHost
4832 MSExchangeFrontendTransport
2072 sftracing
4932 MSExchangeMailboxReplication
7192 Microsoft.Exchange.Store.Worker
6992 Microsoft.Exchange.UM.CallRouter
9640 w3wp
9204 svchost
3244 svcGenericHost
1200 Microsoft.Exchange.Store.Service
876 svchost
10724 rundll32
3040 conhost
2480 w3wp
5992 MSExchangeTransportLogSearch
596 services
12508 w3wp
2636 MSExchangeHMWorker
11892 taskhostex
4796 Microsoft.Exchange.Search.Service
3568 WmiPrvSE
12532 ServerManager
9564 msdtc
4352 Microsoft.Exchange.EdgeSyncSvc
2032 mqsvc
6560 scanningprocess
3404 TmListen
4384 updateservice
3004 scanningprocess
6744 umservice
1424 hostcontrollerservice
828 svchost
432 csrss
696 svchost
1284 spoolsv
8152 w3wp
3576 w3wp
1264 svchost
496 csrss
5928 Microsoft.Exchange.RpcClientAccess.Service
2972 noderunner
2380 conhost
604 lsass
6884 Microsoft.Exchange.Store.Worker
10056 WmiPrvSE
992 svchost
2764 noderunner
5324 msexchangerepl
4 System
3548 Microsoft.Exchange.AntispamUpdateSvc
2168 svchost
0 Idle
Performance Counters Layout information: A process is holding onto a transport performance counter. processId : 1100, counter : datarow seeks total Value=59 SpinLock=0 Lifetime=Type: 1 ProcessId: 1100 StartupTime: 130186827159405062, currentInstance : queue(B351294)
RefCount=0 SpinLock=0 Offset=48552, categoryName: MSExchangeTransport Database
A process is holding onto a transport performance counter. processId : 1100, counter : datarow seeks total Value=0 SpinLock=0 Lifetime=Type: 1 ProcessId: 1100 StartupTime: 130186827159405062, currentInstance : cat event 8(ED0419E7) RefCount=0 SpinLock=0 Offset=44384,
categoryName: MSExchangeTransport Database
A process is holding onto a transport performance counter. processId : 1100, counter : datarow seeks total Value=0 SpinLock=0 Lifetime=Type: 1 ProcessId: 1100 StartupTime: 130186827159405062, currentInstance : cat event 6(ED0419E9) RefCount=0 SpinLock=0 Offset=40216,
categoryName: MSExchangeTransport Database
A process is holding onto a transport performance counter. processId : 1100, counter : datarow seeks total Value=4 SpinLock=0 Lifetime=Type: 1 ProcessId: 1100 StartupTime: 130186827159405062, currentInstance : cat event 3(ED0419EC) RefCount=0 SpinLock=0 Offset=36048,
categoryName: MSExchangeTransport Database
A process is holding onto a transport performance counter. processId : 1100, counter : datarow seeks total Value=3 SpinLock=0 Lifetime=Type: 1 ProcessId: 1100 StartupTime: 130186827159405062, currentInstance : cat event 1(ED0419EE) RefCount=0 SpinLock=0 Offset=31880,
categoryName: MSExchangeTransport Database
A process is holding onto a transport performance counter. processId : 1100, counter : datarow seeks total Value=18 SpinLock=0 Lifetime=Type: 1 ProcessId: 1100 StartupTime: 130186827159405062, currentInstance : cat(B874BB3) RefCount=0 SpinLock=0 Offset=27712,
categoryName: MSExchangeTransport Database
A process is holding onto a transport performance counter. processId : 1100, counter : datarow seeks total Value=0 SpinLock=0 Lifetime=Type: 1 ProcessId: 1100 StartupTime: 130186827159405062, currentInstance : inqueue(56145953) RefCount=0 SpinLock=0 Offset=23544,
categoryName: MSExchangeTransport Database
A process is holding onto a transport performance counter. processId : 1100, counter : datarow seeks total Value=17 SpinLock=0 Lifetime=Type: 1 ProcessId: 1100 StartupTime: 130186827159405062, currentInstance : smtpin(81392C98) RefCount=0 SpinLock=0 Offset=19376,
categoryName: MSExchangeTransport Database
A process is holding onto a transport performance counter. processId : 10416, counter : datarow seeks total Value=0 SpinLock=0 Lifetime=Type: 1 ProcessId: 10416 StartupTime: 130186952059962770, currentInstance : mail(7C6FB7CC) RefCount=1 SpinLock=0 Offset=15208,
categoryName: MSExchangeTransport Database
A process is holding onto a transport performance counter. processId : 10416, counter : datarow seeks total Value=0 SpinLock=0 Lifetime=Type: 1 ProcessId: 10416 StartupTime: 130186952059962770, currentInstance : other(ADC98A1) RefCount=1 SpinLock=0 Offset=11040,
categoryName: MSExchangeTransport Database
A process is holding onto a transport performance counter. processId : 4832, counter : datarow seeks total Value=0 SpinLock=0 Lifetime=Type: 1 ProcessId: 4832 StartupTime: 130183498009738545, currentInstance : _total(CFBEE918) RefCount=1 SpinLock=0 Offset=32,
categoryName: MSExchangeTransport Database
Then ESE Recovery starts on the Transport database.
/Andreas

Exchange 2013 - The Microsoft Exchange Transport service is rejecting message submissions because the service continues to consume more memory than the configured threshold

Noticed at about noon that no emails had been received all day. Began to investigate and found that the MS Exchange Transport service had been set to deny email submission because it was using too much memory on the server (91%).
The error message makes me think that we may have been getting used by malware or something similar.“The Microsoft Exchange Transport service is rejecting message submissions because the service continues to consume more memory than the
configured threshold.”
There are also several warning messages that list particular IP addresses and say that a connection from that IP was denied because there were already the maximum number of connections (20).
From what I can tell, all of the IP addresses are from Taiwan.
The time period for which some emails may be missing is from close of business yesterday ( 4/3/2014) through about 12:45 today (4/4/2014).
From the time I spent reading and trying to figure out the error, I think we may need to readjust our throttling policies to prevent this from happening.
The exchange server is currently running at 90%+ CPU and 50%+ memory usage the majority of the time, and I’m not sure how to fix it.
Also, I cannot get into EMS I get a access denied message from the destination computer. (Exchange server) I want to get into there to change the throttling policy back to default, since we disabled it.
The Error reads:
The WinRM client cannot process the request. The WinRM client tried to use Kerberos authentication mechanism, but the destination computer <Exchange> returned an 'access denied' error. Change the configuration to allow Kerberos authentication
mechanism to be used or specify one of the authentication mechanism supported by the server. (How do I do this?) To use Kerberos, specify the local computer name as the remote destination. (I'm trying to use EMS while logged into the local Exchange server)
Also verify that the client computer and the destination computer are joined to a domain. (Exchange is on our domain, and the computer trying to connect is the same computer) To use basic, specify the local computer name as the remote destination, specify
Basic authentication and provide user mane and password. Possible authentication mechanisms reported by server.
At line:1 char:1
+ New-PSSession -ConnectionURI "$connectionUri" -ConfigurationName Microsoft.Excha ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotingTransportException + FullyQualifiedErrorId : AccessDenied,PSSessionOpenFailed
I assumed control of this exchange system already in place and I do not have much experience with exchange 2013 or server 2012. I do know 2008, but that doesn't help very much in this situation.
Recent changes to the system:
About three days ago we switch our sessions policy to allow many more connections, and I believe this caused the issue. This is what I changed it to:
Made the registry DWORD (32-bit) "Maximum Allowed Sessions Per User" and modified the value to 1000. Location of registry change @ HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeIS\ParametersSystem
I just changed it to 10 from the 1000. I'm hoping this solves this. So far no.
Also, I am not the best in the shell or command line interfaces. Any help would be wonderful!

Hi,
Yes, could be hardware performance issue. Try recycle the Transport process and see if the issue persists.
Thanks,
Simon Wu
TechNet Community Support

Microsoft Exchange Transport service terminated unexpectedly

Hi All,
We have configured exchange 2013 in windows server 2012. From last two days exchange transport service getting stopped.
Microsoft Exchange Transport service terminated unexpectedly.
Log Name:      System
Source:        Service Control Manager
Date:          11/13/2014 1:10:28 AM
Event ID:      7031
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      BMBPRMBX01.BMB.LOCAL
Description:
The Microsoft Exchange Transport service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 5000 milliseconds: Restart the service.

Hi,
This issue may due to some of the corrupt message in the queue. Please try these steps to solve this issue.
Pause the transport service and let all the messaged go out.
When queue is empty, stop the transport service and go to the mail.que database in transport-->queue folder. Cut paste all the files from queue folder to some other folder as backup.
Now start the transport service, it will create a fresh mail.que database and observe if the service us crashing again.
In addition, please try to disable any AV software, sometimes it will cause Transport service corrupted.
Best Regards.

Error while installing exchange2007 : Unable to initialize the Microsoft Exchange Information Store service. Failed to find the

Hi,
I am trying fresh install of exchange2007, everything gone well but, finally it thrown a error saying :
Unable to initialize the Microsoft Exchange Information Store service. Failed to find the working directory parameter from the registry - Error 0x80004005.
the installation log says
6/5/2007 3:14:05 PM] [1] Processing component 'Mailbox Service Control (Last)' (Starting mailbox services).
[6/5/2007 3:14:05 PM] [1] Executing 'start-SetupService -ServiceName MSExchangeIS -MaximumWaitTime "unlimited"', handleError = False
[6/5/2007 3:14:05 PM] [2] Launching sub-task '$error.Clear(); start-SetupService -ServiceName MSExchangeIS -MaximumWaitTime "unlimited"'.
[6/5/2007 3:14:05 PM] [2] Beginning processing.
[6/5/2007 3:14:05 PM] [2] The maximum wait for the operation is set to 'unlimited'.
[6/5/2007 3:14:05 PM] [2] Service checkpoint has progressed. Previous checkpoint='0' - Current checkpoint='1'.
[6/5/2007 3:14:05 PM] [2] Will wait '10000' milliseconds for the service 'MSExchangeIS' to reach status 'Running'.
[6/5/2007 3:14:15 PM] [2] Service 'MSExchangeIS' failed to reach status 'Running' on this server after waiting for '10000' milliseconds.
[6/5/2007 3:14:15 PM] [2] Service 'MSExchangeIS' failed to start. Check the event log for possible reasons for the service start failure.
[6/5/2007 3:14:15 PM] [2] [ERROR] Unexpected Error
[6/5/2007 3:14:15 PM] [2] [ERROR] Service 'MSExchangeIS' failed to start. Check the event log for possible reasons for the service start failure.
[6/5/2007 3:14:15 PM] [2] Ending processing.
[6/5/2007 3:14:15 PM] [1] The following 1 error(s) occurred during task execution:
[6/5/2007 3:14:15 PM] [1] 0. ErrorRecord: Service 'MSExchangeIS' failed to start. Check the event log for possible reasons for the service start failure.
[6/5/2007 3:14:15 PM] [1] 0. ErrorRecord: Microsoft.Exchange.Configuration.Tasks.ServiceFailedToStartException: Service 'MSExchangeIS' failed to start. Check the event log for possible reasons for the service start failure.
[6/5/2007 3:14:15 PM] [1] [ERROR] Service 'MSExchangeIS' failed to start. Check the event log for possible reasons for the service start failure.
[6/5/2007 3:14:15 PM] [1] Setup is halting task execution because of one or more errors in a critical task.
[6/5/2007 3:14:15 PM] [1] Finished executing component tasks.
[6/5/2007 3:14:15 PM] [1] Ending processing.
[6/5/2007 3:14:18 PM] [0] End of Setup
[6/5/2007 3:14:18 PM] [0] **********************************************
this I am trying on my test system please help me out in resolving the issue
thanks in advance,

Gary,
Open Registry Editor.
In Registry Editor, navigate to the following registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeIS\ParametersSystem
Create the following value (REG_SZ): Working Directory and give it a value that points to the new database folder.
Make sure you back up the registry before you do any changes on it.
Raj

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

RPC request to the Microsoft Exchange Information Store service for log truncation

Hello all
Running Exchange 2013 CU3 on Windows 2008R2 sp1 in a two node DAG. We are seeing the bellow warning when running a backup. How to resolve this?
RPC request to the Microsoft Exchange Information Store service for log truncation failed for database CoramB3\Servername. Error: Failed to notify source server 'servername.coram.com' about the local truncation point. Hresult: 0xc8000713. Error: Unable to find
the file. Also log files are not being flushed
Bulls on Parade

Hello,
Please verify backup software.
Please use vssadmin list writers command to check the status of the VSS admin. If it is in a
failed state, please restart the Exchange replication service and then check the status again.
Please use Get-MailboxDatabaseCopyStatus cmdlet to view health and status information about mailbox database copies.
Please use Get-DatabaseAvailabilityGroupNetwork “DAG Name” | fl cmdlet to view configuration and state information for a DAG network.
Please use Get-DatabaseAvailabilityGroupNetwork DAG Name\MAPINetwork | fl cmdlet and Get-DatabaseAvailabilityGroupNetwork DAG Name\ReplicationNetwork | fl cmdlet to
check configuration information for MAPI network and Replication Network.
If the above configuration information is ok, please check if there are other related errors in application log.
Cara Chen
TechNet Community Support

The Microsoft Exchange Mailbox Transport Submission service terminated unexpectedly

Similar Messages

Maybe you are looking for