SSIS packages are executed from buffer??

Hi,
I am passing a set of variables from parent SSIS package to child SSIS package through package configuration. 6 variables should be passed from parent to child. When I first developed this package, I accidentally omitted 2 variables. Hence only 4 were getting
passed. However, even after adding the omitted 2 variables, only 4 are getting passed to child and the rest 2 are skipped. Even if I try modifying the package configuration, I am able to see only the 4 variables that were mapped earlier.
If I export the package from server, I see that the package has latest code in it. However, I still see only 4 variables that are being mapped in the output window.
Any suggestions?

First explain how you added the two new variables inside. Did you
1. Create configurations of type parent package variable for the same
2. Make sure you mapped it to corresponding properties within child packages?
3. Try adding breakpoints and run packages in debug mode and made sure values are getting passed onto the child correctly?
Please Mark This As Answer if it helps to solve the issue Visakh ---------------------------- http://visakhm.blogspot.com/ https://www.facebook.com/VmBlogs

Similar Messages

All the SSIS Packages are not editable to the all users after deploying to the other server

Hi All,
I am using sqlserver2012.
How to make all the SSIS Packages are not editable to all users after deploying to the other server. is there any way to achieve this,
if yes, could share the information how to do....
Thanks in advance....
RamarajuC

Typically, you change the protection level as listed in the following steps:
During development, leave the protection level of packages set to the default value,
EncryptSensitiveWithUserKey. This setting helps ensure that only the developer sees sensitive values in the package. Or, you can consider using
EncryptAllWithUserKey, or DontSaveSensitive.
When it is time to deploy the packages, you have to change the protection level to one that does not depend on the developer's user key. Therefore you typically have to select
EncryptSensitiveWithPassword, or EncryptAllWithPassword. Encrypt the packages by assigning a temporary strong password that is also known to the operations team in the production environment.
After the packages have been deployed to the production environment, the operations team can re-encrypt the deployed packages by assigning a strong password that is known only to them. Or, they can encrypt the deployed packages by selecting
EncryptSensitiveWithUserKey or EncryptAllWithUserKey, and using the local credentials of the account that will run the packages.
Please Mark This As Answer or vote for Helpful Post if this helps you to solve your question/problem. http://techequation.com

Ho to find out what stored procedures and ssis packages are connecting to server(For examle: ss-cube)?

Hello Experts,
Is there any efficient way to see what stored procedures and ssis packages are connecting to server ss-cube?
Can you please help me to come across.
Thanks in advance,
Regards,
Hari

Hello Experts,
Is there any efficient way to see what stored procedures and ssis packages are connecting
to server ss-cube?
Can you please help me to come across.
Thanks in advance,
Regards,
Hari

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

How data flow when SSIS packages are run on a different server than the DB server

The scenario is that i have a dedicated SQL SErver 2014 SSIS machine that executes the packages.
The database server is a separate machine with SQL Server 2008R2.
1) Running SSIS packages that transfer data within SQL Server 2008R2 (same machine)
2) Running SSIS packages that transfer data between 2 separate SQL Server servers.
How the data flow in these two cases and what resource is being used where? (cpu,disk,ram,network)
Elias

When you have a dedicated SSIS server, all data read flows to that server, is processed using the resources of that ETL server and then sent back over the network to the destination server.
It doesn't matter if source and destination are the same server. If you use a data flow, all data flows over the network twice.
The only exception is when you don't use a data flow, but only SQL statements. In that case, data flows only between source and destination.
MCSE SQL Server 2012 - Please mark posts as answered where appropriate.

SSIS Package execution error from powershell

Hi I have written a powershell script to exec SSIS packages. I am passing variable values at runtime by reading it from a text file.
But it throws an error.
Here is my script.
#Read Data from Parameter File
$variable=Get-Content D:\Batch\Bin\ETLParameters.txt
$variable.GetType()
$dest_conn_str=$variable[1]
$mail_cc=$variable[2]
$mail_from=$variable[3]
$mail_str=$variable[4]
$mail_to=$variable[5]
$pkg_path=$variable[6]
$ps_exe_path=$variable[7]
$ps_script_cmd=$variable[8]
$ps_script_path=$variable[9]
$src_conn_str=$variable[10]
$src_sys_id=$variable[11]
#Executing SSIS packages from command prompt
$cmd = 'dtexec /f "' + $pkg_path + 'pkg_ntas_all.dtsx' + '"' + ' /SET \Package.Variables[User::src_conn_str].Properties[Value];"' + $src_conn_str + '"' + ' /SET \Package.Variables[User::dest_conn_str].Properties[Value];"'
+ $dest_conn_str + '"' + ' /SET \Package.Variables[User::src_sys_id].Properties[Value];"' + $src_sys_id + '"' + ' /SET \Package.Variables[User::pkg_file_path].Properties[Value];"' + $pkg_path + '"' +
' /SET \Package.Variables[User::mail_str].Properties[Value];"' + $mail_str + '"' + ' /SET \Package.Variables[User::mail_from].Properties[Value];"' + $mail_from + '"' + ' /SET \Package.Variables[User::mail_to].Properties[Value];"'
+ $mail_to + '"'+ ' /SET \Package.Variables[User::mail_cc].Properties[Value];"' + $mail_cc + '"' + ' /SET \Package.Variables[User::ps_exe_path].Properties[Value];"' + $ps_exe_path + '"' + ' /SET
\Package.Variables[User::ps_script_path].Properties[Value];"' + $ps_script_path + '"' + ' /SET \Package.Variables[User::ps_script_cmd].Properties[Value];"' + $ps_script_cmd + '"'
$cmd
DECLARE @returncode int
EXEC @returncode = xp_cmdshell @cmd
Types of error that I get -
If I run the $cmd directly. Which is the concatenated string of dtexec command with parameters. It doesn't do anything, not even an error and the pwoershell execution just completes.
If I use exec EXEC @returncode = xp_cmdshell @cmd    ----- Then it throws me the error that the exec is not recognized name of cmdlet.
Please help as I a noob in any kind of scripting.

I did but it just printed the entire string on the command line and assigned all the values.
PS C:\Users\dev_setup> . D:\Batch\Bin\runETL.ps1
IsPublic IsSerial Name                                     BaseType
True     True     Object[]
System.Array
dtexec /f "D:\ETL\test\test\test_ETL\pkg_all.dtsx" /SET "\Package.
Variables[User::src_conn_str].Properties[Value]";"Data Source=SOURCE1;Initial Catalog=tagtest;Provider=SAOLEDB.11;Integrated Security=SSPI;
" /SET "\Package.Variables[User::dest_conn_str].Properties[Value]";"destinationDb;User ID=FP_DEV;Password=**********;Initial Catalog=xyz;Provider=SQLOLEDB.1;Persist Security Info=True;Auto Translate=False;Packet Size=10240;" /SET " \Package.Variables[User::src_sys_id].Properties[Value]
";"100200" /SET "\Package.Variables[User::pkg_file_path].Properties[Value]";"D:\ETL\test\test\test_ETL\" /SET "\Package.Variables[User::mail_str].Properties[Value]";"SmtpServer=mailhost.test.com;UseWindowsAuthentication=False;EnableSsl=False;" /SET "\Package.Variables[User::mail_from].Properties[Value]
";"[email protected]" /SET "\Package.Variables[User::mail_to].Properties[Value]";"[email protected]" /SET "\Package.Variables[User::mail_cc].Properties[Value]";"[email protected]" /SET "\Package.Variables[User::ps_exe_path].Properties[Value]";"C:\Windows\System32\WindowsPower
Shell\v1.0\PowerShell.exe" /SET "\Package.Variables[User::ps_script_path].Properties[Value]";"D:\ETL\Powershell_Script\" /SET "\Package.Variables[User::ps_script_cmd].Properties[Value]";"create_historical_reject_file.ps1 -input_variable"
PS C:\Users\svc_sp_fp_dev_setup>
But when I just run it without passing the parameters it runs. What might be the issue.

SSIS package fails with the error as given below. But its warning messages are incorrect.

My SSIS package loads data from access database to SQL Server database.
It's a straight copy. It fails with the below warnings and error message as shown below:
Error messages:
[OLE DB Source [113]] Error: There was an error with OLE DB Source.Outputs[OLE DB Source Output].Columns[RetentionID] on OLE DB Source.Outputs[OLE DB Source Output]. The column status returned was: "Text was truncated or one or more characters had no
match in the target code page.".
[OLE DB Source [113]] Error: The "OLE DB Source.Outputs[OLE DB Source Output].Columns[RetentionID]" failed because truncation occurred, and the truncation row disposition on "OLE DB Source.Outputs[OLE DB Source Output].Columns[RetentionID]"
specifies failure on truncation. A truncation error occurred on the specified object of the specified component.
[SSIS.Pipeline] Error: SSIS Error Code DTS_E_PRIMEOUTPUTFAILED. The PrimeOutput method on OLE DB Source returned error code 0xC020902A. The component returned a failure code when the pipeline engine called PrimeOutput(). The meaning of the failure
code is defined by the component, but the error is fatal and the pipeline stopped executing. There may be error messages posted before this with more information about the failure.
There are 3 warning messages even before I run the package. Warnings are all about the mismatch between the source and destination column sizes.
I cross checked the source and destination column sizes. The destination column sizes are fairly high than the source column sizes.
It worked well all the while and when we are going to pre-prod it is throwing errors. Any help is highly appreciated.
Thank you.

It worked well all the while and when we are going to pre-prod it is throwing errors. Any help is highly appreciated.
Please check if the dev destination table has same column data types and size as compared with pre prod table
Thanks, hsbal

SQL SERVER - Error while executing SSIS package on specific environment : Connection manager - The specified module could not be found

I have deployed my SSIS packages on SQL 2008 server.
I have a .bat file which will invoke these packages and also the bat file is placed in the server where the SSIS packages are deployed.
Scenario 1:
I double clicked on the bat file to invoke the SSIS packages and ; this executed successfully
Scenario 2:
I have used the IBM Tivoli work scheduler(TWS) to invoke the bat file which in tern will invoke the ssis packges;
but when i do this i am getting the below error
Code: 0x8007007E
Source: SSIS_Master_Event_Data_Transfer Connection manager "Config DB"
Description: The specified module could not be found.
Config BD is a connection manager which will get the connection string from the config file of the SSIS package.
Please help me to resolve this issue.
Regards,
Prakash

Check you TWS jobmanrc.cmd configuration file. You may need to add a PATH environment variable in that file that includes your SQL Server file locations. When TWS jobs are executed, they may not be executing with the same
PATH variable as when you execute the SSIS outside of TWS.

SSIS package give an error if execute through SQL server agent

I have created a SSIS package in BIDS 2012. If i execute this package through sql server agent it gives the below error:
Executed as user: NT Service\SQLSERVERAGENT. Microsoft (R) SQL Server Execute Package Utility Version 11.0.2100.60 for 64-bit Copyright (C) Microsoft Corporation. All rights reserved. Started: 11:19:47 AM Error: 2015-01-20
11:19:47.83 Code: 0xC0016016 Source: Sub_Hadoop_aggregation Description: Failed to decrypt protected XML node "DTS:Password" with error 0x8009000B "Key not valid for use in specified state.".
You may not be authorized to access this information. This error occurs when there is a cryptographic error. Verify that the correct key is available. End Error Error: 2015-01-20 11:19:47.94 Code: 0xC0016016 Source:
Sub_Hadoop_aggregation Description: Failed to decrypt protected XML node "DTS:Password" with error 0x8009000B "Key not valid for use in specified state.". You may not be authorized to access this information. This error
occurs when there is a cryptographic error. Verify that the correct key is available. End Error Error: 2015-01-20 11:19:48.04 Code: 0xC0016016 Source: Sub_Hadoop_aggregation Description: Failed to
decrypt protected XML node "DTS:Password" with error 0x8009000B "Key not valid for use in specified state.". You may not be authorized to access this information. This error occurs when there is a cryptographic error. Verify that the correct
key is available. End Error Error: 2015-01-20 11:19:48.92 Code: 0xC00291EC Source: alter_keys Execute SQL Task Description: Failed to acquire connection "mstr_warehouse". Connection may not be
configured correctly or you may not have the right permissions on this connection. End Error DTExec: The package execution returned DTSER_FAILURE (1). Started: 11:19:47 AM Finished: 11:19:48 AM Elapsed: 1.42 seconds.
The package execution failed. The step failed.
so i have change some properties in our package like protectionlevel change from encrypted to dontsavesensitive. After that i have created configuration file for the package and use that configuration file. It executes the package through sql server agent
smoothly.
Thanks
Azhar Khan

Hi selfdestruct80,
According to your description, you created SSIS package and it works fine. But you got the error message when the SSIS package was called from a SQL Server Agent job.
According to my knowledge, the package may not run in the following scenarios:
The current user cannot decrypt secrets from the package.
A SQL Server connection that uses integrated security fails because the current user does not have the required permissions.
File access fails because the current user does not have the required permissions to write to the file share that the connection manager accesses.
A registry-based SSIS package configuration uses the HKEY_CURRENT_USER registry keys. The HKEY_CURRENT_USER registry keys are user-specific.
A task or a connection manager requires that the current user account has correct permissions.
According to the error message, the SSIS Package ProtectionLevel property to EncryptSensitiveWithPassword as ArthurZ mentioned. To solve the problem, you need to go to Command Line tab, manually specify the paassword in SQL Agent Job with the command like below:
/FILE "\"C:\Users\xxxx\Documents\SQL Server Management Studio\SSIS\Package.dtsx\"" /DECRYPT somepassword /CHECKPOINTING OFF /REPORTING E
If you have any more questions, please feel free to ask.
Thanks,
Wendy Fu
Wendy Fu
TechNet Community Support

Getting XML data of SSIS Package (which is located in File System) from a query

Hi,
We have around 200 SSIS packages deployed to File System. These pacakges are being scheduled using SQL Agent job.
So, currently I have a list of all the packages and their respective File Path.
Note : **They are NOT deployed to Server**.
Now, my task is to search all the packages which has a specific connection in it.
From the below blog, I got to know we can achieve this by querying the XML data of the SSIS Package.
https://www.simple-talk.com/sql/ssis/-exploring-ssis-architecture-and-execution-history-through-scripting/.
But in the above article they are getting the XML definition of the Package from msdb(as it was deployed to server).
In my requirement, SSIS Packages are in File System. Is there any way to to get the XML definition of these packages using a query.
Please let me know if the above requirement is not clear or if any further information is required.
Thanks
Raksha

Hi Visakh & Praveen,
Thanks for the response.
@Visakh: The query provided by you gives the information about all the connection strings in the package.
@Praveen: The query in the link provided by you lists the values of all the properties of the package like MaxerrorCount, CreatorName, CreatorDate and other properties.
I think, we may have to slightly modify this query to get the connection string values
Praveen, nice to hear from you after a long time and that too in this forum !! :) Hope you are doing good.
Thanks
Raksha

SSIS PACKAGE MIGRATION FROM 2005 to 2008 - Script task/component errors

HI All,
We have to migrate ssis packages (about 300) from ssis 2005 to 2008 .
1. I understand that the major concern is regarding the script component/tasks.
I searched a lot about this and also consulted with many friends , all of them are aware of this issue but not able to provide what could be the issues and the solution.
Can some one help me with the common script issues that can happen during migration and the solution for the same.
2. I do have one more question.
As per my understanding given in the below link
http://blogs.msdn.com/b/mattm/archive/2008/03/21/package-upgrade-wizard.aspx
there is this part which says ...
Once the packages have been chosen, the next page asks you to pick the output location. This can be:
Same as the source location
File System
SSIS Service (Package Store)
SQL Server
Does this mean I can deploy in sql server directly on fly while upgrading ?
Any help highly appreciated .
Regards
Praveen..

Hi Praveen,
Question 1: The error may occur if there are duplicate input columns in the Script Task/Component or the current user cannot access the C:\Windows\Temp directory. Except for the link provided by SanBhaumik, you can also refer to the following
threads:
http://www.sqlservercentral.com/Forums/Topic811208-148-1.aspx
http://social.technet.microsoft.com/Forums/sqlserver/en-US/5c11eb57-59d6-4f81-bfdc-13bd6489a0ac/sql-server-2008-ssis-package-script-component-error?forum=sqlintegrationservices
Question 2: We can directly save the package to the File System, SSIS Package Store, or SQL Server by selecting the proper destination during the package upgrade. However, this operation is not equal to the package install operation identically.
For example, if we have enabled package configurations for a package, the package configurations won’t be upgraded or installed during the package upgrade.
Regards,
Mike Yin
TechNet Community Support

[Forum FAQ] How to get SSIS packages XML definition which are stored in SQL Server Integration Services instance

Introduction
Integration Services gives you the ability to import and export packages, and by doing this change the storage format and location of packages. But after import packages into package store, how can we get the package XML definition?
Solution
As we know, SSIS packages are stored in msdb using existing SSIS storage table([msdb].[dbo].[sysssispackages]). The “packagedata” column store the actual SSIS package with Image data type. In order to get the package XML definition, we need to convert “packagedata”
column through Varbinary to XML. You can refer to the following steps:
Using the following query to get package GUID:
SELECT [name],
[id]
FROM [msdb].[dbo].[sysssispackages]
Using the following query to convert packagedata column to XML: SELECT id, CAST(CAST(packagedata AS VARBINARY(MAX)) AS XML) PackageDataXML
FROM [msdb].[dbo].[sysssispackages]
WHERE id= 'ABB264CC-A082-40D6-AEC4-DBF17FA057B2'
More Information
sysssispackages (Transact-SQL):
http://msdn.microsoft.com/en-us/library/ms181582.aspx
Applies to
SQL Server 2005
SQL Server 2008
SQL Server 2008R2
SQL Server 2012
SQL Server 2014
Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

Hi Ketak. Thank you for replying. I already followed your instructions - specifically -
You do not see the SQL Server Reporting Services service in SharePoint Central Administration after installing SQL Server 2012 SSRS in SharePoint mode
I get the following error when I run rssharepoint.msi on the APP sever (where Central Admin is installed). I have to run this other wise
Install-SPRSService and Install-SPRSServiceProxy
are not recognized as commands on that server.
Failed to call GetTypes on assembly Microsoft.AnalysisServices.SPAddin, Version=11.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91. Could not load file or assembly Microsoft.AnalysisServices.SPClient, Version=11.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91'
or one of its dependencies. The system cannot find the file specified.
macrel

Calling SSIS package from C# Windows Service Fails

Hi All.
I've got an SSIS package that reads from an Excel file and populates a database. The Excel file location gets passed in to the package as a variable. Also the Protection Level of the package is set to EncryptSensitiveWithPassword.
This all works fine when I run the package from Visual Studio or using DTEXEC. When I try to run it from a C# Windows Service though I get the following exception:
SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80004005.
An OLE DB record is available. Source: "Microsoft Office Access Database Engine" Hresult: 0x80004005 Description: "The Microsoft Office Access database engine cannot open or write to the file ''. It is already opened exclusively
by another user, or you need permission to view and write its data.".
SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager "Input Excel Connection" failed with error code 0xC0202009. There may be error messages posted before this
with more information on why the AcquireConnection method call failed.
Dedupe Worksheet failed validation and returned error code 0xC020801C.
One or more component failed validation.
There were errors during task validation.
The windows service runs with LocalSystem account and the following code is used to call the SSIS Package:
                Application app = new Application();
                Package package = null;
                app.PackagePassword = "*******";
                //Load the SSIS Package which will be executed
                package = app.LoadPackage(@"C:\Projects\DataDedupeMatch\DataDedupeMatch\DataDedupe.dtsx", null);
                //Pass the varibles into SSIS Package
                package.Variables["User::FilePath"].Value = e.FullPath.Replace(@"\\", @"\");
                Microsoft.SqlServer.Dts.Runtime.DTSExecResult results = package.Execute();
I would really appreciate if someone could help me out with this.
Thanks in advance,
Deon

Instead of hosting the SSIS runtime in your service, you should use a separate host process for your SSIS package. You're using the Office drivers, which aren't designed or supported for running in long-lived unattended processes like a Windows Service.
You can use your own SSIS hosting code, or just use dtexec.exe to host your package. In either case you would start the child process with
Process.Start.
David
David http://blogs.msdn.com/b/dbrowne/

Execute jobs running SSIS package

I'm testing a domain login that will have the permissions to run a job that will execute an SSIS package transferring data from DB123 to DB456 in SQL Server 2008.
This is what I have so far:
1) Create login with a domain test account (domain\xyz)
2) Create job with Owner as SA. SA account login is disabled.
3) Job calls an SSIS package, does not have a schedule and meant to be called from a SP from the front end app. So, essentially on demand.
4) Besides public on the databases mentioned below, domain\xyz account also has the following db permissions:
a) db_datareader, db_datawriter on DB123
b) db_datareader, db_datawriter on DB456
c) db_ssisadmin, db_ssisltduser, db_ssisoperator, SQLAgentOperatorRole, SQLAgentReaderRole, SQLAgentUserRole.
The issues:
Issue #1: When I login to SSMS as domain\xyz and execute
exec msdb..sp_start_job 'TestPermJob', I get the following errors
Msg 229, Level 14, State 5, Procedure xp_sqlagent_is_starting, Line 1
The EXECUTE permission was denied on the object 'xp_sqlagent_is_starting', database 'mssqlsystemresource', schema 'sys'.
Msg 229, Level 14, State 5, Procedure xp_sqlagent_notify, Line 1
The EXECUTE permission was denied on the object 'xp_sqlagent_notify', database 'mssqlsystemresource', schema 'sys'.
Before I start granting those permissions explicitly to a role and assign the role to the login, I thought msdb SQLAgentOperatorRole should allow the execution of jobs, doesn't it?
Issue #2: As domain\xyz, I cannot see any jobs on SQL Server Agent. Again, I thought granting msdb SQLAgentOperatorRole should be sufficient to do that.
Please help. Thanks.

Before I start granting those permissions explicitly to a role and assign the role to the login, I thought msdb SQLAgentOperatorRole should allow the execution of jobs, doesn't it?
Issue #2: As domain\xyz, I cannot see any jobs on SQL Server Agent. Again, I thought granting msdb SQLAgentOperatorRole should be sufficient to do that.
Hi Ami,
According to your description, in theory, SQLAgentOperatorRole is the most privileged of the SQL Server Agent fixed database roles. It includes all the permissions of SQLAgentUserRole and SQLAgentReaderRole. Members of this role can also view properties
for operators and proxies, and view all jobs on the server.
I do a test in SQL Server 2012, if we create a login name, and create a user for this login, then configure this user to
add a SQL Server Agent fixed database role(SQLAgentOperatorRole) under
Database role membership for: msdb.
When we login the SQL Server instance via this login name, we can check all jobs under SQL Server Agent. So I recommend you check if you
add a SQL Server Agent fixed database role successfully. For more information, you can review the following
article.
http://www.mssqltips.com/sqlservertip/1041/sql-server-agent-fixed-database-roles/
Regards,
Sofiya Li
Sofiya Li
TechNet Community Support

SSIS 2012 -Not Executing file from other server.

Hi Experts ,
I am working on SQL 2012
I have a SSIS Package -
1) Execute SQL Task - calling Storeprocedure
my StoreProcesdure contain OpenRowser Query which Pull Data from Excel and Load into SQL Table.
Scenario 1
On Development Server example IP: (10.11.12.13)- File is present in D\ExcelSource\ folder of dev server
1)My SP Run/execute successfuly on SSMS
2)MY SSIS package execute successfuly which contain above SP
Scenario 2
I have deployed SP and SSIS to production server
On Production server example IP: (10.11.12.100)- File is Still Present in D\ExcelSource\ folder of dev server
1) MY SP Execute successful on SSMS Picking file from '\\10.11.12.13\D\ExcelSource\' folder
2) SSIS Package Fails where SP is picking file from '\\10.11.12.13\D\ExcelSource\' folder
"exec [dbo].[spLoadexcelEMPdata]" failed with the following error: "Cannot initialize the data source object of OLE DB provider "Microsoft.ACE.OLEDB.12.0" for linked server "(null)".".
Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.
3)When I copy excel file from dev to prod server and Give prod server path ,then SSIS package execute Successfully
NOTE :
a)ACE.OLEDB 64 bit (2010 )driver is installed on prod server
b)Same SP execute successful in Prod SSMS
c) SSIS and SP execute successful in Dev server
I have even Share development server Folder with everyOne so that File in it is accessible
Also given Read Write permission to excel file and folder
WHY my SSIS package with SP FAIL when Picking file from dev server ??? where as same SP runs fine on SSMS
HOW to resolve this.... ?? Please assist

You just gave more valuable info...
exec [dbo].[spLoadexcelEMPdata] runs locally on the prod machine
Thing is, you have the 64 bit driver, so it might work from the package or SSDT/VS if you set them to 64 Bit mode
It is because the complete office is not necessary for OpenRowset.
I assume, you referenced the driver
OPENROWSET('Microsoft.ACE.OLEDB.12.0', 'Excel xyz.0;...
Arthur
MyBlog
Twitter

SSIS packages are executed from buffer??

Similar Messages

Maybe you are looking for