Post reply

Package Validation Error. I cannot run the package any more. After I stopped execution in the middle of tasks in runtime.

  • August 1, 2018 at 10:01 am

    #414483

    I launched the package. BIDS 2008. Then after the first task executed successfully (the top task in the sequence container in the attached screenshot)
    I stopped the execution by pressing stop button. So the runtime did not complete.
    Then I restarted the execution. Immediately the attached error popped up. I closed the entire solution (with intention not to save it and open the solution again but no save dialog box was there).
    When I reopened the .SLN  and ran the package again, same Package Validation Error! and it saved itself. 
    Please advice what to do. 
    I cannot run package any more.

    Likes to play Chess

  • August 1, 2018 at 10:51 am

    #1999912

    Here is that image inline:

    Does object BCPLStudent_diff exist?

    The absence of evidence is not evidence of absence.
    Martin Rees

    You can lead a horse to water, but a pencil must be lead.
    Stan Laurel

  • August 1, 2018 at 11:16 am

    #1999917

    This object (table)  is Created in step 1 of the package and  used in last task.

    if exists (select object_id(N'dbo.BCPLStudent_diff') from sys.objects where type = N'U')
    DROP TABLE [dbo].[BCPLStudent_diff];

    Select * into BCPLStudent_diff
    From (Select * from BCPLStudent
    Except Select * from BCPLStudent_Prev) a

    and in the last step
    Select * from  BCPLStudent_diff

    So I need to somehow turn off validation on the OLEDB Source? This is strange. Even if table did not exist but it is created in step 1. Why validation happens on Last step when i am starting to run the project  all tasks from the beginning?

    Likes to play Chess

  • August 1, 2018 at 11:42 am

    #1999921

    VoldemarG - Wednesday, August 1, 2018 11:16 AM

    This object (table)  is Created in step 1 of the package and  used in last task.

    if exists (select object_id(N'dbo.BCPLStudent_diff') from sys.objects where type = N'U')
    DROP TABLE [dbo].[BCPLStudent_diff];

    Select * into BCPLStudent_diff
    From (Select * from BCPLStudent
    Except Select * from BCPLStudent_Prev) a

    and in the last step
    Select * from  BCPLStudent_diff

    So I need to somehow turn off validation on the OLEDB Source? This is strange. Even if table did not exist but it is created in step 1. Why validation happens on Last step when i am starting to run the project  all tasks from the beginning?

    Far easier to leave the table there permanently and just TRUNCATE it, followed by an INSERT. Then your validation issues will go away.

    The absence of evidence is not evidence of absence.
    Martin Rees

    You can lead a horse to water, but a pencil must be lead.
    Stan Laurel

  • August 1, 2018 at 12:17 pm

    #1999929

    Thank you!

    Likes to play Chess

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

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