Post reply

SSIS package Login failed but still Package is executed...

  • February 2, 2012 at 12:48 pm

    #254738

    HI,

    I had built a package which pulling out the Customer Name from database and send to

    text file.So i have one OLEDB Source in the Data Flow Task and Flat File Destination in the

    data flow task.

    Package is executed sucessfully.Then i closed the BIDS.

    Again i open it and i see some error message.

    Please help me out in this issue....

    Please read this below error message.

    SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80040E4D. An OLE DB record is available. Source: "Microsoft SQL Server Native Client 10.0" Hresult: 0x80040E4D Description: "Login failed for User\ABC123

  • February 2, 2012 at 1:06 pm

    #1442038

    How are you storing the security credentials for the login.

    What is the package protection level set to?

    Bru Medishetty

    Blog -- LearnSQLWithBru

    Join on Facebook Page Facebook.comLearnSQLWithBru

    Twitter -- BruMedishetty

  • February 2, 2012 at 1:18 pm

    #1442049

    Package Protection Level :DontSaveSensitive

    Is that correct??

  • February 2, 2012 at 1:26 pm

    #1442054

    If you set that up, every time the package needs to be executed, it has to have that login credentials and it will eventually missed.

    I would suggest you have protection level set to EncryptSensitiveWithPassword and provide a password, so that when you deploy the package provide that password and it will continue running from then on..

    Note> this password is for the SSIS Package only..

    Bru Medishetty

    Blog -- LearnSQLWithBru

    Join on Facebook Page Facebook.comLearnSQLWithBru

    Twitter -- BruMedishetty

  • February 2, 2012 at 1:30 pm

    #1442056

    Once package is developed in DEV environment.Then it is moved to QA and Prod

    environment.Because of this reason , i can't set the password on SSIS package.

    IS there any way to resolve this issue...?

  • February 2, 2012 at 1:34 pm

    #1442061

    There should be some kind of security involved in SSIS packages where there is sensitive data (passwords or login info)..

    Read these resources and they might help you..

    http://msdn.microsoft.com/en-us/library/ms141747.aspx

    http://msdn.microsoft.com/en-us/library/ms137833.aspx

    Bru Medishetty

    Blog -- LearnSQLWithBru

    Join on Facebook Page Facebook.comLearnSQLWithBru

    Twitter -- BruMedishetty

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

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