Comments on: Can’t connect to new Exchange mailboxes revisited

By: stevesz

stevesz — Mon, 14 Aug 2006 19:25:55 +0000

looks like you might have some problems thre. You’ll probably have to do some digging to find oout why your active directory is failing the test. Do you have more than one active directory server in your organization? Look at your event logs to see icf any errors are present and then follow up on them.

If this does not do the trick, go to support,microsoft.com and search on rebuild RUS selecting your version of Exchagne for the product. Thre are a number of articles that may point you in the right dorection.

By: bacsguy

bacsguy — Mon, 14 Aug 2006 14:25:05 +0000

Thanks for all the info and believe you’re all on the right track.

We did add another DC recently. when we run DCDIAG everything passes except this section

Starting test: frsevent
There are warning or error events within the last 24 hours after the
SYSVOL has been shared. Failing SYSVOL replication problems may cause
Group Policy problems.
……………………. MINE failed test frsevent

How do we go about fixing this?

EXACTLY how do we remove and recreate the Recipient Update Service (RUS) without clobbering Exchange? We use the default settings.

thanks

By: pdmeat

pdmeat — Mon, 14 Aug 2006 09:17:57 +0000

You can remove the recipient update service from ESM and just create a new one. I’ve seen one instance where the RUS just decided to stop working for some reason, didn’t throw any errors. The only fix was to remove and recreate another RUS and then everything started working normally again.

I support nearly 30 clients with exchange 2003 and have been an exchange admin since 5.5 and I’ve only seen this happen once.

I’d look very carefully at your domain controllers and their and the exchange server event logs. Try these steps:

1) If you’re running exchange 2003 and win2003, make sure you “raise domain functional level” in win2003 AD.
2) Update the Exchange 2003 to exchange 2003 native mode if not.
3) Turn up logging on the exchange server. If the problem is with exchange, it might not log the issue if you don’t on the proper level of logging. Go into ESM and turn on logging for MSExchangeDSAccess, MSExchangeAL and MSExchangeADDXA. You can decide the logging level but medium is prob fine and it will start the busy the app log. You may have to restart various exchange services to get them to use the new logging level (reboot exchange if you can).