SQL Express under Vista....is this problem a Vista Issue? [modified]
-
Okay....I'm writing an enterprise application but testing on my local machine. I've got my clients talking to the server which is a WCF service. The services then connect to the database and does the reads/writes/etc. I have the 2.0 and 3.0 framework installed. I'm running Sql Server Express 2005 SP2. When I connect to SQL Server 2005 on the network, all works fine. When I connect to my local machine I get the login failure error. I've added my service userID to the server, I've checked all databases for access approval, and I've marked the server approved to be connected remotely. Yet I still keep getting the server connection fail exception. Does anyone know if there is a security issue accessing Sql Server 2005 Express under Vista remotely? Need help ASAP! Thanks. -- modified at 17:50 Friday 29th June, 2007
-
Okay....I'm writing an enterprise application but testing on my local machine. I've got my clients talking to the server which is a WCF service. The services then connect to the database and does the reads/writes/etc. I have the 2.0 and 3.0 framework installed. I'm running Sql Server Express 2005 SP2. When I connect to SQL Server 2005 on the network, all works fine. When I connect to my local machine I get the login failure error. I've added my service userID to the server, I've checked all databases for access approval, and I've marked the server approved to be connected remotely. Yet I still keep getting the server connection fail exception. Does anyone know if there is a security issue accessing Sql Server 2005 Express under Vista remotely? Need help ASAP! Thanks. -- modified at 17:50 Friday 29th June, 2007
Hi, SQL Server 2005 Express doesn't allow remote connections on a Vista machine by default. You need to alter a few settings. See following articles : - http://samirhelps.wordpress.com/2007/06/27/hello-world/[^] - http://blogs.msdn.com/sqlexpress/archive/2005/05/05/415084.aspx[^] - http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1696957&SiteID=1[^] Kind regards Sven
-
Hi, SQL Server 2005 Express doesn't allow remote connections on a Vista machine by default. You need to alter a few settings. See following articles : - http://samirhelps.wordpress.com/2007/06/27/hello-world/[^] - http://blogs.msdn.com/sqlexpress/archive/2005/05/05/415084.aspx[^] - http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1696957&SiteID=1[^] Kind regards Sven
Thanks for the info Sven. The first link is total, useless crap. The second and third are really good. I've done everything in those links without success. My server is marked for remote connections. My server has tcp/ip active. The browser is running and both services are added to the firewall. The connection string is pointing to (local) sqlcmd connects to the server. WCF refuses to see the database. An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)
-
Thanks for the info Sven. The first link is total, useless crap. The second and third are really good. I've done everything in those links without success. My server is marked for remote connections. My server has tcp/ip active. The browser is running and both services are added to the firewall. The connection string is pointing to (local) sqlcmd connects to the server. WCF refuses to see the database. An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)
Hi, The first link was more about the common info for this problem, not really a solution, maybe I must have mentioned it. Normally if you following the guidelines of those 2 other links, it must work. It did for us. But I have asked the question to 2 collegues (one of them is an expert in WCF). So as soon as they send me answer I will post it here.
Sven Cipido (http://blog.svencipido.be)
-
Thanks for the info Sven. The first link is total, useless crap. The second and third are really good. I've done everything in those links without success. My server is marked for remote connections. My server has tcp/ip active. The browser is running and both services are added to the firewall. The connection string is pointing to (local) sqlcmd connects to the server. WCF refuses to see the database. An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)
Hi Sven here again. One of my collegues told me that he had that error also and that it has todo with the security on your SQL server. Propably only Integrated Security is set on. iIf that's true, you must conenct through SQl Authentication. So check under the security proeprties of your server what the connection is (Windows authentication or SQL Server authentication). Be sure you have to right connection in your conenction string. We hope this is the solution.
Sven Cipido (http://blog.svencipido.be)
-
Hi Sven here again. One of my collegues told me that he had that error also and that it has todo with the security on your SQL server. Propably only Integrated Security is set on. iIf that's true, you must conenct through SQl Authentication. So check under the security proeprties of your server what the connection is (Windows authentication or SQL Server authentication). Be sure you have to right connection in your conenction string. We hope this is the solution.
Sven Cipido (http://blog.svencipido.be)
Sven, Thanks for the info. I finally gave up and installed SQL instead of the Express version. We are testing services and they have to do Integrated Security. Thanks, Michael