Exchange 2003 - Outlook Web Access works. Outlook 2003 clients cannot connect. Background: unscheduled power outage caused all our servers to shut down. They all re-started OK with the exception of our old exchange server. The old exchange server works well except that any attempt to connect via Outlook 2003 results in an 0x8004011D error. This is normally caused because the store is dismounted but our stores are mounted OK and are accessible through OWA. It is just Outlook clients that cannot connect. No outlook 2003 client can connect to the old server. Despite this suggesting a server-related problem we tried re-installing the client and re-creating a client profile - no solution. Users mailboxes are accessible once moved to the new server. Connecting to the same mailboxes through outlook web access and the same login credentials works OK. If I dismount the first storage group on old server OWA then fails with HTTP/1.1 503 Service Unavailable. Re-mount the storage group and access via OWA resumes We have moved most of the affected users to our new Exchange server ( just using the move mailboxwizard then editing their mail profile ) and they are now working happily. I am keen to find out what the problem is in case our remaining server suffers the same problem. The server runs sophos puremessage anti-spam and mcafee antivirus. Both were turned off ( services set to disabled ) and the server rebooted. The problem persists. Both mailbox store and public store have no errors according to eseutil /mh ping reports the server DNS names we expect, as does nbtstat -n for the NETBIOS names. All machines are on the same private subnet. We have googled this for days without resolution. Any suggestions?

I am experiencing the same problem too and I have been googling for two days now.we just recently switch over to exchange 2007 from 2003 and is using outlook 2003 for our client PCs. there one PC that keep getting this error message every morning when she first boot up her PC.Task "Microsoft Exchange Server" reported error (0x8004011D): "The server is not available. Contact your administrator if this condition persists."Outlook is disconnected and I try to work offline close outlook then reopen outlook and connect again failI tried OWA and it works fine. just that her outlook is not connecting, but the weird thing is after some time has passed outlook is connected again. Outlook fix itself automatically and this happen every time she reboot. help??

Hello, Update your outlook (SPs and hotfixes.) http://support.microsoft.com/kb/870924/ and try to press F9 to synchronize when you offline http://support.microsoft.com/kb/289971

The reason that you are experiencing this problem is due to the fact that Exchange 2007 and Exchange 2003 SP1 onwards have a setting allowing only 32 sessions to be made by an account to it for performance reasons. If you look at your application log you will see Error 9646 message telling you that the session limit has been reached. This problem normally comes up with VPN users and sometimes the firewall keeps sessions 'open' on behalf of the client. If you look at system manager in Exchange and on the Information store on which the mailbox is hosted you will see 32 connections by that user. You will need to clear these connections before outlook can work again. 1)you can restart the information store, which is not always possible 2) Find TCPView from the microsoft site, and use that to kill the sessions held by that user. You will need to know the IP addresses that the user was using. 3) Search MSKB for 9646 errors and you can modify the IS so that more than 32 sessions can be made. But don't use this as a solution because it is bad. The reason this problem occurs is an underlying network issue which causes sessions to be terminated abnormally. Hope this helps - that's what solved my problem in my case, the user (who was connecting thru a VPN) had a dodgy wireless connection which kept on dropping causing her to reconnect which meant she would increasing use up all the 'sessions' until she reached it, and then it stopped working unless it was thru OWA! This is definitely the cause of your problem!

Okay, just throwing out some facts. server: exchange 2003 enterprise. cluster envirment. client: mix mode, Outlook 2003 and Outlook 2007 w/sp1 user max out at session 32, symtoms: exchange server disconnected. action applie to try to fix: on outlook re-do profile. server name and typed in user and click check name doesn't resolved so this action did't work have user use OWA = works so here comes the question. If the theory of outlook client reached session # 32 and they won't be able to have the 33 session. how come OWA works where as using Outlook client 2007 didn't? and this lead to another question? Is OWA has it's own 32 available session on top of Outlook client? johnli123abc@hotmail.com

Because the process under which the users log on via OWA uses the security context of the Exchange system account or something.If you look at system manager, you will see the user accessing the mailbox via 'HTTP' ... Something to that effect.

Hi,A few years late with another post but.......I had the same issue as this since the last 2 days...Had to repair an SBS2003 server, after a crash, and since, OWA works fine for all users, but nobody could connect using Outlook client, all getting same error as OP.The fix was this:http://support.microsoft.com/?id=325930(How to troubleshoot connectivity issues that are caused by RPC client protocol registry entries )Somehow, on the exchange server, the RPC entries in the registry got removed. Once I added the 4 entries in the exchange server's registry,as listed on the support page under ClientProtocols,and rebooted, everything worked!!Hope this can help anyone else with the same issue, as I found it very difficult to diagnose this problem, was always being referred to the "32 MAPI" requests problem..

hi, Install windows 2003 support Tool on the server and run rpcdump /i > rpcdump.txt Check if all the services for exchange are registered correctly. If any service is missing then restart thoser services and check again . secondly, Run portqryUI.exe from the client and check the connectivity for port 135 . RPC registry mentioned by deepspeed is the first thing to check.!!!

I am marking this as the answer to our issue because it led me to our solution. This article helped too: http://www.techrepublic.com/forum/discussions/102-249934 We are running Exchange 2010 and Outlook 2010. We had a single user experiencing this issue with the 32 session limit being met. OWA still worked. Connecting to the users mailbox why logged in as me worked, but anytime you connected to the user's mailbox while logged onto any machine under that users credentials didn't work. Any machine is a key detail. After questioning the individual about where they were we discovered they were at one of our branch locations and they were connecting to a HUB that was setup in a meeting room. I asked the user if they were getting Outlook disconnected messages and they said they were repeatedly so they would then connect to our wireless that was available, but then later they would reconnect through the HUB and they did this multiple times because they kept losing outlook connectivity. These multiple disconnected connections through the HUB tells me that this is where the TCP sessions were getting setup and dropped for some reason and each time the user was getting a new IP address. I believe the HUB is faulty and it is being removed from the network. (We shouldn't have a stupid hub out there anyway. It was someone's idea of getting more connections in a meeting room) When I run a Get-LogonStatistics for the user you can see the connections and when they were established and to what mailbox server. We are going restart the mailstore tonight. Another user complained of the same issue but said it went away on its own after a couple reboots. This user was also on the same team and was locked in the meeting room with the HUB. I don't believe the reboots fixed this individual. I think it was because we did a switchover on that MailStore for some maintenance and it happened to be at that exact time he experienced his issue.