Error validating users agent execution access No registration online local chat xxx
This article details the attributes and syntax to create dynamic membership rules for users or devices.
When I created a new Credential for the new Admin account and associated it with Package Executor, I started to get the following error when I tried to run one of my SQL jobs as a test: Unable to start execution of step 1 (reason: Error authenticating proxy *Domain\Admin_Account*@*fully.qualified.domain.com*, system error: Logon failure: unknown user name or bad password.). If I'm understanding this reasonably explicit error, what it's telling me is that the Credential accounts, associated with my proxy is in correct. I know that this account is legitimate-- I've already associated it with every associated server group, I've made it a sysadmin user on the server. To be clear, I haven't mis-typed the account name or the password associated with the Proxy Credential. Resolution method #1 is what I've been doing for years.We went through all the other suggestions (checking that the password hasn't changed, switching to a local service acct for SQL Agent User, rebuilding the credentials and proxy, etc.) and until we made sure the account was a user in its default DB, for some reason, that was causing it to pass a Null SID when it was trying to authenticate to AD.In the windows event log I'm getting Logon Audit Failure with Security ID: my account, but then below Account for which Login Failed: Security ID: NULL SID.Once I updated the agent service with a valid service account(See this) and restarted it my issue was resolved.In Azure Active Directory (Azure AD), you can create advanced rules to enable complex attribute-based dynamic memberships for groups.
However, when I entered the account name and clicked the Check Names button, SQL Server automatically transformed the User ID to the fully-qualified version. The others don't seem to apply, or I'm missing something. portion, it will save/accept the credential, but when I execute the package, I get the same response as mentioned above, accept, the name of the account in the error message has changed to reflect my removal of the @