Here is the exception.

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

Exception Details: System.Data.SqlClient.SqlException: Invalid object name 'dbo.ns_Newsletters'.

Source Error:

Stack Trace:

[SqlException (0x80131904): Invalid object name 'dbo.ns_Newsletters'.]
   System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection) +404
   System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning() +412
   System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj) +1363
   System.Data.SqlClient.SqlDataReader.ConsumeMetaData() +59
   System.Data.SqlClient.SqlDataReader.get_MetaData() +118
   System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString) +6387889
   System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async) +6389458
   System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result) +538
   System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method) +28
   System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior, String method) +256
   System.Data.SqlClient.SqlCommand.ExecuteDbDataReader(CommandBehavior behavior) +19
   System.Data.EntityClient.EntityCommandDefinition.ExecuteStoreCommands(EntityCommand entityCommand, CommandBehavior behavior) +553

[EntityCommandExecutionException: An error occurred while executing the command definition. See the inner exception for details.]
   System.Data.EntityClient.EntityCommandDefinition.ExecuteStoreCommands(EntityCommand entityCommand, CommandBehavior behavior) +10645559
   System.Data.Objects.Internal.ObjectQueryExecutionPlan.Execute(ObjectContext context, ObjectParameterCollection parameterValues) +11487941
   System.Data.Objects.ObjectQuery`1.GetResults(Nullable`1 forMergeOption) +11119929
   System.Data.Objects.ObjectQuery`1.GetIListSourceListInternal() +30
   System.Web.UI.DataSourceHelper.GetResolvedDataSource(Object dataSource, String dataMember) +115
   System.Web.UI.WebControls.ReadOnlyDataSource.System.Web.UI.IDataSource.GetView(String viewName) +52
   System.Web.UI.WebControls.DataBoundControl.ConnectToDataSourceView() +420
   System.Web.UI.WebControls.DataBoundControl.GetData() +9
   System.Web.UI.WebControls.ListView.PerformSelect() +209
   NewsletterStudio.Usercontrols.Dashboard.Page_Load(Object sender, EventArgs e) +491
   System.Web.Util.CalliHelper.EventArgFunctionCaller(IntPtr fp, Object o, Object t, EventArgs e) +25
   System.Web.UI.Control.LoadRecursive() +71
   System.Web.UI.Control.LoadRecursive() +190
   System.Web.UI.Control.LoadRecursive() +190
   System.Web.UI.Control.LoadRecursive() +190
   System.Web.UI.Control.LoadRecursive() +190
   System.Web.UI.Control.LoadRecursive() +190
   System.Web.UI.Control.LoadRecursive() +190
   System.Web.UI.Control.LoadRecursive() +190
   System.Web.UI.Control.LoadRecursive() +190
   System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +3064

I just tested on version 4.7.1 and it works fine, just doesn't work in 4.7.2.

Hi James!

Thank you for posting! We'll have to look closer at this. I'll keep you posted.

Hi Markus,

Any word on a fix to get this working on 4.7.2? If not I will need to downgrade back to 4.7.1.1.

Thanks,

James

Hi Marcus

I still got the problem with the Newsletter Studio 1.2.4 package om my Umbraco 4.7.1

My errormessage is the same as James:

Hi Jan,

I was able to fix this issue by making the SQL database user the dbo.owner. I guess it didn't have the right permissions to add or access the tables. This worked in both 4.7.1 and 4.7.2.

Sorry for my late anwser, just got back for a week of in Greece. =D

@Jan did James solution fix the problem for you?

Of not, have a look in the log-table and see if there is any errors during the installatioin of Newsletter Studio. When installing package some of them (including Newsletter Studio) requires access to create new tables. Thank you James for sharing your solution!

// Markus

Thank you, @James.

Yes, the Umcraco credentials was the problem, my ISP has changed this for the Umbraco login, for a reason I do not know.

After a change of the Umbraco login to dbo.Owner, the module installes correctly, and I will try it out.

@Markus, I have 2 questions for the Newsletter Studio (don't know it I should make theese in a new thread ?)

1) Is it possible to add custom attributes to the subscribers, Like "Customer type" and "Category", and filter by theese attributes when sending a newsletter?

2) When sending a newsletter to a lot of subscribers on my old system, I sometimes get an unexpected timeout from the SMTP server so the system stops, and then later I can reconnect and resend to the remaining subscribers, does the Newsletter Studio handle this  ? 

Best regards

Jan Borup Coyle

Hi!

Good to hear that you fixed the problems!

1. Yes. Not in the current version but in the end of july we will ship a new version with something called SubscriptionProviders where you can and your own sources/filers to the lists of subscripts. Ie. you could hook it up to an ecommerce-system or what ever. If you would like to play around with that i can hook you up with an very early beta of the feature? Send me an email on markus [at sign goeshere] enkelmedia.se

2. Newsletter Studio will start each send out with createding "EmailTrackingItems" for each reciver. During the send out the engine grabs one item, sends it and then change its state to "Sent". If something happens with the server during the send out it will just restart the next time the server is back again, if one uniq email throw an error, that will be tracked and listed under "erros" in the analytics dashboard - you can then go though the list and correct any errors with email adresses, typos etc.

// Markus

is working on a reply...