Error 0XC0048000 when running a SSIS package via SQL Server Agent

Question

Error 0XC0048000 when running a SSIS package via SQL Server Agent

christine.lawrie

Ten Centuries

Points: 1146
More actions
July 29, 2010 at 12:41 am

#146481

I have a SQL Server Agent job that runs a SSIS package via the File System rather than Integration Services, as the server I'm running the package on doesn't have Integration Services installed. The package was deployed to the same server as the SQL Server Agent.
When I try to run the package, I get the following error:
Executed as user: HNEAHS\AppDev. ...sion 9.00.4035.00 for 64-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 4:21:06 PM Warning: 2010-07-29 16:21:18.50 Code: 0xC0048000 Source: dtf Get Theatre Room Data dtf Get Theatre Room Data (DTS.Pipeline) Description: The registry key "SOFTWARE\Classes\CLSID\{DE50D3C7-41AF-4804-9247-CF1DEB147971}\DTSInfo" cannot be opened. End Warning Warning: 2010-07-29 16:21:18.50 Code: 0x8004801E Source: dtf Get Theatre Room Data dtf Get Theatre Room Data (DTS.Pipeline) Description: Cannot find the "CurrentVersion" value for component {DE50D3C7-41AF-4804-9247-CF1DEB147971}. The CurrentVersion value for the component cannot be located. This error occurs if the component has not set its registry information to contain a CurrentVersion value in the DTSInfo section. This message occurs during component development, or when the component is used in a package, if the component is no... The package execution fa... The step failed.
Does anyone have any ideas? I don't have any ownership over the server, and I suspect the owners don't want to install Integration Services on it - hence why I'm running the package via the File system.
November 29, 2016 at 4:25 am

This was removed by the editor as SPAM

Viewing 8 posts - 1 through 7 (of 7 total)

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

edwin.de.jonge SSC Enthusiast Points: 126 More actions · Answer 1

You can't invoke a SSIS package on a server that has no SSIS installed on it. If you look at the log in your post, you'll see it's trying to reference a SSIS class in the registry. Since your server isn't running SSIS it's not a big surprise it cannot find these components.

I would suggest you schedule the package on the SSIS server. Not under SSIS, but connect to the database engine on that server and proceed as you would on the server without SSIS.

Otherwise install SSIS on the database server.

Phil Parkin SSC Guru Points: 246693 More actions · Answer 2

Good answer, but note that you have answered a question which is more than a year old 🙂

If you haven't even tried to resolve your issue, please don't expect the hard-working volunteers here to waste their time providing links to answers which you could easily have found yourself.