Quote:2016-02-11 22:10:29.368 [ERROR][4] Unexpected error starting web server:
System.AppDomainUnloadedException: The application domain in which the thread was running has been unloaded.
at System.Web.Hosting.HostingEnvironment.Initialize(ApplicationManager appManager, IApplicationHost appHost, IConfigMapPathFactory configMapPathFactory, HostingEnvironmentParameters hostingParameters, PolicyLevel policyLevel)
at System.Web.Hosting.ApplicationManager.CreateAppDomainWithHostingEnvironment(String appId, IApplicationHost appHost, HostingEnvironmentParameters hostingParameters)
at System.Web.Hosting.ApplicationManager.CreateAppDomainWithHostingEnvironmentAndReportErrors(String appId, IApplicationHost appHost, HostingEnvironmentParameters hostingParameters)
at System.Web.Hosting.ApplicationManager.CreateInstanceInNewWorkerAppDomain(Type type, String appId, VirtualPath virtualPath, String physicalPath)
at System.Web.Hosting.ApplicationHost.CreateApplicationHost(Type hostType, String virtualDir, String physicalDir)
at Cassini.Server.CreateHost()
at Cassini.Server..ctor(Int32 port, String virtualPath, String physicalPath)
at NRecord.RecordingService.OnStart(String[] args)
Your logs confirm the web server isn't starting.
Along the lines of what Martin asked, do you have a "Temporary ASP.NET Files" directory in C:\WINDOWS\Microsoft.NET\Framework\v4.0.30319?
mvallevand Wrote:We know for sure the webserver wasn't starting (as expected)
Code:
2016-02-07 22:38:28.544 [ERROR][4] Unexpected error starting web server:
System.AppDomainUnloadedException: The application domain in which the thread was running has been unloaded.
at System.Web.Hosting.HostingEnvironment.Initialize(ApplicationManager appManager, IApplicationHost appHost, IConfigMapPathFactory configMapPathFactory, HostingEnvironmentParameters hostingParameters, PolicyLevel policyLevel)
at System.Web.Hosting.ApplicationManager.CreateAppDomainWithHostingEnvironment(String appId, IApplicationHost appHost, HostingEnvironmentParameters hostingParameters)
at System.Web.Hosting.ApplicationManager.CreateAppDomainWithHostingEnvironmentAndReportErrors(String appId, IApplicationHost appHost, HostingEnvironmentParameters hostingParameters)
at System.Web.Hosting.ApplicationManager.CreateInstanceInNewWorkerAppDomain(Type type, String appId, VirtualPath virtualPath, String physicalPath)
at System.Web.Hosting.ApplicationHost.CreateApplicationHost(Type hostType, String virtualDir, String physicalDir)
at Cassini.Server.CreateHost()
at Cassini.Server..ctor(Int32 port, String virtualPath, String physicalPath)
at NRecord.RecordingService.OnStart(String[] args)
I would delete
C:\WINDOWS\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files
and then manually recreate it and restart the recording service.
Martin
I tried this last night and it worked. The webserver is running and the front end is now working with Kodi. Thanks for the help everyone. Sorry, for just posting this update but I just got out of a meeting that lasted all morning.
hey everyone it appears that I am now getting the same error once more when I fire up Kodi (v15.2), nextpvr client connection lost kodi. I am unable to connect to the server at 127.0.0.1:8886 and when I type this into my browser of choice I am unable to see the server running. I also deleted the following folder like last time C:\WINDOWS\Microsoft.NET\Framework\v4.0.30319\Temp orary ASP.NET Files, manually recreated it and restarted the recording with no luck. Sorry to bring this problem up again , but I am posting my logs and any help you all can render will once again be greatly appreciated. Thanks
It's not clear exactly why, but for whatever reason, the Microsoft .NET web components on your machine don't seem to be able to load. It's not clear from the log why that is though.
You could maybe check if there is some more details in the Windows Event Viewer.
Otherwise maybe check with antivirus software or firewall software turned off, to see if this see somehow a factor.
I'm not sure what type error it might be. Restart the recording service, wait 30 seconds, then look for any error events logged in the last 30 seconds.