"imited number of items open" - I'm tearing out my hair!

[No_hair_left]

Please, please, please with sugar, icing and a cherry on top, can someone
help us. We currently have 3 clients running Outlook 2007 BCM and SBS running
Exchange 2003 with all clients connected to the same SQL Server database.

On all clients we receive the following warning popup constantly: "Your
server administrator has limited the number of items you can open
simultaneously. Try closing messages you have opened or removing attachments
and images from unsent messages you are composing."

This warning occurs at start up (i.e. no items, mails or records are open).

Also on a seperate issue when 1 of the clients has BCM installed he cannot
send any mails whatsoever.

Your help is eagerly awaited..........

 

[John Huang [MSFT]]

I searched online with your error message, got a lot of asks but very few
answers. This may not be a BCM-related issue.

My closest find suggests you to ask your Exchange admin for
this(http://www.eggheadcafe.com/software/aspnet/29706872/you-server-administrator.aspx).
Could someone on your team accidentally changed the setting in Exchange? It
won't hurt to look around in that direction...

Good luck!

 

[No_hair_left]

Hi John. Thanks for the response. The link you've included in your reply
seems to take me to exactly the same question with no advice or answer. Was
this intended? What is the setting you are suggesting. Many thanks.

I searched online with your error message, got a lot of asks but very few
answers. This may not be a BCM-related issue.

My closest find suggests you to ask your Exchange admin for
this(http://www.eggheadcafe.com/software/aspnet/29706872/you-server-administrator.aspx).
Could someone on your team accidentally changed the setting in Exchange? It
won't hurt to look around in that direction...

Good luck!
--
John Huang [MSFT]

This posting is provided "AS IS" with no warranties, and confers no rights.

Please, please, please with sugar, icing and a cherry on top, can someone
help us. We currently have 3 clients running Outlook 2007 BCM and SBS running
Exchange 2003 with all clients connected to the same SQL Server database.

On all clients we receive the following warning popup constantly: "Your
server administrator has limited the number of items you can open
simultaneously. Try closing messages you have opened or removing attachments
and images from unsent messages you are composing."

This warning occurs at start up (i.e. no items, mails or records are open).

Also on a seperate issue when 1 of the clients has BCM installed he cannot
send any mails whatsoever.

Your help is eagerly awaited..........

 

[Luther]

Hi John. Thanks for the response. The link you've included in your reply
seems to take me to exactly the same question with no advice or answer. Was
this intended? What is the setting you are suggesting. Many thanks.









- Show quoted text -

Both your questions are email related, and BCM should not affect how
Outlook talks to Exchange. If BCM is causing Outlook to behave
differently, then that's a new bug in this newsgroup, and Microsoft
support may be your best option.

 

[Steve]

I believe this is a problem with Outlook 2007 not releasing Exchange objects
from memory, then triggering the Exchange open limits.

It may be with Outlook directly, but can not say for sure, but what I can
say is that this is certainly a problem with any COM add-ins or interop code
using Outlook 2007.

There is a certain combination of permissions (which my Exchange
administrator has not yet isolated) which allows the user to ignore the
Exchange email/attachment open limits - but this just allows Outlook (or the
outlook plug-in, or the interop application) to continue creating Exchange
objects in memory without limit.

If it is with Outlook 2007 directly, then hopefully a hotfix or service pack
will soon address this issue.

For anyone writing interop code or plugins, the only solution I have found
is to release the 'Outlook.Application' object and recreate it before it hits
the limits set on Exchange.

The method I use works, but does not fix the underlying problem.
Here is my (heavy handed) method which I call every 50 items:

private void RefreshOutlookConnection()
{
//log off session
_olApp.Session.Logoff();
_olNs.Application.Session.Logoff();

//release COM objects
System.Runtime.InteropServices.Marshal.ReleaseComObject(_olApp);
System.Runtime.InteropServices.Marshal.ReleaseComObject(_olNs);
GC.Collect();

//renew objects and logon
_olApp = new Microsoft.Office.Interop.Outlook.Application();
_olNs = _olApp.GetNamespace("MAPI");
_olNs.Logon("", "", false, true);
}