AppVolumes: Missing roles after fresh installation [EN version]
Symptoms: In a new installation of VMware AppVolumes Manager, the roles are missing after the end of the installation. The dropdown menu in the initial configuration for assigning the administrator role is empty. In the SQL Server database for the AppVolumes Manager it can be seen that the table dbo.rbac_roles is empty.
This appears to be a very rare issue according to VMware.
Our configuration is as follows:
- Manager: Windows Server 2019, (4 vCPUs, 8GB RAM, 80GB NVME disk, ODBC driver 17).
- SQL Server: Dedicated Microsoft SQL Server 2019 Standard on Windows Server 2019.
This issue occurs with DB_owner and sysadmin permissions. All other tables have valid data.
A workaround to manually populate the dbo.rbac_roles table with the necessary records. The following records are present in the database in 6 columns
Administrators Perform all operations, including the permissions of additional
administrators. 1 2018-11-05 20:26:06.200 2018-11-05 20:26:06.200
2 Administrators (Read only) View, but not modify, all configuration settings, logs and user created objects. 1 2018-11-05 20:26:06.280 2018-11-05 20:26:06.280
3 Security Administrators Manage roles and privileges, including the permissions of additional administrators. 1 2018-11-05 20:26:06.297 2018-11-05 20:26:06.297
4 AppStacks Administrators Perform operations related to AppStack objects. View everything except configuration. 1 2018-11-05 20:26:06.403 2018-11-05 20:26:06.403
5 Writables Administrators Perform operations related to Writable Volume objects. View everything except configuration. 1 2018-11-05 20:26:06.497 2018-11-05 20:26:06.497
With the following SQL statement the roles can be created in the database:
ID is the primary key. This can be omitted, so that MS SQL itself assigns an ID.
INSERT INTO dbo.rbac_roles
VALUES ('Administrators','Perform all operations, including the permissions of additional administrators.',1,GETDATE(),GETDATE());
This should be repeated until all roles are integrated. It should be noted that this is a workaround. The issue is currently in analysis between me and VMware support.