Exchange internal emails not received

Have you checked the Message Tracking Center to see if the emails went through or at what point they fail?

http://www.amset.info/exchange/message-tracking.asp
http://www.msexchange.org/tutorials/The_Exchange_Message_Tracking_Center_or_How_to_Save_Your_A_in_a_Pinch.html

OK I enabled msg tracking and sent an email from tkitson to temail .. I reoppened System manager and went to tools - message tracking center - selected the AD sender ID and hit find .. received an error occurred a call to windows management instrumentation ID no: 80041010 Exchange system manager

I went out to the actual log file and opened it but obviously I am not experienced enough to read it propperly

# Message Tracking Log File
# Exchange System Attendant Version 6.5.7638.1
# Date      Time      client-ip      Client-hostname      Partner-Name      Server-hostname      server-IP      Recipient-Address      Event-ID      MSGID      Priority      Recipient-Report-Status      total-bytes      Number-Recipients      Origination-Time      Encryption      service-Version      Linked-MSGID      Message-Subject      Sender-Address


2007-9-29      21:41:52 GMT      -      -      -      SELHSEXCHANGE      -      /O=SOUTHEAST LANCASTER HEALTH SERVICES/OU=FIRST ADMINISTRATIVE GROUP/CN=RECIPIENTS/CN=Temail      1027      07C0966D1781804FA0A2AD71000694BB096CD6@selhsexchange.selhs.org      0      0      419      1      2007-9-29 21:41:52 GMT      0      -      c=US;a= ;p=SouthEast Lancas;l=SELHSEXCHANGE-070929214152Z-3      -      EX:/O=SOUTHEAST LANCASTER HEALTH SERVICES/OU=FIRST ADMINISTRATIVE GROUP/CN=RECIPIENTS/CN=TKITSON      -

2007-9-29      21:41:52 GMT      -      -      -      SELHSEXCHANGE      -      /O=SOUTHEAST LANCASTER HEALTH SERVICES/OU=FIRST ADMINISTRATIVE GROUP/CN=RECIPIENTS/CN=Temail      1029      07C0966D1781804FA0A2AD71000694BB096CD6@selhsexchange.selhs.org      0      0      419      1      2007-9-29 21:41:52 GMT      0      -      c=US;a= ;p=SouthEast Lancas;l=SELHSEXCHANGE-070929214152Z-3      -      EX:/O=SOUTHEAST LANCASTER HEALTH SERVICES/OU=FIRST ADMINISTRATIVE GROUP/CN=RECIPIENTS/CN=TKITSON      -

2007-9-29      21:41:55 GMT      -      -      -      SELHSEXCHANGE      -      /O=SOUTHEAST LANCASTER HEALTH SERVICES/OU=FIRST ADMINISTRATIVE GROUP/CN=RECIPIENTS/CN=TKITSON      1027      07C0966D1781804FA0A2AD71000694BB096677@selhsexchange.selhs.org      0      0      1317      1      2007-9-29 21:41:55 GMT      0      -      c=US;a= ;p=SouthEast Lancas;l=SELHSEXCHANG070929174155AC002C00      -      -      -

2007-9-29      21:41:56 GMT      -      -      -      SELHSEXCHANGE      -      /O=SOUTHEAST LANCASTER HEALTH SERVICES/OU=FIRST ADMINISTRATIVE GROUP/CN=RECIPIENTS/CN=TKITSON      1029      07C0966D1781804FA0A2AD71000694BB096677@selhsexchange.selhs.org      0      0      1317      1      2007-9-29 21:41:55 GMT      0      -      c=US;a= ;p=SouthEast Lancas;l=SELHSEXCHANG070929174155AC002C00      -      -      -

Message tracking logs are not designed to be read by someone - they are for the message tracking centre to read and process. There are also some third party tools that can read them.

The only fix I know of for the WMI error you have is to reinstall Exchange on top of the existing installation (choosing reinstall from add/remove programs). Then reinstalling the service pack. The error usually means some WMI elements haven't been registered, but can mean something else hasn't been done correctly elsewhere.

Simon.

I just ran the WMIDiag.vbs from microsoft and it shows errors in WMI .. ran the WMI repair and still WMIdiag shows errors .. Looks like the windows pop3 service is causing the error .. going to remove the pop3 windows component then reinstall exchange and service packs .. WIll reply with results

OK after manually editing in the WMI console all WMI issues resolved .. Microsofts WMIdiag.vbs gives it a clean bill of health .. pop removed from windows components .. reinstalled Exchange .. looks like the only issue I have is getting the Information correct for X400 .. This server was built by the former tech but left in disaray and never completed. Reinstalling does not change settings back to default and I highly doubt he got the information correct for Recipient policies - default policy. I've cleaned up everything I could find wrong .. I still get the msg ID no: 80041010 in msg tracking .. OWA clients still send msg but recipient OWA client does not receive. Both OWA clients can post in public folders and see/reply to others post.

I have the following in the Recipient policy - default policy:

O: Company Name
OU: FIRST ADMINISTRATIVE GROUP
pmdn: ourdomain.org
amdm: ourdomain.org

Top level in System manager Shows "Company name (Exchange)"

For Organization should it just be Exchange rather then the company name?
Organizational Unit or pmdn required with this being the only exchange server?
Could I get away with using the exchange server name rather then the domain name in amdn?

I made this server a secondary DC as well as a secondary DNS since he had no redundancy in case of failure. I'd rather not have but the company does not have the funds to afford another server to setup for these rolls.

any help is appreciated.

Thanks

The name of the Exchange org has no effect on delivery of email.  
Exchange always has an Admin Group and Routing Group. However you can change the configuration of ESM so that they aren't displayed.

When you made the server a domain controller, was Exchange already installed? If not then you have probably broken Exchange. Changing the role of the server after Exchange is installed is not supported.

Simon.

--
If your question has been answered, pleased remember to accept the answer and close the question.

This problem was "prior" to me adding the BDC and DNS roles to the server and I cannot say what the previous technician had done. I have since reinstalled exchange in case of any possible issue with it with no luck. I'd be happy to completely uninstall exchange and start from scratch but I have 2 concerns ... 1) Will completely uninstalling exchange remove all the settings or is there registry keys that should be removed as well? .. 2) Looking at the mailboxes it created, system attendant and system mail are not removable, yet the one time I considered removing exchange it had told me I must move those stores before I could remove exchange .. I didn't want to go moving those stores without advice ... suggestions?