Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.

Dismiss

Mail sitting in E2k3->E2k7 (Routing Group Connctor) Queue?

440 views

Skip to first unread message

Scott Townsend

unread,

Dec 13, 2007, 7:36:44 PM12/13/07

We have an Exchange 2003 Server that gets the mail from the internet then
passes it along to the users on the Exchange 2007 Server.

Users are complaining that mail is taking 10+ minutes to get from the
internet.

Looking at the Headers and the Queue on the 2003 server , you can see it
stuck on the 2003 server.

I've also posted this:
http://forums.microsoft.com/TechNet/showpost.aspx?postid=2531367&siteid=17

I had to set the 2003 SMTP virtual server from 100 to 300 concurrent
connections, then restart SMTP, No Luck

for recipient policies, I've converted over all my "Address Lists", and my
"E-mail Address Policies" to OPATH filters instead of LDAP filters

Under Accepted Domain, I have all of them listed and all set to
Authoritative, though They were there, I don't remember doing anything to
them.

Both my E2k3 and E2k7 server are in the same site, same AD, same subnet,
same room, though Different Racks... (-;

HELP! the delay is annoying!

Scott<-

Terence Liu [MSFT]

unread,

Dec 14, 2007, 5:24:35 AM12/14/07

Hello Scott,

Thank you for posting here.

According to your description, I understand that the emails send from
Exchange 2003 to Exchange 2007 will delay. If I have misunderstood the
problem, please don't hesitate to let me know.

Based on my research, when you set up a new Exchange 2007 Server and joined
it into his existing Exchange 2003 Organization, also created a
bi-direction Routing Group Connector between his Exchange 2003 RG and
Exchange 2007 RG. Then, you found e-mail from the mailbox in Exchange 2003
server to the mailbox in Exchange 2007 server will fail or delay.

This issue is caused by the LinkState table in Exchange 2003 which is no
longer supported in Exchange 2007 and that will cause message routing issue.

I suggest you disable LinkState on all his old Exchange 2003 Server and
reboot the server. To disable LinkState information:

a) Open a command prompt and navigate to the ..\Exchsrvr\bin directory in
your Exchange installation directory. By default, this directory is <drive
letter>:\Program Files\Exchsrvr\bin.
b) Type the following command:

Regsrv32 -u xlsasink.dll

c) Restart the following services:

Microsoft Exchange Routing Engine service (RESvc)
SMTP service (SMTPSVC)
Microsoft Exchange MTA Stacks (MSExchangeMTA)

More Information:
--------------------------
To make the mail flow working between Exchange 2003 and Exchange 2007
servers in a mixed Org, we need to ensure the following 3 pre-requirements
done:

1. Create two RGCs (bi-direction) between Exchange 2003 RG and Exchange
2007 virtual RG by using Exchange System Manager in Exchange 2003 (don't
recommend do this by using Exchange 2007 Management Shell), and make sure
select one Exchange 2007 Hub Transport Server as local bridgehead server.

2. Disable LinkState info on all old Exchange 2003 Servers.

3. Ensure the computer account of all old Exchange 2003 servers is
belonging to the ExchangeLegacyInterop security group under the Microsoft
Exchange Security Groups OU in ADUC. This is because old Exchange 2003
servers need appropriate permissions to access Exchange 2007 resource.

Hope this will help you handle such kind of issues in the future. Also I am
looking forward to more and more knowledge sharing messages regarding
Exchange 2007 and this will help us get solid on the new product support in
a short period.

I hope these steps will give you some help.

Thanks and have a nice day!

Best regards,

Terence Liu(MSFT)

Microsoft CSS Online Newsgroup Support

Get Secure! - www.microsoft.com/security

=====================================================
This newsgroup only focuses on SBS technical issues. If you have issues
regarding other Microsoft products, you'd better post in the corresponding
newsgroups so that they can be resolved in an efficient and timely manner.
You can locate the newsgroup here:
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx

When opening a new thread via the web interface, we recommend you check the
"Notify me of replies" box to receive e-mail notifications when there are
any updates in your thread. When responding to posts via your newsreader,
please "Reply to Group" so that others may learn and benefit from your
issue.

Microsoft engineers can only focus on one issue per thread. Although we
provide other information for your reference, we recommend you post
different incidents in different threads to keep the thread clean. In doing
so, it will ensure your issues are resolved in a timely manner.

For urgent issues, you may want to contact Microsoft CSS directly. Please
check http://support.microsoft.com for regional support phone numbers.

Any input or comments in this thread are highly appreciated.
=====================================================

This posting is provided "AS IS" with no warranties, and confers no rights.

--------------------
| Reply-To: "Scott Townsend" <scoot...@community.nospam>
| From: "Scott Townsend" <scoot...@community.nospam>
| Subject: Mail sitting in E2k3->E2k7 (Routing Group Connctor) Queue?
| Date: Thu, 13 Dec 2007 16:36:44 -0800
| Lines: 30
| Message-ID: <499BCF9C-D244-46D3...@microsoft.com>
| MIME-Version: 1.0
| Content-Type: text/plain;
| format=flowed;
| charset="iso-8859-1";
| reply-type=original
| Content-Transfer-Encoding: 7bit
| X-Priority: 3
| X-MSMail-Priority: Normal
| X-Newsreader: Microsoft Windows Mail 6.0.6000.16480
| X-MimeOLE: Produced By Microsoft MimeOLE V6.0.6000.16545
| X-MS-CommunityGroup-MessageCategory:
{E4FCE0A9-75B4-4168-BFF9-16C22D8747EC}
| X-MS-CommunityGroup-PostID: {499BCF9C-D244-46D3-A14C-A759256F3032}
| Newsgroups: microsoft.public.exchange.connectivity
| Path: TK2MSFTNGHUB02.phx.gbl
| Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.exchange.connectivity:3145
| NNTP-Posting-Host: TK2MSFTNGHUB02.phx.gbl 127.0.0.1
| X-Tomcat-NG: microsoft.public.exchange.connectivity

