The FaxMaker error that won’t go away

Home Forums Messaging Software Exchange 2007 / 2010 / 2013 The FaxMaker error that won’t go away

Viewing 1 post (of 1 total)
  • Author
    Posts
  • Avatar
    mhashemi
    Member
    #156627

    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:

    Quote:
    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, IEnumerable1 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:CurrentReleaseSharedDatacenterSetup
    [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.

    I tried preparing AD again and got the same error.

    Finally, I also saw the Microsoft KB948211 and looked at the “disabledGatewayProxy” attribute of each of our policies, but they are all blank.

    What gives? Thanks.

Viewing 1 post (of 1 total)

You must be logged in to reply to this topic.