DESPERATE!!! MSExchangeIS EventID

I don't know how to correct this!

PLEASE HELP! - this has shut off our incoming messages.

Mapi session "/o=testdomain/ou=FIRST ADMINISTRATIVE
GROUP/cn=RECIPIENTS/cn=STEVE" exceeded the maximum of 500 objects of type
"objtMessageView".

For more information, click http://www.microsoft.com/contentredirect.asp.

This is what the link says -

Explanation
A single MAPI session has exceeded the maximum number of objects of a
given type. To prevent a single client from affecting the performance of the
entire server, this MAPI session was terminated.


User Action
This can be caused by a very high usage level by an individual user.
If these errors are happening regularly, you can raise the default maximum
for the affected object type (for example, to twice its default level). If
at this level the specified user is continuing to generate this warning,
investigate the user actions that are causing this warning. It can be caused
by improper client design or unusual client usage patterns.

microsoft
Mon Jan 19 20:09:26 CST 2004

http://support.microsoft.com/default.aspx?scid=kb;en-us;830829&Product=exch2003 -
this has taken care of some issues although I have new ones - mapi related -
gotta go - hope this helps some people with similar issues.
"microsoft" <ayzen1@hotmail.com> wrote in message
news:OfhkWGv3DHA.2000@TK2MSFTNGP11.phx.gbl...
> I don't know how to correct this!
>
> PLEASE HELP! - this has shut off our incoming messages.
>
> Mapi session "/o=testdomain/ou=FIRST ADMINISTRATIVE
> GROUP/cn=RECIPIENTS/cn=STEVE" exceeded the maximum of 500 objects of type
> "objtMessageView".
>
> For more information, click http://www.microsoft.com/contentredirect.asp.
>
> This is what the link says -
>
> Explanation
> A single MAPI session has exceeded the maximum number of objects of
a
> given type. To prevent a single client from affecting the performance of
the
> entire server, this MAPI session was terminated.
>
>
> User Action
> This can be caused by a very high usage level by an individual user.
> If these errors are happening regularly, you can raise the default maximum
> for the affected object type (for example, to twice its default level). If
> at this level the specified user is continuing to generate this warning,
> investigate the user actions that are causing this warning. It can be
caused
> by improper client design or unusual client usage patterns.
>
>
>
>
>
>
>
>
>
>
>
>