MSExchangeSA Event 9396 while generating Offline Address Book

by Shijaz Abdulla on 28.01.2009 at 09:49

January 28, 2009

Log Name:      Application
Source:        MSExchangeSA
Date:          1/28/2009 10:18:59 AM
Event ID:      9396
Task Category: OAL Generator
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      servername
OALGen is running on a single-copy cluster (SCC) node that does not have the registry value ‘SYSTEMCurrentControlSetServicesMSExchangeSAParameters
servernameOabDropFolderLocation’ or it is set to a non-existing path. Offline address book generation will not be performed.

This typically happens on an SCC cluster when the OabDropFolderLocation registry entry:

  • does not exist (was accidentally deleted). The key should exist on all nodes with the same value.
  • the location/folder mentioned in this registry value was deleted or renamed
  • the location is on a non-shared disk (like C:). On an SCC cluster, this folder should always be on a shared disk.

To fix the problem, recreate the registry entry if it doesn’t exist, or edit the value so that it points to a valid location.


ExTRA crashes when you try to restore a mailbox

by Shijaz Abdulla on 26.01.2009 at 09:24

January 26, 2009

On Exchange Server 2007 SP1, Exchange Troubleshooting Agent hangs/crashes after you mount the database in the recovery storage group and begin the actual ‘merge or copy mailbox’ process with the following (or similar) crash information:

Problem signature:
  Problem Event Name:      APPCRASH

  Application Name:            ExTRA.exe
  Application Version:
  Application Timestamp:       47342a91
  Fault Module Name:           migbase.dll
  Fault Module Version:
  Fault Module Timestamp:      47427ba1
  Exception Code:              c0000005
  Exception Offset:            000000000006741e
  OS Version:                  6.0.6001.
  Locale ID:                   1033
Operating System: Windows 2008 Server
Time Zone: (GMT+04:00) Abu Dhabi, Muscat
Alternate Language: en-US
Support topic(s): Tools/ExTRA

The solution would be to install Rollup Update 5 on Exchange Server 2007 SP1.

***Lighten your load. Store, Backup and Access Important Files Online using ElephantDrive – Free Trial.***

Blackberry Enterprise 4.1 and Exchange Server 2007

by Shijaz Abdulla on 27.09.2008 at 13:57

After I moved Blackberry-enabled mailboxes over from Exchange 2003 to Exchange 2007, there were no major problems as far as Blackberry was concerned – except that calendar items created on the blackberry devices did not get synchronized with Exchange/Outlook.

The primary reason for the problem is that Blackberry uses public folders to sync calendar items – and Exchange Server 2007 by default has no public folders!

To workaround the problem:

1 – Create a Public Folder database on the Exchange Server that has the mailbox server role installed.

2 – Link the Exchange Server 2007 mailbox database to the Public folder database you just created. To do this, open the properties of the mailbox database containing the blackberry user mailboxes and select the new public folder store in the Client Settings tab.

PF store

Creating Exchange 2007 mailboxes through AD attributes

by Shijaz Abdulla on 30.07.2008 at 15:31

If you are using a third-party/home-grown application or script to provision user accounts and mailboxes, you can still create mailboxes by populating Active Directory attributes. The recommended way would be to use PowerShell aka Exchange Management Shell or the Exchange Management Console. However, this may not always be possible – so here’s something that I’ve tried and it works.

Please pay special attention to the disclaimer at the bottom of the page. This (and any other post) is my own view and not endorsed by Microsoft. Supportability of this method is at Microsoft’s discretion. You are on your own when it comes to risk. 🙂

The following attributes need to be populated, just like earlier versions of Exchange Server:

  • HomeMTA
  • HomeMDB
  • legacyExchangeDN
  • msExchHomeServerName

In addition, the following "mandatory attributes" need to be added. To know the values for these attributes in your environment, see the values on existing mailboxes using ADSIEDIT.

  • msExchVersion
  • msExchMobileMailboxFlags
  • msExchRecipientDisplayType
  • msExchRecipientTypeDetails

If you prefer not to add the "mandatory attributes", you can always run the following Shell command, and Exchange will do that stuff for you.

Set-Mailbox <mailboxname> -applymandatoryproperties

Login problems on Exchange 2007 OWA

by Shijaz Abdulla on 30.04.2008 at 14:13

If you have two separate Exchange Server 2007 mailbox servers, and users in one mailbox server can login to Outlook Web Access using your Client Access Server, while the users on the second mailbox server cannot log in to Outlook Web Access using the same Client Access Servers, the following might help.

This issue is seen if the mailbox server is running Exchange Server 2007 SP1 on Windows Server 2008. From Server Manager, open Web Server (IIS). Make sure the following Role services are added:

Under Application Development, select the following:

  • .Net Extensibility
  • ASP
  • ISAPI Extensions
  • ISAPI Filters
  • Server Side Includes
  • .NET environment

Under Security, select the following:

  • Basic authentication
  • Windows Authentication

Do an IISRESET /noforce.

You should be able to login now. If you can’t try logging in using the domainusername format, even if you chose the option for ‘user name only’ on your Client Access Server. If you are able to log in with domainusername and not just username, and you have enabled ‘username’ only option under Forms based Authentication on your Client Access Servers, try the following.

On the IIS of your Exchange Server 2007 mailbox server, navigate to the /exchange virtual directory, open Authentication, and change the properties for Basic Authentication and enter a "" without the quotes for the Default Domain.