[ 
https://issues.apache.org/jira/browse/LOG4NET-578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16189977#comment-16189977
 ] 

Blake edited comment on LOG4NET-578 at 10/3/17 5:06 PM:
--------------------------------------------------------

Unfortunately, this exception is resulting in 500 internal server error being 
returned to the browser, and the exception itself isn't being caught by VS 
intellitrace (I managed to grab the exception from the windows event viewer), 
meaning I currently have no way to provide anymore information / debug this 
further. 


was (Author: blakewills):
Unfortunately, this exception is resulting in 500 internal server error being 
returned to the browser, and the exception doesn't seem to be being caught by 
intellitrace inside VS (I managed to grab the exception from the windows event 
viewer), meaning I _currently_ have no way to provide anymore information / 
debug this further. 

> Type is not resolved for member 'log4net.Util.PropertiesDictionary'
> -------------------------------------------------------------------
>
>                 Key: LOG4NET-578
>                 URL: https://issues.apache.org/jira/browse/LOG4NET-578
>             Project: Log4net
>          Issue Type: Bug
>          Components: Builds
>    Affects Versions: 2.0.7, 2.0.8
>         Environment: MS Windows 10. ASP.NET 4
>            Reporter: Blake
>
> After upgrading log4net from v1.2.11 to v2.0.8 we are now getting the 
> following exception on startup (inc stack trace):
> An error occurred while trying to start an integrated application instance.
> Exception: System.Runtime.Serialization.SerializationException
> Message: Type is not resolved for member 
> 'log4net.Util.PropertiesDictionary,log4net, Version=2.0.8.0, Culture=neutral, 
> PublicKeyToken=669e0ddf0bb1aa2a'.
> StackTrace:    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.GetAppDomainWithHostingEnvironment(String
>  appId, IApplicationHost appHost, HostingEnvironmentParameters 
> hostingParameters)
>    at System.Web.Hosting.ApplicationManager.CreateObjectInternal(String 
> appId, Type type, IApplicationHost appHost, Boolean failIfExists, 
> HostingEnvironmentParameters hostingParameters)
>    at System.Web.Hosting.ProcessHost.StartApplication(String appId, String 
> appPath, Object& runtimeInterface)
> I've also tested this on v2.0.7 and the same issue occurs.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to