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 18 hours 20 minutes ago Additional Info

Hi,

According to your description, I understand that run "Get-Queue -Server HOEX02" with error "Exchange can't connect to the Microsoft Exchange Transport service on computer "HOEX02"".
If I misunderstand your concern, please do not hesitate to let me know.

I assume you run this command in Exchange 2007 server and HOEX02 is Exchange 2013. If so, it's normal. Exchange 2007 cannot run all command and function for Exchange 2013, however, you can run it correctly in Exchange 2013.

Thanks

Hi Glarter,

Are you sure the Microsoft Exchange Transport service on computer "HOEX02" is running fine. Check if you have any errors listed in the eventlog.

Satyajit, Allen Wang:

HOEX01 is the server we're running the command from and it is Exchange 2013. When the error occurs, we've checked and double-checked the service only to find it running every time.

The event logs do not show any errors from MSExchangeTransport.