I just about went crazy trying to do a SSRS install on a named instance. Every time I ran through the database configuration, I got this error.
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()
Turns out, this issue has a simple, but hidden workaround. Specify the Server Name as outlined on this blog post:
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.
No comments:
Post a Comment