SSIS 2014 and DTexec

I have developped an SSIS package running on SQL Server 2014 on Windows server 2012. When I start the package in VS 2013 environment it works fine. I deployed the package to SSISDB and tried to run it from there, still successfully. But When I tried to launch my package from dtexec with the following statement in SSMQ the below error is displayed:

EXEC xp_cmdshell 'dtexec /ISSERVER "\SSISDB\MyFolder\MyProject\PKG Sales Debit.dtsx" /SER "ServerName\Instance" '

Error Message:

Remove Batch Worksheet:Error: Executing the query "Drop Table `Batch`" failed with the following error: "Cannot modify the design of table `Batch`. It is in a read-only database" Possible failure reasons: Problens with the query, "ResultSet" property not set correctly, parameters not set correclty, or connection not established correclty.

The drop batch is an execute sql task to remove worksheet named Batch in an excel file.



February 2nd, 2015 3:36am

I was about to post a similar question where the package runs fine on VS2013 but errors when I run DTEXEC from the command prompt. 

Error:

 Code: 0xC0016020
 Source: Package
 Description: Package migration from version 8 to version 6 failed with error 0xC001700A

Free Windows Admin Tool Kit Click here and download it now
February 2nd, 2015 3:47am

I was about to post a similar question where the package runs fine on VS2013 but errors when I run DTEXEC from the command prompt. 

Error:

 Code: 0xC0016020
 Source: Package
 Description: Package migration from version 8 to version 6 failed with error 0xC001700A

Your issue is caused because you are probably trying to run the package on an older version of SQL Server.
VS2013 is for making SQL 2014 SSIS packages.
February 2nd, 2015 3:54am

VS2013 for making SQL 2014 SSIS Packages which is exactly what I am doing.
Free Windows Admin Tool Kit Click here and download it now
February 2nd, 2015 4:07am

OK, but why is your package getting downgraded?

How exactly are you trying to run the package?

February 2nd, 2015 4:18am

My package is not downgraded (this was an addition from user TheDenver). Here is my first post:

I have developped an SSIS package running on SQL Server 2014 on Windows server 2012. When I start the package in VS 2013 environment it works fine. I deployed the package to SSISDB and tried to run it from there, still successfully. But When I tried to launch my package from dtexec with the following statement in SSMQ the below error is displayed:

EXEC xp_cmdshell 'dtexec /ISSERVER "\SSISDB\MyFolder\MyProject\PKG Sales Debit.dtsx" /SER "ServerName\Instance" '

Error Message:

Remove Batch Worksheet:Error: Executing the query "Drop Table `Batch`" failed with the following error: "Cannot modify the design of table `Batch`. It is in a read-only database" Possible failure reasons: Problens with the query, "ResultSet" property not set correctly, parameters not set correclty, or connection not established correclty.

The drop batch is an execute sql task to remove worksheet named Batch in an excel file.

Free Windows Admin Tool Kit Click here and download it now
February 2nd, 2015 4:32am

Remove extended property "IMEX=1" for connectionstring properties in your excel connection manager. And also Give Full Permission to User.
http://www.proteanit.com/b/2008/04/01/excel-a-read-only-database/
February 3rd, 2015 2:16am

It seems like a permission issue to me. Are you trying to delete a sheet from excel file?

Free Windows Admin Tool Kit Click here and download it now
February 3rd, 2015 2:53am

Remove extended property "IMEX=1" for connectionstring properties in your excel connection manager. And also Give Full Permission to User.
http://www.proteanit.com/b/2008/04/01/excel-a-read-only-database/
February 3rd, 2015 10:13am

The excel connection string does not contain this propoerty. Here it is as generated by SSIS 2014:

Provider=Microsoft.ACE.OLEDB.12.0;Data Source=E:\Integration\Templates\TemplateSalesDebit.xlsx;Extended Properties="EXCEL 12.0 XML;HDR=YES";

It definitely is an access right problem but I do not see where to set it as the package runs when I execute it from SSISDB . The problem occurs when the package is deleting a worksheet of the excel file.


Free Windows Admin Tool Kit Click here and download it now
February 4th, 2015 4:50am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics