Hi all,
We have a weird SQL SE issue I'm hoping someone might be able to help with.
The customer has an APP server, separate SQL server and RDS servers the users connect to. SQL SE is still in testing currently so not live, thankfully.
An active directory group called 'XRL' has been setup for the users requiring XRL access. When I try to add this into SAM I get this error
I can confirm the domain group does exist because I have added it into the SQL permissions on the SQL server already. I can also see the group if I go to update share/security permissions on a folder in Windows.
The Pegasus Opera Service is running under the Local System account on the APP server. In SQL I have added in the computer name so the APP server can access SQL data. Opera 3 SQL SE works, I can log into it and browse/amend data within it.
I've also added the SQL server name to the COMMON share.
If I change the account the Pegasus Opera Service runs under to our domain account (oasys_admin), then I can update SAM with the domain/group name, it works as you would expect. Then I can log into Opera and link the Windows user accounts to the Opera User Profiles.
If I do this then change the service back again to run under Local System, it continues to work but the Domain User dropdown in Opera is greyed out. This means we can't setup any new users for XRL.
I've set a few of these up now and I've never had this happen on any other sites. It's like there is a permissions issue with the Local System account but I have no idea what that might be.
Does anyone have any ideas?
Thanks,
Alex
