![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
Thread-Topic: Execution of Job Failed - SSIS Package thread-index: AcZRKi26hWtbjQyXS1CsuLKhYm0VjQ== X-WBNR-Posting-Host: 66.78.74.98 From: =?Utf-8?B?TWF0dE9EQQ==?= <mattoda (AT) newsgroup (DOT) 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 (AT) microsoft (DOT) 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 |
![]() |
| Thread Tools | |
| Display Modes | |
| |