Server 2012 Standard, Exchange 2013 queue stuck...
Dear Support,
Two Day back did the migration from Exchange 2010 to exchange 2013, but both Exchange server Live Due to Some Mailboxes need to move.
Today is the first days all users using Exchange 2013, it was fine first few hours after that stared in Queue and through the attached Error message.
"The Remote Pipeline has been stopped. It was running the command 'get-message -result size '1000' -ReturnPageInfo $true - SortOrder '+From Address' -server 'OurExchange.our.domain' -SearchForward $true -BookmarkObject $null -BookmarkIndex '-1' -IncludeBookmark $false -Filter '{{Queue -eq "OurServer\430"}}"
Thx
Exchange2013.jpg
Two Day back did the migration from Exchange 2010 to exchange 2013, but both Exchange server Live Due to Some Mailboxes need to move.
Today is the first days all users using Exchange 2013, it was fine first few hours after that stared in Queue and through the attached Error message.
"The Remote Pipeline has been stopped. It was running the command 'get-message -result size '1000' -ReturnPageInfo $true - SortOrder '+From Address' -server 'OurExchange.our.domain' -SearchForward $true -BookmarkObject $null -BookmarkIndex '-1' -IncludeBookmark $false -Filter '{{Queue -eq "OurServer\430"}}"
Thx
Exchange2013.jpg
ASKER
I tried with Restart the service, Space & RAM Good, Frequently Mails in Queue for 10 to 15 mins and its releasing automatically after some time...
Are there entries in event logging which might explain what is going on?
ASKER
Yes, there is an error : Event ID 12017, An Internal transport certificate will expire soon. Thumbprint: *Long Digit*, hours remaining 1247
Nice, thats the only error that is not really significant.
It just means there is a certificate bound to IIS,smtp or other exchange mechanisms that is about to expire.
Did you test how long mails take to arrive at their destination while suspect to queeing? Both externally as internally.
It just means there is a certificate bound to IIS,smtp or other exchange mechanisms that is about to expire.
Did you test how long mails take to arrive at their destination while suspect to queeing? Both externally as internally.
There are still Some options left. Or, again, there are not enough resources available which Will stop the service or there is a issue with a DNS server somewhere.
ASKER
How to check if there is an issue with DNS server.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thx
Restart the transport service and watch if it happens again.
Check the Application event log and make sure you have enough resources to run 2013. CPU ram fast enough disks etc...
Cheers