We're having problems referencing a secondary archive collective member programmatically using the PI AF SDK because of a persistent alias pointing from the secondary archive to the primary archive. We've deleted the alias in AboutPI-SDK and from the AFSDK.Config file, but the alias reappears in AboutPI-SDK shortly after deleting it.
Are there any other locations where the alias might be stored that is causing it to repopulate?