Exchange 2010 msgs in Unreachable queue.

Exchange 2010 on SBS 2011
Unreachable Domain queue has 60 msgs in it with the following content in each msg.

Identity: SERVER01\Unreachable\667919
Subject: Folder Content
Internet Message ID: <0C51C69C07A80D439A8D2BE25B7C0FA41C1A38F5@SERVER01.x.local>
From Address:
Status: Ready
Size (KB): 6
Message Source Name: FromLocal
Source IP:
SCL: -1
Date Received: 11/14/2013 3:15:16 PM
Expiration Time: 11/16/2013 3:15:16 PM
Last Error: There is currently no route to the mailbox database.
Queue ID: SERVER01\Unreachable

The client used to run SBS 2003 with Exchange configured. It was migrated about 2 yrs ago.
There is no mailbox for
Mail flow is fine.

Any ideas as to cause of msgs?

Who is Participating?
Shreedhar EtteConnect With a Mentor Commented:
Open Exchnage Management Conosle

Go to Toolbox

Open Public Folder Manangement Console

Over here you will find diffent folders - Right Click on each folder you will find Replication tab and servers under that.
Seth SimmonsConnect With a Mentor Sr. Systems AdministratorCommented:
does that folder have a replica on that server?
looks like it's a mail-enabled public folder

that error basically means the address is valid but has no idea where to send the message
Shreedhar EtteCommented:
Those mails are for public folder replication.

Please remove old server from Replication Tab of public folders.
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

rojiruAuthor Commented:
I've checked various areas within EMC for any info leading to old server, but I have not found anything. On properties for Public Folder Database, Replication tab, there is no place for entry of a server. Only fields are Replication interval and limits for replication. I do remember removing entries previously in EMC for the old server, but not sure on the location. In further checking the domain there were still entries for the old server, in dns, AD Computer/Users, AD Sites & Services, which I have removed. Hopefully these last bits are all that is required.

rojiruAuthor Commented:
Thanks for the info...
Done! We'll see what happens.
rojiruAuthor Commented:
Thanks for the info.... I located the erroneous info, and changed it accordingly. Looking good now.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.