Scott Townsend

unread,

Dec 17, 2007, 3:05:25 PM12/17/07

Thank you for your reply.

I've Unregistered xlsasink.dll on the 2003 Server. I do have a 2000 server
in the Mix, What should I do with that? Its a Secondary MX to the 2003.
Right now, it sends all of its messages to the 2003 server, then 2003 send
it on to the 2007, What will Turning off LinkState on 2003 do to this?
Seems like I would also need a Routing Connector on the 2000 to bridge to
the 2007?

So on Creating the Routing Group Between the 2003 and 2007 server via the
2003 ESM.

I do not see a way to Create a Routing Group Connector, though there are
bi-directional connectors there for the 2003/2007 servers. .
Though under Administrative Groups I have:
Exchange Administrative Group (FYDIBOHF23SPDLT)
MAIL-SERVER <-- this is where our 2000 and 2003 server is.

Under each there is a Connectors Folder.
In "Exchange Administrative Group (FYDIBOHF23SPDLT)" connectors Folder there
is:
SMTP Connector for the 2007 server
Routing Group Connector for 2007 -> 2003 (installed by installing 2007
into the 2003 site)

In "Exchange Administrative Group (FYDIBOHF23SPDLT)" connectors Folder there
is:
SMTP Connector for the 2000 server IMS
SMTP Connector for the 2003 server IMS
Routing Group Connector for 2003 -> 2007 (installed by installing 2007
into the 2003 site)

I rebooted the Exchange 2003 Server.

"Terence Liu [MSFT]" <v-te...@online.microsoft.com> wrote in message
news:ZVIdNujP...@TK2MSFTNGHUB02.phx.gbl...

Terence Liu [MSFT]

unread,

Dec 18, 2007, 4:19:30 AM12/18/07

Hello Scott,

Thank you for update.

The Routing Group Connector for 2007 -> 2003 (installed by installing 2007
into the 2003 site) and Routing Group Connector for 2003 -> 2007 (installed
by installing 2007 into the 2003 site) are the RGCs (bi-direction) between
2003 and 2007.

Why do you set the secondary MX to the 2003? Where is the first MX record?
You said "it sends all of its messages to the 2003 server", if the first MX
record does not point to 2003, how do you achieve this goal.

Then, ensure the computer account of all old Exchange 2003 servers is

belonging to the ExchangeLegacyInterop security group under the Microsoft
Exchange Security Groups OU in ADUC. This is because old Exchange 2003
servers need appropriate permissions to access Exchange 2007 resource.

Do the users on Exchange 2003 get Internet email delay?

I appreciate your time and look forward to hearing from you.

Merry Christmas and happy new year!

Best regards,

Terence Liu(MSFT)

Get Secure! - www.microsoft.com/security

| References: <499BCF9C-D244-46D3...@microsoft.com>
<ZVIdNujP...@TK2MSFTNGHUB02.phx.gbl>
| In-Reply-To: <ZVIdNujP...@TK2MSFTNGHUB02.phx.gbl>
| Subject: Re: Mail sitting in E2k3->E2k7 (Routing Group Connctor) Queue?
| Date: Mon, 17 Dec 2007 12:05:25 -0800
| Lines: 203
| Message-ID: <02A6FEA3-F8C5-4E3C...@microsoft.com>

| X-MS-CommunityGroup-PostID: {02A6FEA3-F8C5-4E3C-A597-956182714843}
| X-MS-CommunityGroup-ThreadID: 499BCF9C-D244-46D3-A14C-A759256F3032
| X-MS-CommunityGroup-ParentID: 22488933-4E7D-44B1-A0AD-9839FDEDB225
| Newsgroups: microsoft.public.exchange.connectivity
| Path: TK2MSFTNGHUB02.phx.gbl
| Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.exchange.connectivity:3161

Scott Townsend

unread,

Dec 18, 2007, 8:54:52 AM12/18/07

The 2003 Server is the Primary MX, the 2000, is the Secondary MX. the 2007
is not listed.

So All mail is typically sent to the 2003 server, then routed to the 2007
server.
If mail comes in on the 2000 server, it then gets sent to the 2003 server,
then on to the 2007 server.

Both the 2000 and 2003 servers are in the groups you mentioned.

The only account left on the 2000/2003 servers is a test account. I logged
in, sent it some mail from Yahoo, and its in the 2003->2007 Routing Queue.

Scott<-0

"Terence Liu [MSFT]" <v-te...@online.microsoft.com> wrote in message

news:dsqfbcV...@TK2MSFTNGHUB02.phx.gbl...

Terence Liu [MSFT]

unread,

Dec 19, 2007, 5:30:15 AM12/19/07

Hello Scott,

Thank you for reply.

Based on my research, I suggest you try to delete the automatically created
Routing Group Connector on 2003 and 2007. Then recreate the Routing Group
Connector between 2003 and 2007:

1 - From Exchange System Manager in Exchange 2003/2000, select the legacy
routing group, right-click and choose: New -> Routing Group Connector.
2 - Configure the connector with the Exchange 2003/2000 source bridgehead.
3 - Select the Exchange 2007 Routing Group as the target routing group, and
choose the 2007 server as the target bridgehead.
4 - Click Apply and, when prompted, click OK to create the Routing Group
Connector in the other direction; from Exchange 2007 to Exchange 2003/2000.

If we cannot resolve the issue after we perform the above steps, please
help me collect some information for further investigation:

1. Can you send email from 2003 to 2007? Does the email will be delay?

2. Please capture screenshots on the routing queue and send the pictures to
me at v-te...@microsoft.com

3. Gather Receive connector log on 2007

a. Open the Exchange Management Console, and perform one of the following
steps:

a) To modify an existing Receive connector on an Edge Transport server, in
the console tree, select Edge Transport, and then, in the work pane, click
the Receive Connectors tab.

