Groups: Administration
Joined: 11/3/2005(UTC)
Posts: 2,253
Thanks: 28 times
Was thanked: 60 time(s) in 59 post(s)
|
Hi! We've looked at the log and here what we have found:
- Our design expects that application hosting process, UWS.AppHost.XXX.exe, can sometimes be crashed by an application. Although exceptions occurring within the context of serving an HTTP request normally lead to an "ASP.NET yellow page of death", in some cases exceptions may crash UWS host process as any .NET application can be crashed by an unhandled exception. For example, if an exception occurs outside of the request handling context (say you have started a thread on application_start() and that threw an exception), the host process will crash. UWS as a whole is designed to expect this, and to survive by UWS Monitoring Service sending heartbeats to host processes, and restarting the host processes if they have died.
It is unclear from the log whether the exception that crashed UWS.AppHost process was outside of the request handling context or not:Quote:Exception: System.Runtime.Serialization.SerializationException
Message: Unable to find assembly 'SolarWinds.KiwiSyslog.WebAccess.Core, Version=1.3.0.0, Culture=neutral, PublicKeyToken=null'.
StackTrace: at System.Runtime.Serialization.Formatters.Binary.BinaryAssemblyInfo.GetAssembly()
at System.Runtime.Serialization.Formatters.Binary.ObjectReader.GetType(BinaryAssemblyInfo assemblyInfo, String name)
at System.Runtime.Serialization.Formatters.Binary.ObjectMap..ctor(String objectName, String[] memberNames, BinaryTypeEnum[] binaryTypeEnumA, Object[] typeInformationA, Int32[] memberAssemIds, ObjectReader objectReader, Int32 objectId, BinaryAssemblyInfo assemblyInfo, SizedArray assemIdToAssemblyTable)
at System.Runtime.Serialization.Formatters.Binary.__BinaryParser.ReadObjectWithMapTyped(BinaryObjectWithMapTyped record)
at System.Runtime.Serialization.Formatters.Binary.__BinaryParser.Run()
at System.Runtime.Serialization.Formatters.Binary.ObjectReader.Deserialize(HeaderHandler handler, __BinaryParser serParser, Boolean fCheck, Boolean isCrossAppDomain, IMethodCallMessage methodCallMessage)
at System.Runtime.Serialization.Formatters.Binary.BinaryFormatter.Deserialize(Stream serializationStream, HeaderHandler handler, Boolean fCheck, Boolean isCrossAppDomain, IMethodCallMessage methodCallMessage)
at System.Runtime.Remoting.Channels.CrossAppDomainSerializer.DeserializeObject(MemoryStream stm)
at System.AppDomain.Deserialize(Byte[] blob)
at System.AppDomain.UnmarshalObject(Byte[] blob)
If you could shed a light on what is this deserialization call is called by, we could probably see whether this is by design or there is a problem to be fixed.
- What's more disturbing, is the other exception - the crash of UWS Monitoring Service (your screenshot is attached). Although it gets automatically restarted, that's a fail-safe, and is not supposed to happen. This is more or less guaranteed to be our bug to be fixed. Unfortunately, the log file is huge, and for whatever reason filtering and searching it is not working, so we could not find the relevant error entry in the EVTX file.
Would it be possible for you to clear the event log on that box, then reproduce the problem, and then send us the log only with relevant items? Or if clearing the log is not an option, reproduce the problem and post the exception log text for UWS Monitoring Service crash?
Best regards, UltiDev Team. Ultidev Team attached the following image(s): Please donate at http://www.ultidev.com/products/Donate.aspx to help us improve our products.
|
