Welcome to MSDN Blogs Sign in | Join | Help

Sameer Surve

I have been in the Software Industry for more than 16 years and am currently a senior consultant with Microsoft Consulting Services covering US West Region. After many years of procastination for not writing a blog, here is my attempt at it. My current technology focus is on SharePoint, BizTalk. The purpose of this blog is to help others avoid hours that they may potentially spend in researching the issues discussed in this blog. Disclaimer: The opinions expressed herein are my own personal opinions and do not represent my employer's views in anyway. The thoughts\recommendations offered here comes AS IS. No warranties, express or implied, are given. They have been offered in good faith and any consequential damage due to their use is the sole responsibility of the user.

Syndication

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

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 http://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.

Published Monday, June 15, 2009 12:49 PM by sameers

Comment Notification

If you would like to receive an email when updates are made to this post, please register here

Subscribe to this post's comments using RSS

Comments

# infoblog » ‘No such host is known’ error when configuring SSRS 2008 @ Monday, June 15, 2009 3:57 PM

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

infoblog » ‘No such host is known’ error when configuring SSRS 2008

# re: 'No such host is known' error when configuring SSRS 2008 @ Friday, September 18, 2009 3:58 AM

Excellent post, spot on for my specific problems, thanks for blogging this info.

Iain

Iain Wyatt

# re: 'No such host is known' error when configuring SSRS 2008 @ Thursday, November 05, 2009 6:55 AM

Very helpful indeed!! Thanks a lot,

M

Morten

Leave a Comment

(required) 
required 
(required) 

  
Enter Code Here: Required
Page view tracker