Re: Default e-mail addresses not being created

From: Alan Sun [MSFT] (v-asun_at_online.microsoft.com)
Date: 12/02/04

  • Next message: Michael Turner: "Any one know how to fix this." 
    Date: Thu, 02 Dec 2004 06:09:12 GMT

    Hi Harrison,

    Thanks for your posting back.

    According to the currrent situation, I suggest you use the steps below to
    narrow down the issue further:

    1. Check if the new created user is listed in the Global Address Book on a
    Outlook client.

    2. Try to send a test message to the new created user.

    3. Test if the user can log into his mailbox with the new account.

    4. Check mail attribution of the problematic user using ADSI Editor
    utility.

    Note: ADSI Editor is included in Windows 2000 supporting tools.

    A. Start ADSI Editor.
    B. Expand Domain[your_domain], and navigate to the problemtic user.
    C. Open the user's Properties.
    D. Check the value of the attibution mail.

    Please inform me of the results at your convenience. Have a nice day!

    Thanks & Regards
    Alan Sun
    Microsoft Online Partner Support

    Get Secure! - www.microsoft.com/security
    =====================================================
    When responding to posts, please "Reply to Group" via your newsreader so
    that others may learn and benefit from your issue.
    =====================================================

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

    --------------------
         Reply-To: "Harrison Midkiff" <HMidkiff@aviinc.com>
         From: "Harrison Midkiff" <HMidkiff@aviinc.com>
         References: <OtjUNQx1EHA.1204@TK2MSFTNGP10.phx.gbl>
    <Ejppp$01EHA.2732@cpmsftngxa10.phx.gbl>
         Subject: Re: Default e-mail addresses not being created
         Date: Wed, 1 Dec 2004 10:37:05 -0500
         Lines: 151
         Organization: Audio Visual Innovations, Inc.
         X-Priority: 3
         X-MSMail-Priority: Normal
         X-Newsreader: Microsoft Outlook Express 6.00.2900.2180
         X-RFC2646: Format=Flowed; Original
         X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
         Message-ID: <u10Tfu71EHA.2624@TK2MSFTNGP11.phx.gbl>
         Newsgroups: microsoft.public.exchange2000.general
         NNTP-Posting-Host: 65.218.176.126
         Path:
    cpmsftngxa10.phx.gbl!TK2MSFTFEED01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP11
    phx.gbl
         Xref: cpmsftngxa10.phx.gbl microsoft.public.exchange2000.general:62119
         X-Tomcat-NG: microsoft.public.exchange2000.general
         
         Alan:
         
         Thanks for reply to my post.
         
         All the steps you listed are what I have already tried. In addition I
         followed the troubleshooting in KB822794, but didn't show anything new.
         
         My event log is basically clean despite increasing the logging. Any
    other
         ideas? Thanks.
         
         Harrison Midkiff
         
         
         
         
         "Alan Sun [MSFT]" <v-asun@online.microsoft.com> wrote in message
         news:Ejppp$01EHA.2732@cpmsftngxa10.phx.gbl...
    > Hey Harrison,
    >
    > Thanks for your posting here.
    >
    > Based on my experience, this behavior is mostly related to Recipient
    > Update
    > Service (RUS), which is responsible for populating email address.
    >
    > You mentioned that you have rebuilt the RUS. I suggest you run an
    update
    > or
    > a rebuild operation again, use the following steps:
    >
    > 1. Click Start, point to Programs, point to Microsoft Exchange, and
    then
    > click System Manager.
    >
    > 2. Expand the Recipients object, and then click the Recipient Update
    > Services container.
    >
    > 3. Right-click the Recipient Update Service instance that you want to
    > configure, and then click either Update Now or Rebuild. If you click
    > Rebuild, you receive a message that states that this operation may
    take
    > some time.
    >
    > Note: If you select Rebuild to rebuild the RUS, you still have to
    click
    > Update Now again after rebuilding RUS.
    >
    > Then, please check the configuration of RUS using the following
    steps:
    >
    > 1. Click Start, point to Programs, point to Microsoft Exchange, and
    then
    > click System Manager.
    >
    > 2. Double-click Recipients, and then click Recipient Update Services.
    >
    > 3. In the right pane of the Exchange System Manager window,
    right-click
    > "Recipient Update Service (Enterprise Configuration)", and then click
    > Properties.
    >
    > 4. Verify that a valid Exchange server name appears in the "Exchange
    > server" box. If the server name does not appear, or if the one that
    > appears
    > is incorrect, click Browse. In the Select Exchange Server dialog
    box,
    > click
    > a valid Exchange server in the site, click OK, and then click OK
    again.
    >
    > 5. In the right pane of the Exchange System Manager window,
    right-click
    > "Recipient Update Service <domain>", where <domain> is the name of
    your
    > domain, and then click Properties.
    >
    > 6. Verify that a valid Exchange server name appears in the "Exchange
    > server" box. If the server name does not appear, or if the name that
    > appears is incorrect, click Browse. In the Select Exchange Server
    dialog
    > box, click a valid Exchange server in the site, click OK, and then
    click
    > OK
    > again.
    >
    > For more information about RUS, refer to the following article:
    > 253828 How the Recipient Update Service Populates Address Lists
    > http://support.microsoft.com/?id=253828
    >
    > In addition, if the issue persists, please increase the diagnostic
    > logging,
    > and produce the issue. To do so, use the following steps:
    >
    > 1. Increase diagnostic logging to Maximum on the MSExchangeAL
    service for
    > the following categories: LDAP Operations, Service Control and
    Address
    > List
    > Synchronization.
    >
    > 2. Restart the System Attendant service.
    >
    > 3. Create a new account and rebuild the Recipient Update Service.
    >
    > 3. Examine application log for indications of problems. If possible,
    sene
    > a
    > copy to my working email: v-asun@microsoft.com.
    >
    > Hope this helps! If anything is unclear or you need further help,
    just
    > post
    > back to let me know. Have a nice day!
    >
    > Thanks & Regards
    > Alan Sun
    > Microsoft Online Partner Support
    >
    > Get Secure! - www.microsoft.com/security
    > =====================================================
    > When responding to posts, please "Reply to Group" via your
    newsreader so
    > that others may learn and benefit from your issue.
    > =====================================================
    >
    > This posting is provided "AS IS" with no warranties, and confers no
    > rights.
    >
    >
    >
    > --------------------
    > Reply-To: "Harrison Midkiff" <HMidkiff@aviinc.com>
    > From: "Harrison Midkiff" <HMidkiff@aviinc.com>
    > Subject: Default e-mail addresses not being created
    > Date: Tue, 30 Nov 2004 14:37:36 -0500
    > Lines: 12
    > Organization: Audio Visual Innovations, Inc.
    > X-Priority: 3
    > X-MSMail-Priority: Normal
    > X-Newsreader: Microsoft Outlook Express 6.00.2900.2180
    > X-RFC2646: Format=Flowed; Original
    > X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
    > Message-ID: <OtjUNQx1EHA.1204@TK2MSFTNGP10.phx.gbl>
    > Newsgroups: microsoft.public.exchange2000.general
    > NNTP-Posting-Host: 65.218.176.126
    > Path:
    >
    cpmsftngxa10.phx.gbl!TK2MSFTFEED02.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP10
    > phx.gbl
    > Xref: cpmsftngxa10.phx.gbl
    microsoft.public.exchange2000.general:62078
    > X-Tomcat-NG: microsoft.public.exchange2000.general
    >
    > Hello:
    >
    > When I create a new mailbox for a user all of a sudden it is not
    > creating
    > the e-mail address on the "E-mail Addresses" tab. I am not sure
    what
    > is
    > going on. I tried removing and recreating the exchange
    attribute and
    > rebuilding the Recipient Update Server but still nothing.
    >
    > Does anyone have any ideas?
    >
    > Harrison Midkiff
    >
    >
    >
    >
         
         
         

  • Next message: Michael Turner: "Any one know how to fix this."

    Relevant Pages

    • RE: Exchange accounts not being created
      ... On first glance I would say that the Recipient Update Service (RUS) is not working. ... Since you removed what was essentially the first server in the site you will need to do a few things to get back to a working situation. ... sure the Exchange Server listed is not the server you deleted. ... Exchange accounts not being created ...
      (microsoft.public.exchange2000.admin)
    • Re: 1 Exchange 2003 server with 2 AD domains
      ... I setup a RUS for the second domain, ... I tried rebuilding the RUS. ... Server option from each server involved and re-added it after a day. ... > Exchange server to a domain controller in the 2nd domain. ...
      (microsoft.public.exchange.setup)
    • Re: Rebuilding Exchange Server
      ... hands on, bring up a new Exchange server, do all the moves, then ... decommission the old box and rebuild it, ... rebuild my Exchange server. ... you format and re-install the OS - keep the same server name ...
      (microsoft.public.exchange2000.general)
    • Re: email address not generating and name does not show up in GAL
      ... Are you sure that the recipient update service (RUS) for the domain is running? ... Check the event log of the server on which that RUS is supposed to be running. ... create a outlook profile for the user pointing to our exchange server. ...
      (microsoft.public.exchange.admin)
    • Re: RUS not working?
      ... after restarting the server everything works fine... ... >> Do you have any additonal Software installad using the RUS? ... >>> Active directory is Win2000 native mode. ... >>> I have rebuilded all the RUS Twice!!! ...
      (microsoft.public.exchange.admin)