I have been having problems in my bvcommerce content manager. <br style="font-family: Times New Roman;">Whenever I make a change in the content manager and click "save changes", I receive a: Server Error in '/' Application.<br style="font-family: Times New Roman;">I have 2 sites using bvcommerce and the other site is working fine (no issues). The sites have he same setup. <br style="font-family: Times New Roman;"><span style="font-family: Times New Roman;">
Can I copy certain files (aspx files and etc.) from the working site to the damaged site to attempt to fix this? <br style="font-family: Times New Roman;"><span style="font-family: Times New Roman;">
Thank you <br style="font-family: Times New Roman;"><br style="font-family: Times New Roman;">(read error below) What file is the 2nd sentence referring to??

Server Error in '/' Application.
A potentially dangerous Request.Form value was detected from the client (ctl00$MainContent$LongDescriptionField$ctl00$EditorField="...nosine..
&lt;p&gt;&lt;a href="/Supplem...").
Description: Request Validation has detected a potentially dangerous client input value, and processing of the request has been aborted. This value may indicate an attempt to compromise the security of your application, such as a cross-site scripting attack. To allow pages to override application request validation settings, set the requestValidationMode attribute in the httpRuntime configuration section to requestValidationMode="2.0". Example: &lt;httpRuntime requestValidationMode="2.0" /&gt;. After setting this value, you can then disable request validation by setting validateRequest="false" in the Page directive or in the &lt;pages&gt; configuration section. However, it is strongly recommended that your application explicitly check all inputs in this case. For more information, see http://go.microsoft.com/fwlink/?LinkId=153133.

Exception Details: System.Web.HttpRequestValidationException: A potentially dangerous Request.Form value was detected from the client (ctl00$MainContent$LongDescriptionField$ctl00$EditorField="...nosine..
&lt;p&gt;&lt;a href="/Supplem...").

Source Error:

The source code that generated this unhandled exception can only be shown when compiled in debug mode. To enable this, please follow one of the below steps, then request the URL:

1. Add a "Debug=true" directive at the top of the file that generated the error. Example:

&lt;%@ Page Language="C#" Debug="true" %&gt;

or:

2) Add the following section to the configuration file of your application:

&lt;configuration&gt;
&lt;system.web&gt;
&lt;compilation debug="true"/&gt;
&lt;/system.web&gt;
&lt;/configuration&gt;

Note that this second technique will cause all files within a given application to be compiled in debug mode. The first technique will cause only that particular file to be compiled in debug mode.

Important: Running applications in debug mode does incur a memory/performance overhead. You should make sure that an application has debugging disabled before deploying into production scenario.

Stack Trace:

[HttpRequestValidationException (0x80004005): A potentially dangerous Request.Form value was detected from the client (ctl00$MainContent$LongDescriptionField$ctl00$EditorField="...nosine..
&lt;p&gt;&lt;a href="/Supplem...").]
System.Web.HttpRequest.ValidateString(String value, String collectionKey, RequestValidationSource requestCollection) +8855748
System.Web.HttpRequest.ValidateNameValueCollection(NameValueCollection nvc, RequestValidationSource requestCollection) +122
System.Web.HttpRequest.get_Form() +150
System.Web.HttpRequest.get_HasForm() +9028559
System.Web.UI.Page.GetCollectionBasedOnMethod(Boolean dontReturnNull) +97
System.Web.UI.Page.DeterminePostBackMode() +69
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +8431
System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +253
System.Web.UI.Page.ProcessRequest() +78
System.Web.UI.Page.ProcessRequestWithNoAssert(HttpContext context) +21
System.Web.UI.Page.ProcessRequest(HttpContext context) +49
ASP.bvadmin_catalog_products_edit_aspx.ProcessRequest(HttpContext context) +4
System.Web.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +100
System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean&amp; completedSynchronously) +75


Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.0.30319.237

I have had html in my "long description" field for years and have not had this problem.
Are you referring to the "long description" field as a form field?

I questioned the hosting company about this and they said nothing had been changed. I did have some problems back in August when I had some mods done to the site. The hosting company had to move the site to a different server. It was due to a asp.net 3.5 framework error.

The error message is directly related to HTML data or Javascript data being posted in a form. Is it possible that your hosting company changed security policies, upgraded the software or made some other change? Maybe even a Microsoft hot fix applied to the server could cause this?