Prev: OAB path change
Next: Event ID 10016
From: Suresh M V on 1 Apr 2008 06:08
I am using exchange 2003.I am getting an error in the even log for one user
"exceed a maximum of 32 objects type of session". The client side i am using
microsoft outlook 2002 (office XP).
can any one help???
From: Rene Frenger on 1 Apr 2008 06:23
Mapi connections are not reset by the Exchange server:

Typical things you see:
- Outlook is unable to connect to server.
- Outlook connections dropped.

Things you have to do are:
- Update networkdrivers to latest version.
- Disable TCP Chimney offload (throught registry settings).
- Implement some MSExchangeIS registry settings.
- Release TCP/IP connections faster.

Symptoms:
Clients connected through VPN. Every time the session is interrupted and
they reconnect three new sessions are opened.
Also three days old sessions are available on the server. I.e. a user that
logged off three days ago can still have an active session.

On a server that is running Microsoft Exchange Server 2003, an event that
resembles the following event is logged in the Application log:

Event Type: Error
Event Source: MSExchangeIS
Event Category: General
Event ID: 9646
Description:
Closing Mapi session "/o=Organization/ou=Administrative
Group/cn=Recipients/cn=Recipient" because it exceeded the maximum of 32
objects of type "session".

When this issue occurs, you may also receive the following error message in
Microsoft Office Outlook 2003:
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 is down for maintenance.

Scope: This issue will be considered resolved when the sessions are reset
faster.

Solutions:
Caused by Desktop search engines:
http://support.microsoft.com/?id=905184
This problem occurs if the Outlook client computer or the other MAPI client
computer is running a desktop search engine (Google desktop search) that
integrates with Outlook to index the user's mailbox or public folder data
that resides on the Exchange server.

TCP Chimney offload:
After installing Windows 2003 SP2, we no longer see TCPIP keepalives package
on
network connections. For Exchange, administrators will see old, orphaned
connections, especially from users who connect via WiFi, VPN, etc. The
connection
counts will grow until users reach a maximum number of connections, causing
various
connection-related errors in Outlook.

This is because the TCP chimney function is enabled by default in Windows
2003
SP2. TCP Chimney offload enables TCP/IP processing to be offloaded to network
adapters that can handle the TCP/IP processing in hardware. If the Network
Card did
not handle the TCP Keep Alive packet correctly, the orphaned connections
cannot be
cleaned up. If you disable TCP Chimney, then the Operating System will
handle the TCP/IP protocol and reset the connections.

Disable TCP Chimney through the registry:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
The global registry entries are as follows:
• EnableTCPChimney
Type: REG_DWORD
Values: 1 (enabled) 0 (disabled))
• EnableRSS
Type: REG_DWORD
Values: 1 (enabled) 0 (disabled))
• EnableTCPA
Type: REG_DWORD
Values: 1 (enabled) 0 (disabled))

Set all these to 0.

Restart the server after done this setting.

See for backgroup information these articles:
http://msexchangeteam.com/archive/2007/07/18/446400.aspx
http://support.microsoft.com/?kbid=912222

Registry settings you can do to tweak MSExchangeIS:
http://support.microsoft.com/kb/830829
http://support.microsoft.com/kb/842022
Implement these registry settings:
"HKLM\SYSTEM\CurrentControlSet\Services\MSExchangeIS\ParametersSystem\MaxObjsPerMapiSession\session" a decimal value of 350

"HKLM\SYSTEM\CurrentControlSet\Services\MSExchangeIS\ParametersSystem\Maximum
Allowed Sessions Per User" a decimal value of 250

TCP registry settings:
Implement the following registry key which will cause Exchange to clean up
the connections sooner:
"HKLM\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\KeepAliveTime"
Setting the value to anything between 1 and 7,200,000 milliseconds.
Recommended value is 600,000 (10 mins)
Default time for Exchange is 7,200,000 (2 hours)


--
Regards,

Rene Frenger
MCITP E2K7
MCP EX5.5, 2000, 2003
MCSE


"Suresh M V" wrote:

