Hi,

I'm calling a known-working DTS package from .NET but it is failing with
the following error:

"ERROR: System.Exception: COMException -2147220441

Execution was canceled by user.
at DTS.Package2Class.Execute()

at Diary.xadmin.ExportToAccessPage.ExecutePackage() in
export-to-access.aspx.cs:line 92"


All references that I can find online to this error seem to imply it's a
bug in VB - but I'm not using VB - I'm using C# under .NET

If I run the package from Enterprise Manager it runs OK. The package and
C# code are working fine on another server (identical code and
package), but on this server it just says "Execution canceled by user."
(with the spelling mistake of the single L in cancelled). The error
happens instantly so it is not due to a timeout of any kind.

I have tried implementing the fix mentioned for VB, but it has no effect.

Any ideas on how I can fix this problem would be appreciated.

Thanks,

Nick....

Hello Nick,

Based on my research, this error could occur if more than one
Transformation tasks will try to use the same connection that is defined
through Dynamic Property Task. If it is the case, you may try the following
method to work around the issue:

Under DTS Package Properties --> General --> Execution Parameters, set
"Limit the maximum number of tasks executed in parallel to: " to 1 (default
is 4).

Thanks & Regards,

Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.

================================================== ===



This posting is provided "AS IS" with no warranties, and confers no rights.

I have changed the maximum number of tasks executed in parallel to 1 but
the problem is still happening. Additionally, on another server where
it's working perfectly, this value is set to 4.

Do you have any other ideas why this problem is happening?

Nick...

Hello Nick,

Based on the situation, it seems the issue is on .Net interop side, you may
want to contact CSS so that they may look into the issue by using dump
analysis or live debug.

Also, from the error code, the error code indicates that COM object cannot
be instanted due to some issues. You may want to use filemon and regmon to
capture the log when the issue occurs to check if it is related to some
permission error.

http://www.sysinternals.com/ntw2k/source/filemon.shtml
http://www.sysinternals.com/ntw2k/source/regmon.shtml

Regards,

Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.

================================================== ===


This posting is provided "AS IS" with no warranties, and confers no rights.

I've fixed this problem now. It turned out to be a setting of "use
trusted connection" in the connection to SQL Server. Somehow this had
got turned on on the new machine. Disabling this causes the package to
work fine.

As is usual with SQL Server, it is VERY poor error messages have caused
me to waste hours of time. The error message shown has NOTHING
WHATSOEVER to do with actual error which is occurring. It is actually a
permissions error. I can't believe bugs like this still exist in a 6
year old database system that's had so many service packs released for it.

Nick...

Hello Nick,

Thank you for your feedback on this issue and I agree it is not useful for
users to get proper information from this interop exception message. Please
rest assured this has been routed to the product team.

Best Regards,

Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.

================================================== ===



This posting is provided "AS IS" with no warranties, and confers no rights.