Skip to Content (Press Enter)
2018-06-01 14-37-59
Rebecca Hall
176Views
8Comments
Strange publishing error - lifetime
Question
Lifetime

When I try publishing I am getting the following error message:

An item with the same key has already been added. Details : System.ArgumentException: An item with the same key has already been added. at System.Collections.Generic.Dictionary`2.Insert(TKey key, TValue value, Boolean add) at #2bo.#uJk.#veo(ICompilerContext ctx, String eSpaceName, Int32 eSpaceVersionId, Boolean debugMode, ICompilerReference[] producers, String uniqueId, String username)

Any ideas how to fix this?  I didn't have problems pushing to our other environment.

/Becky
0
0
04 May 2015
Copy Link
2020-09-15 13-07-23
Kilian Hekhuis
 
MVP
Better report that to support :).
0
0
06 May 2015
Copy Link
2016-08-24 14-28-34
Cláudia Frutuoso
Staff
Hello, Rebecca,

There are some particular patterns in Lifetime in version 9.0.0+ that might cause the error you are encountering. Please contact support, they will be able to help you overcome this situation.

In order to correctly finish the deployment, you can republish the modules which had that error via Service Center (they are available on the target environment, just not correctly published) and publish a solution with all applications to clear any outdated references.

The new version, 9.0.1+ already has that situation fixed.

Best Regards,

Cláudia
0
0
07 May 2015
Copy Link
UserImage.jpg
Pravin Sable

Hello Rebecca,


Were you able to get this fixed?

thanks

Pravin

0
0
29 Aug 2016
Copy Link
2018-06-01 14-37-59
Rebecca Hall

We were never able to identify the problem.  We haven't seen the error since either.

0
0
30 Aug 2016
Copy Link
UserImage.jpg
Pravin Sable

Rebecca Hall wrote:

We were never able to identify the problem.  We haven't seen the error since either.

Thanks for replying back. We traced it back to a particular application and refresh all the references. Also, republished everything on target environment. So fix was essentially

1. Create a solution on target environment with all apps.

2. Publish running version solution on target.

3. Note down all the errors.

4. Fix non-deployment related errors on target.

5. Fix deployment related errors on source environment by refreshing references on source environment.

6. Deploy from source to target.



0
0
30 Aug 2016
Copy Link
2018-06-01 14-37-59
Rebecca Hall

We did fix some circular references so maybe references couldn't be refreshed.  We couldn't publish all of the applications on our environment because we have so manu of them.

0
0
30 Aug 2016
Copy Link
UserImage.jpg
Pravin Sable

Rebecca Hall wrote:

We did fix some circular references so maybe references couldn't be refreshed.  We couldn't publish all of the applications on our environment because we have so manu of them.

To publish all, trick is to create a solution and instead of selecting individual apps type * in seachbox. Then click associate. It will add all the applications.


0
0
30 Aug 2016
Copy Link
2018-06-01 14-37-59
Rebecca Hall

Yeah, we've done it in the past but our environment has grown too large.

0
0
31 Aug 2016
Copy Link
Community GuidelinesBe kind and respectful, give credit to the original source of content, and search for duplicates before posting.