Re: Error running DTS package on a schedule (only!)



You can have a look at the properties of the Agent

Right Click on the SQL Server Agent icon in EM and choose properties. The
page here will tell you the account.

Have a look here

http://support.microsoft.com/?kbid=269074

--



Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP)
www.SQLDTS.com - The site for all your DTS needs.
www.SQLIS.com - You thought DTS was good. here we show you the new stuff.
www.konesans.com - Consultancy from the people who know


"Tyler" <tylerf(REMOVETHISPART)@bocafed.org> wrote in message
news:14C6F3D0-6A3D-41EC-876D-92DEC5676875@xxxxxxxxxxxxxxxx
> How do I determine which account was used to start SQL Agent?
>
> My userid is a local administrator.
> I have:
> Stopped & restarted the SQL Service Manager
> Rebooted the SQL Server 2000
> Upgraded to SP4.
>
> The problem remains.
>
> Thanks for your help.
>
> --
> Tyler
>
>
> "Philippe" wrote:
>
>>
>> "Tyler" <tylerf(REMOVETHISPART)@bocafed.org> wrote in message
>> news:A38F5285-9162-4C98-AADD-6F59800BFFCF@xxxxxxxxxxxxxxxx
>> |I created a DTS package & CAN run it (successfully) from Enterprise
>> Manager
>> | and from a command prompt.
>> |
>> | When I try to schedule a job for this DTS package under SQL Server
>> Agent
>> | Jobs it gets the following error:
>> |
>> | ATTRIBUTE_TYPES to [ThankYouAcknowledgements].[dbo].[ATTRIBUTE_TYPES]
>> Step
>> | DTSRun OnError: Copy Data from ATTRIBUTE_TYPES to
>> | [ThankYouAcknowledgements].[dbo].[ATTRIBUTE_TYPES] Step, Error =
>> | -2147467259 (80004005) Error string: [Sybase][ODBC Driver]Unable
>> to
>> | connect to database server: specified database not found Error
>> source:
>> | Microsoft OLE DB Provider for ODBC Drivers Help file: Help
>> | context: 0 Error Detail Records: Error: -2147467259
>> (80004005);
>> | Provider Error: 83 (53) Error string: [Sybase][ODBC
>> Driver]Unable
>> to
>> | conn. The step failed.
>> |
>> | Why does this package get an error ONLY when it's a scheduled job?
>> |
>> | Thanks in advance.
>> | --
>> | Tyler
>>
>>
>> Hi,
>>
>> This is a problem of security context
>>
>> - If the package is run from a command prompt by using DTSRun.exe or from
>> DTS Designer, the credentials of the currently logged-in Windows NT
>> account
>> is used
>> - If the package is run as a SQL Server Agent job, then the integrated
>> security connection is made using the account you used to start SQL Agent
>>
>> Notes :
>> if the SQL Server was started using the Local System account, the DTS
>> package has no permissions outside of the computer that is running SQL
>> Server.
>>
>> SQL Server Agent account must be a sysadmin group member.
>>
>> So, your schedule package fails because the account you use to start SQL
>> Server Agent has NOT enought rights to make a connection to your
>> database
>> server from your ODBC DSN
>>
>> Hope it's help you
>> ------
>> Philip
>>
>>
>>


.



Relevant Pages

  • Re: Scheduling a simple local package wont stick
    ... Well my domain account is the owner, and it is member of the local ... Where do I find out if this Sql server service account has the necessary ... - When you run the DTS package yourself, it runs with your credentials, ... DTS packages do not retain a schedule. ...
    (microsoft.public.sqlserver.dts)
  • Re: problem with Execute SQL Task
    ... If the owner of the job is a sysadmin then the guy executing the package is the same guy as the SQL Server Agent account. ... >>> I'm trying to use the Execute SQL Task to call up a batch store procedure>> that takes typically 1 hour to run. ...
    (microsoft.public.sqlserver.dts)
  • Re: Problems with SQL Srv. Agent and Proxy Account
    ... I have tried with both the sa account and with Use Windows ... Authentication on the SQL Server AGent Connection tab. ... >>rights recording to INF: Reset Proxy and the ...
    (microsoft.public.sqlserver.security)
  • Re: cant find directory when package scheduled as job
    ... the batch file to map the drive. ... from the DTS designer but fails when it is scheduled as a SQL Server Agent ... under my windows account and the packages executes correctly when run via ...
    (microsoft.public.sqlserver.dts)
  • Re: Problems with SQL Srv. Agent and Proxy Account
    ... You need to go to the General Tab of the SQL Server Agent ... >I have tried with both the sa account and with Use Windows ...
    (microsoft.public.sqlserver.security)