'No such host is known' error when configuring SSRS 2008

  • Makale

 

Environment

  • SQL backend, SSRS server: SQL 2008 SP1
  • SQL backend is behind the firewall with only specific DB port open (port used by SQL browser is not open…hence the need to specify specific port)
  • RS service login has DB Creator and Security Admin privileges

 

Issue

During initial configuring SSRS (in creating RS database) we kept getting (during 'generating Rights script' step)

 

System.Net.Sockets.SocketException: No such host is known

   at System.Net.Dns.GetAddrInfo(String name)

   at System.Net.Dns.InternalGetHostByName(String hostName, Boolean includeIPv6)

   at System.Net.Dns.GetHostEntry(String hostNameOrAddress)

   at ReportServicesConfigUI.RSDatabase.IsLocalDbServer(String dbServer)

   at ReportServicesConfigUI.RSDatabase.GrantRSConnectionRights()

   at ReportServicesConfigUI.RSDatabase.CreateNewDatabase()

 

RS database does get created but is in incomplete state.

 

Per https://blogs.msdn.com/psssql/archive/2009/03/05/socketexception-when-creating-a-new-report-server-database.aspx specifying port will not work.

 

This has been verified (that it does not work) by using SQL alias (which references port) as well as specifying it within "server name,port\SQL Instance" name format (for e.g. SQL_Server,1234\SQL_Instance…port used by SQL instance is 1234)

 

Using without port references works (for e.g. SQL_Server\SQL_Instance format)…but for this to work,SQL Browser service needs to be enabled and UDP 1434 port needs to be opened through the firewall (if one exists)

 

Using format SQL_Server\SQL_Instance format works as long as SQL Browser service is running and in case of firewall the SQL Browser port is open (which is not always the case)

 

 

Btw, little more digging we did find a workaround….

 

It seems if you use a connection format like “ServerName\InstanceName,Port”, then SSRS Configuration manager is able to connect without requiring the SQL Browser service.

 

Without SQL Browser service running (either shutdown or blocked behind the firewall), SSRS Configuration Manager still does not work with “ServerName,Port\InstanceName” format or via SQL Aliases.

Comments

  • Anonymous
    June 15, 2009
    PingBack from http://blog.a-foton.ru/index.php/2009/06/15/no-such-host-is-known-error-when-configuring-ssrs-2008/

  • Anonymous
    September 17, 2009
    Excellent post, spot on for my specific problems, thanks for blogging this info. Iain

  • Anonymous
    November 04, 2009
    Very helpful indeed!! Thanks a lot, M

  • Anonymous
    January 21, 2010
    wonderful i look for the solution for two days. great post  

  • Anonymous
    February 19, 2010
    Thank you - this sorted my problem!

  • Anonymous
    March 17, 2010
    I am glad I found this blog. It saved me lots of time. Microsoft needs to step up and address the failure of the sql browser to reslove the default instance to a port other than 1433. It is now standard practice for DBAs to change the ip port to something other than 1433 since viruses target the default port number. The SQL browser assumes that the default instance is using 1433 which requires a workaround. I guess SSRS can not figure out how to put a port number in the script and thus we have this issue.

  • Anonymous
    October 09, 2011
    Excellent post. Saved lot of my time. I was looking for the solution for last 2 hours and the trick mentioned by Sameer worked for me. ServerName,PortInstanceName. Thank you so much and keep the good work.

  • Anonymous
    August 28, 2013
    The comment has been removed

  • Anonymous
    May 09, 2014
    I have the same problema, no instance, no firewall. Everything works fine. I have used the CRTL+V and a space at the end is causing the error. Just typing the name again and work as a charm.