December 24, 2010 at 8:37 am
BTW, I added this account to work with SQL Server Agent between some Linked servers I have.
December 24, 2010 at 9:40 am
For Logins from Windows accounts, no options may be specified, hence the somewhat misleading message. Correct is
CREATE LOGIN [FREEDOM\SqlAgentWorke] from WINDOWS
go
SQL = Scarcely Qualifies as a Language
December 24, 2010 at 11:39 am
Hi Carl,
Thanks for the reply. Now I have an issue with the SQL Server Agent not running. I have assigned the new user id to the SQL Agent Job (by adding the user id to the Owner field of the Job properties. "Run As" is empty. When I run this job I get the following error message from the error logs:
Date12/24/2010 1:21:10 PM
LogSQL Server (Current - 12/24/2010 1:21:00 PM)
SourceLogon
Message
Error: 18456, Severity: 14, State: 11.
I have given this new ID sysadmin Server Role. Actually I selected all the items in the Server roles box to make sure it would have the needed rights. May be overboard, but willing to cut some of those roles once I'm sure what works.
The new User ID is located on the Linked server and the main server I'm trying to access from the SQL Agent Job.
In the Linked server properties, I have added the User Id to the Security section under "Local Server login to remote server login mappings" and Impersonate is checked (No remote user or Remote Password). I didn't add any password because I'm not sure if SQL Server will recognize the Password setup for the domain account.
Do you have any suggestions?
Thanks again for you first reply. I was not sure if I'd get a reply today being its Christmas Eve. Happy Holidays.
Viewing 3 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply