Need Adventureworks 2014 DW SSIS Packages

Hi All,
I want Analyse the design of Adventure works 2014 Data Warehouse from Adventure works 2014 DB(OLTP).
If any have or any one have link to download SSIS Packages/Project, Could you please share it or Can you guys please suggest me to build SSIS Packages from Adventure works 2014 DB to Adventure works 2014 Data Warehouse.
Thanks in Advance,
Kareem

You can download packages while installing SQL Server
C:\Program Files\Microsoft SQL Server\100\Samples\Integration Services\Package Samples\
I don't think AdeventureWorkDW2014 packages are available for download but you can design your own. Consider reading below books:
Kimball- Micosoft Data Warehouse DW toolkit
Professional
Micorosft SQL Server 2014 Integration Services
You can always refer older version SSIS packages for best practices and practice because the basic table structure and views are same.

Similar Messages

Need help on executing ssis package from ssrs report

i want to develop a load test tool.
we do load test on beta servers i need to capture server statistics during load test and make a report out of it.
basically as a tool to start and stop capturing server info from ssrs report.
Any help is highly appreciated !!

Whats the need of a report for starting and stopping of jobs here? Isnt it enough to capture the details from MSDB system tables or SSISDB tables (in case of 2012) for capturing the details. The package execution can be done using procedures/t-sql scripts
using sp_start_job or catalog.create_execution procedure
http://msdn.microsoft.com/en-us/library/ff878034.aspx
Please Mark This As Answer if it helps to solve the issue Visakh ---------------------------- http://visakhm.blogspot.com/ https://www.facebook.com/VmBlogs

How to insert CLEAR SSIS Package in another SSIS Package

Hi All,
We have a requirement to run CLEAR SSIS Package in another SSIS Package whish extracts data from Oracle database system. Needed to run CLEAR SSIS Package if data exists in BPC application else run extract to Oracle system. Basically continue with SSIS Package and extract to Oracle system.
In Outlooksoft 4.2 we didn't have any issue, since all evModify is going to be in DTS Package and we didn't have any issues in placing a condition connection to CLEAR Package. Basically we were running CLEAR Package inside anther DTS Package twice successfully.
When we tried to create same functionality in SAP BPC 5.1, the code from EVMODIFY not doing correctly in executing the CLEAR inside another SSIS Package.
If any body knows how to create SSIS Package with a combination of 2 or more SSIS Packages by taking above scenario, please let me know.
The basic requirement is, how do we include a SSIS Package in another SSIS Package and use EVMODIFY to run this meta package in SAP BPC 5.1 environment.
Any information would be appreciated.
Regards,
Sreekanth.

Yes, I have the job , and tried running this, Looks like it started executing. Will update in next 5 mins if it runs fine.
Looking at the command it generated, it looks like it is setting few more parameters like LoggingLevel, Synchronized , callerInfo etc.. I believe these should be optional right?
Also now I have to set two Parameters out of 10 parameters the project takes, If I add additional /Par Project.starttime , will the package pick the values passed from this prompt?
/ISSERVER "\"\SSISDB\FFF\PPP\Xpackage2.dtsx\"" /SERVER "\".\"" /Par "\"$ServerOption::LOGGING_LEVEL(Int16)\"";1 /Par "\"$ServerOption::SYNCHRONIZED(Boolean)\"";True /CALLERINFO SQLAGENT /REPORTING E

To configure SSIS packages out of these SQL Server Standard, Web and Workgroup editions which is preferred?

Hi All,
To configure SSIS packages out of these SQL Server Standard, Web and Workgroup editions which is preferred?
Grateful to your time and support. Regards, Shiva

Hi Shiva,
SSIS designer and runtime, basic transforms, and data profiling tools are only supported by Standard and higher editions. Besides, some advanced SSIS adapters such as High performance Oracle/Teradata destination and Dimension processing destination adapter
are only supported in Enterprise edition. So, if you need to develop/modify SSIS packages on this server, Standard or even Enterprise editor is recommended.
Reference:
http://msdn.microsoft.com/en-us/library/cc645993.aspx#SSIS
Regards,
Mike Yin
TechNet Community Support

Execute the SSIS packages (2008 version) using SQL job 2008

We need to execute the SSIS packages (2008 version) using SQL job Please help with details information how to execute it.
1.Protection level of the SSIS packages.
2.Configuration File (Curently using XML file)
3.Please provide details how to create Credential (Windows User etc) Do we need to create windows cred explicitly to run the Job etc..
4.Please provide details for creating Proxy.
5.How can we configure the xml file since the xml is reading from local box but when the package is moved from developement box to production box
then the local drive might not be mapped with Production box .
6.Roles that need to be tagged for the Proxy/Credential.
7.Which is the best and safest way to execute ssis packages either msdb deployment or filesystem deployment and other necessary details.

Hi,
If you want to Execute your SSIS package using SQL job then best solution is to first deploy your Package
either using msdb deployment or filesystem deployment.The simplest approach to deployment is probably to deploy to the file system.
So, here is the deployment steps;
There are four steps in the package deployment process:
    The first optional step is optional and involves creating package
configurations that update properties of package elements at run time. The configurations are automatically included when you deploy the packages.
    The second step is to build the Integration Services project to create a package deployment utility. The deployment utility for the project contains the packages that you want to deploy
    The third step is to copy the deployment folder that was created when you built the Integration Services project to the target computer.
    The fourth step is to run, on the target computer, the Package Installation Wizard to install the packages to the file system or to an instance of SQL Server.
you can use below link also;
http://bharath-msbi.blogspot.in/2012/04/step-by-step-ssis-package-deployment.html
After that you need to Schedule package using SQL Agent then Have a look at the following link. It explains how to create an SQL job that can execute an SSIS package on a scheduled basis.
http://www.mssqltips.com/sqlservertutorial/220/scheduling-ssis-packages-with-sql-server-agent/
Deployment in msdb deployment or filesystem deployment has there own merits and demerits.
For security point of view msdb deployment is good.
it provides Benefits from database security, roles and Agent interaction
Protection Level;
In SQL Server Data Tools (SSDT), open the Integration Services project that contains the package.
Open the package in the SSIS designer.
If the Properties window does not show the properties of the package, click the design surface.
In the Properties window, in the Security group, select the appropriate value for the
ProtectionLevel property.
If you select a protection level that requires a password, enter the password as the value of the
PackagePassword property.
On the File menu, select Save Selected Items to save the modified package.
SSIS Provide different Protection levels;
    DontSaveSensitive
    EncryptSensitiveWithUserKey
    EncryptSensitiveWithPassword
    EncryptAllWithPassword
    EncryptAllWithUserKey
    ServerStorage
For better undertsnading you can use below link;
http://www.mssqltips.com/sqlservertip/2091/securing-your-ssis-packages-using-package-protection-level/
Thanks

Updating dimension with SSIS Package

Hello there, I have a dimension thats basically taking all the rows of two other dimensions, but it needs to b updated frequently. I need to build a SSIS package that can do this. Its easy to build one that updates the SQL table, but how to make those changes appear on BPC Admin side??? I tried updating both mbr and dim tables but nothing seems to work. please advise. thanks.

Hi,
You need to update your mbr table ONLY, and then add a BPC task called "Admin Task" to your package and choose the "Process Dimension" option. In any case, from your SSIS package, your dimension should be processed, and your application as well.
This process is moving members from the "mbr" table into the "dim" table.
After that, when relogging to BPC, your changes should be reflected.
Hope this helps.
Kind Regards,
Patrick

Unexpected Termination SSIS package - Issue with SSIS packages after upgrading to SQL Server 2014

Hello everyone.
We performed an upgrade of SQL Server 2012 installation to SQL Server 2014 (with last CU5 update). We found that all SSIS packages (even the simplest with just Execute SQL tasks) fail with Unexpected termination message. The issue reproduces with both new
packages (that are created from scratch with SSDT 2014) and old packages (migrated from SQL 2012).
Any ideas, please? We googled and found that it is a known issue that should have fixed with CU4. But we use CU5 and the issue is still here.
MCP

Hi. Yes...
- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="SQLISServer" />
<EventID Qualifiers="0">1</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2015-02-12T07:41:56.000000000Z" />
<EventRecordID>469950</EventRecordID>
<Channel>Application</Channel>
<Computer>abtru1a11.oneabbott.com</Computer>
<Security />
</System>
- <EventData>
<Data>The SSIS Execution Process could not write to the IS catalog: ABTRU1A11\DEV:SSISDB Error details: Cannot find the symmetric key 'MS_Enckey_Proj_Param_5', because it does not exist or you do not have permission.; at System.Data.SqlClient.SqlConnection.OnError(SqlException
exception, Boolean breakConnection, Action`1 wrapCloseInAction) at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose) at System.Data.SqlClient.TdsParser.TryRun(RunBehavior
runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady) at System.Data.SqlClient.SqlDataReader.TryConsumeMetaData() at System.Data.SqlClient.SqlDataReader.get_MetaData()
at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString) at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream,
Boolean async, Int32 timeout, Task& task, Boolean asyncWrite, SqlDataReader ds) at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, TaskCompletionSource`1 completion,
Int32 timeout, Task& task, Boolean asyncWrite) at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method) at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior
behavior, String method) at System.Data.SqlClient.SqlCommand.ExecuteReader() at Microsoft.SqlServer.IntegrationServices.Server.Shared.ExecutionParameterLoader.GetExecutionParameter() at Microsoft.SqlServer.IntegrationServices.Server.ISServerExec.ProjectOperator.StartPackage()
at Microsoft.SqlServer.IntegrationServices.Server.ISServerExec.ProjectOperator.PerformOperation()</Data>
</EventData>
</Event>
MCP

SSIS packages are failing after upgrade to SQL server 2014

Hi,
I have some SSIS packages running on SQL server 2012 .
After I upgraded to SQL server to 2014 from 2012 , the SSIS jobs are failing on the SQL agent.
And i can see its related to Data source connectivity to the SQL agent. I hope it not able to identify the connection manager in SQL agent. And connection adapter is not upgraded.
I read some articles about this and they say it not able to connect to SQL server agent job.
And, I can see that the package is running if i run manually using SQL 2012 run time.
Why its not running on SQL 2014 ?
did i miss anything while upgrading SQL server 2014 ?
Please give me some suggestions to solve this issue.
And is there any way i can change the SQL server agent 2014 to adapt this and run ?
Below is the error :
The Package filed to load due to error 0XC00100014 " One or more error occurres. There should be more specific errors preceding this one that expalins the details of the erroes. This message is used as a return value from functions that encounter
errors.: This occures when CPackage::LoadFormXML fails.
Regards,
Vinodh Selvaraj.

I think you have typed this error message by yourself.
Anyway, as it says there should be more error preceeding to this. Do you have any other errors which describles the exact issue stating at what task it fails?
If not, then there are various reasons behind this issue. 3rd party connection manager such as Oracle Attunity or it may be 32/64 bit issue.
You may try executing package in 32 bit mode from SQL Agent Job.
Please refer:
http://blogs.msdn.com/b/farukcelik/archive/2010/06/16/why-package-load-error-0xc0010014-in-cpackage-loadfromxml-error-appears-while-trying-to-run-an-ssis-package.aspx
http://www.bidn.com/blogs/timmurphy/ssas/1397/package-failed-to-load-due-to-error-0xc0010014
-Vaibhav Chaudhari

Error running SSIS package to do with encrypting/decrypting password. Help needed.

Getting this error. Can anyone shed some light? This is the first promote since 2009. Protection level of the package is 'EncryptSensitiveWithPassword' I'm new at SSIS so don't assume I know anything.
10/30/2014 16:11:06,HPAddress_Export,Error,0,SSQLTST01\SSQLTST02,HPAddress_Export,(Job outcome),,The job failed.
The Job was invoked by User AHCCCS\Administrator. The last step to run was step 1 (Step 1).,00:00:02,0,0,,,,0
10/30/2014 16:11:06,HPAddress_Export,Error,1,SSQLTST01\SSQLTST02,HPAddress_Export,Step 1,,Executed as user: AHCCCS\svcssqltst01. ....00.5324.00 for 32-bit
Copyright (C) Microsoft Corp 1984-2005. All rights reserved.
Started: 4:11:06 PM Error: 2014-10-30 16:11:07.05
Code: 0xC001405F     Source:
Description: Failed to decrypt an encrypted XML node because the password was not specified or not correct. Package load will attempt to continue without the encrypted information.
End Error Error: 2014-10-30 16:11:07.37
Code: 0xC001405F     Source:
Description: Failed to decrypt an encrypted XML node because the password was not specified or not correct. Package load will attempt to continue without the encrypted information.
End Error Error: 2014-10-30 16:11:07.79
Code: 0xC0202009     Source: HPAddress_ExportPackage Connection manager "SQL.HealthPlanAddressChanges.hpac"
Description: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80040E4D.
An OLE DB record is available. Source: "Micros...
The package execution fa... The step failed.,00:00:02,0,0,,,,0

Hi,
From the error message “Failed to decrypt an encrypted XML node because the password was not specified or not correct. Package load will attempt to continue without the encrypted information.“, it seems that the error is caused by the password to decrypt
an encrypted XML node was not specified or incorrect.
Besides, the EncryptSensitiveWithPassword Protection level means user should use a password to encrypt only the values of sensitive properties in the package. To open the package in SSIS Designer, the user must provide the package password. If the password
is not provided, the package opens without the sensitive data and the current user must provide new values for sensitive data. If the user tries to execute the package without providing the password, package execution fails.
So in order to resolve this issue, we should provide the password when executing the package. When you execute a package with this setting using DTEXEC, you can specify the password on the command line using the /Decrypt password command line argument.
Reference:
Access Control for Sensitive Data in Packages
Securing Your SSIS Packages Using Package Protection Level
Thanks,
Katherine Xiong
Katherine Xiong
TechNet Community Support

Need help on ssis package xml using query

I have used this reference
http://sqlblog.com/blogs/peter_debetta/archive/2006/07/13/Using-XML-Data-Type-Methods-to-query-SSIS-Packages.aspx
I'm able to achieve packagename, taskname, tasktype,parentnodename,childnodename,level,currentnode,childnode,configurationtype.
Problem - My Package consists of half a dozen sql task & data flow tasks in a single container. After execution of tasks in container, it will call package. Each data flow task consists of source & destination as well, which are not part of the below
table. I also want to know which source & destination will fall under which tasktype?
How do I establish under which taskType which TaskType will come? I want to know relationship between tasktype. How can I figure it out which task will come, under that what will be other task? From level field, I can only find at which level but not able
to figure it out which tasktype. Is it possible can I get 1 and 1.1. and 1.1.1.1 and 2 and 2.1 and...under each object subobjects will be identified in this way.
Note: I have entered only few rows.
Microsoft.SqlServer.Dt.Tasks.Execute....=Microsoft.SqlServer.Dts.Tasks.ExecuteSQLTask.ExecuteSQLTask, Microsoft.SqlServer.SQLTask, Version=10.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91
Packagename
Taskname
TaskType
ParentNodeName
NodeName
level
CurrentNode
ChildNode
ConfigurationType
test1
Tax_m
SSIS.Pckage.2
Tax_m
1
some xml
some xml
test1
Seq_Tax_m
STOCK.SEQUENCE
Tax_m
Seq_Tax_m
2
some xml
some xml
test1
Ept_Tax_m
SSIS.ExecutePackageTask2
Tax_m
Ept_Tax_m
2
some xml
test1
Sql_valid_key_Tax_m
Microsoft.SqlServer.Dt.Tasks.Execute....
Seq_Tax_m
Sql_valid_key_Tax_m
3
some xml
test1
Sql_Dst_Del_Tax_m
Microsoft.SqlServer.Dt.Tasks.Execute....
Seq_Tax_m
Sql_Dst_Del_Tax_m
3
some xml
test1
Dft_Tax_M
SSIS.Pipeline.2
Seq_Tax_m
Dft_Tax_M
3
some xml
test1
Sql_valid_key_TL_m
Microsoft.SqlServer.Dt.Tasks.Execute....
Seq_Tax_m
Sql_valid_key_TL_m
3
some xml
test1
Sql_Dst_Del_TL_m
Microsoft.SqlServer.Dt.Tasks.Execute....
Seq_Tax_m
Sql_Dst_Del_TL_m
3
some xml
test1
Sql_valid_key_TM_m
Microsoft.SqlServer.Dt.Tasks.Execute....
Seq_Tax_m
Sql_valid_key_TM_m
3
some xml
test1
Sql_valid_key_TC_m
Microsoft.SqlServer.Dt.Tasks.Execute....
Seq_Tax_m
Sql_valid_key_TC_m
3
some xml
test1
Sql_Dst_Del_TM_m
Microsoft.SqlServer.Dt.Tasks.Execute....
Seq_Tax_m
Sql_Dst_Del_TM_m
3
some xml
test1
Dft_TL_M
SSIS.Pipeline.2
Seq_Tax_m
Dft_TL_M
3
some xml

I am moving it to SSIS.
Kalman Toth Database & OLAP Architect
SQL Server 2014 Database Design
New Book / Kindle: Beginner Database Design & SQL Programming Using Microsoft SQL Server 2014

Unable to upgrade SSIS packages to SQL Server 2014

Hi there,
I'm trying to upgrade our SSIS packages from SQL Server 2012 to 2014 (in Visual Studio 2013). The wizard pops up the minute the project loads and I leave everything to default.
It errors immediately though on almost every package with the following error:
Error 0xc001000e: MyPackage: The connection "{5F69F91E-8CD7-49A7-A76A-815244411037}" is not found. This error is thrown by Connections collection when the specific connection element is not found.
That connection is a project connection manager and most definitely exists. In fact, I can open the individual package and it upgrades it for me and the package is completely fine. It seems to me that the upgrade wizard has a bug whereby it doesn't
look for project connection managers.
Any help would be greatly appreciated, otherwise I might just post it to connect as a bug.

I was able to fix it using the following steps:
Open project, "Upgrade Package Wizard" opens automatically
Select all packages, click next, some packages will fail. Ignore them, close wizard.
Open every package. A message says "Package was upgraded" for each package.
Save every package, save solution, close solution
Open the solution again. This time no "Upgrade Wizard" opens, upgrade was successful
Deploy the solution to SSIS server (my project already had package configuration)
This is what worked for me, I hope it'll help others.

SSIS Package : Needs SQL Tables get refreshed every hour

Hello,
I have created a SSIS Package which includes,
Step 1 : Using Execute SQL Task to truncate all the tables
Step 2 : Data Flow Tasks to extract data from SharePoint lists and fill the SQL Tables for SSRS Reporting from that.
Requirement is to refresh SQL Tables every hour. I can do this using SQL Server Agent Job to run SSIS Package.
But, I am not sure is this the feasible way of do this, as we are truncating all the tables. There are around 10-15 tables. Database size is also not large.
Is there any in SSIS to impose only changes done in the SharePoint list to SQL tables rather than truncating them and creating new ones?
Thank you,
Mittal.

@Visakh,
Yes I am getting Created,CreatedBy, Modified, ModifiedBy audit fields data from all the SharePoint List.
So, can we just trust these fields and update tables accordingly ?
And how can I do this using SSIS ? Is there any particular control I can use to compare the data and time and update the SQL Tables?
Thank you,
Mittal.
Yes. Provided they have proper data thiat should work fine.
Yes you can use it inside SSIS
You can have a logic like below
1. In execute sql task capture max date for the source table
2. Use data flow task with source query having filter based on date field
ie like
WHERE Modified > ?
And map parameter to maxdate
3. add destination step to populate data
Please Mark This As Answer if it helps to solve the issue Visakh ---------------------------- http://visakhm.blogspot.com/ https://www.facebook.com/VmBlogs

Not able to run the SSIS package in SQL Server Agent Job in SQL 2012

Hi,
I scheduled a job (SQL SERVER AGENT) which will call my SSIS package. This package will execute 5 packages in loop.
When I execute this job I am getting error as below
============================================================
Started  : 12:30:19 PM
Error  : 2014-01-23 12:30:20.37
Code  : 0xC00220EC
Source  : Execute Package Task
Description : Error 0x80070005. Failed to create an instance of empty child package.
    The Distributed Component Object Model (DCOM) configuration or the installation of SQL Server Integration Services,
    may be corrupted on your machine. End Error
Error  : 2014-01-23 12:30:20.37
Code  : 0xC00220DE
Source  : Execute Package Task
Description : Error 0x80070005 while loading package file "D:\SSIS\RetailMobileApp\Staging_Pkg\stg_Category_Master.dtsx". Access is denied.End Error
DTExec  : The package execution returned DTSER_FAILURE (1).
Started  : 12:30:19 PM
Finished : 12:30:20 PM
Elapsed  : 1.123 seconds.
The package execution failed.
The step failed.
============================================================
In the STEPS I have selected as follows:
Type : SQL Server Integration Services Package
Run as: SQL Server Agent Service Account
Package Source: File System
What config I need to check here ? This job is not able to access the package stored in the folder.
Sridhar

Thanks for your reply. I had created credentials and used this while creating the Proxy account. With the Proxy account I am able to execute the Job Successfully. Concern here is I used my NT account to create this Proxy. Suppose If I left from the
current project if some one is coming to this project later they need to change the credential with their NT account and run the JOB? Is this right way or we an create any other account in common? If so how?
Sridhar

SSIS package with OData connection - can't connect

I need to read some data from a SP list. I have the OData connection manager setup. When I test the connection to my sharepoint site, it says it's successful. I added in a data flow task and then an OData Source. In the OData Source editor, I select the
Odata connection manager. I want to use a collection. However, it says "Unable to load collection for the connection Odata Source, reason: Cannot open this connection"
Anybody know how to resolve this?

Hi kayla,
Just as you said, the current
SharePoint List Adapter that extracting and loading SharePoint Data in SQL Server Integration Services supports x86/x64 systems using SQL 2005 / SQL 2008 / SQL 2008 R2/ SQL 2012. It doesn’t support SQL 2014. Maybe we need waiting the update.
The
OData Source component can be used to read data from SharePoint lists in SSIS 2014. Please download and install the 64 bit ODataSourceForSQLServer2014-amd64.msi or 32 bit ODataSourceForSQLServer2014-x86.msi from the
Microsoft® SQL Server® 2014 Feature Pack.
Reference:
Tutorial: Using the OData Source
Using the SSIS OData Source Connector to read data from SharePoint lists
If there are any other questions, please feel free to ask.
Thanks,
Katherine Xiong
If you have any feedback on our support, please click
here.
Katherine Xiong
TechNet Community Support
Hi Katherine,
I did install that already. I added the OData source to my SSIS package. The odata connection manager successfully connects to the sharepoint site. However, when I use the data source in the Odata Source within the Data Flow, it gives me the "cannot
open this connection" in the Collection list within the Odata source editor. I'm stumped as to why the connection manager has a successful test connection, but the collections don't pull up. Does the list need some special permissions? I'm able to access
it directly on the sharepoint site and add items (the odata connection manager is running with my windows credentials)

Unable to run SSIS Package using Stored Procedure

Hi Guys,
        I have create one simple SSIS Package(Move the first table record to second table).It will execute fine in locally.
But, If i'm going call/execute .dtsx file using stored procedure. I'm getting Error. so please let me know the valuable solution.
My Package Path : D:\Temp\SSIS_TESTING\TESTSSIS\TESTSSIS\Package.dtsx
Stored Procedure
================
CREATE PROCEDURE SPEXECUTESSISPACKAGE
@FILEPATH VARCHAR(8000)
,@STATUS VARCHAR(500) = NULL OUTPUT
AS
BEGIN
DECLARE @SQLQUERY VARCHAR(8000)
DECLARE @STATUSCODE INT
SET @SQLQUERY = 'DTEXEC /FILE "'+ @FILEPATH +'"'
SELECT @SQLQUERY AS 'SSIS FULL PATH'
EXEC @STATUSCODE = master..xp_cmdshell @SQLQUERY
SELECT @STATUSCODE AS 'STATUSCODE'
IF @STATUSCODE <> 0
BEGIN
SET @STATUS = 'PACAKGE EXECUTE FAILED'
PRINT @STATUS
END
ELSE
BEGIN
SET @STATUS = 'PACAKGE EXECUTE SUCCESS'
PRINT @STATUS
END
END
GO
RUN
============================================================================
EXEC SPEXECUTESSISPACKAGE 'D:\Temp\SSIS_TESTING\TESTSSIS\TESTSSIS\Package.dtsx', NULL
Error
=============================================================================
Microsoft (R) SQL Server Execute Package Utility
Version 9.00.4035.00 for 32-bit
Copyright (C) Microsoft Corp 1984-2005. All rights reserved.
NULL
Started: 5:06:26 AM
Error: 2014-11-14 05:06:26.07
   Code: 0xC0011007
   Source: {1244CD18-F96A-4DAD-8FC2-35F794015CA1}
   Description: Unable to load the package as XML because of package does not have a valid XML format. A specific XML parser error will be posted.
End Error
Error: 2014-11-14 05:06:26.07
   Code: 0xC0011002
   Source: {1244CD18-F96A-4DAD-8FC2-35F794015CA1}
   Description: Failed to open package file "D:\Temp\SSIS_TESTING\TESTSSIS\TESTSSIS\Package.dtsx" due to error 0x80070003 "The system cannot find the path specified.". This happens when loading a package and the file cannot
be opened or loaded correctly
into the XML document. This can be the result of either providing an incorrect file name was specified when calling LoadPackage or the XML file was specified and has an incorrect format.
End Error
Could not load package "D:\Temp\SSIS_TESTING\TESTSSIS\TESTSSIS\Package.dtsx" because of error 0xC0011002.
Description: Failed to open package file "D:\Temp\SSIS_TESTING\TESTSSIS\TESTSSIS\Package.dtsx" due to error 0x80070003 "The system cannot find the path specified.". This happens when loading a package and the file cannot be opened
or loaded correctly int
o the XML document. This can be the result of either providing an incorrect file name was specified when calling LoadPackage or the XML file was specified and has an incorrect format.
Source: {1244CD18-F96A-4DAD-8FC2-35F794015CA1}
Started: 5:06:26 AM
Finished: 5:06:26 AM
Elapsed: 0.047 seconds
NULL
I'm getting Execte SSIS Package Status : 4
===================================
4

Two things to check
1. The account executing the package has access to the path. If package is stored in different server you need to pass the UNC path (ie like \\machinename\...)
2. Make sure the version of SSIS service is the same in both the servers ie where package is created/stored and where its getting executed. A lower version SSIS service will not be able to load and execute higher version package and it will throw you similar
error messages as you posted above.
Please Mark This As Answer if it solved your issue
Please Mark This As Helpful if it helps to solve your issue
Visakh
My MSDN Page
My Personal Blog
My Facebook Page

Need Adventureworks 2014 DW SSIS Packages

Similar Messages

Maybe you are looking for