MTA issue on Exchange 2003 cluster

[adfreek]

We just stood up a 2 node a/p Exch2003 cluster in an existing 5.5 Org. I'm getting the following error message in my app log and I also can't send test messages from Exch2003 mailboxes to 5.5 mailboxes. Also, when a 5.5 user sends a test message to 2003, it makes it to the cluster, but sits in the Queue:

The error is:

Source: MSExchangeIS Mailbox
Cat: MTA Connections
Event id: 2000

Verify that the Microsoft Exchange MTA service has started. Consecutive ma-open calls are failing with error code 3051.

I've removed the EVS and recreated once already. Then today, I completed uninstalled and reinstalled Exch2003 on the cluster again and I'm still getting the error!!!!

I just ran MTACHECK.EXE and all looks well.

Please help

 

[xmsre]

I suspect that it is related to this issue, fixed in SP1:

http://support.microsoft.com/default.aspx?scid=kb;en-us;894094

While you're at it, you may want to tune the MTA for coedxistance with 5.5

http://support.microsoft.com/default.aspx?scid=kb;en-us;899302

 

[adfreek]

I'm running SP2 on my Exchange 2003 Cluster and that other article doesn't qualify with my situation.

Thanks. Any other ideas?

 

[xmsre]

have you run MTAcheck yet? What is your MTA database path?

 

[adfreek]

My MTA database path is:

S:\Exchsrvr\mtadata

S is the drive on the SAN dedicated to the mailbox stores.

I ran Mtacheck and it came back clean.

Should I be changing the path to something else? If so, how?

My Drives are:

C:\ OS and Exchange Binary
T:\ Trans Logs on SAN
S:\ DB's on SAN

Desperate now...been ongoing for 3 days...

 

[xmsre]

The path needs to be on a shared drive, so you have to leave it on S: in your case.
The SA cluster resource depends on S: I assume. is the MTA resource coming online in cluster admin?

 

[adfreek]

Yes, the SA resource is set to depend on S drive and T drive along with Network Name.

The MTA Cluster Resource comes online fine, no problems which is why I'm going insane

 

[Koonan]

Is this cluster the only Exchange 2003 server(s) in your 5.5 site?

If so, there might be some site replication issues with your Exchange 2003 servers. The SRS service can't run on a cluster, it needs to be on a standalone Exchange 2003 server.

Just a shot in the dark.

=====================================
The good ole days weren't always good
and tomorrow ain't as bad as it seems
=====================================

 

[adfreek]

actually, we have two FE Exch2k3 servers we installed prior to the cluster and one of them has the SRS DB on it.