January 10, 2010 at 12:30 pm
Hi all
I have a problem when I use SSIS Package Configuration and Conenctions using SQL Authentication.
I develop simple to complex packages....but everything work in my machine and the conenctions in the connection manager use all SQL Authentication.
When package is ready, i decide to create package configurations for each of the conenctions in the connetion manager and deploy it to the server.
Well the problem start here....becasue as soon as i enable the package configuration and i run it again from my machine it does not work anymore.
The error is something like this:
error acquiring connectionmanager...etc...etc....the user do not have permission to connect with the database.
the problem goes away when i modify the connections to use windows authentication.
but if i use the windows authentication then when i deploy the package....the package fail becasue it will be executed by the SQL Service user account....which have minimal privilages...i guess...
If i remove the package configuration at all...WORK!!! even when deployed....
Anybody knows this problem?
I use OLEDB\Native SQL Server Client 10 or something like that....
Thanks
August 2, 2012 at 8:51 am
Hi Sugnu,
I now your post is a little bit old but i´m facing the same situation right now and I would like to know if you resolved this issue and if so, how you did it.
Kind Regards,
Paul
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply