|
Home > Archive > MS SQL Server DTS > March 2006 > Execution of Job Failed - SSIS Package
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Execution of Job Failed - SSIS Package
|
|
| MattODA 2006-03-26, 8:27 pm |
| Hi, I have a SSIS package that executes a SQL Task.
It does a simple insert to a table. It works in the BIDS.
When I deploy to SQL Server (same machine) it fails to execute the SQL Agent
Job
I have tried as many combinations of sa vs windows authentication, file vs
server deployement as i could think of.
I must be missing something simple.
?
What method should i used to see what caused the failure? The history logs
stop at the fail of the job. I would like to see why the Execute SQL Task of
the package failed.
? I'm guessing this is a permissions issue since it works in the dev
environment. Is there a sample Hello World package available that I can use
to test?
Thanks
| |
| privatenews 2006-03-27, 3:28 am |
| Hello,
You could check the sqlagent.out under %programfiles%\micro
soft sql
server\mssql.1\mssql\log. Also, you could edit step property of the job to
output the job failure to a output file.
If you installed SQL 2005 samples, you could find SSIS sample include
executeSQLsatement samples.
To troubleshoot the issue, you may want to change the job owner to a user
with SQL server admin role. Also, you may want to change SQL agent service
account to a user with local admin rights to test.
Best Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
====================
====================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
>Thread-Topic: Execution of Job Failed - SSIS Package
>thread-index: AcZRKi26hWtbjQyXS1Cs
uLKhYm0VjQ==
>X-WBNR-Posting-Host: 66.78.74.98
>From: =?Utf-8?B?TWF0dE9EQQ==?= <mattoda@newsgroup.nospam>
>Subject: Execution of Job Failed - SSIS Package
>Date: Sun, 26 Mar 2006 15:08:22 -0800
>Lines: 17
>Message-ID: <3AA0F71D-00B2-4AEB-8910- FFFA96D14238@microso
ft.com>
>MIME-Version: 1.0
>Content-Type: text/plain;
> charset="Utf-8"
>Content-Transfer-Encoding: 7bit
>X-Newsreader: Microsoft CDO for Windows 2000
>Content-Class: urn:content-classes:message
>Importance: normal
>Priority: normal
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830
>Newsgroups: microsoft.public.sqlserver.dts
>NNTP-Posting-Host: TK2MSFTNGXA02.phx.gbl 10.40.2.250
>Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA02.phx.gbl
>Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.dts:64713
>X-Tomcat-NG: microsoft.public.sqlserver.dts
>
>Hi, I have a SSIS package that executes a SQL Task.
>It does a simple insert to a table. It works in the BIDS.
>When I deploy to SQL Server (same machine) it fails to execute the SQL
Agent
>Job
>I have tried as many combinations of sa vs windows authentication, file vs
>server deployement as i could think of.
>I must be missing something simple.
>?
>What method should i used to see what caused the failure? The history logs
>stop at the fail of the job. I would like to see why the Execute SQL Task
of
>the package failed.
>? I'm guessing this is a permissions issue since it works in the dev
>environment. Is there a sample Hello World package available that I can
use
>to test?
>
>Thanks
>
>
|
|
|
|
|