all the sudded my exchange 2013 server is not processing messages. all services are up and running. restarted the server. running coexistance with 2010. restarted that server as well. windows updates were done last night. an uattempt to update to cu 9 failed at start

exchange 2013 version build 15.0

Hi,

would you provide more details:

- Exchange 2013 is not processing any messages, or just in some scenarios?
- Did you you check event logs? What did you see in protocol logs?
- Did you enable Logging of receive connectors? Have you seen any error?
- Did you check queues? If message stucks in a queue, you can get a message details, which might help

- Did you make any configuration change or what has happened before it stopped working?

not processing any messges.

nothing showing up in the queus.

all we have been doing is moving mailboxes from 2010 to 2013. we tried an cu9 update but it didnt go so we reverted to out previous server snaphot

i am still going through rest of log

This was in the application log

The store driver failed to submit event 2978128 mailbox bf5a8a2f-bce7-4cbb-a73b-6be6f7b12731 MDB fcf546b9-4a17-44e5-8e70-c31cd9ff24c9 and couldn't generate an NDR due to exception Microsoft.Exchange.MailboxTransport.StoreDriverCommon.InvalidSenderException
   at Microsoft.Exchange.MailboxTransport.Shared.SubmissionItem.SubmissionItemUtils.CopySenderTo(SubmissionItemBase submissionItem, TransportMailItem message)
   at Microsoft.Exchange.MailboxTransport.Submission.StoreDriverSubmission.MailItemSubmitter.GenerateNdrMailItem()
   at Microsoft.Exchange.MailboxTransport.Submission.StoreDriverSubmission.MailItemSubmitter.<>c__DisplayClass1.<FailedSubmissionNdrWorker>b__0()
   at Microsoft.Exchange.MailboxTransport.StoreDriverCommon.StorageExceptionHandler.RunUnderTableBasedExceptionHandler(IMessageConverter converter, StoreDriverDelegate workerFunction).

this was also detected

Process w3wp.exe (ECP) (PID=15956). Object [CN=Exchange Admin,CN=Users,DC=berkshire,DC=loc]. Property [PreviousDatabase] is set to value [berkshire.loc/Configuration/Deleted Objects/EX10test
DEL:be387a86-29c2-4e91-bee1-56ca53857dde], it is pointing to the Deleted Objects container in Active Directory. This property should be fixed as soon as possible.

you can step by step troubleshooting this problem,

event ID need for resolve this issue , you are restored your exchange previous server snapshot, does its contend mailbox database then its have database issue .

1. check inside your organization mail flow is working. if its flow 

then

any changes received connector  ,

Public Domain server

mx record and host Record 

accepted domain.

Thanks,

Public Domain server mx record and host Record or accepted domain.

after restarting again i found these errors in the app log

There was an error setting up WacConfiguration. Wac will be disabled and we will fall back to stellent. The WacUrlHostName was invalid. Expected a valid Uri. Actual value was ''. Value read from 'OrganizationConfig'

Watson report about to be sent for process id: 7176, with parameters: E12IIS, c-RTL-AMD64, 15.00.0913.022, w3wp#MSExchangeOWAAppPool, M.E.Data.ApplicationLogic, M.E.D.S.GccUtils.GetClientIPEndpointsFromHttpRequest, System.NullReferenceException, 5f30, 15.00.0913.017.
ErrorReportingEnabled: True

Mail connectivity test fails

Outbound mail test passes

inbound passes according the connectivity analyzer but my spam filter says Error performing SMTP test:
Connected to 10.2.0.29:25 session output follows:

"Missing EXPR element in Autodiscover XML Response."

Hi,

Please Check

Internal and external url of outlook anywhere setting and AutoDiscovery services are running , 

Thanks,

try to manually update to cu 9 on exchange server , there is no need to change any setting , cause of no one done any changes on server , I hope you resolve

today I'm going to Cu9 update manually on Exchange Cluster environment, if i find any info, I will let you know. 

i got the following when trying to update to cu9

Error:
The following error was generated when "$error.Clear();
    initialize-ExchangeUniversalGroups -DomainController $RoleDomainController -ActiveDirectorySplitPermissions $RoleActiveDirectorySplitPermissions

