April 25, 2008 at 7:09 am
My staff and I have been working on the following issue for several days now:
Our SQL Server services are configured to run under an account we'll call SQLSERVICES.
1) We create a package to drop and create a table (this package will do much more, but we kept it simple during troubleshooting).
2) We then create a job to run the package.
3) The job fails unless the following criteria have been met:
a) We are logged into SQL Server Management Studio using SQLSERVICES account
b) We create the package and job to use the SQLSERVICES account as it will not work even as sa
Occasionally, we'll receive an error that the client does not have the appropriate credentials, but generally receive only "job failed at step 1". The log files do not provide any other useful information. The job fails even if we use a proxy account that uses the SQLSERVICES credentials. This job even fails when using my account which is both a SQL Server System Admin and has full Admin rights on the server itself.
Thanks in advance for your assistance.
Jim
"Everything needs more cow bell!"
April 25, 2008 at 7:13 am
Hi Jim,
The account that runs the SQL Server Agent will need approiate permissions to run the job sucessfully. If not then it will fail.
Hope this helps
Gethyn
Gethyn Elliswww.gethynellis.com
April 25, 2008 at 7:24 am
Thanks for the quick reply, but...
The job fails unless I login as SQLSERVICES, create the job as SQLSERVICES, and run the job while logged in as SQLSERVICES.
It will not run if I create the package or job while logged in with any other account, including my own, which has full admin rights. This includes the sa account.
For example, I log into SSMS with the sa account. I create the package and configure it to use SQLSERVICES. I then create a job and configure it use SQLSERVICES. When I run the job, it fails.
Jim
"Everything needs more cow bell!"
April 25, 2008 at 8:59 am
The service account that runs the SQL Server Agent...is that the same as the SQL Server Account? For the job to run successfully the users that runs the agent will need the neccessary permissions
Gethyn Elliswww.gethynellis.com
April 25, 2008 at 9:41 am
Hello all,
Here is the problem and I cannot find a definite answer on the web.
I created an SSIS package on my development environment. I want to create a job and schedule it on the production SQL Server 2005. I cannot do this successfully as there is/are permission problems. I was wondering if anybody can give a step by step example on how to do this. I do have access to the account that runs the SQL Serve Agent. It is a domain account that has admin rights on the SQL Server 2005 server and also SA privledges in SQL Server 2005. I am not an admin nor do I have admin rights or SA rights on the SQL Server 2005. I want to take the package I create locally and run it in a scheduled job on the SQL Server 2005. An easy scenerio would be to drop a table and recreate. Keep in mind the package is being created on a different computer than the SQL Server 2005 resides. Any help would be much appreciated. If more information is needed, I will provide what I can. Thank you in advance. :unsure:
Frank Adams
Viewing 5 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply