My Application works fine until I move to my production environment.  Then, whenever I launch a dialog I get

Server Error in
'/cutesoft_client' Application.

Setting Not Fould!

Description:    An unhandled exception occurred during the execution of
the current web request.  Please Review the stack trace for more information
information about the error and where it originated in the code.

Exception Details:      System.Exception: Setting Not Fould!

Source Error:

An unhandled exception was generated during the execution of the current web request.
Information regarding the origin and location of the exception can be identified
using the exception stack trace below.     

Stack Trace:    

[Exception: Setting Not Fould!]
   CuteEditor.EditorSetting.a(String A_0) +363
   CuteEditor.EditorSetting..ctor(Editor editor, String hash) +173
   CuteEditor.EditorSetting.GetFromHash(HttpContext context, Editor editor, String hash) +112
   CuteEditor.EditorSetting.GetFromContext(HttpContext context, Boolean bthrow) +64
   CuteEditor.Impl.ResourceContext.LoadResources(HttpContext context, Editor editor, CultureInfo culture) +64   
   CuteEditor.EditorUtilityPage.OnInit(EventArgs e) +92
   System.Web.UI.Control.InitRecursive(Control namingContainer) +241
   System.Web.UI.Page.ProcessRequestMain() + 197
 

My production environment is a multiple server web farm environment. I am using 5.2.0.0.   I have changed the CuteEditor\Configuration\Editor.config to
<setting name="MultipleServerMode" value="True" />

Any ideas?

Ok, I spent the day trying to figure this out.  It looks like Setting Not Fould! exception is only in version 4.5 (which is the one I had been using).  So I have meticulously gone through my severs and cleaned out any cached stuff in Temporary ASP.NET files...  I am still getting these errors.  Any idea where this stuff might be cached?  

---

asp.net Chat http://cutesoft.net/ASP.NET+Chat/default.aspx
Web Messenger: http://cutesoft.net/Web-Messenger/default.aspx
asp.net wysiwyg editor: http://cutesoft.net/ASP.NET+WYSIWYG+Editor/default.aspx
asp wysiwyg html editor: http://cutesoft.net/ASP
asp.net Image Gallery: http://cutesoft.net/ASP.NET+Image+Gallery/default.aspx
Live Support: http://cutesoft.net/live-support/default.aspx

I am on version 5.2.  I have figured out the nature of the problem.  I am in a Web Farm with 8 Web Servers.  There is a difference in the settingshash parameter in the query string.

On 5 of these servers
clean.Aspx?settinghash=5807c27d

On 2 of these servers
clean.aspx?settinghash=e06e035d

On 1 of these servers
clean.aspx?settinghash=6618abbd

How can I make the settinghash the same on every server?

---

asp.net Chat http://cutesoft.net/ASP.NET+Chat/default.aspx
Web Messenger: http://cutesoft.net/Web-Messenger/default.aspx
asp.net wysiwyg editor: http://cutesoft.net/ASP.NET+WYSIWYG+Editor/default.aspx
asp wysiwyg html editor: http://cutesoft.net/ASP
asp.net Image Gallery: http://cutesoft.net/ASP.NET+Image+Gallery/default.aspx
Live Support: http://cutesoft.net/live-support/default.aspx

They all look the same:

<?xml version="1.0" encoding="utf-8" ?>
<configuration>
    <!-- set to True for NLB/Cluster -->
    <setting name="MultipleServerMode" value="True" />
</configuration>

I noticed the settingshash querystring values have corresponding txt files in the C:\WINNT\Temp directory.  I copied all three of the txt files to all 8 of the servers.  This seems to have cured the problem. 

I guess what worries me now is what will happen when I add additional servers to the mix.  Is there any way I could get a breakdown on how these files get their names so I can set things up with consistency?

---

asp.net Chat http://cutesoft.net/ASP.NET+Chat/default.aspx
Web Messenger: http://cutesoft.net/Web-Messenger/default.aspx
asp.net wysiwyg editor: http://cutesoft.net/ASP.NET+WYSIWYG+Editor/default.aspx
asp wysiwyg html editor: http://cutesoft.net/ASP
asp.net Image Gallery: http://cutesoft.net/ASP.NET+Image+Gallery/default.aspx
Live Support: http://cutesoft.net/live-support/default.aspx

JohnGrady:

I am having the same problem with v5.2 in our production web farm environment, with Insert Template.  The problem started when "sticky sessions" were removed. 

 

I set MultipleServerMode = True in Editor.config and added the CuteEditorTempPath to Web.config on all machines.  Are there any other changes that need to be made?  Or will upgrading to 6.x resolve the problem?

 

It appears that the problem occurs due to the .txt file getting created in the CuteEditorTempPath on one machine, but the subsequent call actually hits a different machine (for example, the error message indicates that the error occurred on server 2, but the .txt file was created on server 1).

 

I tried pointing the CuteEditorTempPath to a network share but it caused the page to hang when loading, and also, the directory structures are not identical on all machines, so the pathes stored in those .txt files may not match.

 

Any suggestions would be greatly appreciated.

 

Thanks,

 

John