Sharepoint error unable to access SQL database

Hello EE,

We have a SQL cluster of 2 stand alone servers.  We have a SharePoint VM that I can access just fine now and the backup server can ping via DNS and DHCP, however backups are not working at night with the following errors.

Unknown SQL Exception 10060 occurred. Additional error information from SQL Server is included below.  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.)
operationsITAsked:
Who is Participating?
 
Vitor MontalvãoMSSQL Senior EngineerCommented:
Looks like the port is refusing the connection. There's any firewall between the hosts? Or the Windows firewall is activated?
0
 
Rich WeisslerProfessional Troublemaker^h^h^h^h^hshooterCommented:
Unfortunately that's a relatively generic error.  I would check the following to start:
First, confirm that the backup system is attempting to connect to the SQL Cluster Instance name, not one of the physical server names.  
Second, check the SQL Server Log at around the same time you are getting this error.  Are there any relavent errors in that log?
Third, are there any firewall scope restrictions or is IPSec configured on the SQL port?
0
 
operationsITAuthor Commented:
The backup is getting to SharePoint and SharePoint is trying to access SQL via alias name and the backup fails.  The errors above are from the SharePoint server at the same time as the backup fails.
There are no firewalls and no errors on SQL server side
0
Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

 
Rich WeisslerProfessional Troublemaker^h^h^h^h^hshooterCommented:
So the backup is Sharepoint aware and is attempting to use the mechanism within Sharepoint to initiate a backup?  I can't think of any reason the SQL Client alias would fail.  I assume it's only the backup which is failing at night... that sharepoint itself is available during the operation.  I assume if you kick off a backup during the day, it fails the same way it fails at night?  

Something to try for troubleshooting... does the backup server software have the option to specify the database server and instance rather than relying on the alias on the Sharepoint server?
0
 
Vitor MontalvãoMSSQL Senior EngineerCommented:
Verify that the instance name is correct and that SQL Server is configured to allow remote connections
Just for confirm, did you verify this, right?

The backup is getting to SharePoint and SharePoint is trying to access SQL via alias name
How did you define the alias?
0
 
operationsITAuthor Commented:
@Rich - Yes and Sharepoint is working, it is just the backup and will during the day with a manual backup as well.

@ Victor - Yes and the alias is defined on the server, is there something I can check here I am concerned with this as well.
0
 
Rich WeisslerProfessional Troublemaker^h^h^h^h^hshooterCommented:
>  Yes and Sharepoint is working, it is just the backup and will during the day with a manual backup as well.

I interpret that as 'a manual backup works during the day'?  I assume that's a manual backup kicked off with your credentials.  Is the manual backup that works initiated from the backup server, or from the sharepoint server?  What credentials is the scheduled backup job configured to use?
0
 
Vitor MontalvãoMSSQL Senior EngineerCommented:
Yes and the alias is defined on the server,
Which server? Can you post a screen shot of the alias configuration?
0
 
operationsITAuthor Commented:
Yes, I will get this and post.  Thank you
0
 
operationsITAuthor Commented:
Here is the sharepoint server
SQL-ALIAS.docx
0
 
Vitor MontalvãoMSSQL Senior EngineerCommented:
Just re read your question and can't understand what you mean with: "We have a SQL cluster of 2 stand alone servers"
Or they are stand alone or they are clustered. They can't be both.

Did you try to run a telnet on the alias to verify the connection?
0
 
operationsITAuthor Commented:
Clustered sorry meant standalone as in not virtual, but yes clustered.

Cannot telnet to alias name
0
 
Vitor MontalvãoMSSQL Senior EngineerCommented:
Ok. You meant physical servers and not stand alone servers.
What's the error from the telnet command?
0
 
bergquistcompanyCommented:
Could not open connection to host on port.  Connection failed.

Though again Sharepoint works just not backups
0
 
operationsITAuthor Commented:
I apologize I was at another premise dealing with another emergency, but there is no firewall between the two.
0
 
operationsITAuthor Commented:
Based on this I need to be able to telnet to "MSSQL" on port 1433?
I can telnet to the server name in this alias USGUSXMSSQLP01 on port 1433.
0
 
Vitor MontalvãoMSSQL Senior EngineerCommented:
In comment #ID: 40682780 you said you couldn't telnet to the alias name and now you can. So problem fixed?
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.