Quantcast
Channel: SQL Server Integration Services forum
Viewing all articles
Browse latest Browse all 24688

SSIS ruining from other Server

$
0
0

I have Created SSIS package using visual studio 2013 professional (SSDT) where the data are pulled from SQl Server 2008R2 (serverName\instance) in Domain 1

This package is deployed to sql server 2014 as Destination (Domain 2), with sql server 2014 server Name and instance with SSISDB path

then I have Created the JOBS Steps with

1. type:  SQL Server Integration Server Package

2. run as: SQL Server Agent Service Account

3. Package Source : SSIS Catagory

4. Server: SQL2014 server and instance

5. Package : \\..\Master.dtsx  

I get this error message in SQL 2014 server where the jobs run

Package execution on IS server failed. execution id: 194 execution Status:4 

Error Message

Date2/9/2016 6:39:05 PM
LogJob History (SSISLogistics)

Step ID1
ServerserverName\SPSQL
Job NameSSISLogistics
Step NameSSISLogistics Data Load
Duration00:00:06
Sql Severity0
Sql Message ID0
Operator Emailed
Operator Net sent
Operator Paged
Retries Attempted0

Message
Executed as user: servername\SYSTEM. Microsoft (R) SQL Server Execute Package Utility  Version 12.0.4100.1 for 64-bit  Copyright (C) Microsoft Corporation. All rights reserved.    Started:  6:39:05 PM  Package execution on IS Server failed. Execution ID: 197, Execution Status:4.  To view the details for the execution, right-click on the Integration Services Catalog, and open the [All Executions] report  Started:  6:39:05 PM  Finished: 6:39:09 PM  Elapsed:  4.125 seconds.  The package execution failed.  The step failed.




Viewing all articles
Browse latest Browse all 24688

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>