We are facing issue in configuring SP 2013 using SQL Always on on IaaS server   When we are running SharePoint Config wizard its successfully creating dbs if we give one SQL server name instead of listener.   If we give listener its failing. It creates SharePoint_config db in the listener with no tables in it.

 

  The service account had full permissions    This is causing only for SharePoint components ,we were able to create sample databases in listener and it reflects in primary node  

• Edited by Benjamin KNR 22 hours 42 minutes ago

Hi Benjamin,

Please make sure you have followed the steps in the following article to configure SQL alwayson for SharePoint 2013:

https://technet.microsoft.com/en-in/library/jj715261.aspx?f=255&MSPPError=-2147217396#overview

We recommend the following installation sequence and key configuration steps to deploy a SharePoint farm that uses an AlwaysOn availability group:

• Select or create a Windows Server failover cluster.
• Install SQL Server 2012 on each cluster node.
• Create and configure an availability group.
• Install and configure SharePoint 2013.
• Add the SharePoint databases to the availability group.
• Test failover for the availability group.

To enable AlwaysOn, your logon account must have the permission levels to create an availability group. The account must have membership in the db_owner fixed database role and either CREATE AVAILABILITY GROUP server permission, CONTROL AVAILABILITY GROUP permission, ALTER ANY AVAILABILITY GROUP permission, or CONTROL SERVER permission.

To create the availability group, make sure that your logon account has the required permissions to create an availability group. This requires membership in the db_owner fixed database role and either CREATE AVAILABILITY GROUP server permission, CONTROL AVAILABILITY GROUP permission, ALTER ANY AVAILABILITY GROUP permission, or CONTROL SERVER permission.

Before running config wizard, you need to run Setup to install binaries, configure security permissions, and edit registry settings for SharePoint 2013.

For more information:

http://blogs.msdn.com/b/sambetts/archive/2013/04/24/sharepoint-2013-and-sql-server-alwayson-high-availability-sharepoint.aspx

http://blogs.technet.com/b/canitpro/archive/2013/08/20/step-by-step-creating-a-sql-server-2012-alwayson-availability-group.aspx

Regards,