Exchange 2010 install Failure "an Item with the same key has already been added"

Have you had a server with the same name in your domain before?

Try changing the name of the server to something else and then reinstall.

Jeff
TechSoEasy

FYI, if that doesn't work, run the pre-deployment analyzer and it should tell you where the problem is:
http://www.microsoft.com/en-us/download/details.aspx?id=11636

Jeff
TechSoEasy

Thank you for the reply.

I did rename the server to an original name after uninstalling Exchange, And the same thing still happened.

I will re-run the pre deployment analyzer, and respond.

I ran it, no errors, everything came back clean.

Just to verify, you said there is a GC in your environment... is DC1 that GC? or is it another DC?

Jeff

Yes, that server is a GC.

I completely rebuilt the server from scratch yesterday. Gave it a new name, and still have that issue.

same error.

MY AD is very clean, no issues.

Ok, since you've had some unsuccessful installs, please check your existing Exchange Server for references to those in the registry on this key:
HKLM\Software\Exchange and HKLM\Software\Exchange Server keys

Reference: http://windowsitpro.com/exchange-server/how-uninstall-stubborn-exchange-server

Also, before starting the install, be sure the NGEN service is running and not disabled (on your new server).

Jeff
TechSoEasy

there were four NGEN services, two were disabled by default. I enabled them and set them to automatic,

No change,

I could not find references to this server, in the registry of my other exchange servers.
I found no references in the registry of the server i was installing on.

Then please post an updated install log.

Thanks.

Jeff

I am attaching the exchangesetup.log from the last install.
ExchangeSetup.log

How many other Exchange Servers do you have?  Is there a DAG which you are trying to add an additional mailbox server to?

Jeff

There is no DAG, yet, I was hoping at some point this new server would be used for that.

Right now there are three Exchange servers, in addition to the one I am trying to add, Names are as follows:

mf-xch1   -mailbox role only
mf-xch2   -cas, hub transport
mf-xch3   -cas, hub transport

The one I am trying to add was called

mf-xchdb1 -mailbox role only

I actually see it in the Exchange management console, but am unable to do anything with it, such as create a new mailbox DB.

Well, that's a completely different issue than not being able to install the server at all.

After installing it, because you have multiple DC's you need to be sure that AD replication has occurred.  Because when you attempt to create a new DB, the new server may try to authenticate the other DC which doesn't know it exists yet.

Jeff

The install does essentially fail. It literally said unsuccessfull.

If i look in the EMC, under server configuration I do see the server. But if i try to add a mailbox database to it, i recieve the following: Microsoft Exchange Critical Error 0x716a2b43.

the addtional information is as follows:

 at Microsoft.Exchange.Configuration.MonadDataProvider.MonadPipelineProxy.ClosePipeline(MonadAsyncResult asyncResult)
   at Microsoft.Exchange.Configuration.MonadDataProvider.MonadPipelineProxy.InternalEndInvoke(IAsyncResult results)
   at Microsoft.PowerShell.HostingTools.PipelineProxyBase.EndInvoke(IAsyncResult results)
   at Microsoft.Exchange.Configuration.MonadDataProvider.MonadCommand.EndExecute(MonadAsyncResult asyncResult)
   at Microsoft.Exchange.Configuration.MonadDataProvider.MonadCommand.Execute(WorkUnit[] workUnits)
   at Microsoft.Exchange.Management.SystemManager.WinForms.SingleTaskDataHandler.OnSaveData()
   at Microsoft.Exchange.Management.SystemManager.WinForms.SingleTaskDataHandler.OnSaveData(CommandInteractionHandler interactionHandler)
   at Microsoft.Exchange.Management.SystemManager.WinForms.DataHandler.Save(CommandInteractionHandler interactionHandler)
   at Microsoft.Exchange.Management.SystemManager.WinForms.DataHandler.OnSaveData(CommandInteractionHandler interactionHandler)
   at Microsoft.Exchange.Management.SystemManager.WinForms.

At this point, I would HIGHLY suggest that you open a support case with Microsoft.  Generally they do not charge for installation issues -- at least it doesn't hurt if you ask them for a free support call.

Jeff

I will be opening a case with MS. I will post the solution, once I know what it is.

So, Apparently when the first 3 servers in this organization were installed (by my predecessor) there was a bunch of replication errors at the time.

I was on the phone with Microsoft for hours, they did get it working by cleaning up some legacy objects created by the replication errors.

I think bottom line is if you have this issue, call MS. :/

I've requested that this question be closed as follows:

Accepted answer: 0 points for sattermc's comment #a39851361

for the following reason:

Ended up calling MS.

I've requested that this question be closed as follows:

Ended up calling Microsoft.

They stated, that during the initial install of the first three original exchange servers by my predecessor, there must have been replication problems which caused duplicate exchange objects in AD, which prevented the installation of further mailbox servers.

Really?  A C Grade!?!?

You had a problem and asked for advice -- I gave you the absolute best advice possible which ended up resolving your problem.  A C grade is really unwarranted here.

It was not a reflection on your advice, I was grading the overall solution, which was to make a $259.00 call MS.

If anything it is a reflection on general vagueness of MS error logs, as they didn't really point to a solution at all, that either one of us could find.

You are taking this personal, and you shouldn't be, as i appreciate all help I've ever received from anyone anywhere,

If you wish to file a complaint with the site, I will gladly give it whatever grade you feel is warranted. it does not appear i can alter it at this point.

Thanks mo.

@sattermc:  "You are taking this personal, and you shouldn't be"  -- actually the grading system is VERY personal.  You are giving ME a grade on how I handled the problem.

I fully understand your frustration with not being able to identify the exact problem, but since all network environments are unique unto themselves (ie, yours had legacy issues from a former administrator), it is often the BEST option to get the Microsoft Support Team involved.  You've been struggling with this issue for over a week without resolution -- while you were on the phone with them for "hours" -- if they had not assisted you may have spent many more hours trying to fix it -- wasting much more than $259.00 worth of your own time.

Jeff

Whatever you guys think is best..