> I am using exchange 2003.I am getting an error in the even log for one user
> "exceed a maximum of 32 objects type of session". The client side i am using
> microsoft outlook 2002 (office XP).
> can any one help???
From: Cary Shultz on 1 Apr 2008 06:59
Rene,

Just something you threw together, huh?

Excellent answer....exactly what I was going to write (riiiighhhttttt!).

Cary


"Rene Frenger" <ReneFrenger(a)discussions.microsoft.com> wrote in message
news:6652EF3D-3C3E-4458-97C0-6C78E9B53559(a)microsoft.com...
> Mapi connections are not reset by the Exchange server:
>
> Typical things you see:
> - Outlook is unable to connect to server.
> - Outlook connections dropped.
>
> Things you have to do are:
> - Update networkdrivers to latest version.
> - Disable TCP Chimney offload (throught registry settings).
> - Implement some MSExchangeIS registry settings.
> - Release TCP/IP connections faster.
>
> Symptoms:
> Clients connected through VPN. Every time the session is interrupted and
> they reconnect three new sessions are opened.
> Also three days old sessions are available on the server. I.e. a user that
> logged off three days ago can still have an active session.
>
> On a server that is running Microsoft Exchange Server 2003, an event that
> resembles the following event is logged in the Application log:
>
> Event Type: Error
> Event Source: MSExchangeIS
> Event Category: General
> Event ID: 9646
> Description:
> Closing Mapi session "/o=Organization/ou=Administrative
> Group/cn=Recipients/cn=Recipient" because it exceeded the maximum of 32
> objects of type "session".
>
> When this issue occurs, you may also receive the following error message
> in
> Microsoft Office Outlook 2003:
> 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 is down for maintenance.
>
> Scope: This issue will be considered resolved when the sessions are reset
> faster.
>
> Solutions:
> Caused by Desktop search engines:
> http://support.microsoft.com/?id=905184
> This problem occurs if the Outlook client computer or the other MAPI
> client
> computer is running a desktop search engine (Google desktop search) that
> integrates with Outlook to index the user's mailbox or public folder data
> that resides on the Exchange server.
>
> TCP Chimney offload:
> After installing Windows 2003 SP2, we no longer see TCPIP keepalives
> package
> on
> network connections. For Exchange, administrators will see old, orphaned
> connections, especially from users who connect via WiFi, VPN, etc. The
> connection
> counts will grow until users reach a maximum number of connections,
> causing
> various
> connection-related errors in Outlook.
>
> This is because the TCP chimney function is enabled by default in Windows
> 2003
> SP2. TCP Chimney offload enables TCP/IP processing to be offloaded to
> network
> adapters that can handle the TCP/IP processing in hardware. If the Network
> Card did
> not handle the TCP Keep Alive packet correctly, the orphaned connections
> cannot be
> cleaned up. If you disable TCP Chimney, then the Operating System will
> handle the TCP/IP protocol and reset the connections.
>
> Disable TCP Chimney through the registry:
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
> The global registry entries are as follows:
> . EnableTCPChimney
> Type: REG_DWORD
> Values: 1 (enabled) 0 (disabled))
> . EnableRSS
> Type: REG_DWORD
> Values: 1 (enabled) 0 (disabled))
> . EnableTCPA
> Type: REG_DWORD
> Values: 1 (enabled) 0 (disabled))
>
> Set all these to 0.
>
> Restart the server after done this setting.
>
> See for backgroup information these articles:
> http://msexchangeteam.com/archive/2007/07/18/446400.aspx
> http://support.microsoft.com/?kbid=912222
>
> Registry settings you can do to tweak MSExchangeIS:
> http://support.microsoft.com/kb/830829
> http://support.microsoft.com/kb/842022
> Implement these registry settings:
> "HKLM\SYSTEM\CurrentControlSet\Services\MSExchangeIS\ParametersSystem\MaxObjsPerMapiSession\session"
> a decimal value of 350
>
> "HKLM\SYSTEM\CurrentControlSet\Services\MSExchangeIS\ParametersSystem\Maximum
> Allowed Sessions Per User" a decimal value of 250
>
> TCP registry settings:
> Implement the following registry key which will cause Exchange to clean up
> the connections sooner:
> "HKLM\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\KeepAliveTime"
> Setting the value to anything between 1 and 7,200,000 milliseconds.
> Recommended value is 600,000 (10 mins)
> Default time for Exchange is 7,200,000 (2 hours)
>
>
> --
> Regards,
>
> Rene Frenger
> MCITP E2K7
> MCP EX5.5, 2000, 2003
> MCSE
>
>
> "Suresh M V" wrote:
>
>> I am using exchange 2003.I am getting an error in the even log for one
>> user
>> "exceed a maximum of 32 objects type of session". The client side i am
>> using
>> microsoft outlook 2002 (office XP).
>> can any one help???


