Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

SSIS package fails giving "System.Runtime.InteropServices.COMException" Expand / Collapse
Author
Message
Posted Wednesday, April 2, 2008 8:59 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Monday, December 22, 2008 10:46 AM
Points: 2, Visits: 9
Hi,



I have one SSIS package which is written in Visual studio business intelligence tool. For that SSIS packages i have scheduled a job from SQL server management studio 2005. I mean i have scheduled a job in SQL server agent.



But it is failing giving some com.interop exception. Not sure what type of error is this?



It give following type error:



Microsoft (R) SQL Server Execute Package Utility Version 9.00.3042.00 for 32-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 11:00:00 PM Error: 2008-03-27 23:00:00.81 Code: 0x00000000 Source: Execute DTS 2000 Package Task Description: System.Runtime.InteropServices.COMException (0x80040427): Execution was canceled by user. at DTS.PackageClass.Execute() at Microsoft.SqlServer.Dts.Tasks.Exec80PackageTask.Exec80PackageTask.ExecuteThread() End Error DTExec: The package execution returned DTSER_FAILURE (1). Started: 11:00:00 PM Finished: 11:00:00 PM Elapsed: 0.579 seconds. The package execution failed. The step failed.



I get the same error when i try to execute the package from Visual studio Business Intelligence tool.



Can you please help me out as to what is this "System.Runtime.InteropServices.COMException" exception occuring when scheduling or executing the job.

Post #478593
Posted Wednesday, April 2, 2008 9:15 AM
SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Tuesday, August 10, 2010 5:07 AM
Points: 2,732, Visits: 23,078
This would typically be caused by using a connection manager for managed code with an OLEDB component (or the other way around).

It is hard to do in most cases because the IDE prevents it, but if you used any script components, they are likely the cause. Make sure you use .Net data sources in script components - you cannot use native OLEDB connections because they are com components.
Post #478613
Posted Thursday, April 3, 2008 7:33 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Monday, December 22, 2008 10:46 AM
Points: 2, Visits: 9
I am not using any native OLEDB connection or provider.

This is problem is with only one SSIS packages which is executing DTS 2000 pacakge.

There are other SSIS packages which are also using DTS 2000 packages and they are executing successfully.

So why it is giving error for only this SSIS package. And that too a Com type of exception.

NOt sure what to do as this is a production server issue.

Please help

Thanks,
Post #479193
Posted Tuesday, September 9, 2008 2:56 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Wednesday, August 4, 2010 10:51 AM
Points: 1, Visits: 7
I am getting this same error on a very simple SSIS package. If you run the package manually, it works fine, but as soon as you schedule it as a job and run it, I get the following:

Date,Source,Severity,Step ID,Server,Job Name,Step Name,Notifications,Message,Duration,Sql Severity,Sql Message ID,Operator Emailed,Operator Net sent,Operator Paged,Retries Attempted
09/09/2008 16:40:00,Employee Import,Error,0, . The last step to run was step 1 (Import Employees).,00:00:02,0,0,,,,0
09/09/2008 16:40:00,Employee Import,Error,1, tempEmployees Description: System.Runtime.InteropServices.COMException (0x80040427): Execution was canceled by user. at DTS.PackageClass.Execute() at Microsoft.SqlServer.Dts.Tasks.Exec80PackageTask.Exec80PackageTask.ExecuteThread() End Error DTExec: The package execution returned DTSER_FAILURE (1). Started: 4:40:00 PM Finished: 4:40:02 PM Elapsed: 1.344 seconds. The package execution failed. The step failed.,00:00:02,0,0,,,,0

Any help would be greatly appreciated.
Post #566493
Posted Tuesday, November 11, 2008 4:46 AM
SSC-Addicted

SSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-Addicted

Group: General Forum Members
Last Login: Friday, January 31, 2014 8:07 AM
Points: 462, Visits: 119
Are you by any chance using local/localhost as your server

I had a similar problem on a development server while migrating a SQL 2000 database to SQL 2005.

The original DTS was developed on a SQL 2000 machine and used a SQL login for a connection.

The server was changed to localhost with Windows Auth but failed with your error message.
It was changed again to local and it worked.

In short for SQL 2000 dts use local
for SQL 2005 use localhost
Post #600561
Posted Wednesday, January 8, 2014 2:45 PM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Wednesday, January 8, 2014 2:44 PM
Points: 18, Visits: 104
matthew.pullen

You are me Hero !!! 2hours of searching and now it works !!! Thanx!!!

Switch vom "(local)" to the real Servername in DTS solve the problem
Post #1529112
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse