Exchange 2013 cu6 Schema update failed

I am trying to install Exchange 2013 on server 2012 r2. AD level is 2012 r2 and I currently have exchange 2010 sp3 with all the rollups running. DCdiag passes with no errors.

The setup fails at the first step which is schema and AD preparation with the following error.

Error:
The following error was generated when "$error.Clear(); 
	install-ExchangeSchema -LdapFileName ($roleInstallPath + "Setup\Data\"+$RoleSchemaPrefix + "schema85.ldf")

" was run: "Microsoft.Exchange.Configuration.Tasks.TaskException: There was an error while running 'ldifde.exe' to import the schema file 'C:\Windows\Temp\ExchangeSetup\Setup\Data\PostExchange2003_schema85.ldf'. The error code is: 8245. More details can be found in the error file: 'C:\Users\hhemmati\AppData\Local\Temp\ldif.err'
   at Microsoft.Exchange.Configuration.Tasks.Task.ThrowError(Exception exception, ErrorCategory errorCategory, Object target, String helpUrl)
   at Microsoft.Exchange.Management.Deployment.InstallExchangeSchema.ImportSchemaFile(String schemaMasterServer, String schemaFilePath, String macroName, String macroValue, WriteVerboseDelegate writeVerbose)
   at Microsoft.Exchange.Management.Deployment.InstallExchangeSchema.InternalProcessRecord()
   at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
   at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".

The file ldiff.err contains the following

Entry DN: CN=ms-DS-GeoCoordinates-Altitude,CN=Schema,CN=Configuration,DC=palatribe,DC=com
Add error on entry starting on line 134: Unwilling To Perform

The server side error is: 0x20bb Schema update failed: duplicate OID.

The extended server error is:

000020BB: SvcErr: DSID-032603C0, problem 5003 (WILL_NOT_PERFORM), data 8379


An error has occurred in the program

I have been searching all over the place for an answer to this with no luck.


October 25th, 2014 5:52pm

Hi hamedhemmati,

From the detailed information you provided, I find the issue can be occurred if the following attributes are duplicated or already existed in AD.

CN=ms-DS-GeoCoordinates-Altitude,CN=Schema,CN=Configuration,DC=palatribe,DC=com

Please use ADSIEDIT or LDP tool to check about this issue.

Thanks,

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 27th, 2014 5:41am

Hi Simon,

Thanks for the response. Yes the GeoCoordinates already exists. I have one for Altitude, longitude and latitude. Should I delete these? Are they not used by the Exchange 2010?

October 27th, 2014 4:55pm

Would you be able to confirm if these attributes are ok to delete even if I am upgrading from 2010 to 2013?
Free Windows Admin Tool Kit Click here and download it now
October 29th, 2014 2:38pm

Hello,

Yes, It worked for one of my customer. However, the scenario and environment can be differed. I suggest we backup the AD before doing this operation. Also, it is recommended to contact a Microsoft Support to avoid any potential issues.

Thanks,

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 30th, 2014 7:26am

Hi,

Is there any update on this thread?

Thanks,

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
November 4th, 2014 1:36am

Was this ever solved? I'm having the exact same issue here, except I never had Exchange installed: https://social.technet.microsoft.com/Forums/windowsserver/en-US/1056021b-6171-482c-8001-93d6662ea6ae/error-extending-2012-r2-ad-schema-for-exchange-2013-rtmcu6-for-office-365-attributes?forum=winserverDS


March 24th, 2015 6:04pm

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

Other recent topics Other recent topics