July 23, 2015 at 2:23 am
Hi all
I've got an SSIS package built in VS2010 that needs to connect to a SQL2012 database (the database already exists with tables, etc).
I've set up a SQL-only login using SSMS, entered the password and removed password expiry, etc.
When I try to use the SQL-only login to connect to the database in VS, I get an error stating :-
"Test connection failed because of an error initializing provider. Login failed for <username>".
Under Provider at the top of the wizard, I've got "Native OLE DB\SQL Server Native Client 11.0".
The server name is correct and I'm 100% certain the username and password are exactly the same as the SQL-only I've created on the server.
Anyone any ideas?
July 23, 2015 at 7:52 am
richardmgreen1 (7/23/2015)
Hi allI've got an SSIS package built in VS2010 that needs to connect to a SQL2012 database (the database already exists with tables, etc).
I've set up a SQL-only login using SSMS, entered the password and removed password expiry, etc.
When I try to use the SQL-only login to connect to the database in VS, I get an error stating :-
"Test connection failed because of an error initializing provider. Login failed for <username>".
Under Provider at the top of the wizard, I've got "Native OLE DB\SQL Server Native Client 11.0".
The server name is correct and I'm 100% certain the username and password are exactly the same as the SQL-only I've created on the server.
Anyone any ideas?
Have you checked to see if the SQL instance is set to only allow Windows logins ?
Steve (aka sgmunson) 🙂 🙂 🙂
Rent Servers for Income (picks and shovels strategy)
July 23, 2015 at 8:08 am
DOH! :blush:
Thanks for that. It was set to allow Windows only so I've changed it to Windows and SQL authentication.
July 23, 2015 at 8:15 am
richardmgreen1 (7/23/2015)
DOH! :blush:Thanks for that. It was set to allow Windows only so I've changed it to Windows and SQL authentication.
You're welcome... and been there, and DOH! 'd :blush: that...
Steve (aka sgmunson) 🙂 🙂 🙂
Rent Servers for Income (picks and shovels strategy)
July 23, 2015 at 8:21 am
Now for a stupid question.
We're setting up a DEV server and a PROD server.
If I design an SSIS package on DEV, can I deploy it on PROD?
I'm going to try it anyway, just wanting to check in case there's anything different I need to do.
July 23, 2015 at 9:45 am
Yeah why not, just remember to change your connection manager in your package to point to the live database not the dev.
July 24, 2015 at 1:53 am
Thanks for the confirmation, it all seems to have worked anyway.
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply