"Unable to delete the Selection List" after migrating to Backup Exec 2012
I'm having trouble with a particular server after upgrading to Backup Exec 2012. Other servers, none of which had this problem, were migrated from 2010 and 2010 R3. This one was migrated from 12.5 (on the same server.)
Due to a problem installing SQL 2005 Express during the upgrade, I had to use the manual BEMig method of migrating Backup Exec on all of our servers. This means stopping all services and backing up the Data and Catalog folders, uninstalling Backup Exec, and installing a fresh copy of 2012. Then I stop all services, copy the Data and Catalog folders back, start just the SQL service, set the registry keys to migrate the database, and run BEMig. Here is the article on this procedure:
Attached to this discussion is the log from the BEMig tool. Nothing appears out of sorts to me.
My opinion on Backup Exec's job migration process from previous versions to 2012, is that it creates such a mess that I prefer to just delete and re-add the servers. This is understandable, since Backup Exec 2012 is so different from previous versions. I'm not interested in maintaining the selection lists and backup history as much as I am interested in maintaining catalogs. Therefore, the first thing I do after migrating to Backup Exec 2012 is that I delete and re-add all of the servers and set up fresh selection lists and schedules.
On this particular server, I can't seem to do that. Whether I try to delete the server, the individual jobs, or set the selection list up from scratch and tryo to delete the job, I get the error "Unable to delete the Selection List." The backups also refuse to run in this state. The agents were successfully upgrade to the latest version, after all updates to this point in time were installed via LiveUpdate.
I have tried all of the different database functions in the BEUtility program, starting with a consistency check, repair, rebuild, compact, and age, and I have also tried re-migrating the database. I did keep a copy of the unmigrated database.
Does anyone have any fresh ideas on what I can try? Thanks!