b) To modify an existing Receive connector on a Hub Transport server,
expand Server Configuration in the console tree, and select Hub Transport.
In the result pane, select the server that has the Receive connector that
you want to modify, and then click the Receive Connectors tab.

b. In the work pane, select the Receive connector to modify.

c. Under the name of the Receive connector in the action pane, click
Properties to open the Properties page.

d. Click the General tab and use the drop-down box next to Protocol logging
level to enable protocol logging. Verbose enables protocol logging.

e. After you make your protocol logging selection, click Apply to save
changes and remain in the Properties page, or click OK to save changes and
exit the Properties page.

f. By default, the Receive connector protocol log files are located at
C:\Program Files\Microsoft\Exchange
Server\TransportRoles\Logs\ProtocolLog\SmtpReceive. Please gather the log
files here to me at v-te...@microsoft.com

I hope these steps will give you some help.

Merry Christmas and happy new year!

Best regards,

Terence Liu(MSFT)

Get Secure! - www.microsoft.com/security

<02A6FEA3-F8C5-4E3C...@microsoft.com>
<dsqfbcV...@TK2MSFTNGHUB02.phx.gbl>
| In-Reply-To: <dsqfbcV...@TK2MSFTNGHUB02.phx.gbl>

| Subject: Re: Mail sitting in E2k3->E2k7 (Routing Group Connctor) Queue?

| Date: Tue, 18 Dec 2007 05:54:52 -0800
| Lines: 351
| Message-ID: <D83E5B76-EDC5-41EA...@microsoft.com>

| X-MS-CommunityGroup-PostID: {D83E5B76-EDC5-41EA-B1C1-CF46838E1A4F}
| X-MS-CommunityGroup-ThreadID: 499BCF9C-D244-46D3-A14C-A759256F3032
| X-MS-CommunityGroup-ParentID: 62C8317D-4C3F-486C-A22C-3965E9C3EB14
| Newsgroups: microsoft.public.exchange.connectivity
| Path: TK2MSFTNGHUB02.phx.gbl
| Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.exchange.connectivity:3170

Scott Townsend

unread,

Dec 19, 2007, 10:14:25 AM12/19/07

Yeah!!!
I deleted the Routing Connectors that were in the folder
Admin Groups
<Group Name>
Connectors

Then when I Right Click the <Group Name>, my option is not to Create a
Routing Group, but a 'Routing Groups Container'
from there my 'Connector' folder goes away and I get the Following:
Admin Groups
<Group Name>
Routing Groups
<Group Name>
Connectors

Now when I right click Connectors folder I have the option to create a
routing group. This option was not there in the old Connectors folder.

I've tested and mail is getting through from both the 2000 and the 2003
servers with no noticeable delay...

Thanks again...

Scott<-

So here is the Thing....

"Terence Liu [MSFT]" <v-te...@online.microsoft.com> wrote in message

news:9S6XooiQ...@TK2MSFTNGHUB02.phx.gbl...

Scott Townsend

unread,

Dec 19, 2007, 11:34:55 AM12/19/07

&(%*#@# I take it back. I should have sent more test emails... they are
all stuck in the Queue again

I had only sent one test email from Yahoo to each of the Servers. They went
through with no delay. Then in Showing a co-working the issue, there are
now 8 Items in the Queue. A few more tests from Yahoo are now in the Queue
too...

So on to Part 2....

1) Mail from 2003 to 2007 does not delay. Almost instant
2) Sending picts
3) Sending Logs

"Terence Liu [MSFT]" <v-te...@online.microsoft.com> wrote in message

news:9S6XooiQ...@TK2MSFTNGHUB02.phx.gbl...

Terence Liu [MSFT]

unread,

Dec 20, 2007, 5:16:25 AM12/20/07

Hello Scott,

Thank you for email.

First I want to explain that I think this problem may be a little complex
and our troubleshooting maybe time-consuming. So if you would like to call
CSS for assistance, I would be appreciate and think it is a more effective
ways. To obtain the phone numbers for specific technology request please
take a look at the web site listed below.

http://support.microsoft.com/default.aspx?scid=fh;EN-US;PHONENUMBERS

If you are outside the US please see http://support.microsoft.com for
regional support phone numbers.

However I will do my best to be of assistance if you still want to continue
here.

From the error message of your screenshot: Exchange System Manager version
8.0.30535.0 or greater is required to edit this object. See About dialog
for version information, I suggest you try the following steps:

Using ADSIEdit.msc, extend to

Configuration-->
Services-->
Microsoft Exchange-->
"Org Name"-->
Recipient Policies-->

Pull up the properties of the Policy objects And clear out any entries in
the following Attributes:
msExchQueryFilter
msExchPurportedSearchUI
msExchVersion
msExchMinAdminVersion

If we cannot resolve the issue after we perform the above steps, please
help me collect some information for further investigation:

Message Tracking information
===================

Enable Message Tracking Center
--------------------------------------
Please enable Message Tracking Center via the steps included in the
following article:

How to Enable Message Tracking Center on a Server
http://technet.microsoft.com/en-us/library/cb3d10f6-ad5d-40c7-a0f5-718e67c25
5d3.aspx

After enabling Message Tracking Center, please reproduce the issue. Please
wait for a while and perform the following steps to track the message:

Track the message:
-------------------------------
a. Open Exchange System Manager.
b. Click Tools-> Message Tracking Center.
c. In the right pane, click Sender, enter the name/alias of the user, click
Check Names, and click OK.
d. Click Server, enter the FQDN of the Exchange server, click Check Names
and click OK.
e. Set the time correctly.
f. Click Find Now.
g. In the bottom pane, the e-mail just sent appears.
h. Click it and the Message History window will pop up.
i. Take a screenshot of the Message History.

Take a screenshot
-------------------------------
a. Leave the Message History on the screen and press the Print Screen key
(PrtScn) on the keyboard.
b. Click "Start", click "Run", type "mspaint" (without quotation marks),
and click "OK".
c. In the Paint program, click the "Edit" menu, click "Paste", click the
"File" menu, and click "Save".
d. The "Save As" dialogue box will appear. Type a file name in the "File
name:" box, for example: "screenshot".
e. Make sure "JPEG (*.JPG;*.JPEG;*.JPE;*.JFIF)" is selected in the "Save as
type" box, and then click "Save".

Please send this saved JPEG file to my email account at
v-te...@microsoft.com

I hope these steps will give you some help.

Merry Christmas and Happy New Year!

Best regards,

Terence Liu(MSFT)

Get Secure! - www.microsoft.com/security

<D83E5B76-EDC5-41EA...@microsoft.com>
<9S6XooiQ...@TK2MSFTNGHUB02.phx.gbl>
| In-Reply-To: <9S6XooiQ...@TK2MSFTNGHUB02.phx.gbl>

| Subject: Re: Mail sitting in E2k3->E2k7 (Routing Group Connctor) Queue?

| Date: Wed, 19 Dec 2007 08:34:55 -0800
| Lines: 568
| Message-ID: <6A5D61B4-4515-46BC...@microsoft.com>

| X-MS-CommunityGroup-PostID: {6A5D61B4-4515-46BC-A033-61993384D53B}
| X-MS-CommunityGroup-ThreadID: 499BCF9C-D244-46D3-A14C-A759256F3032
| X-MS-CommunityGroup-ParentID: 27516461-C2D3-432B-8796-E6A224532C1B
| Newsgroups: microsoft.public.exchange.connectivity
| Path: TK2MSFTNGHUB02.phx.gbl
| Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.exchange.connectivity:3189

Terence Liu [MSFT]

unread,

Dec 21, 2007, 4:59:58 AM12/21/07

Hello Scott,

Thank you for reply.

From the screenshot of message tracking, we can see the 8 minutes delay of
the mail deliver. However, we do not know what the Exchange doing during
the 8 minutes. I suggest we try the following steps:

1. I still suggest you try to delete the automatically created Routing

Group Connector on 2003 and 2007. Then recreate the Routing Group Connector
between 2003 and 2007:

a. From Exchange System Manager in Exchange 2003, select the legacy routing

group, right-click and choose: New -> Routing Group Connector.

b. Configure the connector with the Exchange 2003 source bridgehead.
c. Select the Exchange 2007 Routing Group as the target routing group, and

choose the 2007 server as the target bridgehead.

d. Click Apply and, when prompted, click OK to create the Routing Group
Connector in the other direction, from Exchange 2007 to Exchange 2003.

You can find the location here:

Admin Groups
<Group Name>
Routing Groups
<Group Name>

Connectors (here I think)

2. In the 2003 to 2007 connector properties window, select General tab,
select These servers can send mail over this connector option, and add the
server 2003.

3. In the 2 new connectors properties window of 2003 and 2007, select
Delivery Options tab, ensure "Always run" is selected in the Connection
time box.

4. To suppress link state updates on Exchange 2003

a. Open Registry Editor.
b. Locate
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\RESvc\Parameters.
c. Right-click Parameters and select New | DWORD value. Name the new DWORD
value SuppressStateChanges.
d. Double-click SuppressStateChanges.
e. In the Value data field, enter 1.
f. Close Registry Editor and then restart the Simple Mail Transfer Protocol
(SMTP) service, the Microsoft Exchange Routing Engine service, and the
Microsoft Exchange MTA Stacks services for the change to take effect.

For detail information:
How to Suppress Link State Updates
http://technet.microsoft.com/en-us/library/aa996728.aspx

5. Please try to disable any anti-spam software on Exchange 2003 if you
have. Then, test this issue.

If we cannot resolve the issue after we perform the above steps, please
help me collect some information for further investigation:

WinRoute Information
=============================
1. Please download the WinRoute tool from the following link:
http://www.microsoft.com/downloads/details.aspx?familyid=c5a8afbf-a4da-45e0-
adea-6d44eb6c257b&displaylang=en

2. Start WinRoute.exe.
3. On the File menu, click New Server Query.
4. Type the server name and bind options that you want to use to connect to
an Exchange server.
5. Click File, click Save As to save the routing information to a .rte
file.
6. Send the file to me at v-ry...@microsoft.com

How to use the WinRoute tool
http://support.microsoft.com/?id=281382

Terence Liu [MSFT]

unread,

Dec 23, 2007, 11:12:42 PM12/23/07

Email from customer:
===========================

I did re-create the groups. That was 2 Messages ago. That was when the
Connectors folder went away and was replaced be the Routing Groups Folder
with the Routing Group underneath.

That was when I thought it was working as mail was going through, though
the 3rd message I sent got delayed.

So 1, 2 & 3 are already done.
Looking at #4, SuppressStateChanges was set to 1 on both servers already.

Do I need to unregister the DLL for LInkState on the 2000 server too? I
only did it on the 2003 server.

I've included the WinRoute info.

Terence Liu [MSFT]

unread,

Dec 24, 2007, 4:35:14 AM12/24/07

Hello Scott,

Thank you for your update.

Thanks for your prompt. Yes, you are right, we need to disable LinkState on
all non-Exchange2007 servers. We also need suppress link state updates on
all non-Exchange2007 servers.

Therefore, please perform the following steps on all Exchange 2003 and
Exchange 2000 servers:

1. To disable LinkState information:

a) Open a command prompt and navigate to the ..\Exchsrvr\bin directory in
your Exchange installation directory. By default, this directory is <drive
letter>:\Program Files\Exchsrvr\bin.

b) Type the following command:

Regsrv32 -u xlsasink.dll

c) Restart the following services:

Microsoft Exchange Routing Engine service (RESvc)
SMTP service (SMTPSVC)
Microsoft Exchange MTA Stacks (MSExchangeMTA)

2. To suppress link state updates:

For detail information:
How to Suppress Link State Updates
http://technet.microsoft.com/en-us/library/aa996728.aspx

Then, test this issue.

Hope this is the root cause of this issue.

Merry Christmas and Happy New Year!

Best regards,

Terence Liu

Best regards,

Terence Liu(MSFT)

Get Secure! - www.microsoft.com/security

--------------------
| X-Tomcat-ID: 25516454

| References: <499BCF9C-D244-46D3...@microsoft.com>
<ZVIdNujP...@TK2MSFTNGHUB02.phx.gbl>
<02A6FEA3-F8C5-4E3C...@microsoft.com>
<dsqfbcV...@TK2MSFTNGHUB02.phx.gbl>
<D83E5B76-EDC5-41EA...@microsoft.com>
<9S6XooiQ...@TK2MSFTNGHUB02.phx.gbl>

<6A5D61B4-4515-46BC...@microsoft.com>
<Z7OXjFvQ...@TK2MSFTNGHUB02.phx.gbl>
<W#94Bh7QI...@TK2MSFTNGHUB02.phx.gbl>
| MIME-Version: 1.0
| Content-Type: text/plain
| Content-Transfer-Encoding: 7bit
| From: v-te...@online.microsoft.com (Terence Liu [MSFT])
| Organization: Microsoft
| Date: Mon, 24 Dec 2007 04:12:42 GMT

| Subject: Re: Mail sitting in E2k3->E2k7 (Routing Group Connctor) Queue?

| X-Tomcat-NG: microsoft.public.exchange.connectivity
| Message-ID: <xp5#$MeRIH...@TK2MSFTNGHUB02.phx.gbl>
| Newsgroups: microsoft.public.exchange.connectivity
| Lines: 16
| Path: TK2MSFTNGHUB02.phx.gbl
| Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.exchange.connectivity:3219
| NNTP-Posting-Host: tomcatimport2.phx.gbl 10.201.218.182

Albert Widjaja

unread,

Apr 20, 2011, 3:46:49 AM4/20/11

Yes, I also have similar problem when some of the users somehow still sending to the old Routing group connectors ?

so is there any way to view which email is sent to this old routing group then that'll be great.

Thanks,

>> On Friday, December 14, 2007 5:24 AM v-terli wrote:

>> Hello Scott,
>>

>> Thank you for posting here.
>>
>> According to your description, I understand that the emails send from
>> Exchange 2003 to Exchange 2007 will delay. If I have misunderstood the
>> problem, please don't hesitate to let me know.
>>
>> Based on my research, when you set up a new Exchange 2007 Server and joined
>> it into his existing Exchange 2003 Organization, also created a
>> bi-direction Routing Group Connector between his Exchange 2003 RG and
>> Exchange 2007 RG. Then, you found e-mail from the mailbox in Exchange 2003
>> server to the mailbox in Exchange 2007 server will fail or delay.
>>
>> This issue is caused by the LinkState table in Exchange 2003 which is no
>> longer supported in Exchange 2007 and that will cause message routing issue.
>>
>> I suggest you disable LinkState on all his old Exchange 2003 Server and

>> reboot the server. To disable LinkState information:

>>
>> a) Open a command prompt and navigate to the ..\Exchsrvr\bin directory in
>> your Exchange installation directory. By default, this directory is <drive
>> letter>:\Program Files\Exchsrvr\bin.
>> b) Type the following command:
>>
>> Regsrv32 -u xlsasink.dll
>>
>> c) Restart the following services:
>>
>> Microsoft Exchange Routing Engine service (RESvc)
>> SMTP service (SMTPSVC)
>> Microsoft Exchange MTA Stacks (MSExchangeMTA)
>>

>> More Information:
>> --------------------------
>> To make the mail flow working between Exchange 2003 and Exchange 2007
>> servers in a mixed Org, we need to ensure the following 3 pre-requirements
>> done:
>>
>> 1. Create two RGCs (bi-direction) between Exchange 2003 RG and Exchange
>> 2007 virtual RG by using Exchange System Manager in Exchange 2003 (don't
>> recommend do this by using Exchange 2007 Management Shell), and make sure
>> select one Exchange 2007 Hub Transport Server as local bridgehead server.
>>
>> 2. Disable LinkState info on all old Exchange 2003 Servers.
>>
>> 3. Ensure the computer account of all old Exchange 2003 servers is
>> belonging to the ExchangeLegacyInterop security group under the Microsoft
>> Exchange Security Groups OU in ADUC. This is because old Exchange 2003
>> servers need appropriate permissions to access Exchange 2007 resource.
>>
>> Hope this will help you handle such kind of issues in the future. Also I am
>> looking forward to more and more knowledge sharing messages regarding
>> Exchange 2007 and this will help us get solid on the new product support in
>> a short period.
>>

>> I hope these steps will give you some help.
>>

>> Thanks and have a nice day!
>>

>> {E4FCE0A9-75B4-4168-BFF9-16C22D8747EC}
>> my

>>>> On Tuesday, December 18, 2007 4:19 AM v-terli wrote:

>>>> Hello Scott,
>>>>

>>>> Thank you for update.
>>>>
>>>> The Routing Group Connector for 2007 -> 2003 (installed by installing 2007
>>>> into the 2003 site) and Routing Group Connector for 2003 -> 2007 (installed
>>>> by installing 2007 into the 2003 site) are the RGCs (bi-direction) between
>>>> 2003 and 2007.
>>>>
>>>> Why do you set the secondary MX to the 2003? Where is the first MX record?
>>>> You said "it sends all of its messages to the 2003 server", if the first MX
>>>> record does not point to 2003, how do you achieve this goal.
>>>>
>>>> Then, ensure the computer account of all old Exchange 2003 servers is
>>>> belonging to the ExchangeLegacyInterop security group under the Microsoft
>>>> Exchange Security Groups OU in ADUC. This is because old Exchange 2003
>>>> servers need appropriate permissions to access Exchange 2007 resource.
>>>>
>>>> Do the users on Exchange 2003 get Internet email delay?
>>>>
>>>> I appreciate your time and look forward to hearing from you.
>>>>
>>>> Merry Christmas and happy new year!
>>>>

>>>> <ZVIdNujP...@TK2MSFTNGHUB02.phx.gbl>
>>>> server
>>>> send
>>>> there
>>>> 2007
>>>> there
>>>> 2007
>>>> 2003
>>>> in
>>>> <drive
>>>> pre-requirements
>>>> sure
>>>> server.
>>>> Microsoft
>>>> I
>>>> support
>>>> corresponding
>>>> manner.
>>>> are
>>>> newsreader,
>>>> Please
>>>> microsoft.public.exchange.connectivity:3145
>>>> it
>>>> http://forums.microsoft.com/TechNet/showpost.aspx?postid=2531367&siteid=17
>>>> and
>>>> anything

>>>>> On Tuesday, December 18, 2007 8:54 AM Scott Townsend wrote:

>>>>> The 2003 Server is the Primary MX, the 2000, is the Secondary MX. the 2007
>>>>> is not listed.
>>>>>
>>>>> So All mail is typically sent to the 2003 server, then routed to the 2007
>>>>> server.
>>>>> If mail comes in on the 2000 server, it then gets sent to the 2003 server,
>>>>> then on to the 2007 server.
>>>>>
>>>>> Both the 2000 and 2003 servers are in the groups you mentioned.
>>>>>
>>>>> The only account left on the 2000/2003 servers is a test account. I logged
>>>>> in, sent it some mail from Yahoo, and its in the 2003->2007 Routing Queue.
>>>>>
>>>>> Scott<-0
>>>>>
>>>>> "Terence Liu [MSFT]" <v-te...@online.microsoft.com> wrote in message
>>>>> news:dsqfbcV...@TK2MSFTNGHUB02.phx.gbl...

>>>>>> On Wednesday, December 19, 2007 5:30 AM v-terli wrote:

>>>>>> Hello Scott,
>>>>>>
>>>>>> Thank you for reply.
>>>>>>
>>>>>> Based on my research, I suggest you try to delete the automatically created

>>>>>> Routing Group Connector on 2003 and 2007. Then recreate the Routing Group
>>>>>> Connector between 2003 and 2007:
>>>>>>

>>>>>> 1 - From Exchange System Manager in Exchange 2003/2000, select the legacy

>>>>>> routing group, right-click and choose: New -> Routing Group Connector.

>>>>>> 2 - Configure the connector with the Exchange 2003/2000 source bridgehead.

>>>>>> 3 - Select the Exchange 2007 Routing Group as the target routing group, and

>>>>>> choose the 2007 server as the target bridgehead.

>>>>>> 4 - Click Apply and, when prompted, click OK to create the Routing Group
>>>>>> Connector in the other direction; from Exchange 2007 to Exchange 2003/2000.

>>>>>>
>>>>>> If we cannot resolve the issue after we perform the above steps, please
>>>>>> help me collect some information for further investigation:
>>>>>>

>>>>>> I hope these steps will give you some help.
>>>>>>

>>>>>> Merry Christmas and happy new year!

>>>>>> <ZVIdNujP...@TK2MSFTNGHUB02.phx.gbl>
>>>>>> <02A6FEA3-F8C5-4E3C...@microsoft.com>
>>>>>> <dsqfbcV...@TK2MSFTNGHUB02.phx.gbl>
>>>>>> 2007
>>>>>> server,
>>>>>> logged
>>>>>> 2007
>>>>>> between
>>>>>> record?
>>>>>> first
>>>>>> Microsoft
>>>>>> corresponding
>>>>>> manner.
>>>>>> are
>>>>>> newsreader,
>>>>>> Please
>>>>>> Queue?
>>>>>> microsoft.public.exchange.connectivity:3161
>>>>>> 2003.
>>>>>> bridge
>>>>>> are
>>>>>> from
>>>>>> the
>>>>>> and
>>>>>> Exchange
>>>>>> is
>>>>>> routing
>>>>>> directory
>>>>>> 2007
>>>>>> 2003
>>>>>> resource.
>>>>>> Also
>>>>>> regarding
>>>>>> there
>>>>>> your
>>>>>> Although
>>>>>> In
>>>>>> numbers.
>>>>>> Queue?
>>>>>> internet
>>>>>> http://forums.microsoft.com/TechNet/showpost.aspx?postid=2531367&siteid=17
>>>>>> concurrent
>>>>>> Lists",
>>>>>> filters

>>>>>>> On Wednesday, December 19, 2007 10:14 AM Scott Townsend wrote:

>>>>>>> Yeah!!!
>>>>>>> I deleted the Routing Connectors that were in the folder
>>>>>>> Admin Groups
>>>>>>> <Group Name>
>>>>>>> Connectors
>>>>>>>
>>>>>>> Then when I Right Click the <Group Name>, my option is not to Create a
>>>>>>> Routing Group, but a 'Routing Groups Container'
>>>>>>> from there my 'Connector' folder goes away and I get the Following:

>>>>>>> Admin Groups
>>>>>>> <Group Name>
>>>>>>> Routing Groups
>>>>>>> <Group Name>
>>>>>>> Connectors
>>>>>>>

>>>>>>> Now when I right click Connectors folder I have the option to create a
>>>>>>> routing group. This option was not there in the old Connectors folder.
>>>>>>>
>>>>>>> I've tested and mail is getting through from both the 2000 and the 2003
>>>>>>> servers with no noticeable delay...
>>>>>>>
>>>>>>> Thanks again...
>>>>>>>
>>>>>>> Scott<-
>>>>>>>
>>>>>>>
>>>>>>> So here is the Thing....

>>>>>>> "Terence Liu [MSFT]" <v-te...@online.microsoft.com> wrote in message
>>>>>>> news:9S6XooiQ...@TK2MSFTNGHUB02.phx.gbl...

