Exchange 2003 Users cannot connect to mail box

[CAPPBC]

Good morning, I have exhausted all options before submitting this post.

Exchange 2003 with SBS 2003.

History:
Sharepoint needed to be reinstalled. After reinstall, IIS gave trouble. Reinstalled IIS and Sharepoint. Sharepoint is working.

Now, MS Exchange routing engine cannot find file to start service. I had to reinstall IIS then MS Exchange. Routing engine service starts now. When I create users, a mailbox is created but when setting up Outlook, the name could not be resolved issue. Mailboxes are listed in ESM. My old accounts that were created before the issue can connect to Exchange fine but newly created users have trouble.

I have come a long way but now I am stumped. All Google searches relate back to the same steps in which I tried. Maybe someone can shed the light.

 

[TechyMcSe2k]

What is in your event logs on both server and pc (where you are trying to setup Outlook)

________________________________________
Achieving a perception of high intelligence level can only be limited by your manipulation skills of the Google algorithm!

 

[CAPPBC]

On the users desktop log, nothing is generated when I encounter the error. On the server, nothing is encountered also. The MSExcahgneAL (Recipient Update) is set to always run and shows up about every 2 seconds. I have no errors pertaining to exchange.

This is mind boggling. MS is something else!

 

[CAPPBC]

Here is an update:

I am trying to pin point this issue. RUS is not updating the x.400 addresses. I have to create an SMTP address, send an email to it, then it will create the account. Aftre creation, I manually updata RUS and not x.400 address is created. In my event logs, RUS completes fine. There is a missing component. The setup is not complex either. SBS 2003 with Exchange 2003. Both are up to SP2.

As I read more and more posts, SBS is a headache and POS!

 

[TechyMcSe2k]

make sure the accounts are being created on the server within ADUC that ALSO has the ESM installed.


May need to rebuild their mailbox from scratch:
Right-click the User in ADUC and choose "Exchange Tasks". If you have the option to delete the mailbox, then the mailbox has been created. If you don't have that option, choose to create the mailbox. If you do have the option to delete the mailbox...suggest doing so. Then, in ESM, go to your mailbox store > mailboxes...run the mailbox cleanup agent. If the user has a mailbox there, it should have a red x. Right-click it and choose to "purge". Then go back to the user in ADUC, run Exchange Tasks again and create a new mailbox.

From:

http://www.experts-exchange.com/Software/Server_Software/Email_Servers/Exchange/Q_24021067.html

________________________________________
Achieving a perception of high intelligence level can only be limited by your manipulation skills of the Google algorithm!

 

[CAPPBC]

I have deleted the mailbox, recreated the mailbox and still nothing. I have deleted the user created the user and still no go. I figure it has to be a permissions issue somewhere. The UC is set to inherit settings from parent.
Thanks for the reply. Keep them coming so I can get you to think more. I have been running SBS Best Practices, Exchange Best Practices, and trouble shooting agent and none have helped me out.

I am still looking.

 

[58sniper]

As I read more and more posts, SBS is a headache and POS!

No need for that here.

The RUS isn't working correctly. That's been discussed here before. Go into the Recipient Update Services, right click the one for the domain and choose update. Wait for a few minutes and see if your new users have the correct addresses. If not, go back to the RUS and right click>Rebuild.

Pat Richard MVP
Plan for performance, and capacity takes care of itself. Plan for capacity, and suffer poor performance.

http://www.ucblogs.net/blogs/exchange/

 

[CAPPBC]

I have done that too. Update, Rebuild....Still no luck. Best Practices and Analyzer states everything is ok. No critical issues reported. Trust me when I say I tried everything. Someone out there must have had the same issue. I am rerunning Best Practices analyzer which takes about two hours to complete. All the rest of scans checked out fine.

To further help explain my situation. On my own pc, I can connect to my mailbox along with others. With the ones I newly created, I cannot connect to them. When I say test the connectivity, I do this by creating a new outlook profile and try adding an exchange server mailbox.

I will let you know if I come up with anything.

 

[58sniper]

I am rerunning Best Practices analyzer which takes about two hours to complete.

Doubt you're going to find anything in the BPA results that's going to help.

If the accounts don't get an address automatically, the problem is with RUS. Period.

Pat Richard MVP
Plan for performance, and capacity takes care of itself. Plan for capacity, and suffer poor performance.

http://www.ucblogs.net/blogs/exchange/

 

[CAPPBC]

Sounds good. Now, I need to know what settings are most likely corrupted.

Default Policy has the correct SMTP/x.400 address. The filter rules uses (mailnickname=*). I cannot edit this.

RUS
Both are set to Always run(testing purposes, once resloved, will change to 5AM). The domain, exchange server, DC are all correct.

Any thoughts?

 

[CAPPBC]

Update:

MS Exchange Best Practices Analyzer shows that the RUS appears to be stalled. RUS(Enterprise Config) has not run. It states a manual restart of the MS SA service to be restarted. I restarted the service before when reading from other posts but no luck. I will try again and let you know what happens.

Thanks,

 

[CAPPBC]

No luck. I ran eseutil and isinteg. isinteg found 7 errors and fixed them but the main issue stands. I can create a new user and access mailbox via OWA but cannot connect with an Outlook profile. I recall reading about this on the web but cannot find it back.

Any direction?

 

[TechyMcSe2k]

can that computer resolve the exchange server name where the users mailbox is located? if not, try using the IP just for testing

________________________________________
Achieving a perception of high intelligence level can only be limited by your manipulation skills of the Google algorithm!

 

[CAPPBC]

Yes it can. Enter the ip, it resolves and enters server/domain name. This is user specific/mailbox specific. I found the post where it states that RUS did not stamp the address.

http://itknowledgeexchange.techtarg...onnect-to-exchange-server-but-owa-works-fine/

I used ADSI to look at my working profile and it does not have anything listed in the msexchangequery field so this is irrelevant. I did notice that these attributes did not have values:

msExchALObjecVersion
msExchMasterAccountSid

From this, I can see that the SID needs to be in place to link the account the mailbox to the username. I will do this and let you know.

 

[CAPPBC]

The SID values are different from the main account and exchange value. Sorted the list by values and the sids are different. This is giving me the biggest headache in the world.

 

[58sniper]

RUS is broken. Call PSS.

Pat Richard MVP
Plan for performance, and capacity takes care of itself. Plan for capacity, and suffer poor performance.

http://www.ucblogs.net/blogs/exchange/

 

[CAPPBC]

How much for support? Issue is we are a non-profit agency and money is slim.

Thanks!

 

[58sniper]

Call them and ask them. I can't tell you how much they'll charge you.

Pat Richard MVP
Plan for performance, and capacity takes care of itself. Plan for capacity, and suffer poor performance.

http://www.ucblogs.net/blogs/exchange/

 

[CAPPBC]

Have you contacted them before? Did they resolve your issue?

 

[58sniper]

Yes. Yes.

Pat Richard MVP
Plan for performance, and capacity takes care of itself. Plan for capacity, and suffer poor performance.

http://www.ucblogs.net/blogs/exchange/