Home Dashboard Directory Help
Search

Issue with Loopback address - SharePoint 2013 installation with SQL Server 2014 by Ashokch


Status: 

Closed
 as External Help for as External


1
0
Sign in
to vote
Type: Bug
ID: 804584
Opened: 10/4/2013 7:40:31 AM
Access Restriction: Public
0
Workaround(s)
view
0
User(s) can reproduce this bug

Description

While installing SharePoint 2013 with SQL Server 2014 noticed following issue with creating content databases. Looking at the details this seems like a loopback address issue. Any resolution on this topic would be helpful with RDP customer.


10/02/2013 20:30:45 9 ERR                    Exception: System.ArgumentException: vmtmebispsql01,3180 is an invalid or loopback address. Specify a valid server address.
at Microsoft.SharePoint.Administration.SPServer.ValidateAddress(String address)
at Microsoft.SharePoint.Administration.SPServer..ctor(String address, SPFarm farm, Guid id)
at Microsoft.SharePoint.Administration.SPConfigurationDatabase.RegisterDefaultDatabaseServices(SqlConnectionStringBuilder connectionString)
at Microsoft.SharePoint.Administration.SPConfigurationDatabase.Provision(SqlConnectionStringBuilder connectionString)
at Microsoft.SharePoint.Administration.SPFarm.Create(SqlConnectionStringBuilder configurationDatabase, SqlConnectionStringBuilder administrationContentDatabase, IdentityType identityType, String farmUser, SecureString farmPassword, SecureString masterPassphrase)
at Microsoft.SharePoint.Administration.SPFarm.Create(SqlConnectionStringBuilder configurationDatabase, SqlConnectionStringBuilder administrationContentDatabase, String farmUser, SecureString farmPassword, SecureString masterPassphrase)
at Microsoft.SharePoint.PostSetupConfiguration.ConfigurationDatabaseTask.CreateOrConnectConfigDb()
at Microsoft.SharePoint.PostSetupConfiguration.ConfigurationDatabaseTask.Run()
at Microsoft.SharePoint.PostSetupConfiguration.TaskThread.ExecuteTask()
The configuration does create the main content database and other tables within it, but then fails. So I know it’s able to see the server and the user logs in and has the right level of access to create the database, etc.

Details
Sign in to post a comment.
Posted by Sethu Srinivasan on 10/4/2013 at 8:42 AM
Can you try connecting to sql instance "vmtmebispsql01,3180 " using SSMS / sqlcmd?

Thanks
Sethu Srinivasan [MSFT]
SQL Server
Sign in to post a workaround.