Symptoms

Large Package Causes PandD To Throw Exception (600+ Artifacts)
 

Diagnoses

While creating packages from your development environment you encounter an exception in the PandD thick client.

On average creating a package with "Include Dependencies" checked will take 20-25 minutes and include ~750 artifacts.

Partway through package creation the attached exception is thrown. The user is able to select OK and the creation continues however, intermittently we see packages that only include 2 or 3 artifacts in the tree-view but then the "Items to be packaged" shows a number around 750. In these cases we will abandon the package creation and start afresh.


1. On the occasions that the package is created. What affect does this exception have? Is this a known issue? Is it possible to safely continue deployment?
2. Are there any known workarounds? If possible we could split the package up, however as there are such a high number of artifacts with complex interdependence it's difficult to create a package in this way. be available for remote sessions if this is required.

 

Resolution

The best option here would be to look to split up the package to allow the deployment of the entire solution to be smoother. 750 artifacts being deployed at one will cause strain on the server and to other applications too.