We are receiving an intermittent save error on some forms, we are finding this really difficult to re-produce in our dev environment, all we have to go on at the moment is the exception which is:
2014-01-03 10:10:07,470 [7] ERROR umbraco.DataLayer.SqlHelper`1[[System.Data.SqlClient.SqlParameter, System.Data, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]] - [Thread 27] Error executing query DELETE from UFfields where id = @id System.Data.SqlClient.SqlException (0x80131904): The DELETE statement conflicted with the REFERENCE constraint "FK_UFFieldConditionRules_UFFields". The conflict occurred in database "sean-msdn-db", table "dbo.UFFieldConditionRules", column 'Field'. The statement has been terminated. at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction) at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction) at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose) at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady) at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString) at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async, Int32 timeout, Task& task, Boolean asyncWrite) at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, TaskCompletionSource`1 completion, Int32 timeout, Task& task, Boolean asyncWrite) at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(TaskCompletionSource`1 completion, String methodName, Boolean sendToPipe, Int32 timeout, Boolean asyncWrite) at System.Data.SqlClient.SqlCommand.ExecuteNonQuery() at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteNonQuery(SqlConnection connection, CommandType commandType, String commandText, SqlParameter[] commandParameters) at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteNonQuery(String connectionString, CommandType commandType, String commandText, SqlParameter[] commandParameters) at umbraco.DataLayer.SqlHelpers.SqlServer.SqlServerHelper.ExecuteNonQuery(String commandText, SqlParameter[] parameters) at umbraco.DataLayer.SqlHelper`1.ExecuteNonQuery(String commandText, IParameter[] parameters) ClientConnectionId:60fa7310-9368-4d81-b45c-385624d7f480
Hmmm not seen that one but seems like it has something todo with conditions, any chance you can provide steps to reproduce... maybe it's deleting a field that is used by a field with conditions on that primary field?
Thanks for getting back to me, we have managed to re-produce using an existing form, is there anyway I can send you the form so you could import it your end and try to re-produce the error? The error occurs when we try to delete one of the fields, I have asked for confirmation about the condtional settings first though as that may be the issue.
A potentially dangerous Request.Form value was detected from the client (ctl00$ctl01$DefaultSiteContentPlaceHolder1$Col2$LoginControl1$btnLogin="حسن...").
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: <httpRuntime requestValidationMode="2.0" />. After setting this value, you can then disable request validation by setting validateRequest="false" in the Page directive or in the <pages> 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$ctl01$DefaultSiteContentPlaceHolder1$Col2$LoginControl1$btnLogin="حسن...").
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:
<%@ Page Language="C#" Debug="true" %>
or:
2) Add the following section to the configuration file of your application:
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.
Errors when saving forms
Hi
We are receiving an intermittent save error on some forms, we are finding this really difficult to re-produce in our dev environment, all we have to go on at the moment is the exception which is:
Has anyone experienced this before?
Thanks
Kev
Comment author was deleted
Hmmm not seen that one but seems like it has something todo with conditions, any chance you can provide steps to reproduce... maybe it's deleting a field that is used by a field with conditions on that primary field?
Hi Tim
Thanks for getting back to me, we have managed to re-produce using an existing form, is there anyway I can send you the form so you could import it your end and try to re-produce the error? The error occurs when we try to delete one of the fields, I have asked for confirmation about the condtional settings first though as that may be the issue.
Thanks
Kev
Hi Tim
Just confirmed it is a field condition, sorry for wasting your time, I tracked it down in SQL and removed the offending conditional rule.
Thanks
Kev
Hi Tim
Just confirmed it is a field condition, sorry for wasting your time, I tracked it down in SQL and removed the offending conditional rule.
Thanks
Kev
Server Error in '/' Application.
A potentially dangerous Request.Form value was detected from the client (ctl00$ctl01$DefaultSiteContentPlaceHolder1$Col2$LoginControl1$btnLogin="حسن...").
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: <httpRuntime requestValidationMode="2.0" />. After setting this value, you can then disable request validation by setting validateRequest="false" in the Page directive or in the <pages> 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$ctl01$DefaultSiteContentPlaceHolder1$Col2$LoginControl1$btnLogin="حسن...").
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:
<%@ Page Language="C#" Debug="true" %>
or:
2) Add the following section to the configuration file of your application:
<configuration>
<system.web>
<compilation debug="true"/>
</system.web>
</configuration>
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:
Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.0.30319.1016
is working on a reply...