This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(19.2, 96%, 11%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJ%3C/text%3E%3C/svg%3E)
Hi All,
I have deployed one ssis package in SQL. It was running fine when execute in visual studio but got error NT AUTHORITY\ANONYMOUS LOGON when execute in SQL Server management studio. The SSIS package contain the copy of table from one server(A) to another server(B). I have only encounter this issue when I connect OLE DB source from another server(B) which I have only public server role for this server (B) and read access&public access from the DB source(in server B). Can anybody help to resolve this error?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(156.8, 65%, 25%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAT%3C/text%3E%3C/svg%3E)
Hi @jn93 ,
Is there any error message?
From your description, it seems like a permission issue.
Try to use proxy account to run the package in SQL, remember to give the account full permission to access the DB server.
running-a-ssis-package-from-sql-server-agent-using-a-proxy-account
Hi @Avery Tang ,
The error message on the description is Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON. I deployed my ssis package inside my destination server. But for my source server I only got limited permission. The proxy account need to be setup in destination server(A) or source server(B)?
Hi @jn93 ,
You need to give the account permission to access the two server.
Hi @Avery Tang
Now I can successfully run using SQL server agent by using proxy I created like you recommend. I create proxy account in the deployed sql server.