Error: Parameter name collection during Edge Transport import process

Share this:

If you are using the built-in scripts to clone Edge Transport configuration in Exchange Server 2013 you may encounter this following error when running ImportEdgeConfig.ps1 on the target server.

WARNING: An unexpected error has occurred and a Watson dump is being generated: Value cannot be null.

Parameter Name: collection

Importing Edge configuration information Failed.

Reason: Value cannot be null.

Parameter name: collection


The issue can be seen in the figure below, and for this Tutorial we are using Exchange Server 2013 CU6 running on top of Windows Server 2012 R2.


A simple solution is to remove the line <SupervisionTags>$null</SupervisionTags> from the XML exported from the source server. This error is caused because the Set-TransportConfig cmdlet does not allow the attribute SupervisionTags to be $null.


After removing the line and saving the file we can rerun the operation and this time the importing process will succeed, as shown in the figure below.



In this Tutorial we went over an importation error using the ImportEdgeConfig.ps1 and we show one possible solution to fix such issue.

Written by Anderson Patricio

Anderson Patricio

Anderson Patricio is a Canadian MVP in Cloud and Datacenter Management, and Office Server and Services, besides the Microsoft Award he also holds a Solutions Master (MCSM) in Exchange and several other certifications. Anderson has been contributing to the Microsoft Community with articles, tutorials, blog posts, twitter, forums and book reviews. He is a regular contributor here at,, and Anderson (Portuguese).

Related Post

Exchange Server 2013 CU3 Available for download Hello there! Microsoft Exchange Team has just released the Exchange Server 2013 CU3. Cumulative Update 3 for Exchange Server 2013 resolves issues th...
How to … avoid Outlook Certificate issues when add... When adding a new Exchange server to the organization the administrator may receive some complaining  from the Service Desk where end-users are receiv...
Error creating a DAG without AAP in Exchange Serve... In this post we are going over the error “Some or all identity references could not be translated” or “A server-side administrative operation has fail...
IMAP inaccessible on Exchange Server 2013 If you are experiencing an issue where the IMAP clients are not able to connect on the Exchange Server 2013/2016 server, and when trying to telnet the...