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

  • christine.lawrie

    Ten Centuries

    Points: 1146

    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.


    SSC Enthusiast

    Points: 126

    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: 244656

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

    If the answer to your question can be found with a brief Google search, please perform the search yourself, rather than expecting one of the SSC members to do it for you.
    See for details of how to post T-SQL code-related questions.


    SSC Enthusiast

    Points: 126


    I noticed when I allready had posted the answer.

    I looked at the last login instead of the original post date.

    Txs anayway ...

  • bird2920

    SSC Journeyman

    Points: 97

    Haha, it was helpful either way.... all the way into 2016 😛

  • This was removed by the editor as SPAM

  • wrojas


    Points: 1

    Until 2019 too!

  • lynetteb


    Points: 4

    Helpful in 2020 too.  Thank you!

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

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