Outlook 2003 - Getting error that Exchange Server is unavailable - Works fine through Webmail
I am using Outlook 2003, with Exchange 2003 (Windows SBS 2003), I have one user that cannot use Exchange with Outlook. Whenever I setup his Exchange profile in any Outlook 2003 client I get the following message - "Unable to open your default e-mail folders. The Microsoft Exchange Server computer is not available. Either there are network problems or the Microsoft Exchange Server computer is down for maintenance."
I can setup other users on the same computer that I am having problems on without any problems. I tried setting the problem user account up on another computer and am getting the same error. I can use the Outlook WebAccess without any problems, logged in with the problem user account. I can ping the exchange server by name or IP, I can access shared folders off of the Exchange server without any problem as well. I have performed a repair on Office, I have completely removed and reinstalled Office, I have removed all Outlook profiles and recreated them. I am not using roaming profiles. I am not experiencing any other problems with this users account. I can even setup a different users email box while logged in as the problem user and after authenticating with Exchange as the different user it works fine. I would assume a problem with the Exchange mailbox, corrupt mailbox or something, but it can be accessed via Webmail without any problems.
I can setup other users on the same computer that I am having problems on without any problems. I tried setting the problem user account up on another computer and am getting the same error. I can use the Outlook WebAccess without any problems, logged in with the problem user account. I can ping the exchange server by name or IP, I can access shared folders off of the Exchange server without any problem as well. I have performed a repair on Office, I have completely removed and reinstalled Office, I have removed all Outlook profiles and recreated them. I am not using roaming profiles. I am not experiencing any other problems with this users account. I can even setup a different users email box while logged in as the problem user and after authenticating with Exchange as the different user it works fine. I would assume a problem with the Exchange mailbox, corrupt mailbox or something, but it can be accessed via Webmail without any problems.
ASKER
Have deleted all pst and ost files and did not work. I logged in as administrator of domain and setup the problem email account and got the same error. However if I use the administrators email account it works fine. Thanks.
did you create another user account on the workstation?
ASKER
I'm not using local profiles, I am using domain accounts, so no, I did not create an all new profile on the workstation, however, I did log in as a different user, thus creating a different profile. Under that profile I tried to open the suspect email and got the same error. I got no errors when I opened a different users email box.
Perhaps the particular users active directory account properties would not be set up for pop3, disabled or even corrupt. Did you check that?
ASKER
Not using pop3, using exchange profiles. If the account was disabled, then I couldn't log in as the user and if it was a corrupt active directory account I shouldn't be able to log in and the webmail shouldn't work, I would assume.
Oops sorry. In AD the user account can be disabled and apart from that under the exchange features tab - there are three options 1. OWA, 2.POP3, 3.IMAP4 - all of these can be enabled or disabled. I am sorry for not being precise earlier but please check the IMAP4 option and see if it is enabled or disabled.
ASKER
Everything is enabled in the Exchange features tab, including the IMAP4.
Whenever I setup his Exchange profile in any Outlook 2003 client I get the following message - "Unable to open your default e-mail folders.
In the above, did you check whether the default path is correctly set?
In the above, did you check whether the default path is correctly set?
ASKER
The problem is with not connecting to Exchange, not any default path. It only tries to bring up the default path when it has problems connecting to Exchange. However, in this instance I can ping the exchange server and everything.
Ok. You can ping means that there is connectivity.
Can you see the Exchange server in the Network Neighbourhood or My Network Places? Also since any other user works on the same pc and since this users email cannot be set up on any other pc, It rules out connectivity problems.
If there were issues like firewall blocking the Outlook access to the server, then other users wont also be able to gain access so it's not that.
Two things come to mind.
1. Purge the users Mailbox. After taking back ups of course. Once a new email comes the mailbox will get created. Then try.
2. Remove the user from AD along with the email box and recreate the user. Same as before backups need to be taken. This is if the above does not work.
HTH
Can you see the Exchange server in the Network Neighbourhood or My Network Places? Also since any other user works on the same pc and since this users email cannot be set up on any other pc, It rules out connectivity problems.
If there were issues like firewall blocking the Outlook access to the server, then other users wont also be able to gain access so it's not that.
Two things come to mind.
1. Purge the users Mailbox. After taking back ups of course. Once a new email comes the mailbox will get created. Then try.
2. Remove the user from AD along with the email box and recreate the user. Same as before backups need to be taken. This is if the above does not work.
HTH
ASKER
I found the fix. I had to create a registry entry for maximum allowed sessions in the properties of the MSExchangeIS service and up the default value. All is working now. I am closing this question with no points to anyone. Thanks.
Glad you got it fixed.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
if that doesn't work, then
how about create another user on the workstation, and new outlook profile.. configure with the suspect mailbox.. does it work?