Hi,

I installed DataSprings_OptInEmail_04_30_80_DNN49PLUS_StandardEdition_32BITONLY on a dnn 6.0.2 on my localhost.
I had no installation errors.

I added an Opt In Mail to a page and navigated to ControlPanel and I get this error.  

Error: is currently unavailable. DotNetNuke.Services.Exceptions.ModuleLoadException: Invalid object name 'datasprings_OptInEmail'. ---> System.Data.SqlClient.SqlException: Invalid object name 'datasprings_OptInEmail'. at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection) at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection) at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning() at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj) at System.Data.SqlClient.SqlDataReader.ConsumeMetaData() at System.Data.SqlClient.SqlDataReader.get_MetaData() 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) at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result) at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method) at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior, String method) at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior) 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, String spName, Object[] parameterValues) at Dataspring.DNN.Modules.OptInEmail.SqlDataProvider.GetOptInEmailListOrderBy(String SortOrder) at Dataspring.DNN.Modules.OptInEmail.OptInEmailController.GetOptInEmailListOrderBy(String SortOrder) at Dataspring.DNN.Modules.OptInEmail.__OptInDashBoard.GenerateDashBoard() at Dataspring.DNN.Modules.OptInEmail.__OptInDashBoard.Page_Load(Object sender, EventArgs e) --- End of inner exception stack trace ---


I got 2 more exceptions in the event viewer related to the same page/module, that look like this:
InnerException: Cannot insert the value NULL into column 'SettingValue', table 'dnn_ com.dnn _usr.ModuleSettings'; column does not allow nulls. INSERT fails. The statement has been terminated.


Any ideas of what went wrong?
Thank you,
Manuela

I installed the Opt In Email module on my production server(64-bit) and it works fine.
The instance with the issue was a duplicate(from a backup) of the production site(64-bit) on my localhost(32-bit os).
It also works on the instances that I installed directly on my localhost server.

Thanks

I just learned that the only difference between 64 and 32 bit is the chilkatDotNet2.dll, so the 64 vs 32-bit is not the culprit for the error that I posted earlier.

I am still looking to fix that error, as it would be easier for me to test the module on my local machine.
Thanks

Hi Manuela,

Yes I don't think the issue would have anything to do with the 32 bit / 64 bit difference... It sounds like possibly a database issue or conflict and not one that I have seen before.

Can you tell me a few things:
What version of SQL Server are you running on? Does the database owner have full rights and is the database user setup as full OWNER?

Did you receive any errors during a full uninstall/reinstall? It sounds like one of the database scripts did not get executed properly.


Thanks,

Chad

The production db is on sql2005. I did the restore db on my sql express 2008, I found an orphaned user that could cause the issue.

No, I didn't get any errors during the install.

Thanks for pointing me into the right direction,
Manuela