>>>>>>>> On Wednesday, December 19, 2007 11:34 AM Scott Townsend wrote:

>>>>>>>> &(%*#@# I take it back. I should have sent more test emails... they are
>>>>>>>> all stuck in the Queue again
>>>>>>>>
>>>>>>>> I had only sent one test email from Yahoo to each of the Servers. They went
>>>>>>>> through with no delay. Then in Showing a co-working the issue, there are
>>>>>>>> now 8 Items in the Queue. A few more tests from Yahoo are now in the Queue
>>>>>>>> too...
>>>>>>>>
>>>>>>>>
>>>>>>>> So on to Part 2....
>>>>>>>>
>>>>>>>> 1) Mail from 2003 to 2007 does not delay. Almost instant
>>>>>>>> 2) Sending picts
>>>>>>>> 3) Sending Logs
>>>>>>>>
>>>>>>>> "Terence Liu [MSFT]" <v-te...@online.microsoft.com> wrote in message
>>>>>>>> news:9S6XooiQ...@TK2MSFTNGHUB02.phx.gbl...

>>>>>>>>> On Thursday, December 20, 2007 5:16 AM v-terli wrote:

>>>>>>>>> Hello Scott,
>>>>>>>>>

>>>>>>>>> Thank you for email.
>>>>>>>>>
>>>>>>>>> First I want to explain that I think this problem may be a little complex
>>>>>>>>> and our troubleshooting maybe time-consuming. So if you would like to call
>>>>>>>>> CSS for assistance, I would be appreciate and think it is a more effective
>>>>>>>>> ways. To obtain the phone numbers for specific technology request please
>>>>>>>>> take a look at the web site listed below.
>>>>>>>>>
>>>>>>>>> http://support.microsoft.com/default.aspx?scid=fh;EN-US;PHONENUMBERS
>>>>>>>>>

>>>>>>>>> If you are outside the US please see http://support.microsoft.com for
>>>>>>>>> regional support phone numbers.
>>>>>>>>>

>>>>>>>>> However I will do my best to be of assistance if you still want to continue
>>>>>>>>> here.
>>>>>>>>>
>>>>>>>>> From the error message of your screenshot: Exchange System Manager version
>>>>>>>>> 8.0.30535.0 or greater is required to edit this object. See About dialog
>>>>>>>>> for version information, I suggest you try the following steps:
>>>>>>>>>
>>>>>>>>> Using ADSIEdit.msc, extend to
>>>>>>>>>
>>>>>>>>> Configuration-->
>>>>>>>>> Services-->
>>>>>>>>> Microsoft Exchange-->
>>>>>>>>> "Org Name"-->
>>>>>>>>> Recipient Policies-->
>>>>>>>>>
>>>>>>>>> Pull up the properties of the Policy objects And clear out any entries in
>>>>>>>>> the following Attributes:
>>>>>>>>> msExchQueryFilter
>>>>>>>>> msExchPurportedSearchUI
>>>>>>>>> msExchVersion
>>>>>>>>> msExchMinAdminVersion
>>>>>>>>>

>>>>>>>>> If we cannot resolve the issue after we perform the above steps, please
>>>>>>>>> help me collect some information for further investigation:
>>>>>>>>>

>>>>>>>>> I hope these steps will give you some help.
>>>>>>>>>

>>>>>>>>> Merry Christmas and Happy New Year!
>>>>>>>>>
>>>>>>>>> Best regards,
>>>>>>>>>

>>>>>>>>> Terence Liu(MSFT)
>>>>>>>>>
>>>>>>>>> Microsoft CSS Online Newsgroup Support
>>>>>>>>>
>>>>>>>>> Get Secure! - www.microsoft.com/security
>>>>>>>>>
>>>>>>>>> =====================================================
>>>>>>>>> This newsgroup only focuses on SBS technical issues. If you have issues
>>>>>>>>> regarding other Microsoft products, you'd better post in the corresponding
>>>>>>>>> newsgroups so that they can be resolved in an efficient and timely manner.
>>>>>>>>> You can locate the newsgroup here:
>>>>>>>>> http://www.microsoft.com/communities/newsgroups/en-us/default.aspx
>>>>>>>>>
>>>>>>>>> When opening a new thread via the web interface, we recommend you check the
>>>>>>>>> "Notify me of replies" box to receive e-mail notifications when there are
>>>>>>>>> any updates in your thread. When responding to posts via your newsreader,
>>>>>>>>> please "Reply to Group" so that others may learn and benefit from your
>>>>>>>>> issue.
>>>>>>>>>
>>>>>>>>> Microsoft engineers can only focus on one issue per thread. Although we
>>>>>>>>> provide other information for your reference, we recommend you post
>>>>>>>>> different incidents in different threads to keep the thread clean. In doing
>>>>>>>>> so, it will ensure your issues are resolved in a timely manner.
>>>>>>>>>
>>>>>>>>> For urgent issues, you may want to contact Microsoft CSS directly. Please
>>>>>>>>> check http://support.microsoft.com for regional support phone numbers.
>>>>>>>>>
>>>>>>>>> Any input or comments in this thread are highly appreciated.
>>>>>>>>> =====================================================
>>>>>>>>>
>>>>>>>>> This posting is provided "AS IS" with no warranties, and confers no rights.
>>>>>>>>>
>>>>>>>>> --------------------

>>>>>>>>> <ZVIdNujP...@TK2MSFTNGHUB02.phx.gbl>
>>>>>>>>> <02A6FEA3-F8C5-4E3C...@microsoft.com>
>>>>>>>>> <dsqfbcV...@TK2MSFTNGHUB02.phx.gbl>
>>>>>>>>> <D83E5B76-EDC5-41EA...@microsoft.com>
>>>>>>>>> <9S6XooiQ...@TK2MSFTNGHUB02.phx.gbl>

>>>>>>>>> are
>>>>>>>>> went
>>>>>>>>> Queue
>>>>>>>>> Group
>>>>>>>>> legacy
>>>>>>>>> bridgehead.
>>>>>>>>> pictures
>>>>>>>>> following
>>>>>>>>> in
>>>>>>>>> click
>>>>>>>>> Transport.
>>>>>>>>> that
>>>>>>>>> and
>>>>>>>>> log
>>>>>>>>> corresponding
>>>>>>>>> manner.
>>>>>>>>> are
>>>>>>>>> newsreader,
>>>>>>>>> Please
>>>>>>>>> Queue?
>>>>>>>>> microsoft.public.exchange.connectivity:3170
>>>>>>>>> installing
>>>>>>>>> is
>>>>>>>>> 2003
>>>>>>>>> resource.
>>>>>>>>> there
>>>>>>>>> your
>>>>>>>>> Although
>>>>>>>>> In
>>>>>>>>> numbers.
>>>>>>>>> 2000
>>>>>>>>> there
>>>>>>>>> server
>>>>>>>>> misunderstood
>>>>>>>>> Server
>>>>>>>>> RG
>>>>>>>>> delay.
>>>>>>>>> which
>>>>>>>>> directory
>>>>>>>>> 2003
>>>>>>>>> bridgehead
>>>>>>>>> is
>>>>>>>>> Exchange
>>>>>>>>> future.
>>>>>>>>> timely
>>>>>>>>> http://www.microsoft.com/communities/newsgroups/en-us/default.aspx
>>>>>>>>> you
>>>>>>>>> from
>>>>>>>>> clean.
>>>>>>>>> directly.
>>>>>>>>> confers
>>>>>>>>> <499BCF9C-D244-46D3...@microsoft.com>
>>>>>>>>> http://forums.microsoft.com/TechNet/showpost.aspx?postid=2531367&siteid=17
>>>>>>>>> to

>>>>>>>>>> On Friday, December 21, 2007 4:59 AM v-terli wrote:

>>>>>>>>>> Hello Scott,
>>>>>>>>>>

>>>>>>>>>> 4. To suppress link state updates on Exchange 2003

>>>>>>>>>>
>>>>>>>>>> a. Open Registry Editor.
>>>>>>>>>> b. Locate
>>>>>>>>>> HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\RESvc\Parameters.
>>>>>>>>>> c. Right-click Parameters and select New | DWORD value. Name the new DWORD
>>>>>>>>>> value SuppressStateChanges.
>>>>>>>>>> d. Double-click SuppressStateChanges.
>>>>>>>>>> e. In the Value data field, enter 1.
>>>>>>>>>> f. Close Registry Editor and then restart the Simple Mail Transfer Protocol
>>>>>>>>>> (SMTP) service, the Microsoft Exchange Routing Engine service, and the
>>>>>>>>>> Microsoft Exchange MTA Stacks services for the change to take effect.
>>>>>>>>>>
>>>>>>>>>> For detail information:
>>>>>>>>>> How to Suppress Link State Updates
>>>>>>>>>> http://technet.microsoft.com/en-us/library/aa996728.aspx
>>>>>>>>>>

>>>>>>>>>> 5. Please try to disable any anti-spam software on Exchange 2003 if you
>>>>>>>>>> have. Then, test this issue.
>>>>>>>>>>
>>>>>>>>>> If we cannot resolve the issue after we perform the above steps, please
>>>>>>>>>> help me collect some information for further investigation:
>>>>>>>>>>
>>>>>>>>>> WinRoute Information
>>>>>>>>>> =============================
>>>>>>>>>> 1. Please download the WinRoute tool from the following link:
>>>>>>>>>> http://www.microsoft.com/downloads/details.aspx?familyid=c5a8afbf-a4da-45e0-
>>>>>>>>>> adea-6d44eb6c257b&displaylang=en
>>>>>>>>>>
>>>>>>>>>> 2. Start WinRoute.exe.
>>>>>>>>>> 3. On the File menu, click New Server Query.
>>>>>>>>>> 4. Type the server name and bind options that you want to use to connect to
>>>>>>>>>> an Exchange server.
>>>>>>>>>> 5. Click File, click Save As to save the routing information to a .rte
>>>>>>>>>> file.
>>>>>>>>>> 6. Send the file to me at v-ry...@microsoft.com
>>>>>>>>>>
>>>>>>>>>> How to use the WinRoute tool
>>>>>>>>>> http://support.microsoft.com/?id=281382
>>>>>>>>>>
>>>>>>>>>> I hope these steps will give you some help.
>>>>>>>>>>

>>>>>>>>>> Merry Christmas and Happy New Year!
>>>>>>>>>>
>>>>>>>>>> Best regards,
>>>>>>>>>>
>>>>>>>>>> Terence Liu

>>>>>>>>>>> On Sunday, December 23, 2007 11:12 PM v-terli wrote:

>>>>>>>>>>> Email from customer:
>>>>>>>>>>> ===========================
>>>>>>>>>>>
>>>>>>>>>>> I did re-create the groups. That was 2 Messages ago. That was when the
>>>>>>>>>>> Connectors folder went away and was replaced be the Routing Groups Folder
>>>>>>>>>>> with the Routing Group underneath.
>>>>>>>>>>>
>>>>>>>>>>> That was when I thought it was working as mail was going through, though
>>>>>>>>>>> the 3rd message I sent got delayed.
>>>>>>>>>>>
>>>>>>>>>>> So 1, 2 & 3 are already done.
>>>>>>>>>>> Looking at #4, SuppressStateChanges was set to 1 on both servers already.
>>>>>>>>>>>
>>>>>>>>>>> Do I need to unregister the DLL for LInkState on the 2000 server too? I

>>>>>>>>>>> only did it on the 2003 server.
>>>>>>>>>>>
>>>>>>>>>>> I've included the WinRoute info.

0 new messages