InstantForum.NET v2.9.0SQLServerCentralhttp://www.sqlservercentral.com/Forums/notifications@sqlservercentral.comWed, 19 Jun 2013 20:32:46 GMT20http://www.sqlservercentral.com/Forums/Topic1361569-391-1.aspxAlthough no more replies here, I figured it out together with my colleague. One thing that went wrong was the UDP port 1434 should be open instead of 1433.Another thing I corrected is Windows Authentication for the website was not enabled (but that shouldn't affect the IIS can't locate the SQL server/instance)This is still a very strange case.Anyway, it is working now. Not fun but OK because I learn some lesson and I want to share with you guys here.Fri, 21 Sep 2012 17:15:12 GMThalifaxdalhttp://www.sqlservercentral.com/Forums/Topic1361569-391-1.aspxI have made the udl working and got the right connection string:Provider=SQLOLEDB.1;Integrated Security=SSPI;Persist Security Info=False;Initial Catalog=AOR;Data Source=ISCSGCSTEST1\SQL_SGCSWhen I used it in web.config, the page returns:Keyword not supported: 'provider'. I then dropped off the provider part:connectionString="Integrated Security=SSPI;Persist Security Info=False;Initial Catalog=AOR;Data Source=ISCSGCSTEST1\SQL_SGCS"/>But I still got this error message:A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) This is driving me nut!Thu, 20 Sep 2012 20:58:50 GMThalifaxdalhttp://www.sqlservercentral.com/Forums/Topic1361569-391-1.aspxI also tried to start profiler to monitor the server, unfortunately it seems it didn't capture any login request.In order to verify that the profiler is working, on the server itself, I use SSMS to log into the server, both windows authentication and SQL authentication are captured.What else I can try?Thu, 20 Sep 2012 20:25:59 GMThalifaxdalhttp://www.sqlservercentral.com/Forums/Topic1361569-391-1.aspx[quote][b]Sean Lange (9/20/2012)[/b][hr]Take a look here. [url=http://www.connectionstrings.com/]http://www.connectionstrings.com/[/url]This site has connection string details for just about everything.[/quote]So far I haven't found a working connection string, it always returns me error like the server/instance couldn't be found, or the remote connection is not enabled.I double checked in configuration manager as well as SSMS and the remote connection is open and TCP/UDP port 1433 is open.But I do have a new finding: I create a udl file and double click it to open a connection window, I then input the server/instance name just like the one I put in SSMS (which works fine), then I choose windows authentication, it fails; I tried to create a SQL account and I enabled the mix mode authentication and restarted the server, it still failed. However, I don't see any items in SQL's errorlogWouldn't this be weird? What did I miss?Any clue is appreciatedThu, 20 Sep 2012 20:15:53 GMThalifaxdalhttp://www.sqlservercentral.com/Forums/Topic1361569-391-1.aspxTake a look here. [url=http://www.connectionstrings.com/]http://www.connectionstrings.com/[/url]This site has connection string details for just about everything.Thu, 20 Sep 2012 07:47:12 GMTSean Langehttp://www.sqlservercentral.com/Forums/Topic1361569-391-1.aspxAfter further troubleshooting, I have manually enabled both servers' inbound/outbound 1433 TCP/UDP portsMy connection string is:connectionString="Data Source=10.40.2.90,1433\SQL_SGCS;I've tried: connectionString="Data Source=servername\SQL_SGCS;connectionString="Data Source=servername,1433\SQL_SGCS;I got similar error message saying the instance couldn't be found:A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: TCP Provider, error: 0 - A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.) How should I write my connection string in this case?On the SQL server, I can get in via management studio by servername\SQL_SGCSThank you in advance.Thu, 20 Sep 2012 04:38:59 GMThalifaxdalhttp://www.sqlservercentral.com/Forums/Topic1361569-391-1.aspxNo problem ping the SQL server, BUT: telnet 1433 failed!The firewalls for both the servers are turned off; netstat -an returns no 1433 is being listened. WHY?Wed, 19 Sep 2012 14:36:20 GMThalifaxdalhttp://www.sqlservercentral.com/Forums/Topic1361569-391-1.aspxYou could test agaisnt an express instance until your license comes in...just change your connection string;there's pretty much only 3 or 4 things in the string anyway; server, database, trusted connection or not, and if not, username and password.you can change those things whenever you need to change to teh Standard version once it gets installed.Wed, 19 Sep 2012 14:13:30 GMTLowellhttp://www.sqlservercentral.com/Forums/Topic1361569-391-1.aspx[quote][b]halifaxdal (9/19/2012)[/b][hr][quote][b]PaulB-TheOneAndOnly (9/19/2012)[/b][hr][quote][b]halifaxdal (9/19/2012)[/b][hr]Event ID: 4105: Windows is in Notification period.[/quote]I think your Windows O/S has also expired the license... message is consistent with unlicensed O/S[/quote]Other than waiting and applying the licenses, is there any way to test it out? I want to save some time before the licenses arrive.Thanks.[/quote]You can see if the IIS server can ping the SQL box. That will at least let you know that it can see the sql box. If it can ping it any other connection issues should be pretty quick and simple to sort out.Wed, 19 Sep 2012 14:08:53 GMTSean Langehttp://www.sqlservercentral.com/Forums/Topic1361569-391-1.aspx[quote][b]PaulB-TheOneAndOnly (9/19/2012)[/b][hr][quote][b]halifaxdal (9/19/2012)[/b][hr]Event ID: 4105: Windows is in Notification period.[/quote]I think your Windows O/S has also expired the license... message is consistent with unlicensed O/S[/quote]Other than waiting and applying the licenses, is there any way to test it out? I want to save some time before the licenses arrive.Thanks.Wed, 19 Sep 2012 13:28:23 GMThalifaxdalhttp://www.sqlservercentral.com/Forums/Topic1361569-391-1.aspx[quote][b]halifaxdal (9/19/2012)[/b][hr]Event ID: 4105: Windows is in Notification period.[/quote]I think your Windows O/S has also expired the license... message is consistent with unlicensed O/SWed, 19 Sep 2012 12:48:30 GMTPaulB-TheOneAndOnlyhttp://www.sqlservercentral.com/Forums/Topic1361569-391-1.aspxHello,I have an IIS server running on Windows 2008, it needs to connect to a SQL 2008 R2 on a remote machine.Both the two servers are newly built and we have not received licenses for them and the 30 days evaluation period already expires.When I test my website, it hangs there forever. I checked the eventlog on SQL server, there is a warning:Event ID: 4105: Windows is in Notification period.I don't know if I can still make connection even the license is ready, is there a way to find out or maybe there is some trick I can at least test out if the connection can be set up or not?I am using Windows Authentication, a dedicated ID is created on the same domain, the ID is used to run the application pool on the IIS server and the ID is also added into the SQL server. Presumably it should be passed over to SQL server.Thank you.Wed, 19 Sep 2012 12:43:56 GMThalifaxdal