asked on

New Exchange 2013 incoming mails stuck in Q

Just started up a new exchange server and while testing I discovered incoming email is often delivered up to 90 mins after it was sent. looking around I discovered it stuck in the delivery q and going nowhere. Any ideas why the q traps some email?

ASKER CERTIFIED SOLUTION

Muhammad Burhan

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

8fort8

ASKER

The server is a vm on the domain controller and its name appears as an a record pointing to the correct ip. There's also a ptr. no mx.

Muhammad Burhan

so what you found in event logs regarding this ?

http://msexchangeguru.com/2015/01/20/mails-queued-error-4-4-1/

8fort8

ASKER

The dns is fine The ms exchange logs show event 6 cmdlet failing claiming unknown ecp and administrator. I'm completely unsure why that is.

Cmdlet failed. Cmdlet Get-Notification, parameters {Summary=True}.

- EventData

Get-Notification
{Summary=True}
ad.xyz.net/Users/Administrator
S-1-5-21-539760016-2852313788-2424403731-500
S-1-5-21-539760016-2852313788-2424403731-500
Local-ECP-Unknown

- EventData

Get-ExchangeServer
{ErrorAction=SilentlyContinue, Identity=VMEXCHANGE2013}

Local-Exchange Management Console-Unknown
2684 ExSetupUI.exe

32
00:00:00.2031245
View Entire Forest: 'True',
Microsoft.Exchange.Data.Directory.ADInvalidCredentialException: Active Directory operation failed on . The supplied credential for 'Server2013\Administrator' is invalid. ---> System.DirectoryServices.Protocols.LdapException: The supplied credential is invalid. at System.DirectoryServices.Protocols.LdapConnection.BindHelper(NetworkCredential newCredential, Boolean needSetCredential) at Microsoft.Exchange.Data.Directory.PooledLdapConnection.BindWithLogging() at Microsoft.Exchange.Data.Directory.PooledLdapConnection.BindWithRetry(Int32 maxRetries)

8fort8

ASKER

Found issue and solution
Here:
http://serverfault.com/questions/693987/exchange-server-2013-receive-connector-confusion
The errors are other separate issues but the Q problem is explained in detail on the link and worked instantly.

8fort8

ASKER

I've requested that this question be closed as follows:

Accepted answer: 0 points for 8fort8's comment #a41182168

for the following reason:

I found the answer in long after I posted the question and thought it may be of use to others. But thanks to everyone who had suggestions.

8fort8

ASKER

The link Mohammad provided did not solve the issue I was trying to solve however, it correctly identified a very common related issue that was misleading my efforts to solve the lesser issue I wrote about.