How to know if connection can be made to SQL 2008 R2 in my case? Thanks.

Question

Post reply

How to know if connection can be made to SQL 2008 R2 in my case? Thanks.

halifaxdal

SSCoach

Points: 19741
More actions
September 19, 2012 at 12:43 pm

#262704

Hello,
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.

Viewing 12 posts - 1 through 11 (of 11 total)

You must be logged in to reply to this topic. Login to reply

PaulB-TheOneAndOnly SSC Guru Points: 66772 More actions · Answer 1

halifaxdal (9/19/2012)
Event ID: 4105: Windows is in Notification period.

I think your Windows O/S has also expired the license... message is consistent with unlicensed O/S

_____________________________________
Pablo (Paul) Berzukov

Author of Understanding Database Administration available at Amazon and other bookstores.

Disclaimer: Advice is provided to the best of my knowledge but no implicit or explicit warranties are provided. Since the advisor explicitly encourages testing any and all suggestions on a test non-production environment advisor should not held liable or responsible for any actions taken based on the given advice.

halifaxdal SSCoach Points: 19741 More actions · Answer 2

PaulB-TheOneAndOnly (9/19/2012)
halifaxdal (9/19/2012)
Event ID: 4105: Windows is in Notification period.
I think your Windows O/S has also expired the license... message is consistent with unlicensed O/S

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.

Sean Lange SSC Guru Points: 286590 More actions · Answer 3

halifaxdal (9/19/2012)
PaulB-TheOneAndOnly (9/19/2012)
halifaxdal (9/19/2012)
Event ID: 4105: Windows is in Notification period.
I think your Windows O/S has also expired the license... message is consistent with unlicensed O/S
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.

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.

_______________________________________________________________

Need help? Help us help you.

Read the article at http://www.sqlservercentral.com/articles/Best+Practices/61537/ for best practices on asking questions.

Need to split a string? Try Jeff Modens splitter http://www.sqlservercentral.com/articles/Tally+Table/72993/.

Cross Tabs and Pivots, Part 1 – Converting Rows to Columns - http://www.sqlservercentral.com/articles/T-SQL/63681/
Cross Tabs and Pivots, Part 2 - Dynamic Cross Tabs - http://www.sqlservercentral.com/articles/Crosstab/65048/
Understanding and Using APPLY (Part 1) - http://www.sqlservercentral.com/articles/APPLY/69953/
Understanding and Using APPLY (Part 2) - http://www.sqlservercentral.com/articles/APPLY/69954/

Lowell SSC Guru Points: 323518 More actions · Answer 4

You 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.

Lowell

--help us help you! If you post a question, make sure you include a CREATE TABLE... statement and INSERT INTO... statement into that table to give the volunteers here representative data. with your description of the problem, we can provide a tested, verifiable solution to your question! asking the question the right way gets you a tested answer the fastest way possible!

halifaxdal SSCoach Points: 19741 More actions · Answer 5

No 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?

halifaxdal SSCoach Points: 19741 More actions · Answer 6

After further troubleshooting, I have manually enabled both servers' inbound/outbound 1433 TCP/UDP ports

My 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_SGCS

Thank you in advance.

Sean Lange SSC Guru Points: 286590 More actions · Answer 7

Take a look here. http://www.connectionstrings.com/[/url]

This site has connection string details for just about everything.

_______________________________________________________________

Need help? Help us help you.

Read the article at http://www.sqlservercentral.com/articles/Best+Practices/61537/ for best practices on asking questions.

Need to split a string? Try Jeff Modens splitter http://www.sqlservercentral.com/articles/Tally+Table/72993/.

Cross Tabs and Pivots, Part 1 – Converting Rows to Columns - http://www.sqlservercentral.com/articles/T-SQL/63681/
Cross Tabs and Pivots, Part 2 - Dynamic Cross Tabs - http://www.sqlservercentral.com/articles/Crosstab/65048/
Understanding and Using APPLY (Part 1) - http://www.sqlservercentral.com/articles/APPLY/69953/
Understanding and Using APPLY (Part 2) - http://www.sqlservercentral.com/articles/APPLY/69954/

halifaxdal SSCoach Points: 19741 More actions · Answer 8

Sean Lange (9/20/2012)
Take a look here. http://www.connectionstrings.com/[/url]
This site has connection string details for just about everything.

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 errorlog

Wouldn't this be weird? What did I miss?

Any clue is appreciated

halifaxdal SSCoach Points: 19741 More actions · Answer 9

I 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?

halifaxdal SSCoach Points: 19741 More actions · Answer 10

I 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_SGCS

When 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!

halifaxdal SSCoach Points: 19741 More actions · Answer 11

Although 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.