Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Friday, November 24, 2017 2:49 PM | 1 vote
Hi, I'm getting this error reported :
Module: Microsoft.SQLServer2016.ReportingServices.Module.Discovery.ReportingServicesNativeProperty
Version: 6.7.31.0
Exception:
Exception happened during module execution:
at Microsoft.SQLServer2016.ReportingServices.Module.Helper.TimeoutThreadExecutor`1.Execute(Func`1 func, Int32 timeout, ManualResetEvent executeFinished)
at Microsoft.SQLServer2016.ReportingServices.Module.Helper.ModuleBasePropertyHelper`1.GetOutputData(DataItemBase[] inputDataItems)
at Microsoft.SQLServer2016.ReportingServices.Module.Helper.ModuleBaseHelper`1.OnNewDataItems(DataItemBase[] dataItems, Boolean logicallyGrouped, DataItemAcknowledgementCallback acknowledgeCallback, Object acknowledgedState, DataItemProcessingCompleteCallback completionCallback, Object completionState)
in Microsoft.SQLServer.2016.ReportingServices.Module.Helper
Inner Exception:
Unable to get FQDN for host 'SSRS_X1_AG,43000'. Attempt log:
Unable to get FQDN via DNS for host 'SSRS_X1_AG,43000': No such host is known
Unable to get FQDN via WMI for host 'SSRS_X1_AG,43000': The RPC server is unavailable. (Exception from HRESULT: 0x800706BA)
at Microsoft.SQLServer2016.ReportingServices.Module.Helper.ComputerNameHelper.SmartGetFqdn(String sName, Func`2 additionalDnsCheck)
at Microsoft.SQLServer2016.ReportingServices.Module.Discovery.ReportingServicesNativeProperty.GetModuleData(DataItemBase[] inputDataItems)
at Microsoft.SQLServer2016.ReportingServices.Module.Helper.TimeoutThreadExecutor`1.<>c__DisplayClass0_0.<Execute>b__0()
in Microsoft.SQLServer.2016.ReportingServices.Module.Helper
Inner Exception:
The RPC server is unavailable. (Exception from HRESULT: 0x800706BA)
at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)
at System.Management.ManagementScope.InitializeGuts(Object o)
at System.Management.ManagementScope.Initialize()
at Microsoft.SQLServer2016.ReportingServices.Module.Helper.Wmi.WmiHelper.ConnectNewScope()
at Microsoft.SQLServer2016.ReportingServices.Module.Helper.Wmi.WmiHelper.Query(String queryString)
at Microsoft.SQLServer2016.ReportingServices.Module.Helper.ComputerNameHelper.GetPrincipalNameData(String netbiosName, String targetHostName, Nullable`1 isClustered, Func`2 getHelper)
at Microsoft.SQLServer2016.ReportingServices.Module.Helper.ComputerNameHelper.SmartGetFqdn(String sName, Func`2 additionalDnsCheck)
in mscorlib
The configuration properties are :
PrincipalName = srv000118.mitiegrp.internal.mitie.co.uk
ClassId = {56A1D2D6-6BD7-24B2-6F97-FD593DF0CFF4}
DiscoverySourceObjectId = {33CB250F-B19D-3A38-00A0-FD76E7B01D3E}
DiscoverySourceManagedEntityId = {0E2B2EE6-8F6F-5874-0C10-6F56873667B5}
Publisher = ReportingServices2016
TimeoutSeconds = 300
The FQDN it's attempting to obtain is for an AlwaysOnAvailability group, but it's including the port information as well so failing to find it.
Any suggestions on how I can get around this issue?
All replies (12)
Monday, November 27, 2017 8:43 AM
Hey,
judging by the error:
Unable to get FQDN for host 'SSRS_X1_AG,43000' I would say you have the DB instance entered wrong.
So as it cannot be resolved (due to the port being attached to the instance name) it then fails with:
"The RPC server is unavailable. (Exception from HRESULT: 0x800706BA)"
Where exactly do you get this error?
Is this an alert?
Regards,
Stoyan (Please take a moment to "Vote as Helpful" and/or "Mark as Answer" where applicable. This helps the community, keeps the forums tidy, and recognizes useful contributions. Thanks!) Blog: https://blog.pohn.ch/ Twitter: @StoyanChalakov
Monday, November 27, 2017 9:16 AM
Hi,
This is during discovery for Reporting Services.
I agree it is because the port is being attached to the server name. I'm not sure quite where this gets picked up from but this works for all our SQL Server discovery and the format is used throughout our estate.
Any ideas / thoughts most welcome!
Monday, November 27, 2017 9:29 AM
Hi,
Have you tried the newest version of SQL management pack :
https://www.microsoft.com/en-us/download/details.aspx?id=53008
Best Regards,
Elton
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].
Monday, November 27, 2017 9:48 AM
Hi,
although the suggestion of Elton makes sense (to use the newest version of the MP) I doubt that this is the issue here. Still you can try using the newest version of the SSRS MP for 2016 (the link Elton provided is for SQL, you need the SSRS one):
Microsoft System Center Management Pack for SQL Server 2016 Reporting Services (Native Mode)
I just took a look at the MP discoveries here:
Microsoft SQL Server 2016 Reporting Services (Discovery, Native Mode)
and it seems the MP does a registry based discovery, creates a seed object and then discovers the seed.
Can you please check how the SSRS instance is entered in the registry?
Stoyan (Please take a moment to "Vote as Helpful" and/or "Mark as Answer" where applicable. This helps the community, keeps the forums tidy, and recognizes useful contributions. Thanks!) Blog: https://blog.pohn.ch/ Twitter: @StoyanChalakov
Monday, November 27, 2017 10:53 AM
The SSRS instance in the registry is entered normally (Name XXXXXSQL13_02, Data MSRS13.XXXXX13_02) - this is the instance where the report server service is located. Our ReportServer database however is located on a different instance 'SSRS_X1_AG,43000' to where reporting services is installed , on a different host entirely . I've searched the registry on the host where reporting services is installed for 'SSRS_X1_AG,43000' , and I can't see it in there at all - so assume it must be coming from elsewhere?
We are on the latest MP for both SQL 2016 and Reporting Services 2016 by the way, thank you for the suggestion though :)
Tuesday, November 28, 2017 12:11 PM
Still no joy with this :( Any further ideas?
Friday, December 8, 2017 12:10 PM
I am also getting the same error, the environment is a SharePoint farm where the 2 WFE's provide the SSRS web and the SQL database is on a separate Always On cluster. the error would suggest that its trying to resolve the "hostname,port" rather than stripping off the ",port"
Monday, December 11, 2017 3:35 PM
Thanks for the reply Sam H.
I don't suppose you have found a way around the issue?
Wednesday, December 13, 2017 2:15 PM
I wish, still trying to work it out, definitely will update here if I do find a resolution though
Monday, December 18, 2017 5:00 PM
Likewise! Also still looking for an answer! :(
Monday, December 18, 2017 5:15 PM
Hello,
I'd suggest to open a case with Microsoft.
Cheers
Sam (Please take a moment to "Vote as Helpful" and/or "Mark as Answer" wherever applicable. Thanks!)
Tuesday, January 16, 2018 4:27 PM
Hi,
SSRS MPs doesn't support such a connection string at the moment. This is a known issue, but could you please contact us at [email protected] with the detailed description so that we can file your request and increase the priority of this issue?