SQL Server Reporting Service - Unable to connect to Web Service and Web Portal URLs after changing SSL Certificate

Steve 21 Reputation points
2022-06-17T13:39:59.087+00:00

My BI solution had been working fine until we needed to change the SSRS certificate as it was due to expire, the certificate was replaced and since then we've not been able to connect to the SSRS URL's.
The build is VMware Server
Windows 2016 Standard
SQL Server 2019 Standard 64 bit 2019.0150.4223.01
SSRS Report Server Version 2018.0150.1102.911

To remove and then add the new Cert bindings and URL's we've run the appropriate netsh commands
In Chrome we're getting the site cannot be reach ERR_CONNECTION_CLOSED
I've tried repairing SSRS, reinstalling, running it without an SSL Cert, Deleting the encrypted content from SSRS Config Manager but we continue to get the same issue, this had been working without issue prior to trying to replace the SSL Cert
In the RSHosting Log it shows
2022-06-17 12:58:24.7076|WARN|9|Child Process [Portal] Died. Check the log for further information
2022-06-17 13:06:20.3097|INFO|12|Throttled restart of process by 475,592.58ms: Portal
2022-06-17 13:06:20.3097|INFO|12|Launching Process : Portal
2022-06-17 13:06:20.3097|INFO|12|Starting Process: C:\Program Files\Microsoft SQL Server Reporting Services\SSRS\Portal\RSPortal.exe
2022-06-17 13:06:24.4160|WARN|14|Child Process [Portal] Died. Check the log for further information
The RSPortal log is blank
The RSManagement log shows
2022-06-17 13:01:18.0486|ERROR|6|Unhandled error in the Web API. Exception: System.Net.Http.HttpRequestException: Error while copying content to a stream. ---> System.IO.IOException ---> System.Net.HttpListenerException: The I/O operation has been aborted because of either a thread exit or an application request
at System.Net.HttpResponseStream.EndWrite(IAsyncResult asyncResult)
at Microsoft.Owin.Host.HttpListener.RequestProcessing.ExceptionFilterStream.EndWrite(IAsyncResult asyncResult)
--- End of inner exception stack trace ---
at Microsoft.Owin.Host.HttpListener.RequestProcessing.ExceptionFilterStream.EndWrite(IAsyncResult asyncResult)
at System.Threading.Tasks.TaskFactory1.FromAsyncCoreLogic(IAsyncResult iar, Func2 endFunction, Action1 endAction, Task1 promise, Boolean requiresSynchronization)
--- End of inner exception stack trace ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Web.Http.Owin.HttpMessageHandlerAdapter.<SendResponseContentAsync>d__33.MoveNext()| RequestID = s_36172802-3488-4812-903a-4e1e55042afb
2022-06-17 13:01:18.0556|INFO|6|NT Service\SQLServerReportingServices ::1: GET /api/v1.0/ManagementState - 0:00:00.025179
Connection dropped| RequestID = s_36172802-3488-4812-903a-4e1e55042afb System.Threading.Tasks.TaskCanceledException: A task was canceled.
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Web.Http.Owin.HttpMessageHandlerAdapter.<SendResponseContentAsync>d__33.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Web.Http.Owin.HttpMessageHandlerAdapter.<InvokeCore>d__20.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.BIServer.Management.WebHost.RequestLoggingMiddleWare.<Invoke>d__2.MoveNext()
The ReportingServices Log
library!DefaultDomain!20c8!06/17/2022-12:50:47:: i INFO: Initializing WatsonDumpOnExceptions to 'Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException,Microsoft.ReportingServices.Modeling.InternalModelingException,Microsoft.ReportingServices.ReportProcessing.UnhandledReportRenderingException' as specified in Configuration file.
library!DefaultDomain!20c8!06/17/2022-12:50:47:: i INFO: Initializing WatsonDumpExcludeIfContainsExceptions to 'Microsoft.PowerBI.ReportServer.WebApi.Catalog.CatalogAccessException,System.Threading.ThreadAbortException,System.Web.UI.ViewStateException,System.OutOfMemoryException,System.Web.HttpException,System.IO.IOException,System.IO.FileLoadException,Microsoft.SharePoint.SPException,Microsoft.ReportingServices.WmiProvider.WMIProviderException,System.AppDomainUnloadedException' as specified in Configuration file.
and
library!DefaultDomain!20c8!06/17/2022-12:50:47:: i INFO: Dump on: Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogExceptionMicrosoft.ReportingServices.Modeling.InternalModelingExceptionMicrosoft.ReportingServices.ReportProcessing.UnhandledReportRenderingException
library!DefaultDomain!20c8!06/17/2022-12:50:47:: i INFO: Do not dump on: Microsoft.PowerBI.ReportServer.WebApi.Catalog.CatalogAccessExceptionSystem.Threading.ThreadAbortExceptionSystem.Web.UI.ViewStateExceptionSystem.OutOfMemoryExceptionSystem.Web.HttpExceptionSystem.IO.IOExceptionSystem.IO.FileLoadExceptionMicrosoft.SharePoint.SPExceptionMicrosoft.ReportingServices.WmiProvider.WMIProviderExceptionSystem.AppDomainUnloadedException
and
library!WindowsService_0!20c8!06/17/2022-12:50:47:: i INFO: Initializing WatsonDumpOnExceptions to 'Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException,Microsoft.ReportingServices.Modeling.InternalModelingException,Microsoft.ReportingServices.ReportProcessing.UnhandledReportRenderingException' as specified in Configuration file.
library!WindowsService_0!20c8!06/17/2022-12:50:47:: i INFO: Initializing WatsonDumpExcludeIfContainsExceptions to 'Microsoft.PowerBI.ReportServer.WebApi.Catalog.CatalogAccessException,System.Threading.ThreadAbortException,System.Web.UI.ViewStateException,System.OutOfMemoryException,System.Web.HttpException,System.IO.IOException,System.IO.FileLoadException,Microsoft.SharePoint.SPException,Microsoft.ReportingServices.WmiProvider.WMIProviderException,System.AppDomainUnloadedException' as specified in Configuration file.
and
servicecontroller!DefaultDomain!20c8!06/17/2022-12:50:48:: e ERROR: Error creating HTTP endpoint. System.Runtime.InteropServices.COMException (0x800704D0): The network location cannot be reached. For information about network troubleshooting, see Windows Help. (Exception from HRESULT: 0x800704D0)
at Microsoft.ReportingServices.HostingInterfaces.IRsUnmanagedCallback.CreateHttpEndpoint(RsAppDomainType application, String[] urlPrefixes, Int32 cPrefixes, String[] hosts, Int32 cHosts, Boolean wildCardPresent, String virtualDirectory, String filePath, Int32 authType, Int32 logonMethod, String authDomain, String authRealm, Boolean authPersist, Int32 extendedProtectionLevel, Int32 extendedProtectionScenario, Boolean enabled)
at Microsoft.ReportingServices.Library.ServiceAppDomainController.SetWebConfiguration(RunningApplication rsApplication, Boolean enabled, String folder)
The EventViewer is picking up
A fatal error occurred while creating a TLS client credential. The internal error state is 10013.
The Reporting service is run with a domain managed service account
I've 3 other servers that I'll need to replace SSRS expiring SSL certificates so any help in resolving this would be greatly appreciated

SQL Server
SQL Server
A family of Microsoft relational database management and analysis systems for e-commerce, line-of-business, and data warehousing solutions.
8,490 questions
SQL Server Reporting Services
SQL Server Reporting Services
A SQL Server technology that supports the creation, management, and delivery of both traditional, paper-oriented reports and interactive, web-based reports.
2,098 questions
Windows Server
Windows Server
A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.
8,160 questions
No comments
{count} votes

2 answers

Sort by: Most helpful
  1. Isabellaz-1451 3,606 Reputation points
    2022-06-20T01:44:47.277+00:00

    Hi @Steve

    This error is logged when there are Schannel Security Service Provider (SSP) related issues. For example, web server might be trying to use an encryption algorithm or protocol that were actually disabled.
    Similarly, incompatible machine keys or machine keys with insufficient file permissions may be other possible reasons of “The internal error state is 10013” error message.

    About how to solve this error:
    Correct the permissions on the c:\ProgramData\Microsoft\Crypto\RSA\MachineKeys folder:

    1. Everyone Access: Special Applies to: This folder only
    2. Network Service Access: Read & Execute Applies to: This folder, subfolders and files
    3. Administrators Access: Full Control Applies to: This folder, subfolder and files
    4. System Access: Full control Applies to: This folder, subfolder and Files
    5. IUSR Access: Full Control Applies to: This folder, subfolder and files

    I refered to this thread:https://port135.com/schannel-the-internal-error-state-is-10013-solved/
    Hope these will help you.

    Best Regards,
    Isabella


    If the answer is the right solution, please click "Accept Answer" and upvote it. If you have extra questions about this answer, please click "Comment".
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.


  2. Steve 21 Reputation points
    2022-06-21T16:16:16.057+00:00

    I found the following command seems have enabled the access via SSMS and the SSRS Webpages to work 'netsh http add iplisten IPAddressOfTheServer', as soon as I ran the command I was able to access the web page and also could connect to SSRS via SSMS. The webpage I found it on had this as the description it was not binding to my ipv4 ip address, but was binding to ipv6 address.
    https://stackoverflow.com/questions/14029629/iis-cant-access-page-by-ip-address-instead-of-localhost

    No comments