I have a customer with Exchange 2013 coexisting with Exchange 2007.

After resolving an issue yesterday, it's been highlighted that the Get-Queue cmdlet is failing to connect to the Transport service on Exchange 2013. This is repeated several times before it actually connects and returns the queue lengths.

[PS] D:\Exchange\scripts>get-queue -Server HOEX02
Exchange can't connect to the Microsoft Exchange Transport service on computer "HOEX02". Verify that the service is
started.
    + CategoryInfo          : InvalidOperation: (:) [Get-Queue], LocalizedException
    + FullyQualifiedErrorId : [Server=HOEX01,RequestId=c1973250-0ab5-4632-a99b-3aad301ab5c1,TimeStamp=28/07/2015 13:08
   :26] [FailureCategory=Cmdlet-LocalizedException] B7967CF,Microsoft.Exchange.Management.QueueViewerTasks.GetQueueIn
  fo
    + PSComputerName        : hoex01.*****************.local

Has anyone come across this before and what can be causing it??

• Edited by GLarter Tuesday, July 28, 2015 1:09 PM Additional Info

Hi,

Check if this helps. What is the antivirus solution you are using, have you excluded the exchange related objects.

Exchange Server 2007 Transport not working - Microsoft Exchange can't connect to the queue viewer server:

http://www.experts-exchange.com/Networking/Protocols/Email/Q_26430891.html

Hi,

Sorry for my misunderstanding, try restart Microsoft Exchange Transport service for testing.
How about run Get-Queue in Exchange 2007 and Exchange 2013 server separately?

If it return similar error message, please try to recreate queue database for testing:
a. Check and ensure that no messages are present in queue
b. Stop Microsoft Exchange Transport Service
c. Rename the current "Queue" folder under C:\Program Files\Microsoft\Exchange Server\Transport Roles\data\ to Queue_Old and created a new Queue Folder
d. Start Microsoft Exchange Transport Service
e. Check the "Queue" folder under C:\Program Files\Microsoft\Exchange Server\Transport Roles\data\ location to see if new mail.que database is created
f. Confirm mailflow

Thanks

Dear All,

Thank you for your help. The comments about the antivirus exclusions did help as we discovered the Transport Service was crashing and restarting every minute. The Mail.Que was full of legacy emails which were trying to load and were bringing down the service.

We stopped the Service, moved the database and log files then restarted the service to recreate the files. Bingo, no service crashes.

Hi Glarter,

Thanks for the update and resolution. Nearly missed it as we didn't had any logs for it strangely.

So we may consider this as a corrupt Mail.que database issue, which got resolved once you reset the queue DB.

So we may consider this as a corrupt Mail.que database issue, which got resolved once you reset the queue DB.

Yeah, pretty much ...

We resolved this on Wednesday, I haven't heard of any further problems.