• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2913
  • Last Modified:

Exchange 2007 & Outlook 2007 - Clients Freezing and Crashing

Hi there,
We are running Exchange 2007 and Outlook 2007 (both have all the latest updates) and I have a massive problem with Outlook clients that keep freezing and crashing. I have enabled high Diagnostic logging on Exchange 2007 but I have not seen anything meaningful in the logs yet, any info on enabling in depth logging in the Outlook client would be welcome.
This is pretty serious as it is stopping people from working but I honestly don't know where to start on this one as:
- The network is not congested
- The speed of the machines in question is fine.
All input and suggestions welcome!
0
the-waves
Asked:
the-waves
  • 5
  • 4
1 Solution
 
Veerappan SundaramSenior Technical ConsultantCommented:
1. If you want to Enable logging in Outlook 2007, follow the below steps:                          Go to Tools > Options > Other tab > Advanced Options > (under General Settings) Enable Logging (Troubleshooting).
2. Try running outlook in Safe mode ( From Run > type outlook / safe) will open outlook in safe mode. If your users does not face any issues in Safe mode, then consider disabling outlook Add-ins from Tools > Trust Center.
3. Turn off the reading pane and check.
>>>> Veera.
 
0
 
abdulzisCommented:
Open outlook with the rpcdiag switch and when the clients freeze, let us know if any of the fields shows disconnected.
Also run ExBPA on the Exchange server and go over the critical errors and warnings if any.
0
 
the-wavesAuthor Commented:
OK,

Following advice given - where can I find the Outlook logs?
0
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

 
Veerappan SundaramSenior Technical ConsultantCommented:

You can find the logs as below:

Windows XP
c:\documents and settings\userName\Local settings\temp\outlook logging
Windows Vista
c:\Users\user name\AppData\Local\Temp\Outlook Logging
>>>> Veera.
0
 
the-wavesAuthor Commented:
OK,

Looks like we are getting somewhere. I am getting loads of Outlook Event ID 19.

Log Name:      Application
Source:        Outlook
Date:          16/02/2009 7:48:02 PM
Event ID:      19
Task Category: None
Level:         Information
Keywords:      Classic
User:          N/A
Computer:      computer.domain.local
Description:
Rpc call (NspiBind) on transport (ncacn_ip_tcp) to server (exchange-server.domain.local) failed with error code (6ba) after waiting (0) ms; eeInfo (Block (0), Error = 6ba, Version = 1, GeneratingComponent = 2, DetectionLocation = 1f5, Flags = 0, Params = 4, [Param (0) Type = eeptUnicodeString, Value = ncacn_ip_tcp], [Param (1) Type = eeptUnicodeString, Value = exchange-server.domain.local], [Param (2) Type = eeptLongVal, Value = f5cc5a18], [Param (3) Type = eeptLongVal, Value = 6ba], Block (1), Error = 6ba, Version = 1, GeneratingComponent = 8, DetectionLocation = 5a2, Flags = 0, Params = 1, [Param (0) Type = eeptUnicodeString, Value = exchange-server.domain.local.local]).
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Outlook" />
    <EventID Qualifiers="16384">19</EventID>
    <Level>4</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2009-02-16T10:48:02.000Z" />
    <EventRecordID>3821</EventRecordID>
    <Channel>Application</Channel>
    <Computer>computer.domain.local</Computer>
    <Security />
  </System>
  <EventData>
    <Data>NspiBind</Data>
    <Data>ncacn_ip_tcp</Data>
    <Data>exchange-server.domain.local</Data>
    <Data>6ba</Data>
    <Data>0</Data>
    <Data>Block (0), Error = 6ba, Version = 1, GeneratingComponent = 2, DetectionLocation = 1f5, Flags = 0, Params = 4, [Param (0) Type = eeptUnicodeString, Value = ncacn_ip_tcp], [Param (1) Type = eeptUnicodeString, Value = exchange-server.domain.local.local], [Param (2) Type = eeptLongVal, Value = f5cc5a18], [Param (3) Type = eeptLongVal, Value = 6ba], Block (1), Error = 6ba, Version = 1, GeneratingComponent = 8, DetectionLocation = 5a2, Flags = 0, Params = 1, [Param (0) Type = eeptUnicodeString, Value = exchange-server.domain.local.local]</Data>
  </EventData>
</Event>
0
 
Veerappan SundaramSenior Technical ConsultantCommented:
I presume that outlook is trying to connect through RPC-over-HTTP. Check the settings in outlook for the same. Check the configuration for RPC-over-HTTP from server side too.
>>>> Veera.
0
 
the-wavesAuthor Commented:
Actually I think only a couple of the clients laptops are. The rest are desktop PC's that shouldn't be using RPC\HTTP.
0
 
the-wavesAuthor Commented:
OK - I have checked and many of the clients are trying to connect over a normal LAN connection. Some of the worst affected clients have Inboxes between 2GB and 3GB.
0
 
Veerappan SundaramSenior Technical ConsultantCommented:
Did you try with Safe mode? If yes, how was the response?
Download ExBPA from Microsoft web and check for any possible bottleneck issues.
>>>> Veera.
0
 
the-wavesAuthor Commented:
I got clients to reduce their PST sizes - still no joy. Turns out it was DNS. The client DNS was pointed at an AD server with no DNS installed!
0

Featured Post

Visualize your virtual and backup environments

Create well-organized and polished visualizations of your virtual and backup environments when planning VMware vSphere, Microsoft Hyper-V or Veeam deployments. It helps you to gain better visibility and valuable business insights.

  • 5
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now