Hi everyone,
I'm launching this thread as I don't find the solution by myself.
Vmware support is in mode best effort as the products are EOL. - I understand - The priorities are not always where they should
Context:
1 AD domain
1 Vcenter 5.5 for Desktops with co-hosting view composer (Windows Machine) member of AD domain
1 SQL server member of the AD domain
8 Connection servers members of the AD domain
5 Security Servers members of the AD domain.
All this components are running View 5.3 (Yes, I know 🙂 , Old stuff!!! )
Because the old SQL servers showed us some instabilities, I've decided to move the Vcenter and composer DB to a fresh installed SQL server.
To limit the impact on the application I decided to keep the same version of SQL on both DB servers.
Tipically, I kept the same SQL credentials between the 2 DB servers to easy the migration (local user on SQL with same login and password).
The users exist in SQL and Windows with no user mapping.
EventDBs have been migrated also on the newer server.
Problem:
As detailed in the thread title, since the migration, the pools for linked clones are not editable anymore.
Error message: Invalid value for parameter dgId passed to View Composer function
Troubleshooting:
Initial procedure found the the DB migration: VMware Knowledge Base
KB followed for the troubleshooting:
I've cleaned up all inconsistencies that I found in ADAM databases of the Connection Servers as well as those located in the SQL database.
I also ran several times on the Connection Servers the tool viewdbcheck.cmd
As a next step in the Troubleshooting process, I investigate the usage of sviconfig tool on the composer server.
Guys, if you have ideas, yours are welcome,
Thanks for the help,
Problem solved, problem linked with the initial setup.
Vcomposer (active) tables and Vcenter tables are in the same DB 😞
Another Vcomposer DB was created with table structure and no data in it... I still don't get it.
Needed to adapt the ODBC configuration.
The ODBC was pointing to the blank tables
Next step is to upgrade this environment!
Problem solved, problem linked with the initial setup.
Vcomposer (active) tables and Vcenter tables are in the same DB 😞
Another Vcomposer DB was created with table structure and no data in it... I still don't get it.
Needed to adapt the ODBC configuration.
The ODBC was pointing to the blank tables
Next step is to upgrade this environment!