Outlook 2007 - Poor Performance after SP1 installation

[lamaslany]

Just before Christmas SP1 for Office 2007 was installed on one of our
terminal servers (Windows Server 2003 R2 x64). The next day we were
inundated with users reporting chronically bad performance within Outlook -
taking between 5-30 seconds to open an email (either in the preview pane or
opening the email with the preview pane hidden).

Can anyone offer any suggestions or confirm whether they have (or have not0
encountered this problem in a similar environment?

Many thanks,

 

[Henri]

Hello,

i'm having exact the same problem:

My Setup:
Hardware (Terminal Server):
2 x Quad Core CPU
16GB Memory
72Gb SAS disks 15K in Raid 1 (OS)

Software:
Windows 2003 SP2 R2 STD Edition x64 fully patched with Terminal Services
installed (english)
Office 2007 with SP1 fully patched (dutch version)
Windows Desktop Search 3.01 (i had before, i removed this, still the same)
eTrust ITM 8.1 x64

This server was running fine, but after the following updates the problem
occured

Microsoft Windows Server 2003
Update for Windows Server 2003 x64 Edition (KB942763)
Windows Malicious Software Removal Tool x64 - December 2007 (KB890830)
Security Update for Windows Server 2003 x64 Edition (KB941568)
Security Update for Windows Server 2003 x64 Edition (KB941569)
Cumulative Security Update for Internet Explorer 7 for Windows Server 2003
x64 Edition (KB942615)
Security Update for Windows Server 2003 x64 Edition (KB944653)
Microsoft Office 2007
Update for Outlook Junk Email Filter 2007 (KB943597)

Office 2007 Service Pack 1

It has nothing to do with the exchange server, other clients are working
fine. If the slowness problems apear and i start outlook and open for example
an pst file, emails opening in that are also slow. even with a profile that
has not an exchange account.

For today i stopped the etrust services, i will post if that helps.

Uninstalling office 2007sp1 isnt an option, uinstall cant be done. Removing
office and reinstall without sp1 is also no option.

Any ideas?

 

[lamaslany]

Thanks for the reply.

I am afraid I have not been able to resolve this problem.

I thought I'd offer a couple of additional notes on my environment:

We have three terminal servers in a farm using Microsoft's Network Load
Balancing and the Session Directory. Users have roaming profiles. All three
servers use the same hardware:
HP BL485c Blades
2x quad-core CPUs
16GB RAM
2x 72GB SAS 10k disk (RAID 1)

Software:
Windows Server 2003 Enterprise Edition R2 x64 SP2 (fully patched)
Adobe Flash Player 9
Adobe Reader 8.1.1
Adobe Shockwave
Java Runtime Environment 5.0 Update 13
McAfee VirusScan 8.5
Microsoft .NET Framework 2.0 (x64)
Microsoft .NET Framework 3.0
Microsoft Office Communicator 2007
Microsoft Office Enterprise 2007
Microsoft Office Project Standard 2007
Microsoft Office Visio Standard 2007
Windows Internet Explorer 7
HP Proliant Support Pack 7.90

Note: I have not installed Windows Desktop Search 3.01

The only change made to the terminal server prior to the poor performance
was the installation of Office 2007 Service Pack 1.

The three servers were:
TS01 (Office 2007 + Office updates pre-SP1)
TS02 (Office 2007 + Office updates pre-SP1)
TS03 (Office 2007 SP1)

Uninstalling Office 2007 and re-installing Office 2007 without SP1 did not
entirely get rid of the problem. Users that had experienced the problem
still experience the problem when connecting to the server (TS03).

If one of the affected users connects to one of the terminal servers in the
farm that were not upgraded to Office 2007 SP1 (TS01 or TS02) they do not
experience any problems.

If a user that did not connect to TS03 while Office 2007 SP1 was installed
connects to TS03 after Office 2007 was re-installed they do not experience a
problem.

I did try stopping McAfee but the problem persists.

I am inclined to agree with you that the problem is with Outlook, or at
least Office, rather than Exchange. I have not yet tried to access a PST via
Exchange with an affected user without a mailbox but I will try it if only to
confirm the issue.

My next steps will be to:
* delete an affected users' profile to see whether this gets rid of the
problem.
* install a temporary terminal server (same software; different hardware),
upgrade to Office SP1 and see whether the problem re-occurs.

 

[Henri]

Hi,

are you sure about this part: ???

Uninstalling Office 2007 and re-installing Office 2007 without SP1 did not
entirely get rid of the problem. Users that had experienced the problem
still experience the problem when connecting to the server (TS03).

If one of the affected users connects to one of the terminal servers in the
farm that were not upgraded to Office 2007 SP1 (TS01 or TS02) they do not
experience any problems.

Maybe when you tested, it has something to do with the load on the server:

for exampe I only have issues i more than for example 10 users have started
outlook.

regards

 

[Henri]

Hi,

someone else has the same issues:

http://www.experts-exchange.com/Microsoft/Applications/Q_23084480.html

He also had eTrust ITm 8.1, but you use mcafee. so that could not be the
problem.
The Office sp1 must be.

I posted there your extra info, i hope you dont bother.

regards

 

[lamaslany]

are you sure about this part: ???

I thought I was but I will double check it.

Uninstalling Office 2007 and re-installing Office 2007 without SP1 did not
entirely get rid of the problem. Users that had experienced the problem
still experience the problem when connecting to the server (TS03).

If one of the affected users connects to one of the terminal servers in the
farm that were not upgraded to Office 2007 SP1 (TS01 or TS02) they do not
experience any problems.

Maybe when you tested, it has something to do with the load on the server:

for exampe I only have issues i more than for example 10 users have started
outlook.

It is entirely possible that there were more than 10 users logged in when I
tested with one of the problematic accounts after the re-install and there
might not have been 10 users logged in when I logged on with an account that
reported no issues.

Unfortunately we're pushing the limits on our terminal servers so it isn't
possible to take TS03 offline to troubleshoot except for out of hours.

 

[lamaslany]

I posted there your extra info, i hope you dont bother.

No problem - the more information sooner the problem is isolated the better.

 

[lamaslany]

I've just gone through the emails we received today regarding Outlook
performance on TS03 and noted that one of the users I *know* had problem
reported that Outlook appeared to be working normally. From the timestamp on
the email I am sure that there were less than half a dozen people logged on
to TS03 at the time (one of which was me to the console session; I has just
taken it out of drainstop to try a couple of things) so I think I may have
mis-interpreted the problem as you suggested.