FaxMaker error during /PrepareAD won't go away
I'm running setup.com /prearead (from our Server 2008r2 DC) in our lab to practice migrating to Exchange 2010. The process fails and ExchangeSetup.log shows: Processing object "company.com". [10/27/2011 21:48:01.0114] [2] [ERROR] The e-mail address policy object must have exactly one primary e-mail address with the prefix "FAXMAKER". Property Name: [10/27/2011 21:48:01.0114] [2] Ending processing set-accepteddomain [10/27/2011 21:48:01.0114] [2] Default domain company.com [10/27/2011 21:48:01.0114] [1] The following 1 error(s) occurred during task execution: [10/27/2011 21:48:01.0114] [1] 0. ErrorRecord: The e-mail address policy object must have exactly one primary e-mail address with the prefix "FAXMAKER". Property Name: [10/27/2011 21:48:01.0114] [1] 0. ErrorRecord: Microsoft.Exchange.Data.DataValidationException: The e-mail address policy object must have exactly one primary e-mail address with the prefix "FAXMAKER". Property Name: at Microsoft.Exchange.Data.Directory.ADSession.Save(ADObject instanceToSave, IEnumerable`1 properties) at Microsoft.Exchange.Management.SystemConfigurationTasks.SetAcceptedDomain.DomainEditValidator.HandleNonAuthoritativeDomains(EmailAddressPolicy policy, HashSet`1 domains) at Microsoft.Exchange.Management.SystemConfigurationTasks.UpdateEmailAddressPolicy.DomainValidator.Validate(EmailAddressPolicy policy) at Microsoft.Exchange.Management.SystemConfigurationTasks.SetAcceptedDomain.DomainEditValidator.ValidateAllPolicies() at Microsoft.Exchange.Management.SystemConfigurationTasks.SetAcceptedDomain.InternalValidate() at Microsoft.Exchange.Configuration.Tasks.Task.ProcessRecord() [10/27/2011 21:48:01.0114] [1] [ERROR] The following error was generated when "$error.Clear(); Write-ExchangeSetupLog -Info "Set the default Accepted domain from the default recipient policy"; $defaultEmailAddressPolicy = get-EmailAddressPolicy -Identity:"Default Policy"; $defaultSmtpTemplate = $defaultEmailAddressPolicy.EnabledPrimarySMTPAddressTemplate; $index = $defaultSmtpTemplate.IndexOf("@"); $eapAuthoritativeDomain = $defaultSmtpTemplate.Substring($index+1); $defaultDomain = get-accepteddomain | where {$_.DomainName -eq $eapAuthoritativeDomain }; $defaultDomain | set-accepteddomain -MakeDefault:$true; Write-ExchangeSetupLog -Info "Default domain $defaultDomain"; " was run: "The e-mail address policy object must have exactly one primary e-mail address with the prefix "FAXMAKER". Property Name: ". [10/27/2011 21:48:01.0114] [1] [ERROR] The e-mail address policy object must have exactly one primary e-mail address with the prefix "FAXMAKER". Property Name: [10/27/2011 21:48:01.0114] [1] [ERROR-REFERENCE] Id=CommonGlobalConfig___6ef41a1df5422d4beb8f803c27b96c59ba Component=EXCHANGE14:\Current\Release\Shared\Datacenter\Setup [10/27/2011 21:48:01.0114] [1] Setup is stopping now because of one or more critical errors. [10/27/2011 21:48:01.0114] [1] Finished executing component tasks. [10/27/2011 21:48:01.0114] [1] Ending processing Install-ExchangeOrganization [10/27/2011 21:48:01.0114] [0] The Exchange Server setup operation didn't complete. More details can be found in ExchangeSetup.log located in the :\ExchangeSetupLogs folder. [10/27/2011 21:48:01.0114] [0] End of Setup [10/27/2011 21:48:01.0114] [0] ********************************************** I opened ESM -> Recipients -> Recipient Policies -> Default Policy -> Properties and removed FaxMaker (we used it long ago, but shouldn't be necessary anymore). We've got several other policies. Only one of them is an e-mail address policy, but it doesn't have FaxMaker either. So I tried preparing AD again and got the same error. What gives? Thanks.
October 27th, 2011 6:09pm

See if these help - http://support.microsoft.com/kb/948211Sukh
Free Windows Admin Tool Kit Click here and download it now
October 27th, 2011 6:53pm

Ah yes. I forgot to mention that I have seen that. I looked at each of our recipient policies and there are no disabledGatewayProxy entries.
October 27th, 2011 9:38pm

Ah yes. I forgot to mention that I have seen that. I looked at each of our recipient policies and there are no disabledGatewayProxy entries. Hi mhashemi, Do you mean there is no disabledGatewayProxy Attribute displayed, or the value of disabledGatewayProxy is <Not Set> ? If the former, please clear "Show only attributes that have values". And if you add the FaxMaker( ESM -> Recipients -> Recipient Policies -> Default Policy -> Properties ) again, can you see the value in ADSIEDIT.MSC? If yes, please try to remove it as the KB said. Similar post: Exchange 2007 SP1 on Server 2008 Installation http://social.technet.microsoft.com/Forums/en/exchangesvrdeploy/thread/f6db6582-42b0-4760-b8d8-2f2542a2ad27 Frank Wang Forum Support Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.
Free Windows Admin Tool Kit Click here and download it now
October 31st, 2011 12:08am

Ah yes. I forgot to mention that I have seen that. I looked at each of our recipient policies and there are no disabledGatewayProxy entries. Hi mhashemi, Do you mean there is no disabledGatewayProxy Attribute displayed, or the value of disabledGatewayProxy is <Not Set> ? If the former, please clear "Show only attributes that have values". And if you add the FaxMaker( ESM -> Recipients -> Recipient Policies -> Default Policy -> Properties ) again, can you see the value in ADSIEDIT.MSC? If yes, please try to remove it as the KB said. Similar post: Exchange 2007 SP1 on Server 2008 Installation http://social.technet.microsoft.com/Forums/en/exchangesvrdeploy/thread/f6db6582-42b0-4760-b8d8-2f2542a2ad27 Frank Wang Forum Support Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.
October 31st, 2011 7:04am

Hi mhashemi, Any updates? Frank Wang
Free Windows Admin Tool Kit Click here and download it now
November 1st, 2011 10:05pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics