Could not create DTS.Application because of error 0x800401F3

Question

Could not create DTS.Application because of error 0x800401F3

Rob-880668

Mr or Mrs. 500

Points: 573
More actions
February 8, 2011 at 9:34 am

#246387

I'm stuck on this one. I hope someone here has some experience with this. Here is the situation. I have set up a web page that allows users to upload flat files to be loaded into SQL Server 2005 using SSIS. There are two difference SSIS processes depending on the file type. The decision of which SSIS process to use is made by the user on the website.
Once the file is uploaded by the user the process is started by a .NET Process object. The command line is the normal command line you'd expect to see to start dtexec with a specific SSIS file and that sets a couple variables. For example:
dtexec /f <packagefile> /De <password> /set <variablepath> value
The ASP.NET Anonymous User is running as a domain user account. All SSIS package files for both SSIS processes are in the same directory. The domain user account has full privileges on that directory. The same method in ASP.NET starts either of the processes. The only difference is the WebMethod called by the website. One WebMethod for each type. It is in these WebMethods where the unique arguments are assigned to the command line text for SSIS.
Here is where I have run into the problem. When running the website process "1", it runs fine, but process "2" fails with the error mentioned above. When I capture the Standard Output I receive this:
Microsoft (R) SQL Server Execute Package Utility
Version 9.00.4035.00 for 32-bit
Copyright (C) Microsoft Corp 1984-2005. All rights reserved.
Started: 10:34:14 AM
Could not create DTS.Application because of error 0x800401F3
Started: 10:34:14 AM
Finished: 10:34:14 AM
Elapsed: 0.016 seconds
I don't understand how everything can be nearly identical yet only one will run. One final thing, both methods work fine when I am testing directly from Visual Studio. I figure it must be something with the Anonymous User account used, but I can't figure out why one process would work and the other not work when they are so similar.
Any help will be greatly appreciated.
Rob

Viewing 6 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply

Phil Parkin SSC Guru Points: 246960 More actions · Answer 1

Could this be relevant?

The absence of evidence is not evidence of absence
- Martin Rees
The absence of consumable DDL, sample data and desired results is, however, evidence of the absence of my response
- Phil Parkin

Rob-880668 Mr or Mrs. 500 Points: 573 More actions · Answer 2

I thought it might be when I looked at it earlier. The primary difference is that this person's process would not run at all.

Both my processes work fine in Debug from Visual Studio. This is probably due to the Web Development Server working under my account.

But in the wild one package works fine and the other won't even start. I would figure that if my problem is like this other that neither of my processes would run.

Just for some extra info, the processes are nearly identical varying primarily in variables and lookups. They both use the same components within the packages.

Thanks for your response,

rob

Phil Parkin SSC Guru Points: 246960 More actions · Answer 3

I agree, this seems puzzling. Is there anything in the Event Log?

The absence of evidence is not evidence of absence
- Martin Rees
The absence of consumable DDL, sample data and desired results is, however, evidence of the absence of my response
- Phil Parkin

Rob-880668 Mr or Mrs. 500 Points: 573 More actions · Answer 4

Just the usual 'Package "<Insert Package Name Here>" failed'. Nothing else.

Rob-880668 Mr or Mrs. 500 Points: 573 More actions · Answer 5

Found the problem. A Connection Component was being fed by a variable that was holding a path to a folder the new account could not go to. Even though in process it would be replaced with a good target it was failing in validation. This is why there was no logs. I didn't have the logging level high enough to see it and it acted like a security issue. Which is was in a way of looking at it.

Thanks for the help.