For starters this is a brand new site installation using DV 14.3.1 and Live. We first noticed issues while trying to access and make changed using DV Live Administration->Workstation Management from an operator workstation. Specifically when logged in using an administrator account that is different than what was used for the original VM creation we receive an error message stating “You do not have permission to access Workstation Management. Please contact the system administrator.”. Looking at the workstation list in DV Live Admin->Workstation Management we noticed that only the initially created, DVS VM Template, workstations are present when opened from an operator station (ProPlus and 5 operator stations created during the initial installation). This same issue was noted at the ProPlus, however after re-running workstation configuration on the ProPlus all 18 workstations now appear in the Workstation management list and multiple “admin” user accounts work on the ProPlus without the permission error stated above. Similarly running workstation configuration on the operator workstations did not correct the issues as it did for the ProPlus.
Digging into this further we noted the SQL Server (“WORKSTATION NAME”\DELTAV_INSTANCE) security->logins doesn’t contain any domain groups, only the typical service accounts, and the original admin account used to create the workstation. The ProPlus SQL Server, after re-running workstation configuration, has both the original admin account, and several domain groups. After additional evaluation it was noted that the other 13 workstations that are not visible in Workstation Management (other than from the ProPlus) also do not have an “ADDBRuntime” despite being setup from the ProPlus as DV Live enabled, and having the correct licensing. There appears to be an issue preventing the database from being created however in DeltaV Live Diagnostics the overall integrity is displayed as “Good” for all workstations. The 13 workstations not showing up were created using Emerson templates, with some created by us and some created by our local impact partner, all exhibiting the same issue.
Another thing we noted is there appears to be some inconsistencies in the SQL server name. If you look within the SQL securities->logins->[admin account]->securables it references the the server as "1431SV16\DELTAV_INSTANCE" on the ProPlus rather than by "WORKSTATION NAME"\DELTAV_INSTANCE. Similarly it on the operator stations it shows the Windows 10 template name vs. the workstation name format. We thought this could affect the synchronization, however our local SQL database admin doesn't believe this is a problem since Emerson is using SQL Server Express which apparently doesn't have native replication functionality. This leads us to believe the synchronization / replication is an Emerson devised approach, but we are unclear how the database synchronization actually works.
I should note we have an open ticket with Guardian Support, but we are looking for some outside help as we haven’t reached a solution yet. We are getting down to crunch time for rolling out our new system and really hope one of the resident experts on Emerson Exchange can assist.
-Jesse
In reply to Jesse Delanoy:
Andre Dicaire
In reply to Andre Dicaire: