1

I've installed SSRS (v14.0.6681.5121) and configured it with my SQL Server 2017 instance. I noticed that my drive was filling up very quickly and tracked it down to this SSRS log as well as a 200MB .mdmp file every minute or so. I haven't been able to track down why this would be happening or any forum posts describing it. Log file below.

2018-09-03 02:15:57.4220|INFO|1|File Logger created: 'C:\Program Files\Microsoft SQL Server Reporting Services\SSRS\LogFiles\RSManagement_${DailyDate}.log' - level Info, will roll at 32 Mb, process id 7108
2018-09-03 02:15:57.5390|INFO|1|CFG : Dumper.path = [..\LogFiles\] (env)
2018-09-03 02:15:57.5390|INFO|1|CFG : Name = [] (env)
2018-09-03 02:15:57.5390|INFO|1|CFG : Dumper.flags = [SendToWatson, AllThreads, AllMemory] (env)
2018-09-03 02:15:57.5450|INFO|1|CFG : Dumper.preventIfContains = [Microsoft.BIServer.HostingEnvironment.Exceptions.TrustedProcessTokenExpiredException] (env)
2018-09-03 02:15:57.5450|INFO|1|Do not dump on: Microsoft.BIServer.HostingEnvironment.Exceptions.TrustedProcessTokenExpiredException
2018-09-03 02:15:57.5450|INFO|1|CFG : listenerUrl = [http://+:8082/] (env)
2018-09-03 02:15:57.5450|INFO|1|CFG : rsConfigFilePath = [..\ReportServer\rsreportserver.config] (env)
2018-09-03 02:15:57.5660|INFO|1|SKU: SQL Server Standard
2018-09-03 02:15:57.6530|ERROR|1|Unhandled exception in Appdomain System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.Net.HttpListenerException: The process cannot access the file because it is being used by another process
   at System.Net.HttpListener.AddAllPrefixes()
   at System.Net.HttpListener.Start()
   at Microsoft.Owin.Host.HttpListener.OwinHttpListener.Start(HttpListener listener, Func`2 appFunc, IList`1 addresses, IDictionary`2 capabilities, Func`2 loggerFactory)
   at Microsoft.Owin.Host.HttpListener.OwinServerFactory.Create(Func`2 app, IDictionary`2 properties)
   --- End of inner exception stack trace ---
   at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)
   at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments)
   at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
   at Microsoft.Owin.Hosting.ServerFactory.ServerFactoryAdapter.Create(IAppBuilder builder)
   at Microsoft.Owin.Hosting.Engine.HostingEngine.Start(StartContext context)
   at Microsoft.BIServer.Management.WebHost.Program.Main(String[] args): 
2018-09-03 02:15:57.6530|ERROR|1|Report server dump occurred: System.Reflection.TargetInvocationException at 
   at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)
   at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments)
   at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
   at Microsoft.Owin.Hosting.ServerFactory.ServerFactoryAdapter.Create(IAppBuilder builder)
   at Microsoft.Owin.Hosting.Engine.HostingEngine.Start(StartContext context)
   at Microsoft.BIServer.Management.WebHost.Program.Main(String[] args)
fixer1234
  • 28,064
Alex
  • 111
  • 6

1 Answers1

0

I ran into this same issue today. We've had an SSRS server running for years and this morning users started receiving "503 Service Unavailable" errors.

Reviewing the SSRS error logs, indicated the same error:

Unhandled exception in Appdomain System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.Net.HttpListenerException: The process cannot access the file because it is being used by another process

Ultimately, the issue was a port conflict on the RSHostingService, which defaults to port 8082. Another service was added listening on the same port. I updated the RSHostingService config file located at C:\Program Files\Microsoft SQL Server Reporting Services\SSRS\RSHostingService\config.json to use port 8083 instead. After saving and restarting the SSRS service, everything was back up and running.

I found this article on druva.com that confirmed what I was seeing:

Port 8082 is used for internal communications on the host for FS, NAS, Hyper-V, VMware, Oracle DTC, and MS SQL. If port 8082 is unavailable, other available ephemeral ports will be used.

To verify on my server I ran the following commands in an elevated command prompt.

netstat -ano -p TCP | find /I "listening" | find /I "8082"

enter image description here

This showed what was listening on port 8082 (Note: This screenshot is after I moved RSHostingService to 8083). Taking the PID on the right of the results, I could then put that in this command to identify the associated executable:

tasklist /fi "PID eq 16216"
Josh Jay
  • 171