Post reply

Error 1326 Error getting file security when installing SSIS

  • September 25, 2017 at 1:37 pm

    #339369

    I'm trying to add the SSIS component to a SQL Server 2014 machine that is a secondary node in an AG test environment.  The installation part starts and about 20-40 seconds into the process I get the following error.

    Error 1326. Error getting file security: L:\SQLLogs\120\DTS\Binn\ISDeploymentWizard.exe GetLastError: 5

    Some Google searches for error 1326 outside of SQL Server indicate a permissions issue.  Initially I was just trying this install with the default SSIS account. I tried with an account that is a local sysadmin in Windows but still doesn't work.  Any suggestions?

  • September 25, 2017 at 1:46 pm

    #1960843

    lmarkum - Monday, September 25, 2017 1:37 PM

    I'm trying to add the SSIS component to a SQL Server 2014 machine that is a secondary node in an AG test environment.  The installation part starts and about 20-40 seconds into the process I get the following error.

    Error 1326. Error getting file security: L:\SQLLogs\120\DTS\Binn\ISDeploymentWizard.exe GetLastError: 5

    Some Google searches for error 1326 outside of SQL Server indicate a permissions issue.  Initially I was just trying this install with the default SSIS account. I tried with an account that is a local sysadmin in Windows but still doesn't work.  Any suggestions?

    Is L: a local drive? If not, local admin does not help you much.

    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

  • September 25, 2017 at 2:08 pm

    #1960851

    Yep Phil.  L is a local drive.

  • September 26, 2017 at 5:40 am

    #1960925

    lmarkum - Monday, September 25, 2017 2:08 PM

    Yep Phil.  L is a local drive.

    OK, I guess that you've already done the exact same install on the primary and everything worked OK?
    The path does look a little odd though ... I'm wondering why the install creates a root-level SQLLogs folder on a (presumably) non-system drive. And why then put an EXE in a logs folder?
    More questions than answers, I'm afraid. Good luck getting this working.

    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

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

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