locked
Sharepoint 2013 Install - The network address is invalid RRS feed

  • Question

  • I am trying to install Sharepoint 2013 onto my Windows Server 2012 box that is already running SQL Server 2012.  The Windows 2012 box is joined to a domain (The controller is 2008 R2 Enterprise).  I am logged in with a Domain Admin account and I have got SQL Server running as a Domain Admin account and created another Domain Admin account called 'sharepoint' for the sharepoint application to run as.  I have also given the sharepoint account db_owner, db Creator and db sysadmin and db_security admin on Sql Server 2012.  I've done all I can to take permissions out of the equation!

    When I run the installer, it does create the sharepoint database in Sql Server, creates tables and populates them.  It then fails with the following error:       An error occurred while getting information about the user sharepoint at server home.mydomain.com: The network address is invalid 

    home.mydomain.com is the domain name of my domain.  It is not the name of a server though, a server would be myserver.home.mydomain.com.  Could this be the reason for the network address is invalid?  How can I fix this?

    01/01/2013 22:44:45 9 ERR Task configdb has failed with an unknown exception

    01/01/2013 22:44:45 9 ERR Exception: System.InvalidOperationException: An error occurred while getting information about the user sharepoint at server home.mydomain.com: The network address is invalid

    at Microsoft.SharePoint.Win32.SPNetApi32.NetUserGetInfo1(String server, String name)

    at Microsoft.SharePoint.Administration.SPManagedAccount.GetUserAccountControl(String username)

    at Microsoft.SharePoint.Administration.SPManagedAccount.Update()

    at Microsoft.SharePoint.Administration.SPProcessIdentity.Update()

    at Microsoft.SharePoint.Administration.SPApplicationPool.Update()

    at Microsoft.SharePoint.Administration.SPWebApplication.CreateDefaultInstance(SPWebService service, Guid id, String applicationPoolId, SPProcessAccount processAccount, String iisServerComment, Boolean secureSocketsLayer, String iisHostHeader, Int32 iisPort, Boolean iisAllowAnonymous, DirectoryInfo iisRootDirectory, Uri defaultZoneUri, Boolean iisEnsureNTLM, Boolean createDatabase, String databaseServer, String databaseName, String databaseUsername, String databasePassword, SPSearchServiceInstance searchServiceInstance, Boolean autoActivateFeatures)

    at Microsoft.SharePoint.Administration.SPWebApplication.CreateDefaultInstance(SPWebService service, Guid id, String applicationPoolId, IdentityType identityType, String applicationPoolUsername, SecureString applicationPoolPassword, String iisServerComment, Boolean secureSocketsLayer, String iisHostHeader, Int32 iisPort, Boolean iisAllowAnonymous, DirectoryInfo iisRootDirectory, Uri defaultZoneUri, Boolean iisEnsureNTLM, Boolean createDatabase, String databaseServer, String databaseName, String databaseUsername, String databasePassword, SPSearchServiceInstance searchServiceInstance, Boolean autoActivateFeatures)

    at Microsoft.SharePoint.Administration.SPAdministrationWebApplication.CreateDefaultInstance(SqlConnectionStringBuilder administrationContentDatabase, SPWebService adminService, IdentityType identityType, String farmUser, SecureString farmPassword) at Microsoft.SharePoint.Administration.SPFarm.CreateAdministrationWebService(SqlConnectionStringBuilder administrationContentDatabase, IdentityType identityType, String farmUser, SecureString farmPassword)

    at Microsoft.SharePoint.Administration.SPFarm.CreateBasicServices(SqlConnectionStringBuilder administrationContentDatabase, IdentityType identityType, String farmUser, SecureString farmPassword) 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()

    Wednesday, January 2, 2013 9:53 AM

Answers

All replies

  • On the Prodcution configuration wizard - Specify the Configuration database setting page,  you need to specify FQDN of your database server or specify  ip address of  your database server.

    Hope this will help you.

    Senthil

    Wednesday, January 2, 2013 10:26 AM
  • I did not try the FQDN of the database server, but I did try its IP Address.   In that case I ended up with the same error.  I will try with the FQDN next, thanks.
    Wednesday, January 2, 2013 10:49 AM
  • I tried that and it did not work either.  (myserver.home.mydomain.com)  The part that seems strange is that it is trying to find a network address at home.mydomain.com when that is a domain name and not a machine name.

    If I try and ping my (myserver.home.mydomain.com) I get a reply so it is a valid address.  Any other idea's?

    Wednesday, January 2, 2013 9:40 PM
  • There seems to be something wrong with communication between your SharePoint server and your domain controller, or your SharePoint server cannot even find the domain controller.

    Please take a look at

    http://blogs.technet.com/b/notesfromthefield/archive/2008/03/25/dns-configuration-for-windows-dns-servers.aspx

    http://support.microsoft.com/kb/825036

    And you may use dcdiag -v to check the configuration for your domain controller.

    • Marked as answer by ravetroll Saturday, January 5, 2013 1:04 PM
    Friday, January 4, 2013 6:50 AM
  • The problem was my domain controllers DNS client setup was pointed to the ISP DNS servers when in fact they should point to itself.  The dcdiag -v showed a problem with my setup, and after fixing the DNS setting, dcdiag -v showed a pass.  Sharepoint installed correctly after that.  Thanks.
    Saturday, January 5, 2013 1:06 PM
  • I had the same incorrect DNS client setup on DC before, it prevent me from installing Exchange 2013, however, i did not remember that it prevent me from installing sharepoint.
    • Edited by GuYuming Sunday, January 6, 2013 6:02 AM
    Sunday, January 6, 2013 6:02 AM