12-08-2026, 09:48 PM
Hello,
Recently got the OK to update our old ASG 2019 environment to a current version, I originally setup the original one (vRD2011inclPatch3) and migrated it to 2019 (vRD2019 v12.0.6261.1)
We use SQL servers, and they are handled by our DBA group, so I cannot poke at anything there, they provided a new DB to me (called RocketRD) and advised they mirrored the permissions of the old DB to the new one.
Ive asked if they can send me a screenshot of the permissions..still waiting for it.
It was discussed and decided we would not migrate the DB, we want to start fresh, with a new layout and fix lessons learned over the years.
Ive fired up a new Windows 11 VM to test the client side, after launching as Admin and entering the new environment (1st pic below) I get an error (2nd pic), Im guessing its a SQL permission issue? (which is why I asked the DBA for a screenshot)
Ive looked through the 'Working with Environments' and a few of the recent threads with Patch3 issues, but havent found anything related to my issue.
Anything different in setting up the DB environment in 2026 version ?
Thanks!
Recently got the OK to update our old ASG 2019 environment to a current version, I originally setup the original one (vRD2011inclPatch3) and migrated it to 2019 (vRD2019 v12.0.6261.1)
We use SQL servers, and they are handled by our DBA group, so I cannot poke at anything there, they provided a new DB to me (called RocketRD) and advised they mirrored the permissions of the old DB to the new one.
Ive asked if they can send me a screenshot of the permissions..still waiting for it.
It was discussed and decided we would not migrate the DB, we want to start fresh, with a new layout and fix lessons learned over the years.
Ive fired up a new Windows 11 VM to test the client side, after launching as Admin and entering the new environment (1st pic below) I get an error (2nd pic), Im guessing its a SQL permission issue? (which is why I asked the DBA for a screenshot)
Ive looked through the 'Working with Environments' and a few of the recent threads with Patch3 issues, but havent found anything related to my issue.
Anything different in setting up the DB environment in 2026 version ?
Thanks!

