Another cryptic message from SQL 2005 SSIS

It reminds me of the "opearation was successful the patient died" scenario.

Compare this to the SSIS Error message:

The Execution method succeeded, but the number of errors raised (1) reached the maximum allowed (1); resulting in failure. This occurs when the number of errors reaches the number specified in MaximumErrorCount. Change the MaximumErrorCount or fix the errors.

SSIS package "myPubs.dtsx" finished: Failure.

Why can't they write meaningful messages?

YOu need enable the logging for SSIS packages in order to see what was that error : http://www.databasejournal.com/features/mssql/article.php/3562406 fyi.|||Did they fix this bug finally?|||

I forgot to indicate my blog entry for this:

http://hodentek.blogspot.com/2007/03/ssis-migration-fiasco.html

|||

I was actaully trying to find an answer for the question I posted:

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1393552&SiteID=1

Please forgive.

|||Moved this thread from SQL Server Tools General to the SSIS forum.

You should know that your error likely has to do with the ProtectionLevel property of the package. Right click on the control flow and select properties. What is it set to?|||

Jayaram Krishnaswamy wrote:

Did they fix this bug finally?

What bug? I don't believe there is a bug here, rather I think there is a lack of understanding of how differently SSIS operates compared to DTS.|||

Reply was not helpful.

Tried all options (somewhat unprofessional, fortunately fewer options). The same result.

Details follow:

Protection Level of package:

DontSaveSensitive: failed

Warning: 0x80019002 at myPubs: The Execution method succeeded, but the number of errors raised (4) reached the maximum allowed (1); resulting in failure. This occurs when the number of errors reaches the number specified in MaximumErrorCount. Change the MaximumErrorCount or fix the errors.
SSIS package "myPubs.dtsx" finished: Failure.

EncryptSensitiveWithPassowrd: failed

Provided a password for the package, myPubs.dtsx.

SSIS package "myPubs.dtsx" starting.
Error: 0xC002F325 at Copy SQL Server Objects, Transfer SQL Server Objects Task: Execution failed with the following error: "Cannot apply value null to property Login: Value cannot be null..".
Task failed: Copy SQL Server Objects
Warning: 0x80019002 at myPubs: The Execution method succeeded, but the number of errors raised (1) reached the maximum allowed (1); resulting in failure. This occurs when the number of errors reaches the number specified in MaximumErrorCount. Change the MaximumErrorCount or fix the errors.
SSIS package "myPubs.dtsx" finished: Failure.

EncryptAllwithPassword:failed
failed
SSIS package "myPubs.dtsx" starting.
Error: 0xC002F325 at Copy SQL Server Objects, Transfer SQL Server Objects Task: Execution failed with the following error: "Cannot apply value null to property Login: Value cannot be null..".
Task failed: Copy SQL Server Objects
Warning: 0x80019002 at myPubs: The Execution method succeeded, but the number of errors raised (1) reached the maximum allowed (1); resulting in failure. This occurs when the number of errors reaches the number specified in MaximumErrorCount. Change the MaximumErrorCount or fix the errors.
SSIS package "myPubs.dtsx" finished: Failure.

EncryptAllwithUserkey:failed (ola didn't ask for a key or anything, it must have assumed some default)

SSIS package "myPubs.dtsx" starting.
Error: 0xC002F325 at Copy SQL Server Objects, Transfer SQL Server Objects Task: Execution failed with the following error: "Cannot apply value null to property Login: Value cannot be null..".
Task failed: Copy SQL Server Objects
Warning: 0x80019002 at myPubs: The Execution method succeeded, but the number of errors raised (1) reached the maximum allowed (1); resulting in failure. This occurs when the number of errors reaches the number specified in MaximumErrorCount. Change the MaximumErrorCount or fix the errors.
SSIS package "myPubs.dtsx" finished: Failure

ServerStorage: failed
TITLE: Microsoft Visual Studio

Failure saving package.

ADDITIONAL INFORMATION:

Failed to apply package protection with error 0xC0014061 "The protection level, ServerStorage, cannot be used when saving to this destination. The system could not verify that the destination supports secure storage capability.". This error occurs when saving to Xml.
(myPubs)

Failed to apply package protection with error 0xC0014061 "The protection level, ServerStorage, cannot be used when saving to this destination. The system could not verify that the destination supports secure storage capability.". This error occurs when saving to Xml.
(myPubs)

BUTTONS:

OK

Open for suggestions

|||Try EncryptSensitiveWithUserKey and then go back in and retype in your credentials for the connections. Make sure you check the save password box.|||

Jayaram Krishnaswamy wrote:

I forgot to indicate my blog entry for this:

http://hodentek.blogspot.com/2007/03/ssis-migration-fiasco.html

You haven't understood the inherent differences between SSIS and DTS. SSIS is a much more secure environment and will not allow you to store passwords with the same freedom as DTS did. Can I politely suggest that you familiarise yourself totally with this new tool before you start to blog about it and thus post inaccurate information. You are not helping the SSIS community by doing so.

-Jamie

|||If the number of people reporting this is large surely somebody should take the responsibility of putting the matter to rest. This is probably one of the problems with proprietary software.|||

Jayaram Krishnaswamy wrote:

If the number of people reporting this is large surely somebody should take the responsibility of putting the matter to rest. This is probably one of the problems with proprietary software.

REPORTING WHAT, *exactly*?

WHAT *IS* THE PROBLEM?|||

Jayaram Krishnaswamy wrote:

If the number of people reporting this is large surely somebody should take the responsibility of putting the matter to rest. This is probably one of the problems with proprietary software.

huh?

If SSIS is proprietary software then show me some software that ISN'T proprietary.

I haven't seen anyone else on this thread reporting any problem, only you. In fact, you haven't actually articulated a problem as far as I can see. In summary, what is the prolem that you speak of?

-Jamie

|||

Phil Brammer wrote:

Try EncryptSensitiveWithUserKey and then go back in and retype in your credentials for the connections. Make sure you check the save password box.

This did not help in my case.

Jayaram, have you resolved this problem finally?|||

Dan Miniyarov wrote:

Phil Brammer wrote:

Try EncryptSensitiveWithUserKey and then go back in and retype in your credentials for the connections. Make sure you check the save password box.

This did not help in my case.

Jayaram, have you resolved this problem finally?

I don't know what that means. What exactly is your issue? What are you trying to achieve?