cancel
Showing results for 
Search instead for 
Did you mean: 

Outlook sp2 HF Article # 2458611

GCSPT
Level 5
Employee Accredited Certified

Just want to start a Discussion/Fact finding effort to have a look at the effects of the MS HF attached to this Article http://support.microsoft.com/kb/2458611

The HF is to overcome the number of MAPI connections restriction implemented by running Outlook 2007.

We are looking for confirmation of the effect on EV operations that this HF has had in the wild.

Either it has had no effect, in which case why was it applied and what errors were you getting to prompt you to apply it.

Or it has had an affect, again, what errors where you getting to prompt you to apply it and whether those errors have gone.

Or it has had a negative effect, in which case we still need to know why it was applied and also the resultant effect it has had since applying it. Has the reason for applying it gone and a new issue arisen or the old errors are still present?

 

6 REPLIES 6

Nick_White
Level 6
Employee

Hi,

the main side-effect for Enterprise Vault of not having this patch is that there is a restriction on the number of active/concurrent profiles you can have at any one time (32 without the fix), which means that we can only have 32 connections for our Exchange agents at any one time. For a small environment this is fine but the more agents you have on a single Enterprise Vault server, the more likely you are to hit the limit. The fix increases the amount to 130 which means that you are very unlikely to hit the limit. By default, a single Exchange Archiving Task will use 5 concurrent connections (1 profile per connection) so hitting 130 is going to require something serious to exceed the maximum with the fix applied

We have been running with the hotfix on a number of environments in-house and are yet to see any reported issues

JesusWept3
Level 6
Partner Accredited Certified

Where I work we're thinking about applying it, however due to the similiarities between that hotfix and the hotfix that Microsoft recently redacted have put off doing so, currently we don't really have any performance issues with Outlook 2007 that would dictate updating Outlook.

This may change when we go to Exchange 2010 shortly, but Outlook 2007 on Windows Server 2008 against Exchange 2003 runs quite well.

https://www.linkedin.com/in/alex-allen-turl-07370146

Rob_Wilcox1
Level 6
Partner

Which was the hotfix that MS pulled?

Working for cloudficient.com

KarlW
Level 6
Employee

Could have been:

http://blogs.office.com/b/microsoft-outlook/archive/2010/12/17/issues-with-the-recent-update-for-out...

The information I have from Microsoft is that this shouldn't impact http://support.microsoft.com/kb/2458611.

Thanks

 

Karl

 

olmit
Level 2

Hello,

we had installed the kb2458611 patch because we had problems with archiving (Event log entries 3411 and 2216). This event entries didn't log anymore after the Installation of the patch.

Unfortunately the Archive Service crashes many times like explained in article http://98.129.119.162/connect/de/blogs/outlook-2007-ev-server-new-ms-hotfix-available.

Now we removed the patch, the Service don't crash anymore, but the 3411 and 2216 events listed again.

Olaf.

KarlW
Level 6
Employee

There was an issue with 2458611.  A new update was released last month.

See thread the following thread for more details:

https://www-secure.symantec.com/connect/forums/fyi-new-outlook-2007-hotfix-released-performance

Regards

Karl