Click here to monitor SSC

SQL Server Tacklebox - Upgrade to SSIS Project Fails!

Last post 07-17-2013, 12:37 AM by PatWilliams. 5 replies.
Sort Posts: Previous Next
  •  03-08-2010, 12:32 PM Post number 90186

    SQL Server Tacklebox - Upgrade to SSIS Project Fails!

    I'm attempting to impliment the DBA Repository from chapter 2. Looks great however.... After opening the DBA_Server_Load project in Visual Studio 9.0 (30729.1 .NET 305 SP1) the upgrade wizard fails the the messages below. Ideas???
    thanks


    - Upgrading package Populate_DBA_REP.dtsx (Error)
    Messages
    Warning 0x4020f42c: : The Maximum insert commit size property of the OLE DB destination "OLE DB Destination" is set to 0. This property setting can cause the running package to stop responding. For more information, see the F1 Help topic for OLE DB Destination Editor (Connection Manager Page).

    Warning 0x4020f42c: : The Maximum insert commit size property of the OLE DB destination "OLE DB Destination" is set to 0. This property setting can cause the running package to stop responding. For more information, see the F1 Help topic for OLE DB Destination Editor (Connection Manager Page).

    Warning 0x4020f42c: : The Maximum insert commit size property of the OLE DB destination "Jobs_Archive" is set to 0. This property setting can cause the running package to stop responding. For more information, see the F1 Help topic for OLE DB Destination Editor (Connection Manager Page).

    Warning 0x4020f42c: : The Maximum insert commit size property of the OLE DB destination "OLE DB Destination" is set to 0. This property setting can cause the running package to stop responding. For more information, see the F1 Help topic for OLE DB Destination Editor (Connection Manager Page).

    Warning 0x4020f42c: : The Maximum insert commit size property of the OLE DB destination "OLE DB Destination" is set to 0. This property setting can cause the running package to stop responding. For more information, see the F1 Help topic for OLE DB Destination Editor (Connection Manager Page).

    Warning 0x4020f42c: : The Maximum insert commit size property of the OLE DB destination "OLE DB Destination" is set to 0. This property setting can cause the running package to stop responding. For more information, see the F1 Help topic for OLE DB Destination Editor (Connection Manager Page).

    Warning 0x4020f42c: : The Maximum insert commit size property of the OLE DB destination "OLE DB Destination" is set to 0. This property setting can cause the running package to stop responding. For more information, see the F1 Help topic for OLE DB Destination Editor (Connection Manager Page).

    Warning 0x4020f42c: : The Maximum insert commit size property of the OLE DB destination "OLE DB Destination" is set to 0. This property setting can cause the running package to stop responding. For more information, see the F1 Help topic for OLE DB Destination Editor (Connection Manager Page).

    Warning 0x4020f42c: : The Maximum insert commit size property of the OLE DB destination "OLE DB Destination" is set to 0. This property setting can cause the running package to stop responding. For more information, see the F1 Help topic for OLE DB Destination Editor (Connection Manager Page).

    Warning 0x4020f42c: : The Maximum insert commit size property of the OLE DB destination "OLE DB Destination" is set to 0. This property setting can cause the running package to stop responding. For more information, see the F1 Help topic for OLE DB Destination Editor (Connection Manager Page).

    Warning 0x4020f42c: : The Maximum insert commit size property of the OLE DB destination "OLE DB Destination" is set to 0. This property setting can cause the running package to stop responding. For more information, see the F1 Help topic for OLE DB Destination Editor (Connection Manager Page).

    Warning 0x80019316: : The provider name for the connection manager "Local.DBA_REP" has been changed from "SQLNCLI.1" to "SQLNCLI10".

    Warning 0x80019316: : The provider name for the connection manager "Multi_Server_9" has been changed from "SQLNCLI.1" to "SQLNCLI10".

    Warning 0x80019316: : The provider name for the connection manager "Multi_Server_9_DMZ" has been changed from "SQLNCLI.1" to "SQLNCLI10".

    Warning 0x80019316: : The provider name for the connection manager "Multi_Server_DMZ" has been changed from "SQLNCLI.1" to "SQLNCLI10".

    Warning 0x80019316: : The provider name for the connection manager "MultiServer" has been changed from "SQLNCLI.1" to "SQLNCLI10".

    Information 0x40016019: : The package format was migrated from version 2 to version 3. It must be saved to retain migration changes.


    Error 0xc0016016: : Failed to decrypt protected XML node "DTS:Password" with error 0x8009000B "Key not valid for use in specified state.". You may not be authorized to access this information. This error occurs when there is a cryptographic error. Verify that the correct key is available.


    Error 0xc0016016: : Failed to decrypt protected XML node "DTS:Password" with error 0x8009000B "Key not valid for use in specified state.". You may not be authorized to access this information. This error occurs when there is a cryptographic error. Verify that the correct key is available.


    Error 0xc001f429: Package Upgrade: The loading of the package Populate_DBA_REP.dtsx has failed.


  •  03-22-2010, 2:33 AM Post number 90330 in reply to post number 90186

    Re: SQL Server Tacklebox - Upgrade to SSIS Project Fails!

    I also encountered the same isse.

    Anybody can help pls?

     

    Thanks.

     

  •  02-24-2011, 1:56 AM Post number 100257 in reply to post number 90330

    Re: SQL Server Tacklebox - Upgrade to SSIS Project Fails!

    Yes I'm also getting the same error.

     

    Regards

    Nitin Gupta

  •  04-05-2011, 6:19 AM Post number 101127 in reply to post number 100257

    • tonny is not online. Last active: 04-07-2011, 2:47 AM tonny
    • Not Ranked
    • Joined on 08-31-2010
    • Level 1: Deep thought

    Re: SQL Server Tacklebox - Upgrade to SSIS Project Fails! Just a warning

    From http://www.networksteve.com/enterprise/topic.php?TopicId=25097

    This clue:


    http://social.msdn.microsoft.com/Forums/en-US/sqlintegrationservices/thread/aa3d854b-e9e1-4cc9-af98-2c71c76ec65d/
    seems to be the answer for you.
    It is simply a warning, you may need to alter the setting in the OLE Db as illustrated here:


    http://www.bidn.com/blogs/ShawnHarrison/ssis/803/maximum-insert-commit-size
  •  01-17-2012, 4:13 PM Post number 105514 in reply to post number 101127

    Re: SQL Server Tacklebox - Upgrade to SSIS Project Fails! Just a warning

    oh thanks alot for answer, I was looking for that all around.
  •  07-17-2013, 12:37 AM Post number 115128 in reply to post number 90186

    Re: SQL Server Tacklebox - Upgrade to SSIS Project Fails!

    I have the book SQL Server Tacklebox as an altime reference for my SQL related issues. This book can be downloaded from website and is capable of providing your queries. Throughout such troublesome periods, you, the DBA, are the inside of consideration. Rodney Landrum, the author of this book has been working with SQL Server technologies for longer than he can remember.

    Thanks
    http://super-beta-prostate.com
View as RSS news feed in XML