SCayr

I recently came across this problem and struggled to find a fix, so now I’ve found one, here it is.

I had done a Swing Migration from SBS 2000 to SBS 2003 a few months ago and thought I’d caught all the gotchas, but after enabling OMA came across another bug in the process.

The problem is that any user that existed before the migration can’t access OMA, any user created post-migration has no problems.

If you test with IE by browsing to HTTP://SERVER/OMA you receive the following error.

A System Error has occurred.

In the Event Log you get this error.

MSExchangeOMA Error 1503

An unknown error occurred while processing the current request:
Message: Index was out of range. Must be non-negative and less than the size of the collection.
Parameter name: startIndex
Source: mscorlib

The problem lies in the fact that the HomeMTA attribute for the original user is pointing to a deleted object.

In order to fix the problem you have to use ADSIEdit. (Don’t do it unless you know what you’re doing!)

In ADSIEdit, browse to the users container and right-click on a working user and select properties, go down the list till you find homeMTA and double-click it. Copy the contents. You’ll notice it starts with…

CN=Microsoft MTA,CN=SERVERNAME......

Next get properties of one of the faulty users, find homeMTA. It contains the wrong value, starting…

CN=Microsoft MTA\0ADEL

Paste the correct value, hit OK, and you’re good to go.  No reboots or service restarts required.

Sphere It