RE: Client unable to connect to Exchange with Outlook 2003
- From: v-natliu@xxxxxxxxxxxxxxxxxxxx ("Nathan Liu [MSFT]")
- Date: Fri, 21 Oct 2005 05:11:51 GMT
Hello Neal,
Thank you for posting in the SBS newsgroup.
According to your description, I understand that the Outlook client cannot
connect to the Exchange Server on the SBS 2003 Standard Server. If I have
misunderstood the problem, please don't hesitate to let me know.
To narrow down this issue, please answer and perform the following
questions and steps:
I. For the Event Error "Event Source: MSExchangeIS, Event ID: 9646", did
you install the Exchange Server 2003 SP1?
If so, by default, Exchange Server 2003 SP1 limits the number of MAPI
sessions that a single MAPI client can open to 32. Technically, Exchange
Server 2003 SP1 imposes a restriction on the number of permitted MAPI
sessions per user. By default, the maximum number of permitted MAPI
sessions per user is set to a hexadecimal value of 0x20 after you apply
Exchange Server 2003 SP1.
Note: A hexadecimal value of 0x20 converts to a decimal value of 32.
Also, I would let you know that an Outlook.exe process only open one MAPI
session. If more than 32 MAPI sessions are accessing the mailbox of the
same user, the 9646 error will occur and report "exceeded the maximum of 32
objects of type "session"."
Similarly, by default, Exchange Server 2003 SP1 prevents an individual user
from opening 250 messages or 100 attachments.
This feature is designed to protect Exchange 2003 from being over-loaded.
As the following KB article 830836 & 830829, you can adjust the number of
permitted MAPI sessions, opening messages, etc per user in the registry.
However, I would remind you that, if you raise the MAPI session limit, try
to determine the minimum value that you can use so that the client program
can run without problems. If you raise the limit too high, the client
program can potentially affect the performance of the Exchange Server
computer.
830836 Event ID 9646 is logged when you try to send many messages in
Exchange
http://support.microsoft.com/?id=830836
830829 Your Exchange Server 2003 computer may stop responding after a MAPI
http://support.microsoft.com/?id=830829
II. For the Outlook error codes 0x8004011d and 0x80040115, please perform
the steps below to narrow down the problem.
1. This issue may be related to some types of firewalls, such as freedom
firewall or Norton Internet Security firewall. Therefore, if you have
installed any Anti-Virus programs or firewalls, please temporarily
uninstall all the firewalls and Anti-Virus programs, as this may be helpful
in resolving this problem.
2. The issue may be related to the Outlook connectivity to Microsoft
Exchange Server. Please check the RPC registry values as below.
(1) Locate the "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Exchange\Exchange
Provider" key. Check whether the order of the "Rpc_Binding_Order" entry is
"ncalrpc,ncacn_ip_tcp,ncacn_spx,ncacn_np,netbios,ncacn_vns_spp" on the
Client side and the order of the "RPC_Svr_Binding_Order" entry is
"ncacn_ip_tcp,ncacn_spx,ncacn_vns_spp" on the Exchange Server side.
(2) Locate the "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Rpc\ClientProtocols"
key. Then, verify that all entries are present and correct by referring to
the tables contained in the "ClientProtocols" section of the article KB
325930 below.
(3) Verify whether the DLL files correspond to the specific subkeys contain
the correct registry entries for TCP/IP in the "ClientProtocols" Part of
the article KB 325930. In the meantime, verify the version of the specific
DLL files.
For more information, please refer to the following Knowledge Base article.
325930 How to troubleshoot connectivity issues that are caused by RPC client
http://support.microsoft.com/?id=325930
3. Please test Outlook in the Safe Mode. The Safe Mode will disable all
add-ins or extensions that will not start, or a corrupted resource, file,
registry, or templates.
Click Start-->Run, type "Outlook /Safe" (Quotation marks are not included
and there is a space between Outlook and /safe) and press Enter.
4. Please refer to the following Microsoft Knowledge Base article to test
the issue in Windows Clean Boot Mode. Windows Clean Boot will isolate the
applications we currently use in a stand alone environment.
310353 How to Perform a Clean Boot in Windows XP
http://support.microsoft.com/?id=310353
5. Double confirm whether the other users can connect to the Exchange
server in this specific computer. In the meantime, try to log this specific
user account on another computer where Outlook runs normally, can you
connect to the Exchange Server now?
6. Please use OWA to try whether you can connect to the Exchange server in
this specific computer. To do this, please browse
http://SBSServerName/exchange/ in Internet Explorer.
I appreciate your time and cooperation. If anything is unclear, please feel
free to let me know. I am looking forward to hearing from you.
Best regards,
Nathan Liu (MSFT)
Microsoft CSS Online Newsgroup Support
Get Secure! - www.microsoft.com/security
======================================================
This newsgroup only focuses on SBS technical issues. If you have issues
regarding other Microsoft products, you'd better post in the corresponding
newsgroups so that they can be resolved in an efficient and timely manner.
You can locate the newsgroup here:
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx
When opening a new thread via the web interface, we recommend you check the
"Notify me of replies" box to receive e-mail notifications when there are
any updates in your thread. When responding to posts via your newsreader,
please "Reply to Group" so that others may learn and benefit from your
issue.
Microsoft engineers can only focus on one issue per thread. Although we
provide other information for your reference, we recommend you post
different incidents in different threads to keep the thread clean. In doing
so, it will ensure your issues are resolved in a timely manner.
For urgent issues, you may want to contact Microsoft CSS directly. Please
check http://support.microsoft.com for regional support phone numbers.
Any input or comments in this thread are highly appreciated.
======================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
>Thread-Topic: Client unable to connect to Exchange with Outlook 2003
>thread-index: AcXV2TvxlrjTt9leS1uSQFcqQHGLNA==
>X-WBNR-Posting-Host: 216.70.142.43
>From: "=?Utf-8?B?TmVhbA==?=" <Neal@xxxxxxxxxxxxxxxxxxxxxxxxx>
>Subject: Client unable to connect to Exchange with Outlook 2003
>Date: Thu, 20 Oct 2005 17:49:04 -0700
>Lines: 28
>Message-ID: <20DC009D-EB98-430C-87E9-60219A7EE2C0@xxxxxxxxxxxxx>
>MIME-Version: 1.0
>Content-Type: text/plain;
> charset="Utf-8"
>Content-Transfer-Encoding: 7bit
>X-Newsreader: Microsoft CDO for Windows 2000
>Content-Class: urn:content-classes:message
>Importance: normal
>Priority: normal
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
>Newsgroups: microsoft.public.windows.server.sbs
>NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
>Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
>Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.windows.server.sbs:163199
>X-Tomcat-NG: microsoft.public.windows.server.sbs
>
>I have one client machine in our office, connected to our network who is
no
>longer able to connect to our Exchange server on SBS 2003 Standard. Prior
to
>yesterday (Oct 19th) all was well. I have checked and determined that he
is
>able to connect (by wire) to our network, but Outlook shows "Disconnected"
as
>the status. I also checked and verified that "working offlline" was not
>checked. The only error in the server event log that mentions this user
is
>Event Type: Error
>Event Source: MSExchangeIS
>Event Category: General
>Event ID: 9646
>Date: 10/19/2005
>Time: 4:08:14 PM
>User: N/A
>Computer: LAW1
>Description:
>Mapi session "/o=NOCUFFS/ou=first administrative
>group/cn=Recipients/cn=Jeff" exceeded the maximum of 32 objects of type
>"session".
>
> For more information, click http://www.microsoft.com/contentredirect.asp.
>
>In Outlook there are two error codes 0x8004011d and 0x80040115. Lookinig
>them up did not bring me closer to a solution. Can you please advise.
>
>Thanks in Advance.
>
>Neal
>
>
.
- Prev by Date: RE: updated to SBS 2003 SP1 and lost monitoring functionality
- Next by Date: Re: SBS and Remote Access Failures
- Previous by thread: RE: updated to SBS 2003 SP1 and lost monitoring functionality
- Next by thread: RE: Intranet/subweb access through RWW
- Index(es):
Relevant Pages
|
