Invalid object name trying to install 1.7

System.Data.SqlClient.SqlException: Invalid object name 'dbo.Nop_Setting'.

searching the forums the only thing i saw was it has something to do with the connectionstrings.config but i can't believe only one person had this error and their fix was to remove connection string (which doesn't make since).

if someone else has an idea, please . . .

suggest you try a reinstall

if that does not work, come back with the version number you are insatlling and let us know how far along the installation process you get

this is on the original install of version 1.7 (as soon as i try to run install.aspx). i found the table that needs that change weight float to decimal (User Databases \ "your db" \ Tables \ dbo.Nop_ProductVariant \ Columns \ Weight) and am trying to change it in MS sql mgmt studio but it keeps "freezing." if tis doesn't work i'll try version 1.6 since it worked for me on godaddy (just switch to softsys)

now i'm getting this:

Server Error in '/' Application.
--------------------------------------------------------------------------------

Invalid column name 'StartDate'.
Invalid column name 'StartDate'.
Invalid column name 'EndDate'.
Invalid column name 'EndDate'.
Invalid column name 'ShowOnHomePage'.
Invalid column name 'ShowOnHomePage'.
Invalid column name 'StartDate'.
Invalid column name 'EndDate'.
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 column name 'StartDate'.
Invalid column name 'StartDate'.
Invalid column name 'EndDate'.
Invalid column name 'EndDate'.
Invalid column name 'ShowOnHomePage'.
Invalid column name 'ShowOnHomePage'.
Invalid column name 'StartDate'.
Invalid column name 'EndDate'.

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.  

Stack Trace:


[SqlException (0x80131904): Invalid column name 'StartDate'.
Invalid column name 'StartDate'.
Invalid column name 'EndDate'.
Invalid column name 'EndDate'.
Invalid column name 'ShowOnHomePage'.
Invalid column name 'ShowOnHomePage'.
Invalid column name 'StartDate'.
Invalid column name 'EndDate'.]
   System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection) +2030802
   System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection) +5009584
   System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning() +234
   System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj) +2275
   System.Data.SqlClient.SqlDataReader.ConsumeMetaData() +33
   System.Data.SqlClient.SqlDataReader.get_MetaData() +86
   System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString) +311
   System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async) +987
   System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result) +162
   System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method) +32
   System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior, String method) +141
   System.Data.SqlClient.SqlCommand.ExecuteDbDataReader(CommandBehavior behavior) +12
   System.Data.Common.DbCommand.ExecuteReader(CommandBehavior behavior) +10
   System.Data.EntityClient.EntityCommandDefinition.ExecuteStoreCommands(EntityCommand entityCommand, CommandBehavior behavior) +443

[EntityCommandExecutionException: An error occurred while executing the command definition. See the inner exception for details.]
   System.Data.EntityClient.EntityCommandDefinition.ExecuteStoreCommands(EntityCommand entityCommand, CommandBehavior behavior) +479
   System.Data.Objects.Internal.ObjectQueryExecutionPlan.Execute(ObjectContext context, ObjectParameterCollection parameterValues) +736
   System.Data.Objects.ObjectQuery`1.GetResults(Nullable`1 forMergeOption) +149
   System.Data.Objects.ObjectQuery`1.System.Collections.Generic.IEnumerable<T>.GetEnumerator() +44
   System.Collections.Generic.List`1..ctor(IEnumerable`1 collection) +315
   System.Linq.Enumerable.ToList(IEnumerable`1 source) +58
   NopSolutions.NopCommerce.BusinessLogic.Content.Polls.PollManager.GetPolls(Int32 languageId, Int32 pollCount, Boolean loadShownOnHomePageOnly) +3472
   NopSolutions.NopCommerce.Web.Modules.TodaysPollControl.BindData() +85
   NopSolutions.NopCommerce.Web.Modules.TodaysPollControl.Page_Load(Object sender, EventArgs e) +83
   System.Web.Util.CalliHelper.EventArgFunctionCaller(IntPtr fp, Object o, Object t, EventArgs e) +14
   System.Web.Util.CalliEventHandlerDelegateProxy.Callback(Object sender, EventArgs e) +35
   System.Web.UI.Control.OnLoad(EventArgs e) +91
   System.Web.UI.Control.LoadRecursive() +74
   System.Web.UI.Control.LoadRecursive() +146
   System.Web.UI.Control.LoadRecursive() +146
   System.Web.UI.Control.LoadRecursive() +146
   System.Web.UI.Control.LoadRecursive() +146
   System.Web.UI.Control.LoadRecursive() +146
   System.Web.UI.Control.LoadRecursive() +146
   System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +2207


things are getting worse

stencel wrote:
It looks like your database is still at version 1.60 (you said in this post softsys restored 1.60 from godaddy) as these fields were added to Nop_Poll and the product variant weight field was converted to a decimal in version 1.70.

Backup your database if you need to and execute the 1.60 to 1.70 upgrade script (NopCommerceStore\Install\Scripts\1.70\nopCommerce_upgrade.sql) in SQL management studio.

.

this is my second day doing anything with databases so please hold my hand:

It looks like your database is still at version 1.60 (you said in this post softsys restored 1.60 from godaddy) as these fields were added to Nop_Poll and the product variant weight field was converted to a decimal in version 1.70.

i managed to convert this to decimal (18,0) already (will this mess up the scripts?)

Backup your database if you need to and execute the 1.60 to 1.70 upgrade script (NopCommerceStore\Install\Scripts\1.70\nopCommerce_upgrade.sql) in SQL management studio.

they're backed up, but how / what do i do in sql mgmt studio (this is all greek me).

thanks in advance!

upgrade script worked like a charm! thanks to all that helped!