board logo
Posted by: drdread - 02 July 2025 08:39:48
Why is this happening? Is it because the old server has the same name as then new one? Log Name: DFS Replication Source: DFSR Date: 02/07/2025 08:33:29 Event ID: 5012 Task Category: None Level: Error Keywords: Classic User: N/A Computer: DC1.ofield.local Description: The DFS Replication service failed to communicate with partner DC2 for replication group Shares. The partner did not recognize the connection or the replication group configuration. Partner DNS Address: DC2.ofield.local Optional data if available: Partner WINS Address: DC2 Partner IP Address: 192.168.1.20 The service will retry the connection periodically. Additional Information: Error: 9026 (The connection is invalid) Connection ID: BA005408-C36E-47E4-A41F-F7FCE8B9DC88 Replication Group ID: 6B33EAFD-5B80-4302-914A-BA3C2148E271 Event Xml: [code=markup]<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="DFSR" /> <EventID Qualifiers="49152">5012</EventID> <Level>2</Level> <Task>0</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2025-07-02T07:33:29.070375600Z" /> <EventRecordID>37</EventRecordID> <Channel>DFS Replication</Channel> <Computer>DC1.ofield.local</Computer> <Security /> </System> <EventData> <Data>BA005408-C36E-47E4-A41F-F7FCE8B9DC88</Data> <Data>DC2</Data> <Data>Shares</Data> <Data>DC2.ofield.local</Data> <Data>DC2</Data> <Data>192.168.1.20</Data> <Data>9026</Data> <Data>The connection is invalid</Data> <Data>6B33EAFD-5B80-4302-914A-BA3C2148E271</Data> </EventData> </Event>[/code]

Posted by: drdread - 02 July 2025 08:47:48
When I try to uninstall I see: Microsoft Exchange Server 2013 Cumulative Update 23 Unattended Setup Mailbox role: Mailbox service Mailbox role: Unified Messaging service Mailbox role: Client Access service Mailbox role: Transport service Client Access role: Front End Transport service Management tools Client Access role: Client Access Front End service Languages Performing Microsoft Exchange Server Prerequisite Check Configuring Prerequisites COMPLETED Prerequisite Analysis COMPLETED Configuring Microsoft Exchange Server Preparing Setup COMPLETED Mailbox role: Mailbox service FAILED The following error was generated when "$error.Clear(); Set-MailboxServer -Identity $RoleFqdnOrName -CalendarRepairWorkCycle $ null -CalendarRepairWorkCycleCheckpoint $null " was run: "Microsoft.Exchange.Configuration.Tasks.ManagementObjectNotFo undException: The operation couldn't be performed because object 'ArgEX-temp.arg ofield.local' couldn't be found on 'ARGDC2.argofield.local'. at Microsoft.Exchange.Configuration.Tasks.DataAccessTask`1.GetDataObject[TObj ect](IIdentityParameter id, IConfigDataProvider session, ObjectId rootID, Option alIdentityData optionalData, Nullable`1 notFoundError, Nullable`1 multipleFoundE rror, ExchangeErrorCategory errorCategory) at Microsoft.Exchange.Configuration.Tasks.DataAccessTask`1.GetDataObject[TObj ect](IIdentityParameter id, IConfigDataProvider session, ObjectId rootID, Option alIdentityData optionalData, Nullable`1 notFoundError, Nullable`1 multipleFoundE rror) at Microsoft.Exchange.Configuration.Tasks.SetObjectWithIdentityTaskBase`3.Res olveDataObject() at Microsoft.Exchange.Configuration.Tasks.SetSystemConfigurationObjectTask`3. ResolveDataObject() at Microsoft.Exchange.Configuration.Tasks.SetObjectTaskBase`2.PrepareDataObje ct() at Microsoft.Exchange.Management.SystemConfigurationTasks.SetMailboxServer.Pr epareDataObject() at Microsoft.Exchange.Configuration.Tasks.SetTaskBase`1.InternalValidate() at Microsoft.Exchange.Configuration.Tasks.SetSystemConfigurationObjectTask`3. InternalValidate() at Microsoft.Exchange.Management.SystemConfigurationTasks.SetMailboxServer.In ternalValidate() at Microsoft.Exchange.Configuration.Tasks.Task.b__b() at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String fun cName, Action func, Boolean terminatePipelineIfFailed)". The Exchange Server setup operation didn't complete. More details can be found in ExchangeSetup.log located in the :\ExchangeSetupLogs folder.

Posted by: DogMan - 06 January 2026 10:58:20
It is because you did not perform the domainprep and org prep with the original software - you used the service pack version instead and it has created phantom orgs that have no backbone.