installing Exchange Step 6 of 13: Mailbox role: Transport Service - Object(EXCH) couldn't be found

%3CLINGO-SUB%20id%3D%22lingo-sub-199931%22%20slang%3D%22en-US%22%3Einstalling%20Exchange%20Step%206%20of%2013%3A%20Mailbox%20role%3A%20Transport%20Service%20-%20Object(EXCH)%20couldn't%20be%20found%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-199931%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20All%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThis%20might%20be%20a%20long%20shot.%3C%2FP%3E%3CP%3E%3CBR%20%2F%3EI'm%20trying%20to%20install%20exchange%202016%20in%20a%20test%20environment.%3C%2FP%3E%3CP%3EI%20have%20already%20encountered%20many%20error%20messages%20and%20I%20have%20succeeded%20in%20solving%20these.%20It%20only%20seems%20that%20I%20do%20not%20get%20this%20solved.%3C%2FP%3E%3CP%3EI%20get%20the%20following%20error%20message%3A%3C%2FP%3E%3CP%3EError%3A%3C%2FP%3E%3CP%3E%3CEM%3EThe%20following%20error%20was%20generated%20when%20%22%24error.Clear()%3B%3C%2FEM%3E%3C%2FP%3E%3CP%3E%3CEM%3E%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20set-ExchangeServerRole%20-Identity%20%24RoleFqdnOrName%20-IsHubTransportServer%3A%24true%20-DomainController%20%24RoleDomainController%3C%2FEM%3E%3C%2FP%3E%3CP%3E%3CEM%3E%26nbsp%3B%3C%2FEM%3E%3C%2FP%3E%3CP%3E%3CEM%3E%22%20was%20run%3A%20%22Microsoft.Exchange.Configuration.Tasks.ManagementObjectNotFoundException%3A%20The%20operation%20couldn't%20be%20performed%20because%20object%20'LCL-TST-EXCH-01.BASWLOCAL.local'%20couldn't%20be%20found%20on%20'LCL-TST-SBS-01.BASWLOCAL.local'.%3C%2FEM%3E%3C%2FP%3E%3CP%3E%3CEM%3E%26nbsp%3B%26nbsp%3B%20at%20Microsoft.Exchange.Configuration.Tasks.DataAccessTask%601.GetDataObject%5BTObject%5D(IIdentityParameter%20id%2C%20IConfigDataProvider%20session%2C%20ObjectId%20rootID%2C%20OptionalIdentityData%20optionalData%2C%20Func%602%20notFoundError%2C%20Func%602%20multipleFoundError%2C%20ExchangeErrorCategory%20errorCategory)%3C%2FEM%3E%3C%2FP%3E%3CP%3E%3CEM%3E%26nbsp%3B%26nbsp%3B%20at%20Microsoft.Exchange.Configuration.Tasks.SetObjectWithIdentityTaskBase%603.ResolveDataObject()%3C%2FEM%3E%3C%2FP%3E%3CP%3E%3CEM%3E%26nbsp%3B%20%26nbsp%3Bat%20Microsoft.Exchange.Configuration.Tasks.SetSystemConfigurationObjectTask%603.ResolveDataObject()%3C%2FEM%3E%3C%2FP%3E%3CP%3E%3CEM%3E%26nbsp%3B%26nbsp%3B%20at%20Microsoft.Exchange.Configuration.Tasks.SetObjectTaskBase%602.PrepareDataObject()%3C%2FEM%3E%3C%2FP%3E%3CP%3E%3CEM%3E%26nbsp%3B%26nbsp%3B%20at%20Microsoft.Exchange.Configuration.Tasks.SetTaskBase%601.InternalValidate()%3C%2FEM%3E%3C%2FP%3E%3CP%3E%3CEM%3E%26nbsp%3B%26nbsp%3B%20at%20Microsoft.Exchange.Configuration.Tasks.SetSystemConfigurationObjectTask%603.InternalValidate()%3C%2FEM%3E%3C%2FP%3E%3CP%3E%3CEM%3E%26nbsp%3B%26nbsp%3B%20at%20Microsoft.Exchange.Configuration.Tasks.Task.%3CPROCESSRECORD%3Eb__91_1()%3C%2FPROCESSRECORD%3E%3C%2FEM%3E%3C%2FP%3E%3CP%3E%3CEM%3E%26nbsp%3B%26nbsp%3B%20at%20Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String%20funcName%2C%20Action%20func%2C%20Boolean%20terminatePipelineIfFailed)%22.%3C%2FEM%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20infrastructure%20is%3C%2FP%3E%3CP%3E1%20DC%3A%20LCL-TST-SBS-01.BASWLOCAL.local%3C%2FP%3E%3CP%3E1%20Exchange%20Server%3A%20LCL-TST-EXCH-01.BASWLOCAL.local.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20underlying%20story%20is%20that%20I%20have%20installed%20a%20SBS%20server%20in%20Hyper-v%20on%20my%20windows%2010%20device%20and%20made%20a%20clone%20of%20it%2C%20and%20thus%20transformed%20it%20into%20the%20Exchange%20server.%20So%20the%20Exchange%20server%20was%20first%20a%20DC%20with%20exactly%20the%20same%20domain%20etc...%20I%20then%20demote%20it%20and%20joined%20the%20domain%20of%20DC%201.%3C%2FP%3E%3CP%3EI%20think%20the%20problem%20has%20to%20do%20with%20demoting%20it%20as%20a%20DC%20with%20the%20exact%20same%20domain..%20hence%20the%20'long%20shot'.%3C%2FP%3E%3CP%3EPerhaps%20there%20is%20someone%20here%20who%20has%20run%20into%20this%20too%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-199931%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3E2016%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EExchange%20Server%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Highlighted
Contributor

