problem with exchange server
hi.i have some wierd problem:i got 1 dc server 2003 and 1 exchange 2003 server.when i create a new user, i cant see him at the GAL after the update.also when i create him with exchange mailbox he dont have the main address that i configured in the reciepient policies at the exchange system manager.i checked my dc with dcdiag and no problems, checked global catalog and also fine.at the exchange side i tried to rebuild the RUS and the OFFLINE ADDRESS BOOK and no errors.i tried to delete \ create many users and the problem repeat with all of them.i tried to create another address book and i cant see him as well.i tried to restart my exchange + dc servers and same problem happens.this problem is for all client users with cached mode and without.and for last i increased the logging server on the exchange and cant see nothing unusual at the event viewer both in the dc and the exchange servers.any ideas?thx,mor.
September 24th, 2009 1:47pm

Looks like the RUS is not stamping email address on newly created mailboxes Here's 4 common reasons why the RUS can break, and what to do about it. To confirm that the Recipient Update Service is working: Confirm that the Recipient Update Service update interval is set to Always Run , and then create a new user object. 1 - The RUS configuration references a deleted domain controller or Exchange 2000 server, or the servers defined in the RUS configuration are not operating correctly. Within the configuration of the RUS, alternative servers can be selected, if available. Further information on doing this can be found in the section entitled 'How To Configure The Default Recipient Update Service Instances' in the Microsoft KB article found here . 2 - Inheritable permissions are removed on an Organizational Unit (OU) and the RUS is no longer able to reach the objects within it. This issue is detailed in the Microsoft KB article found here . 3 - The RUS is unable to generate email addresses because it is unable to locate a third party email address generator, a specific DLL file. This typically occurs in environments where Exchange 5.5 and Exchange 2000 are coexisting, and the Exchange 5.5 server had mixed environments where an Exchange 5.5 server previously had some third party software installed; this is usually fax software. Exchange 2000 builds its recipient policies based on the Exchange 5.5 site addressing, including the third party address, and since the required DLL does not exist on the Exchange 2000 server being used by the RUS, the process fails. This issue is detailed in the Microsoft KB article found here . 4 - If the RUS encounters a distribution list that has its membership hidden, it will not be able to stamp it with the required mail attributes, and will go to sleep for 30 minutes. This issue is detailed in the Microsoft KB article found here . http://hellomate.typepad.com/exchange/2003/07/is_your_rus_not.html Vinod |CCNA|MCSE 2003 +Messaging|MCTS|ITIL V3|
Free Windows Admin Tool Kit Click here and download it now
September 24th, 2009 2:12pm

hi,it happens because of replication issue between DC and Exchange server, please run the setup/domain prep in DC and wait for the replication , and make sure 389 port should be opened from Exchange to DCalso as you said you rebuild the RUS , it will not stamp the email address to new ID until server check all the existing the email ID`s , it takes so much time depending upon the objects creating on exchange serverEnable the diagonistic logging in exchange server from the system manager, please enable the proxy generation , OAL generation and paste the error it here.after enabling the diagnostic logging , create the new user and update the RUS , and see the event viewer regards,jeevan
September 24th, 2009 2:32pm

Hi,To troubleshoot the RUS issue, please refer to the below article:http://support.microsoft.com/?id=822794Please first work out the RUS issue before handle the OAB issue.ThanksAllen
Free Windows Admin Tool Kit Click here and download it now
September 28th, 2009 10:10am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics