- Message 50001, Level 1, State 50001
--XPSQL.CPP: Error 87 From GetProxyaccount (10405)
Open SQLServer's Enterprise Manager, enter "Manage", right-click the "SQL Server Agent" click attribute;
First you have to "allow users to do cmdexec ...", then specify an account.
However, you need to be aware of the security of this existence.
About English reply:
You don't have to use a domain account. When Go INTO The "Job System" Properties on your SQL Agent, Click The "reset proxy account". It will ask you for a new user / password and domain. For the domain Just Put The name of the local server (of course, That Account Has To Exist on The Local Server).
Also, I'm Sure you know what the risk is by allowing non-sydmins the Ability to execute xp_cmdshell ....
You can use the following statement to get the account used by the current agent:
EXEC MASTER.DBO.XP_SQLAGENT_PROXY_ACCOUNT N'GET '
You can use the following statement to set the account used by the current agent:
EXEC MASTER.DBO.XP_SQLAGENT_PROXY_ACCOUNT N'SET ', N' Domain Name, N 'Account Name, N' Password '
It generally indicates that either the SQL Agent account isnot a local admin account so it can not access the informationon the proxy account or you have not set up a proxy account You can execute the following to get the proxy account:. Exec master. dbo.xp_sqlagent_proxy_account N'GET'If it does not return anything, you need to create the proxyaccount.You can set the proxy account with: exec master.dbo.xp_sqlagent_proxy_account N'SET ', N'DomainName', N'UserName ' N'Password '
Message 50001, Level 1, State 50001
Xpsql.cpp: Error 1326 from Logonuserw (620)
