Profile: joster

It is hard for me to believe that what you described as a remedy will work, as it employs pretty much the same procedure I've followed thus far. This is what I did:

I had a version 2.80 database, which I upgraded to 3.0. (their database upgrade script also initially had errors with SQL Azure like yours)..I worked with them and they provided a new database upgrade script, compatible with SQL Azure, which I then executed without issue.)
I installed a fresh copy of the 3.0 nopcommerce website onto my server, and the 3.0 site was functioning perfectly.
After a couple of days, you guys released the 3.0 theme files and I copied in all the 3.0 fashion theme files to my running 3.0 site.
I ran the 7spikes upgrade script over my database.

Then, when the upgrade script errors occurred, I restored a backup of my database and ran the modified-for-SQL-Azure 7spikes upgrade script again, which is all I have done til now.

Steve

Thanks very much for the quick response!
I backed up my database and ran the newly updated script over it, and had no errors at all.

However....

I now get this error when trying to load the site in a browser:
------------------------------------------------------------------------------------------------------
\Server Error in '/' Application.

Invalid object name 'dbo.Store'.

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.Store'.

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:


[SqlException (0x80131904): Invalid object name 'dbo.Store'.]

------------------------------------------------------------------------------------------------------

Did we miss something?

Steve

I did see that there was an upgrade sql script for the Fashion theme, but rather than try to upgrade my 2.80 nopcommerce with version 2.80 Fashion theme to the 3.0 version of each, I decided to just do a fresh install of each.

The new nopcommerce 3.0 site installed fine, When I copied in the freshly downloaded version 3.0 Fashion theme (plugins and theme) to the new site, I already had the Admin Plugins page open. I then clicked the "Reload list of plugins" and saw all the 7Spikes stuff was now in the list.

I did not go to general settings to enable the new theme, but instead clicked on "Public Store" to make sure all was well.

It was not OK(see error pasted below)....and now I cannot even get back into the Admin area.
----------------------------------------------------------------------------------------------------
Server Error in '/' Application.

The controller for path '/' was not found or does not implement IController.

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.Web.HttpException: The controller for path '/' was not found or does not implement IController.

Source Error:


Line 3:  @foreach (var widget in Model)
Line 4:  {
Line 5:      @Html.Action(widget.ActionName, widget.ControllerName, widget.RouteValues)
Line 6:  }

Source File: c:\inetpub\wwwroot\3point0\Views\Widget\WidgetsByZone.cshtml    Line: 5

-------------------------------------------------------------------------------------------------------------
What could be the problem? Did I still need to run the upgrade sql script for the Fashion theme?

Thanks!

We've just installed the Fashion theme on our new version 2.8 nopcommerce site, and the quicktabs won't work. I've un-installed and re-installed them and enabled/un-enabled/re-enabled them several times.

Any ideas?

Thanks!