" was run: "Microsoft.Exchange.Management.Tasks.InvalidWKObjectException: The well-known object entry B:32:B3DDC6BE2A3BE84B97EB2DCE9477E389:CN=Help Desk\0ADEL:59be4e14-d14a-4cef-ae1c-ee5b721982a7,CN=Deleted Objects,DC=berkshire,DC=loc on the otherWellKnownObjects attribute in the container object CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=berkshire,DC=loc points to an invalid DN or a deleted object.  Remove the entry, and then rerun the task.
   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.Management.Tasks.InitializeExchangeUniversalGroups.CreateGroup(ADOrganizationalUnit usgContainer, String groupName, Int32 groupId, Guid wkGuid, String groupDescription, GroupTypeFlags groupType, Boolean createAsRoleGroup)
   at Microsoft.Exchange.Management.Tasks.InitializeExchangeUniversalGroups.CreateRoleGroup(ADOrganizationalUnit usgContainer, RoleGroupDefinition roleGroup)
   at Microsoft.Exchange.Management.Tasks.InitializeExchangeUniversalGroups.CreateAndValidateRoleGroups(ADOrganizationalUnit usgContainer, RoleGroupCollection roleGroups)
   at Microsoft.Exchange.Management.Tasks.InitializeExchangeUniversalGroups.InternalProcessRecord()
   at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
   at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".

i got the following when trying to update to cu9

Error:
The following error was generated when "$error.Clear();
    initialize-ExchangeUniversalGroups -DomainController $RoleDomainController -ActiveDirectorySplitPermissions $RoleActiveDirectorySplitPermissions

" was run: "Microsoft.Exchange.Management.Tasks.InvalidWKObjectException: The well-known object entry B:32:B3DDC6BE2A3BE84B97EB2DCE9477E389:CN=Help Desk\0ADEL:59be4e14-d14a-4cef-ae1c-ee5b721982a7,CN=Deleted Objects,DC=berkshire,DC=loc on the otherWellKnownObjects attribute in the container object CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=berkshire,DC=loc points to an invalid DN or a deleted object.  Remove the entry, and then rerun the task.
   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.Management.Tasks.InitializeExchangeUniversalGroups.CreateGroup(ADOrganizationalUnit usgContainer, String groupName, Int32 groupId, Guid wkGuid, String groupDescription, GroupTypeFlags groupType, Boolean createAsRoleGroup)
   at Microsoft.Exchange.Management.Tasks.InitializeExchangeUniversalGroups.CreateRoleGroup(ADOrganizationalUnit usgContainer, RoleGroupDefinition roleGroup)
   at Microsoft.Exchange.Management.Tasks.InitializeExchangeUniversalGroups.CreateAndValidateRoleGroups(ADOrganizationalUnit usgContainer, RoleGroupCollection roleGroups)
   at Microsoft.Exchange.Management.Tasks.InitializeExchangeUniversalGroups.InternalProcessRecord()
   at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
   at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)&

Hi stonecold,

Thank you for your question.                                         

Did internal user send/receive emails?

In above suggestion, we could check the following things:

1.        Make sure databases are mounted on  Exchange 2013
2.        Run the following command to make sure all server components are active:Get-ServerComponentState Identity <ServerName>
3.        Telnet port 25 to Exchange server from internal or external to check if it is successful
4.        For testing, please create a new database on Exchange with a new account to check if the account could connect to Exchange 2013
5.        Try to manually configure outlook to check if account could send email

The error  which is ActiveDirectorySplitPermissions $RoleActiveDirectorySplitPermissions technet, we could use the LDP.exe tool to remove otherwellknownobjects:

https://technet.microsoft.com/en-us/library/bb288907(EXCHG.80,printer).aspx

If there are any questions regarding this issue, please be free to let me know.

Best Regard,

Jim

Have you checked incoming SMTP emails status with the help of Microsofts remote connectivity analyzer? I believe it will show you few errors in incoming SMTP emails. Test here..https://testconnectivity.microsoft.com/

You may also try out this tutorial as an alternate solution!