There are few places to change in the database and registry when renaming the vault. You should probably involve your VAR with help doing this, however here's what I know as we often copy over the production database and rename it by appending the word "Test" to the end. This is so can clients can have both vault views on their machine for testing purposes.
So try searching the registry for the Vault root name. Also search on the actual database name.
When you copy your production database and rename it, do the EPDM email notifications correctly reflect the new vault name?
I believe this is controlled by the VaultName column in the FileVaults table of the ConisioMasterDb, make sure that got changed.
Yes, that was the first thing I changed after duplicating the vault.
I have searched the DBs and the registry fby Vault ID and Vault Name and cannot find anything. I will have to contact our VAR.
1. Run a Search in registry for you old Vault Name
2. Check ConisioMasterDB's FileVaults Table
3. Check Archiveservers table in your new Vault Db
4. Check Systeminfo Table in your New Vault Db
OK, spoke to my VAR and they sent me KB solution S-08640, which clearly documents how to rename a file vault. I had done everything in the document accept run the SQL query listed. For furture reference, use SQL Server Management Studio and execute the following query in the new database:
ALTER TABLE Projects DISABLE TRIGGER OnUpdateProjectTrigger
SET Name = 'NewVaultName'
WHERE ProjectID = 1
ALTER TABLE Projects ENABLE TRIGGER OnUpdateProjectTrigger
After successfully running the query, subsequent email notifications that were sent for documents awaiting approval reflected the new vault name in the link and the link also successfully opened the document.
It is also worth following the additional steps in S-08640 to have a general tidy-up as well, i.e. get rid of old or non-existent vault names.