SSIS Execution Annonymous Login Error

Question

SSIS Execution Annonymous Login Error

mandavli

SSCrazy

Points: 2122
More actions
December 12, 2016 at 12:31 pm

#401197

I created a package in visual studio data tools , SQL connection works fine. and Package ran fine.
Then I loaded that package on to the server in Integration services catalog., when I execute the package from catalog or the job.
Package and also job fails , Error I see is
Error : SSIS Error Code DTS_E_OLEDBERROR
Login failed for user NT AUTHORITY/ANONYMOUS LOGON'

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

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

Phil Parkin SSC Guru Points: 246960 More actions · Answer 1

mandavli (12/12/2016)
I created a package in visual studio data tools , SQL connection works fine. and Package ran fine.
Then I loaded that package on to the server in Integration services catalog., when I execute the package from catalog or the job.
Package and also job fails , Error I see is
Error : SSIS Error Code DTS_E_OLEDBERROR
Login failed for user NT AUTHORITY/ANONYMOUS LOGON'

What is the name of the user running the SQL Agent service?

The absence of evidence is not evidence of absence
- Martin Rees
The absence of consumable DDL, sample data and desired results is, however, evidence of the absence of my response
- Phil Parkin

mandavli SSCrazy Points: 2122 More actions · Answer 2

mandavli

SSCrazy

Points: 2122

December 12, 2016 at 12:44 pm

#1917470

it's active directory user

Phil Parkin SSC Guru Points: 246960 More actions · Answer 3

mandavli (12/12/2016)
it's active directory user

OK, yet a SQL Agent job which runs the package gives that error ... are you certain?

The absence of evidence is not evidence of absence
- Martin Rees
The absence of consumable DDL, sample data and desired results is, however, evidence of the absence of my response
- Phil Parkin

Thom A SSC Guru Points: 99130 More actions · Answer 4

Phil Parkin (12/12/2016)
mandavli (12/12/2016)
it's active directory user
OK, yet a SQL Agent job which runs the package gives that error ... are you certain?

I agree with Phil that seeing this error on the SQL Agent Job is... unlikely. I would not surprised it appears when running from the catalog though; this due to you not having kerboros set up for "double hopping".

Thom~

Excuse my typos and sometimes awful grammar. My fingers work faster than my brain does.
Larnu.uk

mandavli SSCrazy Points: 2122 More actions · Answer 5

Thank you, I will talk to Net admin and see what can be done.