I get this error in the DNN Event Viewer when I submit a form.

Using DF 4.0.11.16442, DNN 6.1.5

There are no SQL driven default values.

Each field on the form has a value, so no field is left NULL.

We have another form on the site that works as it should.
We recently took the site live and updated the Domain name from dev to the production. We also applied the license following the change in the domain.

This is the error... Can someone help me figure out what's causing it?

Thanks.

DotNetNuke.Services.Exceptions.ModuleLoadException: Value cannot be null. Parameter name: commandText ---> System.ArgumentNullException: Value cannot be null. Parameter name: commandText at Microsoft.ApplicationBlocks.Data.SqlHelper.PrepareCommand(SqlCommand command, SqlConnection connection, SqlTransaction transaction, CommandType commandType, String commandText, SqlParameter[] commandParameters, Boolean& mustCloseConnection) at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteReader(SqlConnection connection, SqlTransaction transaction, CommandType commandType, String commandText, SqlParameter[] commandParameters, SqlConnectionOwnership connectionOwnership) at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteReader(String connectionString, CommandType commandType, String commandText, SqlParameter[] commandParameters) at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteReader(String connectionString, CommandType commandType, String commandText) at DataSprings.Modules.DynamicForms.SqlDataProvider.GetSQLDefault(String strSQL, String strAltConnection) at DataSprings.Modules.DynamicForms.DynamicQuestionController.GetSQLValidation(String strSQL) at DataSprings.Modules.DynamicForms.DynamicForms.ServerSideValidation() at DataSprings.Modules.DynamicForms.DynamicForms.SubmitForm(Boolean ProcessPaymentNotification, String strResponseID, Boolean blnByPassValidation, Boolean blnSaveForLater) --- End of inner exception stack trace ---

Hi - It looks like this is related to a SQL Default. Are you using any SQL Defaults within your form?

Thanks,

Chad

No, as I mentioned in the post, there are no SQL defaults.

The only solution I could come up w/ was to rebuild the form.
I just finished.