(Could not find stored procedure 'msdb.dbo.sp_dts_getfolder'. - sql 2005 - > 2008 R2

  • I have a package on 2008r2 and job on 2005 pointing to the package on 2008r2. When i run the job i get the following message 'Description: While trying to find a folder on SQL an OLE DB error was encountered with error code 0x80040E14 (Could not find stored procedure 'msdb.dbo.sp_dts_getfolder'.). Source"..Does anyone know how to fix this?

  • Have you looked at this kb?

    http://support.microsoft.com/kb/946127

  • matt.bowler (8/29/2011)


    Have you looked at this kb?

    http://support.microsoft.com/kb/946127

    Yep i certainly did. I have NO issue at all viewing the package through the job, as i mentioned in the post the issue is when i RUN the job. Any clues?

  • Can you verify that the stored procedure does exist in msdb?

  • I update this old thread because it is of no use without an answer to the question:

    The [msdb].[dbo].[sp_dts_getfolder] is actually changed to [msdb].[dbo].[sp_ssis_getfolder]

    as naming conventions changed because "DTS" is ugly and "SSIS" is good, according to Microsoft...

    MCITP Database administrator 2008
    MCTS SQL Server 2008 Implementation and maintenance
    MCTS Sharepoint configuration
    MCP Designing Deploying and Managing a Network Solution for the Small and Medium-sized Business
    ITIL V3 Foundation
  • Fabrizio Faleni (11/30/2012)


    I update this old thread because it is of no use without an answer to the question:

    The [msdb].[dbo].[sp_dts_getfolder] is actually changed to [msdb].[dbo].[sp_ssis_getfolder]

    as naming conventions changed because "DTS" is ugly and "SSIS" is good, according to Microsoft...

    I know is an old thread but I am seeing the same issue. We have SS2K8R2 installed. When I click on Maintenance Plans -> New Maintenance Plan I get the error "Could not find stored procedure 'msdb.dbo.sp_dts_getfolder'. I also receive this error message when I run the final step from the Maintenance Plan Wizard.

    As was stated, [msdb].[dbo].[sp_dts_getfolder] is actually changed to [msdb].[dbo].[sp_ssis_getfolder]. So, should I rename sp_dts_getfolder to sp_ssis_getfolder in the msdb database? I am loath to make changes in the msdb database but I don't see any other fixes out there when I Google this issue.

    Any ideas/suggestions on how to fix this problem?

    Thanks,

    Debbie

  • Just to update the ticket.

    I was able to create a maintenance plan when I logged onto the server. I was receiving the message when I tried creating the maint. plan remotely.

  • rockon_dba (8/29/2011)


    I have a package on 2008r2 and job on 2005 pointing to the package on 2008r2. When i run the job i get the following message 'Description: While trying to find a folder on SQL an OLE DB error was encountered with error code 0x80040E14 (Could not find stored procedure 'msdb.dbo.sp_dts_getfolder'.). Source"..Does anyone know how to fix this?

    Hi, I need to dig this up and hope their is someone with an answer to this.

    I am in the same position, except that I am trying to run a 2008 package (stored in SQLServer) from a 2005 job.

    at first I came across the error, and discovered this article (946127), as mentioned in essentially every page on this issue that comes up in google.

    My 2005 SQL server was way behind on updates and did not have the SP needed for the forward compatibility. I was able to get the latest SP installed on the server, which now reads as version 9.0.5000.

    However, the problem still persists. I cannot run the job on the remote 2008 server. Error code / desc as mentioned above.

    It is a simple package, it works when executed on the 2008 machine.

    I am not sure what is referred to when someone above confirmed they "can see the package from the job", unless they are confirming the package appears in the package selection window?

    Side question, does this mean that the 2008 package XML is being interpreted by the 2005 server?

    Any help is appreciated!

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

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