WARNING - Recent Godaddy Upgrade 1.60 to 1.90 Problems

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
12 years ago
Hello,

Recently Godaddy sent a notice saying that current nopCommerce v1.60 users must install a required patch.  The email did not state that it is an upgrade to v1.90.  If the shared server the website is currently hosted does not support or is not configured for ASP 4.0 errors will occur after the upgrade is completed.

There are risks when trying to roll back to v1.60 and worse when migrating to a new shared server that does support ASP 4.0.  Changes may take 24 hours or more before each request is processed.  As a result the website may be offline for a day or more.

Before applying the patch, call Godaddy and investigate what the patch is and if the shared server currently hosting your website meets the requirements.

Regards,
Felix
12 years ago
Hello,

I'm now getting an error that appears to be related to the database.  A previous post discusses that this may be caused by the database being v1.6 but nopcommerce is now v1.9.  Godaddy has washed their hands of the issue claiming that it is now an application problem.  I thought that when they ran the patches the proper scripts were applied to upgrade everything.

How can I upgrade the database from v 1.6 to v 1.9?
Should the upgrades be gradual? 1.6 to 1.7 to 1.8 to 1.9?
How can I backup the database manually because cannot access the administration GUI?
How can I confirm that the database is ok and not corrupted?

I've been dead in the water for about 36 hours now... Thank you in advance for your help!

Felix



Stack Trace:


[SqlException (0x80131904): Invalid column name 'ShowOnHomePage'.
Invalid column name 'StartDate'.
Invalid column name 'EndDate'.]
   System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection) +2062078
   System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection) +5050204
   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.Linq.Enumerable.FirstOrDefault(IEnumerable`1 source) +182
   System.Data.Objects.ELinq.ObjectQueryProvider.<GetElementFunction>b__1(IEnumerable`1 sequence) +41
   System.Data.Objects.ELinq.ObjectQueryProvider.ExecuteSingle(IEnumerable`1 query, Expression queryRoot) +59
   System.Data.Objects.ELinq.ObjectQueryProvider.System.Linq.IQueryProvider.Execute(Expression expression) +150
   System.Linq.Queryable.FirstOrDefault(IQueryable`1 source) +265
   NopSolutions.NopCommerce.BusinessLogic.Content.Polls.PollService.GetPollBySystemKeyword(String systemKeyword) +548
   NopSolutions.NopCommerce.Web.Modules.PollBlockControl.BindData() +174
   NopSolutions.NopCommerce.Web.Modules.PollBlockControl.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
12 years ago
Whoa! I am talking to G0odaddy right now. I got the notice to upgrade m,y account. The only notice I got it was 1.9 was when they said the update was finished. We all know 1.9 can't run on godaddy because of permissions and Net 4.0. Trying to find out if I can revert to the saved copy. My site is down and this doesn't look good.
12 years ago
Here is what godaddy said:
Before doing the update you need to do a few things. If you don't, your site will crash - Like mine did. Don't do this after your site crashes. If it crashes after the update, you need to revert to the previous stored copy that godaddy saved,. Then do this. After you do the following you can do the 1.9 update.
Go to your account
Click on 'web hosting' under 'my products'
Click the 'edit account details tab'
change 'plan' to 'shared windows 4gh'.

After 24 hours or so you should be able to update to 1.9.

Good luck!
My site is still down. They say it should take 24 hours to restore it. I am nervous about it since the last time I went to it there was a different error. I will update.
12 years ago
Did Godaddy tell you to change the programming language to ASP.NET 4.0 after changing the hosting to 4GH?
12 years ago
No, they seemed to think it was automatic - But, seriously, I am not sure I ever believe a help desk 100%. Has anyone else done the godaddy 1.9 update successfully.
12 years ago
In the end I had to give up on trying to upgrade the database and restore the website.  Not only am I losing revenue with the website being offline, I also had to pay Godaddy out of pocket to have a restoration from tape to bring the website online.  The whole process takes an additional 7 to 10 days!

As of today it is not safe to upgrade nopCommerce using the Godaddy upgrade wizard.  Last upgrade to v1.6 was fine but this update to v1.9 is buggy.
12 years ago
I don't think that goDaddy should automatically upgrade application. What if you did some customization?

So if you would like to upgrade from 1.60 to 1.90, do it manually. Here's a simplified step list:
1. Create your database backup
2. Copy 'ConnectionString.config' file from your site root to your computer
3. Execute appropriate upgrade SQL scripts over your database (1.60 => 1.70, 1.70 => 1.80, 1.80 => 1.90). They can be found in \Install\Scripts\ directory
4. Delete all files from your site root
5. Upload 1.90 files to your site root
6. Copy back 'ConnectionString.config' from your local computer (from step 2)

I would also recommend to play with an upgrade on your local machine first
12 years ago
As A.M. and everyone else said, DO NOT DO THE "REQUIRED" NOPCOMMERCE UPDATE PER GODADDY.

Ok, just trying to get my site working again. Don't care if it is 1.6 or 1.9. Been on the phone with godaddy for 3 hours now. They obviously don't know what to do. They offered to go into their archives and upload an older version of the site for $150. I just said, go ahead, but that since they caused the problem there is no way I will be paying.

I also mentioned they need to re-contact all the nopcommerce users who got the required upgrade email and explain they need to to 4gh and net 4.0 before doing the upgrade. Also, they mentioned in the instructions that there was no need for me to backup before the upgrade, that they would do it for me and I could revert at any time.

They are working hard, but the restrictions of a big company are hurting the solution to the problem. They say they will get back to me within 72 hours. That will be 5 days my site is down.

I don't know if this helps, but here is the page that is showing all the errors. If this tells you how I should fix it let me know. Just be aware that I know about computers, but this stuff is new to me so I may not understand what you say unless you make it very simple.

http://winddancevineyard.com/cheesesupplies/default.aspx]http://winddancevineyard.com/cheesesupplies/default.aspx
12 years ago
Here is how to get your site working again if your site crashed when restoring 1.6 from the non-working godaddy upgrade to 1.9 (or patch as they call it - The email requiring the update does not say it is 1.9).

There are 3 v1.9 files you need to remove from your root directory and replace with the 1.6 version files (The restore function did not copy over these files). The rep I spoke with did not know the names of the files, but said they have made a note of it in their cust service instructions. So, just call into godaddy and they will fix it for you.

If you already paid the $150 to get an archive copy installed, fight it. Godaddy is getting calls from almost every Nopcommerce user after their botched update.

Now, if you decide to get the 1.9 upgrade after fixing your site (after changing to the 4gh server and net 4.0, of course), can you post what you did and how well it did or didn't work? There is no way I will be doing it until someone else does.  Thanks!
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.