A Dtrace of the mmc process during the deletion attempt will show the following:
[32128] (mmc) <24332> EV:M CAUIVaultStoreGroup::DeleteVaultStoreGroup: (Entry)
[32128] (mmc) <24332> EV:M CAUIVaultStoreGroup::get_GroupSQLServer: (Entry)
[32128] (mmc) <24332> EV:M CAUIVaultStoreGroup::get_GroupSQLServer: Leaving...
[32128] (mmc) <24332> EV~I DirectoryConnection: Function call: CVersionUpdate::NewInstallation |
[32128] (mmc) <24332> EV:L {CBaseDirectoryServiceWrapper::CreateDirectoryService} Directory Name [localhost], Try Local Service [True]
[32128] (mmc) <24332> EV:L {VaultCreateTrustedInstanceRequest::CreateLocalInstance} Successfully connected to local service
[32128] (mmc) <24332> EV:L {VaultCreateInstanceRequest::CreateInstance} CLSID [{F4D3EB5B-C7C5-11D1-90DB-0000F879BE6A} (EnterpriseVault.DirectoryService.1)] Server Name [localhost] Used Server Name [localhost] Num of attempts [1] Total elapsed [0.001s] Result [Success (0)]
[32128] (mmc) <24332> EV:L CDirectoryVaultObject::GetAttributeListFromType Unknown type - view_VaultStoreGroup_FPCDB
[32128] (mmc) <24332> EV:L {CBaseDirectoryServiceWrapper::CreateAndPopulateVaultObjectEx} Number of records [1]
[32128] (mmc) <24332> EV~I DirectoryConnection: Function call: CVersionUpdate::NewInstallation |
[32128] (mmc) <24332> EV:L {CBaseDirectoryServiceWrapper::CreateDirectoryService} Directory Name [localhost], Try Local Service [True]
[32128] (mmc) <24332> EV:L {VaultCreateTrustedInstanceRequest::CreateLocalInstance} Successfully connected to local service
[32128] (mmc) <24332> EV:L {VaultCreateInstanceRequest::CreateInstance} CLSID [{F4D3EB5B-C7C5-11D1-90DB-0000F879BE6A} (EnterpriseVault.DirectoryService.1)] Server Name [localhost] Used Server Name [localhost] Num of attempts [1] Total elapsed [0.001s] Result [Success (0)]
[32128] (mmc) <24332> EV:H {CDirectoryConnectionObject::IsDatabaseInAG} HRXEX fn trace : Error [0x80070057], [d:\builds\16\ev\v-m-s\sources\source\directory\directoryconnection\directoryconnectionobject_2.cpp, lines {4708,4717,4718}, built Aug 15 09:12:21 2017].
[32128] (mmc) <24332> EV:M CAUIVaultStoreGroup::IsVaultStoreGroupInAG Caught COM error The parameter is incorrect.
[32128] (mmc) <24332> EV:M CACVaultStoreGroup::OnConsoleVerbDelete: Leaving...
Enterprise Vault 12's support for SQL Always On Availability Groups introduced a check during Vault Store Group deletion to determine if the associated fingerprint catalogue database is in an Availability Group. This check generates an exception when run against a Vault Store Group that is not associated to any fingerprint catalogue database. If an environment has been upgraded from Enterprise Vault 2007 or earlier (which predates the Optimized Single Instance Storage (OSIS) storage model and the Vault Store Group feature), and an administrator has never run the wizard to enable sharing and create the fingerprint catalogue database for the automatically created Default Upgrade Group, then it is possible to encounter this exception when deleting the Default Upgrade Group.
Contact Technical Support for a workaround to delete the Vault Store Group.
There are currently no plans to address this issue by way of a patch or hotfix in the current or previous versions of the software at the present time. While this issue may be resolved in a future major revision of the software at a later time, it is not currently scheduled for any release. If you feel this issue has a direct business impact for you and your continued use of the product, please contact your Veritas Sales representative or the Veritas Sales group to discuss these concerns.