Press Ctrl / CMD + C to copy this to your clipboard.
This post will be reported to the moderators as potential spam to be looked at
Below is the required information, I have been unable to pin-point the exact problem or which application is causing it as I am running 5 applications in the same pool for development purposes.
Urgent help would be great as this seems to crash the application pool daily, even though it is a development pool only this will not be an acceptable performance issue for production.
Umbraco Version: 4.0.3ASP.NET Version: 3.0Windows Version: Microsoft Windows Server 2003IIS Version: 6.0
Event Type: ErrorEvent Source: ASP.NET 2.0.50727.0Description: An unhandled exception occurred and the process was terminated.Exception: System.Runtime.Serialization.SerializationExceptionMessage: Type 'umbraco.DataLayer.SqlHelperException' in Assembly 'umbraco.DataLayer, Version=0.3.0.0, Culture=neutral, PublicKeyToken=null' is not marked as serializable.StackTrace: at System.Runtime.Serialization.Formatters.Binary.WriteObjectInfo.InitSerialize(Object obj, ISurrogateSelector surrogateSelector, StreamingContext context, SerObjectInfoInit serObjectInfoInit, IFormatterConverter converter, ObjectWriter objectWriter) at System.Runtime.Serialization.Formatters.Binary.WriteObjectInfo.Serialize(Object obj, ISurrogateSelector surrogateSelector, StreamingContext context, SerObjectInfoInit serObjectInfoInit, IFormatterConverter converter, ObjectWriter objectWriter) at System.Runtime.Serialization.Formatters.Binary.ObjectWriter.Serialize(Object graph, Header inHeaders, __BinaryWriter serWriter, Boolean fCheck) at System.Runtime.Serialization.Formatters.Binary.BinaryFormatter.Serialize(Stream serializationStream, Object graph, Header headers, Boolean fCheck) at System.Runtime.Remoting.Channels.CrossAppDomainSerializer.SerializeObject(Object obj, MemoryStream stm) at System.AppDomain.Serialize(Object o) at System.AppDomain.MarshalObject(Object o)
I dont know the solution to your problem but a good idea is always to run each website in its own application pool. So if it crashes or need more resources your can control the specific app pool. Hope someone else can help you with your problem.
Most likely the problem is caused by Umbraco not being able to access the specified SQL server. Umbraco will get itself into an infinite loop and crash the app pool.
I believe this is fixed in Umbraco 4.1.
Only other possibility is that your /config/umbracoSettings.config file isn't valid XML, but I think in that case it fails with a different error.
I'm having the same problem. Can anyone confirm that upgrading Umbraco will solve this? To latest version 4.5.2? I've been running my 1st production umbraco site on v
18.104.22.168 for a few months and have noticed that every couple of weeks lately the 'app pool' stops and I'm not even aware of it. Based on comments above I'm guessing that the DB briefly becomes unavailable for some reason, but long enough to crash the site. This is surprising, but obviously my connection string is correct if the site is usually running fine.
Yes, we fixed it in 4.5.0 to not bring down the app pool on the several instance outlined here.
is working on a reply...
Write your reply to:
Image will be uploaded when post is submitted