Unable to connect to Exchange 2007 mailbox following full backup

Posted on 2008-11-11
Last Modified: 2013-12-01
Currently we are having an issue where after a Full backup we have some, but not all, Outlook clients who are unable to  connect to our Exchange 2007 environment.  They will receive an "Unable to connect to Exchange Server" error message or some clients will be forced to work offline.

To allow them to reconnect to Exchange 2007 I have to Stop and then Start the Clustered Mailbox Server using the Clustered Mailbox Server wizard in Exchange 2007.  After that Exchange works fine until the next Full backup when the issue occurs all over again.  

The issue does not affect any one storage group or database.  The issue does not affect the same clients every time and has no affect on OWA access at all.

The following is our Exchange Environment:

      -Two CCR clustered Mailbox servers running Exchange 2007 SP1
      -One CAS/Hub Transport server running Exchange 2007 SP1
      -Our clients are Outlook 2000, Outlook 2003, and Outlook 2007 and all three are affected
      -We've used both NTbackup and BackupExec 12 to backup the databases and both cause the issue.
      -Full backups are the only backups that are causing the issues, Incremental or Differential backups have no issues.
Question by:PaulRKrueger
    LVL 28

    Accepted Solution

    Whenever I see weird behaviour like this it often is down to antivirus software. Try uninstalling it.

    I assume this is running on Windows 2003. Apply the latest VSS rollup package if you haven't already. VSS is used extensively in backups of Exchange.


    LVL 1

    Expert Comment

    i would do a integrity check on the database.
    LVL 4

    Author Comment

    Thanks. We'll give them a shot and let you know.
    LVL 4

    Author Comment

    We made two changes (sorry, I know that doesn't help) and our problem has been solved.
    We disabled the TCP Chimney feature on the server using the Netsh.exe tool ( as linked from
    We also started backing up from the passive node.
    As a result, we have improved our network backup speed by 4 hours (a 30% reduction) and did not have any issues this morning. I'm guessing this is primarily due to disabling the TCP Chimney feature.
    Thanks a bunch!

    Featured Post

    Maximize Your Threat Intelligence Reporting

    Reporting is one of the most important and least talked about aspects of a world-class threat intelligence program. Here’s how to do it right.

    Join & Write a Comment

    We are happy to announce a brand new addition to our line of acclaimed email signature management products – CodeTwo Email Signatures for Office 365.
    Not sure what the best email signature size is? Are you worried about email signature image size? Follow this best practice guide.
    This tutorial will walk an individual through the steps necessary to install and configure the Windows Server Backup Utility. Directly connect an external storage device such as a USB drive, or CD\DVD burner: If the device is a USB drive, ensure i…
    This tutorial will walk an individual through setting the global and backup job media overwrite and protection periods in Backup Exec 2012. Log onto the Backup Exec Central Administration Server. Examine the services. If all or most of them are stop…

    754 members asked questions and received personalized solutions in the past 7 days.

    Join the community of 500,000 technology professionals and ask your questions.

    Join & Ask a Question

    Need Help in Real-Time?

    Connect with top rated Experts

    17 Experts available now in Live!

    Get 1:1 Help Now