Hi All,

 

This might be a long shot.


I'm trying to install exchange 2016 in a test environment.

I have already encountered many error messages and I have succeeded in solving these. It only seems that I do not get this solved.

I get the following error message:

Error:

The following error was generated when "$error.Clear();

               set-ExchangeServerRole -Identity $RoleFqdnOrName -IsHubTransportServer:$true -DomainController $RoleDomainController

 

" was run: "Microsoft.Exchange.Configuration.Tasks.ManagementObjectNotFoundException: The operation couldn't be performed because object 'LCL-TST-EXCH-01.BASWLOCAL.local' couldn't be found on 'LCL-TST-SBS-01.BASWLOCAL.local'.

   at Microsoft.Exchange.Configuration.Tasks.DataAccessTask`1.GetDataObject[TObject](IIdentityParameter id, IConfigDataProvider session, ObjectId rootID, OptionalIdentityData optionalData, Func`2 notFoundError, Func`2 multipleFoundError, ExchangeErrorCategory errorCategory)

   at Microsoft.Exchange.Configuration.Tasks.SetObjectWithIdentityTaskBase`3.ResolveDataObject()

   at Microsoft.Exchange.Configuration.Tasks.SetSystemConfigurationObjectTask`3.ResolveDataObject()

   at Microsoft.Exchange.Configuration.Tasks.SetObjectTaskBase`2.PrepareDataObject()

   at Microsoft.Exchange.Configuration.Tasks.SetTaskBase`1.InternalValidate()

   at Microsoft.Exchange.Configuration.Tasks.SetSystemConfigurationObjectTask`3.InternalValidate()

   at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__91_1()

   at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".

 

The infrastructure is

1 DC: LCL-TST-SBS-01.BASWLOCAL.local

1 Exchange Server: LCL-TST-EXCH-01.BASWLOCAL.local.

 

The underlying story is that I have installed a SBS server in Hyper-v on my windows 10 device and made a clone of it, and thus transformed it into the Exchange server. So the Exchange server was first a DC with exactly the same domain etc... I then demote it and joined the domain of DC 1.

I think the problem has to do with demoting it as a DC with the exact same domain.. hence the 'long shot'.

Perhaps there is someone here who has run into this too?

0 Replies