From: Rene Frenger on 1 Apr 2008 07:37
Ehhh, just a copy and paste from something I 'm keeping in my archive.

--
Regards,

Rene Frenger
MCITP E2K7
MCP EX5.5, 2000, 2003
MCSE


"Cary Shultz" wrote:

> Rene,
>
> Just something you threw together, huh?
>
> Excellent answer....exactly what I was going to write (riiiighhhttttt!).
>
> Cary
>
>
> "Rene Frenger" <ReneFrenger(a)discussions.microsoft.com> wrote in message
> news:6652EF3D-3C3E-4458-97C0-6C78E9B53559(a)microsoft.com...
> > Mapi connections are not reset by the Exchange server:
> >
> > Typical things you see:
> > - Outlook is unable to connect to server.
> > - Outlook connections dropped.
> >
> > Things you have to do are:
> > - Update networkdrivers to latest version.
> > - Disable TCP Chimney offload (throught registry settings).
> > - Implement some MSExchangeIS registry settings.
> > - Release TCP/IP connections faster.
> >
> > Symptoms:
> > Clients connected through VPN. Every time the session is interrupted and
> > they reconnect three new sessions are opened.
> > Also three days old sessions are available on the server. I.e. a user that
> > logged off three days ago can still have an active session.
> >
> > On a server that is running Microsoft Exchange Server 2003, an event that
> > resembles the following event is logged in the Application log:
> >
> > Event Type: Error
> > Event Source: MSExchangeIS
> > Event Category: General
> > Event ID: 9646
> > Description:
> > Closing Mapi session "/o=Organization/ou=Administrative
> > Group/cn=Recipients/cn=Recipient" because it exceeded the maximum of 32
> > objects of type "session".
> >
> > When this issue occurs, you may also receive the following error message
> > in
> > Microsoft Office Outlook 2003:
> > 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 is down for maintenance.
> >
> > Scope: This issue will be considered resolved when the sessions are reset
> > faster.
> >
> > Solutions:
> > Caused by Desktop search engines:
> > http://support.microsoft.com/?id=905184
> > This problem occurs if the Outlook client computer or the other MAPI
> > client
> > computer is running a desktop search engine (Google desktop search) that
> > integrates with Outlook to index the user's mailbox or public folder data
> > that resides on the Exchange server.
> >
> > TCP Chimney offload:
> > After installing Windows 2003 SP2, we no longer see TCPIP keepalives
> > package
> > on
> > network connections. For Exchange, administrators will see old, orphaned
> > connections, especially from users who connect via WiFi, VPN, etc. The
> > connection
> > counts will grow until users reach a maximum number of connections,
> > causing
> > various
> > connection-related errors in Outlook.
> >
> > This is because the TCP chimney function is enabled by default in Windows
> > 2003
> > SP2. TCP Chimney offload enables TCP/IP processing to be offloaded to
> > network
> > adapters that can handle the TCP/IP processing in hardware. If the Network
> > Card did
> > not handle the TCP Keep Alive packet correctly, the orphaned connections
> > cannot be
> > cleaned up. If you disable TCP Chimney, then the Operating System will
> > handle the TCP/IP protocol and reset the connections.
> >
> > Disable TCP Chimney through the registry:
> > HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
> > The global registry entries are as follows:
> > . EnableTCPChimney
> > Type: REG_DWORD
> > Values: 1 (enabled) 0 (disabled))
> > . EnableRSS
> > Type: REG_DWORD
> > Values: 1 (enabled) 0 (disabled))
> > . EnableTCPA
> > Type: REG_DWORD
> > Values: 1 (enabled) 0 (disabled))
> >
> > Set all these to 0.
> >
> > Restart the server after done this setting.
> >
> > See for backgroup information these articles:
> > http://msexchangeteam.com/archive/2007/07/18/446400.aspx
> > http://support.microsoft.com/?kbid=912222
> >
> > Registry settings you can do to tweak MSExchangeIS:
> > http://support.microsoft.com/kb/830829
> > http://support.microsoft.com/kb/842022
> > Implement these registry settings:
> > "HKLM\SYSTEM\CurrentControlSet\Services\MSExchangeIS\ParametersSystem\MaxObjsPerMapiSession\session"
> > a decimal value of 350
> >
> > "HKLM\SYSTEM\CurrentControlSet\Services\MSExchangeIS\ParametersSystem\Maximum
> > Allowed Sessions Per User" a decimal value of 250
> >
> > TCP registry settings:
> > Implement the following registry key which will cause Exchange to clean up
> > the connections sooner:
> > "HKLM\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\KeepAliveTime"
> > Setting the value to anything between 1 and 7,200,000 milliseconds.
> > Recommended value is 600,000 (10 mins)
> > Default time for Exchange is 7,200,000 (2 hours)
> >
> >
> > --
> > Regards,
> >
> > Rene Frenger
> > MCITP E2K7
> > MCP EX5.5, 2000, 2003
> > MCSE
> >
> >
> > "Suresh M V" wrote:
> >
> >> I am using exchange 2003.I am getting an error in the even log for one
> >> user
> >> "exceed a maximum of 32 objects type of session". The client side i am
> >> using
> >> microsoft outlook 2002 (office XP).
> >> can any one help???
>
>
>
From: mraposa on 23 Apr 2008 14:40
Hello,
Thank you for this information, it was very informative. I hope that we
could expand this discussion to include products developed based on the
Microsoft Sample Gateway. A customer of ours is running a large batch
process and is "exceeding the maximum of 250 objects of type objtMessage".
Could someone explain or point me to some documentation that would explain
how I would determine if our email gateway is not closing these objects
correctly. We have one MAPI session for the life of the application (so we
are not opening/closing sessions). I'm not sure if I am just missing freeing
some object(s) or if something is occuring under the covers that I am not
aware of. Any help on this issue would be very helpful.

