我们目前有一个SQL Server 2012作业因帐户锁定而无法执行。 在事件查看器中找到的消息如下:
SQL错误:被引用的帐户当前被锁定并可能未被登录。
SQL代理运行一个本地帐户并验证它当前没有被锁定在服务器上的System Admin中。 还确认帐户未锁定在SQL Server框中。 SQL Server作业运行一个SSIS包。 如果我自己运行SSIS包,那么作业就会执行得很好。 当它通过作业执行时,它会失败。
有没有其他人有一个SQL Server作业神秘的帐户锁定问题?
We currently have a SQL Server 2012 job that fails to execute because of an account lock out. The message found within the Event Viewer is the following:
SQL Error: The referenced account is currently locked out and may not be logged on to.
The SQL Agent runs a local account and have verified it is not currently locked out within System Admin on the server. Have also verified that account is not locked out on the SQL Server box. The SQL Server job runs a SSIS package. If I run the SSIS package by itself the job will execute just fine. It is when it is executed via the job that it fails.
Has anyone else had a mysterious account locking problem with a SQL Server Job?
最满意答案
遵循以下步骤:
右键单击SQL代理作业名称 - >查看历史记录 - >检查错误。 它给出了出错的确切细节。 通过SQL代理的SSIS作业需要代理帐户,其中包含SQL Server登录凭据。 因此Security - > Credentials并更新用户名和密码。 一旦完成,确保它反映在代理(SQL Server代理 - > Proxies - > SSIS Package Execution 。 确保在Security - > Login下添加引用的帐户Follow below steps:
Right click sql agent job name -> view history -> check error. It gives exact details of what has gone wrong. SSIS Jobs via SQL Agent needs proxy account, which contains credentials of SQL Server login. Hence Security -> Credentials and update the username and password. Once done, make sure it is reflected in Proxy (SQL Server Agent -> Proxies -> SSIS Package Execution. Make sure the referenced account is added under Security -> Login更多推荐
发布评论