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




To determine wich account was used by SQL Agent :
- On Entreprise Manager, Management, Deploy SQL Agent node
- Right Click on SQL Agent and choose properties

You can change the account SQL Agent will be used

SP4 fixes a bug on scheduled job (http://support.microsoft.com/kb/825042/)
Now, a non-syadmin user could run schedule DTS

So it's resolved your issue

------
Philip


"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: SQL account rights
    ... Please advice what is the best, suitable rights rather than domain admin ... Warren Brunk - MCITP - SQL 2005, ... Add it as a login to the SQL Server ... files, or backups, make sure that the service account has Full ...
    (microsoft.public.sqlserver.security)
  • Re: User authentication
    ... There are 2 SQL Server 2005 ... 1 SQL Server 2000 installed on another server ... Windows account instead to run backup jobs. ...
    (microsoft.public.sqlserver.clients)
  • Re: SQL 2000 Server gets hacked
    ... Thank you Beth. ... > placed a strong password on the 'sa' account?) ... Your SQl Service itself shouldn't be running as a ... (SQL Agent requires more, but not SQL Server). ...
    (microsoft.public.sqlserver.security)
  • Re: SQL 2000 Server gets hacked
    ... Thank you Beth. ... > placed a strong password on the 'sa' account?) ... Your SQl Service itself shouldn't be running as a ... (SQL Agent requires more, but not SQL Server). ...
    (microsoft.public.sqlserver.security)
  • Re: Microsoft Search service cannot be administered under the present user error SP3
    ... - Have not modified Administrator account, but i ran the SQL script anyway. ... SQL account is not a local administrator. ... > has this server ever been upgrade from SQL Server 7.0 or is this SQL ...
    (microsoft.public.sqlserver.setup)