Thank you,

Mark

"Rene Frenger" wrote:

> Ehhh, just a copy and paste from something I 'm keeping in my archive.
>
> --
> Regards,
>
> Rene Frenger
> MCITP E2K7
> MCP EX5.5, 2000, 2003
> MCSE
>
>
> "Cary Shultz" wrote:
>
> > Rene,
> >
> > Just something you threw together, huh?
> >
> > Excellent answer....exactly what I was going to write (riiiighhhttttt!).
> >
> > Cary
> >
> >
> > "Rene Frenger" <ReneFrenger(a)discussions.microsoft.com> wrote in message
> > news:6652EF3D-3C3E-4458-97C0-6C78E9B53559(a)microsoft.com...
> > > Mapi connections are not reset by the Exchange server:
> > >
> > > Typical things you see:
> > > - Outlook is unable to connect to server.
> > > - Outlook connections dropped.
> > >
> > > Things you have to do are:
> > > - Update networkdrivers to latest version.
> > > - Disable TCP Chimney offload (throught registry settings).
> > > - Implement some MSExchangeIS registry settings.
> > > - Release TCP/IP connections faster.
> > >
> > > Symptoms:
> > > Clients connected through VPN. Every time the session is interrupted and
> > > they reconnect three new sessions are opened.
> > > Also three days old sessions are available on the server. I.e. a user that
> > > logged off three days ago can still have an active session.
> > >
> > > On a server that is running Microsoft Exchange Server 2003, an event that
> > > resembles the following event is logged in the Application log:
> > >
> > > Event Type: Error
> > > Event Source: MSExchangeIS
> > > Event Category: General
> > > Event ID: 9646
> > > Description:
> > > Closing Mapi session "/o=Organization/ou=Administrative
> > > Group/cn=Recipients/cn=Recipient" because it exceeded the maximum of 32
> > > objects of type "session".
> > >
> > > When this issue occurs, you may also receive the following error message
> > > in
> > > Microsoft Office Outlook 2003:
> > > 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 is down for maintenance.
> > >
> > > Scope: This issue will be considered resolved when the sessions are reset
> > > faster.
> > >
> > > Solutions:
> > > Caused by Desktop search engines:
> > > http://support.microsoft.com/?id=905184
> > > This problem occurs if the Outlook client computer or the other MAPI
> > > client
> > > computer is running a desktop search engine (Google desktop search) that
> > > integrates with Outlook to index the user's mailbox or public folder data
> > > that resides on the Exchange server.
> > >
> > > TCP Chimney offload:
> > > After installing Windows 2003 SP2, we no longer see TCPIP keepalives
> > > package
> > > on
> > > network connections. For Exchange, administrators will see old, orphaned
> > > connections, especially from users who connect via WiFi, VPN, etc. The
> > > connection
> > > counts will grow until users reach a maximum number of connections,
> > > causing
> > > various
> > > connection-related errors in Outlook.
> > >
> > > This is because the TCP chimney function is enabled by default in Windows
> > > 2003
> > > SP2. TCP Chimney offload enables TCP/IP processing to be offloaded to
> > > network
> > > adapters that can handle the TCP/IP processing in hardware. If the Network
> > > Card did
> > > not handle the TCP Keep Alive packet correctly, the orphaned connections
> > > cannot be
> > > cleaned up. If you disable TCP Chimney, then the Operating System will
> > > handle the TCP/IP protocol and reset the connections.
> > >
> > > Disable TCP Chimney through the registry:
> > > HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
> > > The global registry entries are as follows:
> > > . EnableTCPChimney
> > > Type: REG_DWORD
> > > Values: 1 (enabled) 0 (disabled))
> > > . EnableRSS
> > > Type: REG_DWORD
> > > Values: 1 (enabled) 0 (disabled))
> > > . EnableTCPA
> > > Type: REG_DWORD
> > > Values: 1 (enabled) 0 (disabled))
> > >
> > > Set all these to 0.
> > >
> > > Restart the server after done this setting.
> > >
> > > See for backgroup information these articles:
> > > http://msexchangeteam.com/archive/2007/07/18/446400.aspx
> > > http://support.microsoft.com/?kbid=912222
> > >
> > > Registry settings you can do to tweak MSExchangeIS:
> > > http://support.microsoft.com/kb/830829
> > > http://support.microsoft.com/kb/842022
> > > Implement these registry settings:
> > > "HKLM\SYSTEM\CurrentControlSet\Services\MSExchangeIS\ParametersSystem\MaxObjsPerMapiSession\session"
> > > a decimal value of 350
> > >
> > > "HKLM\SYSTEM\CurrentControlSet\Services\MSExchangeIS\ParametersSystem\Maximum
> > > Allowed Sessions Per User" a decimal value of 250
> > >
> > > TCP registry settings:
> > > Implement the following registry key which will cause Exchange to clean up
> > > the connections sooner:
> > > "HKLM\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\KeepAliveTime"
> > > Setting the value to anything between 1 and 7,200,000 milliseconds.
> > > Recommended value is 600,000 (10 mins)
> > > Default time for Exchange is 7,200,000 (2 hours)
> > >
> > >
> > > --
> > > Regards,
> > >
> > > Rene Frenger
> > > MCITP E2K7
> > > MCP EX5.5, 2000, 2003
> > > MCSE
> > >
> > >
> > > "Suresh M V" wrote:
> > >
> > >> I am using exchange 2003.I am getting an error in the even log for one
> > >> user
> > >> "exceed a maximum of 32 objects type of session". The client side i am
> > >> using
> > >> microsoft outlook 2002 (office XP).
> > >> can any one help???
> >
> >
> >
 | 
Pages: 1
Prev: OAB path change
Next: Event ID 10016