January 15, 2010 at 4:06 pm
hi guys, please your help with this. I have a user which has all the necessary permissions to a Database. The user is trying to run a ssis package from Visual Studio (he does not have management studio installed ). when he goes to test connection in the DestinationConnectionOLDB. he gets this error message:
The test connection failed because of an error initializing provider. An error has ocurred while establishing a connection to the server. When connecting to SQl Server 2005 this failure maybe be caused by the fact that under the default settings SQL Server does not allow remote connections. Client unable to establish connection. Encryption not supported on the client.
This is what i have checked so far:
Make sure user has permissions to connect to the server.
Make sure instance allows remote connections--Yes.
I tried running the package and i don't get the error.
:ermm:
January 18, 2010 at 12:30 am
Hi,
this is what my personal knowledge base sais (got the snippet from somewhere on the net; sorry, no sources cited):
Here is what I've found at
http://blogs.msdn.com/sql_protocols/archive/2005/12/22/506607.aspx
Your client side setting probably was messed up. Please go to SQL Server Configuration Manager and click properties for "SQL Native Client Configuration", if correct, you should be able to see two flags, one is "force client encryption", the other one is "trust server certificate" and value were set "yes" or "no". If you see "No properties are available", that means your client registry key was messed up and leads to the connection error . To fix this, suggest reinstall SNAC (SQL Native Client).
WM_HOPETHATHELPS
Günter
January 20, 2010 at 4:22 pm
hi thank you for your reply, yes it seems to be with his visual studio, because we even tried creating a new package and when you create a new connection, the scroll down of the database is empty. He has SQL Native Client and Visual studio 2005 installed. I suggested to him to reinstall SNAC (SQL Native Client) as well as Visual Studio. Let me cross my finger i will let you know if that fixed the problem.
January 21, 2010 at 6:33 am
check out this link:
http://social.msdn.microsoft.com/forums/en-US/sqlxml/thread/5b259308-1c7a-49ee-898b-09f5b6807e38/
you may just need to repair the msxml 6 service pack 2. go to change remove programs and select change when you locate msxml 6 service pack 2.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply