Take the 2-minute tour ×
Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

My Outlook 2010 freezes a couple of times per day. I am connected to a Exchange 2003 server. Sometimes, when I try to send an email or open an appointment, the interface completely freezes. After a few seconds a balloon pops up saying:Outlook is contacting Server.network.local (where 'Server' is the primary domain controller and not the Exchange server). I checked the event log of that server and I found out that every time my Outlook freezes, three notices are written to the Security Event log:

Event Type: Success Audit Event Source: Security Event Category: System Event Event ID: 515 Date: 4/8/2011 Time: 4:45:26 PM User: NT AUTHORITY\SYSTEM Computer: Server Description: A trusted logon process has registered with the Local Security Authority. This logon process will be trusted to submit logon requests.

Logon Process Name: KSecDD

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Event Type: Success Audit Event Source: Security Event Category: System Event Event ID: 515 Date: 4/8/2011 Time: 4:45:25 PM User: NT AUTHORITY\SYSTEM Computer: Server Description: A trusted logon process has registered with the Local Security Authority. This logon process will be trusted to submit logon requests.

Logon Process Name: KSecDD

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Event Type: Success Audit Event Source: Security Event Category: System Event Event ID: 515 Date: 4/8/2011 Time: 4:45:25 PM User: NT AUTHORITY\SYSTEM Computer: Server Description: A trusted logon process has registered with the Local Security Authority. This logon process will be trusted to submit logon requests.

Logon Process Name: Winlogon\MSGina

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Who can help me solving the freezing Outlook?

share|improve this question
    
Couple suggestions: 1.Run dcdiag/netdiag on your DCs, validate all is good, 2.Validate that on your workstation you have DNS servers for your domain. 3.Check that the time is properly synced between your workstation, Exchange server and DCs. –  Vick Vega Apr 11 '11 at 0:01
    
@Vick All tests are either passed or skipped when run dcdiag and netdiag on the DC's –  jao Apr 11 '11 at 16:36

1 Answer 1

up vote 0 down vote accepted

It looks like it's been solved by enabling Cached Exchange Mode in the account settings tab.

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.