Status: Closed (View Workflow)
Affects Version/s: 5.2.0 GA
Fix Version/s: 5.3.0 GA
To duplicate the problem:
1. create a vdb (say VDB1)
2. right mouse click on vdb, select "Refactor==>Rename"
3. enter the new name of the vdb (say VDB2)
4. deploy the vdb
5. try to connect to vdb "VDB2" and it doesn't exist, because the server thinks the name is still VDB1.
This is because the internal vdb.xml file was not updated on the rename action.
Resolution: delete vdb and recreate a new one.