SSIS Schedule

  • Hi All

    I wrote the ssis package and schedule it in testing machine,after scheduling i personally updated the excel sheet the the when i went and see the history of ssis package in jobs i am getting this error

    Executed as user: NT AUTHORITY\NETWORK SERVICE. Microsoft (R) SQL Server Execute Package Utility

    Version 10.0.1600.22 for 32-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved.

    Started: 8:15:02 AM Error: 2010-03-09 08:15:08.28 Code: 0xC0202009

    Source: excel packege today Connection manager "SourceConnectionExcel"

    Description: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80004005.

    An OLE DB record is available. Source: "Microsoft JET Database Engine" Hresult: 0x80004005 Description:

    "The Microsoft Jet database engine cannot open the file 'E:\Documents and Settings\Administrator\Desktop\LOGSHEET.xls'. It is already opened exclusively by another user, or you need permission to view its data.". End Error Error: 2010-03-09 08:15:08.31 Code: 0xC020801C Source: Data Flow Task 1 Source - Sheet1$ [1] Description: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager "SourceConnectionExcel" failed with error code 0xC0202009. There may be error messages posted before this with more information on why the AcquireConnection method call failed. End Error Error: 2010-03-09 08:15:08.31 Code: 0xC0047017 Source: Data Flow Task 1 SSIS.Pipeline Description: component "Source - Sheet1$" (1) failed validation and returned error code 0xC020801C.

    End Error Error: 2010-03-09 08:15:08.31 Code: 0xC004700C Source: Data Flow Task 1 SSIS.Pipeline

    Description: One or more component failed validation. End Error Error: 2010-03-09 08:15:08.31 Code: 0xC0024107 Source: Data Flow Task 1 Description: There were errors during task validation. End Error DTExec: The package execution returned DTSER_FAILURE (1). Started: 8:15:02 AM Finished: 8:15:08 AM Elapsed: 6.078 seconds. The package execution failed. The step failed.

    can you please advise me on this, which will be very helpful for me.

    and the excel sheet i have saved on my local desktop for your information.

    thanks

    tayyeb

  • Somebody has that Excel file open, or has a dangling lock left on it. My guess would be that its you, since you just changed it. So do you still have it open in Excel? If not, it's still possible that Excel has left a lock on it even after you closed it. Use Task Manager to see if Excel is running in the background.

    [font="Times New Roman"]-- RBarryYoung[/font], [font="Times New Roman"] (302)375-0451[/font] blog: MovingSQL.com, Twitter: @RBarryYoung[font="Arial Black"]
    Proactive Performance Solutions, Inc.
    [/font]
    [font="Verdana"] "Performance is our middle name."[/font]

  • I agree with Barry, I have done EXACTLY what he is describing several times when working with Excel files and SSIS.

    CEWII

  • No Not All , just checked as per your suggestion in background also excel not running still same error popping any idea guys ?

    thanks

    tayyeb

  • Try running this free utility from MS, on your server, it should tell you what's going on.

    [font="Times New Roman"]-- RBarryYoung[/font], [font="Times New Roman"] (302)375-0451[/font] blog: MovingSQL.com, Twitter: @RBarryYoung[font="Arial Black"]
    Proactive Performance Solutions, Inc.
    [/font]
    [font="Verdana"] "Performance is our middle name."[/font]

  • did you ever solve your problem?

    [font="Times New Roman"]-- RBarryYoung[/font], [font="Times New Roman"] (302)375-0451[/font] blog: MovingSQL.com, Twitter: @RBarryYoung[font="Arial Black"]
    Proactive Performance Solutions, Inc.
    [/font]
    [font="Verdana"] "Performance is our middle name."[/font]

  • Oh yes mr.barry,thank you very much for your responce, And sorry i was busy in other project work so couldn't reply you saying thanks 🙂

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

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