Hi David

Please consider the following advice when upgrading (on the mail Evolution server)

1. Download Sage Evolution Evolution.11.1.0.1 (the current latest version).

2. Install it in a new separate folder than the currently installed Evolution (ver 10.1.2.006 folder).

3. Backup the live company and the SageCommon DB's.

4. Restore the company backup as DEMO and the SageCommon as SageCommonDEMO

5. Locate the DEMO company and link it in the same time to SageCommonDEMO.

6. Open and the upgrade both DEMO and  SageCommonDEMO.

7. Now you have a test environment where you can test it properly, including integration with Card machines (EFT POS). This is done while your live Evolution environment still carries on as normal. 

Of course, testing it yourself will identify all potential upgrade issues and then we can handle it from there when you log it with us.

Kind Regards

Bennie 

Thank you Bennie i will let you know how it goes

Always a pleasure, David!

I have done as requested successfully,  but when trying to do the database upgrade am told i don't have "the necessary scripts to perform the upgrade" and i must contact sage to do it? Please advise

I have got past the problem posted above , however during the database upgrade i received this message -i cant seem to go any further

Any Ideas?

Incorrect syntax near the keyword 'IF'

DROP TRIGGER IF EXISTS [dbo].[_btrFAAssetCapexOrderDel]

Hi David 

Please confirm the following:

1. Windows Operating System version of the Evolution server? Is this still  Windows Server 2008 R2?
2. MS SQL Server version? And is it Express, Standard or Developer edition? 
3. Can you please also paste a screenshot of the actual error message in this chat?
4. Finally, it seems that someone has customized the _btrFAAssetCapexOrderDel database trigger? Or is this a newly created custom trigger on it own?

Morning Bennie

Answers

1. We are running W server 2008 R2 and SQL 2014 express.

2. 

3. We have NOT customized the database file mentioned at all 

Thanks, David

I may be wrong but I honestly think either, or perhaps both Windows Server 2008 and SQL 2014 could be the reason for the upgrade error.

Let's start with the easy option: SQL version:

Therefore, do the following:

1. Install MS SQL Express 2022 

2. Restore the backup on the new SQL 2022 Express instance 

3. Locate the new DB in Evolution version 11 

4. Now try to upgrade it and check what happens

Please update me on the the outcome

Blessings!

ok can i go back to Express 2014 if it fails, otherwise i will do the upgrade on a workstation?

Hi David

Yes, as long as you have a backup of both the Evolution company and the SageCommon (or EvolutionCommon) databases, you can of course go back to MS SQL 2014.

No, always run the company upgrade on the main Evolution server where SQL is also installed on.

i have now installed windows server2022 on another server and done a clean install of Ver11.01 with SQL2022 

this is the screenshot of the error , i have downloaded and installed the April update of SQL2014 as instructed but still get the same error. Please advise ?

The operating system on this computer does not meet the minimum requirements for Microsoft SQL Server 2022 Express.For Windows 8.1 or Windows Server 2012 R2, the April 2014 update or later is required.For more information, see Hardware and Software Requirements for installing Microsoft SQL Server 2022 Express at:


 https://docs.microsoft.com/en-us/sql/sql-server/install/hardware-and-software-requirements-for-installing-sql-server?view=sql-server-2017

Hi David

There is a lot going on here! 

From what I can deduct from the above error message: The specific, physical  Server PC box is perhaps not powerful enough to run SQL Server 2022 Express.

Please discuss the technical specifications required to run MS SQL 2022 with your local IT technician.

Or am I thinking the wrong way here? 

We have installed SQL2022 on a new workstation/server and have successfully installed Sage Evo ver 11.01 and upgraded our common and database files. All works well on the new workstation. However we cannot access the database on the network workstations and cannot see the new SQL server and /or databases.

Hi David

The dreaded DBNETLIB error I'm noting from the above.

But, don't despair, we have you covered

Open this link for a detailed and comprehensive article on how to resolve it.

Hello David Dunkley 

You had a tough question, but I'm glad Bennie could assist you. To improve our community, please click "Verify answer" on Bennie's suggested answer if it solved your query. This will show that the answer was helpful.

Sharon