This week I have downloaded the 7.3.1 updater and ran the updatestore.asp script.

After this I have postponed uploading the new pages as we want to check for some customchanges and some styling issues.

Now we experience a problem with clients trying to login to their account or creating a new account. Also in the admin section we cannot open orders from clients with an account. Opening orders from clients without an account (guests) is no problem.

Also when opening the admin home page this page loads but in the section for the last orders there is an 500 error message.

Are there some changes made by updatestore.asp that affect the clientlogin accounts and do require all the latest files to be uploaded?

Greetings,

Jaap


jaapg@promanent.com
Promanent b.v.
www.promanent.com | www.vaarwinkel.nl

You should never run the updater before uploading changed files. There are changes to the database made by the updater that are dependent on the newer admin and admin/inc files. See https://www.ecommercetemplates.com/support/topic.asp?TOPIC_ID=113814

Marshall
CENLYT Productions - ms designs
Affordable Web Design
Custom Ecommerce Designs
Responsive Websites
Cenlyt.com

Hi Jaap
Yes, as Marshall says you should run the updatestore.asp script at the same time as uploading the files from the new updater. To cure the problems you should just copy the new updater files now.

Vince

Click Here for Shopping Cart Software
Click Here to sign up for our newsletter
Click Here for the latest updater

Hi Marshall and Vince,

Thanks.

We have been following these steps for many years now without any problems.

If we would do it the other way round (first update scripts) then the database, visitors of our site during this process might run in to problems. When we do it 'our way' we never had any problems even if we waited for some days before uploading the new scripts.

Will update the scripts right away.

Greetings,

Jaap


jaapg@promanent.com
Promanent b.v.
www.promanent.com | www.vaarwinkel.nl

Hi Jaap
There are two releases at any time, the "Stability" (currently v7.2.x) release and the "Advanced" release (currently v7.3.x). For updates of the Stability release we try not to make changes to the database that would also require script changes so you can normally get away with doing things the way you do. But in the Advanced release or across major versions, (like v7.2 to v7.3) there may well be changes to the database that require the scripts be updated and not doing so will result in errors such as missing database columns or tables. It's really just best to carry out both actions at the same time.

Vince

Click Here for Shopping Cart Software
Click Here to sign up for our newsletter
Click Here for the latest updater

Hi Vince,

Apparently there seems to be a problem in our SQL database. It might well be that the updater scripts for several updates have not been able to change some major stuff. This might have been caused by our db login seems to have no db_owner role. For this reason changes in the design of the SQL Database might have never been implemented in the correct way. For example we see a lot of fields that still use the NVARCHAR while the updater expects VARCHAR.

At the moment our store is completely down and not working.

I have used the SQL Creator script and updatestore.asp on a new database and this all seems to run and we have sample data.

Using MS SQL Manager to import the data from the live store database to the newly created SQL database however does not work as the import in MS SQL Manager seems to be having problems with NVARCHAR (source db) to VARCHAR (new db).

We have contacted our hosting provider about the db_owner role, but this has not been solved yet.

Is there a trick or tool to use to be able to copy our old data to the new without having this conflicts of NVARCHAR versus VARCHAR?

Greetings,

Jaap



jaapg@promanent.com
Promanent b.v.
www.promanent.com | www.vaarwinkel.nl

Hi Jaap
Having NVARCHAR and VARCHAR shouldn't cause an error, but the NVARCHAR fields will just take up more space. You have an error on the site but do you know what the error message is you are getting?
If there was an error running the updatestore.asp script then you could try getting the v7.2 updater and copy those files. If the database hasn't been updated then the database may well still be on v7.2
If you don't know what the error message is, can you ask your host to turn on detailed error messages so you can see the error?

Vince

Click Here for Shopping Cart Software
Click Here to sign up for our newsletter
Click Here for the latest updater

Hi Vince,

Thanks for the tip. We have found the problem to be corrupt data in our SQL database. Several tables incl. cart, orders, ratings and customerlogin have corrupted records causing a SQL Fatal error 824. So we are forced to take drastic actions.

We have renamed all old tables and with the SQL Server tables creation script created an all new set of tables. After this we executed all updaters we have secured starting at 7.0 and up to 7.2.5. The whole admin of the site is now working again.

We noted 2 minor issues in these updaters.

Updater 7.1.6 checks for 'Orders Loyalty Points upgrade'. Here the script stopped. I checked the orders table and at start there is only one order with OrdID=501.
I changed line 364 to '…. OrdID>0' and after this the script would execute fine.

Updater 7.2.4 has a section that created the adminshipping table. This table was created but no record was being entered. Second time executing this updater all seems fine.

And we also found one major issue in all updaters.

Some sections in the updater scripts check to see of a returned error is not 0. If so do something or skip a section.

When the SQL database has big problems like we experience the error returned is also not 0, but when executing some code based on this you might run in to more errors as a table is corrupted. Or as we also experienced a 2nd table of the same name can be created based on the user of the SQL database. For example we found two adminshipping tables. [dbo].[adminshipping] and [ourusername].[adminshipping]. And the same with the customerlogin table, which is quite essential for all shop scripts to work.

I am not sure if this is the reason why our database got corrupted, but might be worth looking in to.

We will now try to get the storefront of our shop working again. And when this all is working we will copy all stored orders etc into the new tables.

Greetings,

Jaap

jaapg@promanent.com
Promanent b.v.
www.promanent.com | www.vaarwinkel.nl