I am also getting this error and it is definitely because we renamed what VMware is calling the "tablespaces" to match the different sites. We have HQ and DR. The HQ SQL cluster replicates to the DR site SQL cluster, the DR SQL cluster also has a few production databases for SRM and vCenter.
So the problem we have with this "hard-coded" policy is that with SQL replication, it replicates the tables, not just the database.
I'm stuck. I need the tablespace names different so both vCenters do not cross or misplace data when the replication happens (plus it's vital that they be on seperate tables)
Soooooo... my question is, can i have the single sign on service on BOTH vCenter servers pointing to ONE database? Leaving vCenter's DB's alone (along with SRM's, VUM and everything else) so that i can still replicate, plus install the "manditory" service just to get vCenter upgraded?
Has anyone had this issue? What was the work around? I will be calling VMware in the morning, but in the mean time i have to get vcenter upgraded in order to get SRM working again..