RE: Running SSIS Package using a scheduled Job in SQL2005

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

This article should help:

918760 - An SSIS package does not run when you call the SSIS
package from a SQL Server Agent job step
http://support.microsoft.com/?kbid=918760

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
SQL troubleshooting: http://sql.veranoest.net
___ please respond in newsgroup, NOT by private email ___

=?Utf-8?B?TWFuanVuYXRoIEJhc3J1cg==?=
<ManjunathBasrur@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote on 24 maj 2006
in microsoft.public.sqlserver.tools:

Thanks for your reply Tom. I checked in the "Services". The
Logon for the SQL Agent Service is "Local Machine". Now, does
that mean I have to use Windows Authentication only for all the
connecctions I use within the SSIS Package? if not then what
ammendments do I make to ensure that SQL Authentications works
fine.

Let me know your thoughts.

Thanks!
Manjunath Basrur

"TomT" wrote:

What account is used for your SQL Agent service? I believe that
is the account under which the job will be run.....

"Manjunath Basrur" wrote:

Hi, I have created a SSIS package. The connection used in the
SSIS is SQL Authenticated. This runs perfectly when executed
even after it is deployed. However, I face problems when I
want to execute this package as a job. The error I get is -
"Login failed for user - <user name>".

While creating a step as part of the job, if i select the
"Package Soruce" as "SSIS Package Soruce", then the SQL
Authentication option is disabled. I am forced to use Windows
Authentication.

However, I have noticed that if I use Windows Authentication
through out, i.e. when i create the connection within SSIS
Package, while deploying the SSIS package and while creating
the step in the Job, all goes fine. Unfortunately, this is
not what i want. All the connections should be SQL
Authenticated as against Windows Authentication.

Please help! Thanks!
Manjunath Basrur
.

Relevant Pages

  • Re: Authentication
    ... available are Windows authentication only or mixed mode. ... else how can enforce SQL authentication only!!!!! ... Though you can't disable the mechanism for Windows authentication, ... the right to connect to SQL Server - you have to explicitly allow this ...
    (comp.databases.ms-sqlserver)
  • Re: NT authentication vs. SQL auth
    ... During a recent data migration from a SQL 6.5 db to a SQL ... about 1 hour and 10 minutes using SQL authentication. ... >information and pass it back to SQL Server. ... >sense that Windows Authentication is more demanding, ...
    (microsoft.public.sqlserver.security)
  • Re: Login failed for ServerGuest
    ... You can enable the guest account but that's a security risk ... For SQL ... although Windows Authentication is more secure than ...
    (microsoft.public.sqlserver.connect)
  • Re: IIS Webservice + SQL 2008
    ... Windows Authentication is enabled. ... When I change something in sql from ... webservice same thing happens. ...
    (microsoft.public.inetserver.iis.security)
  • Re: How can I avoid using SQL Authentication with the Office Web Parts?
    ... authenticate via another authentication protocol to the backend ... SQL server. ... We are using Office Web Parts on several Web Part pages to display data retrieved from a SQL Server ...
    (microsoft.public.office.developer.web.components)