Sage 100

------------------------------
Dana Halpin
Vrakas/Blum Computer Consulting, Inc.
------------------------------

Make sure port 1433 is open on the firewall of the server you are migrating from. Also, make sure that both instances of SQL Server are exactly the same... same product updates, everything.   If SQL server instance 1 is version 15.0.4261.1 then SQL server instance 2 needs to be 15.0.4261.1.

------------------------------
Doug Higgs
Midwest Commerce Solutions, Inc
(312) 315-0960
Chauffeur, Chef, and Personal Assistant to Sprinkles
------------------------------

Original Message:
Sent: 1/28/2023 11:38:00 AM
From: Doug Higgs
Subject: RE: 2019 Premium to 2022 Premium Upgrade Issue

Make sure port 1433 is open on the firewall of the server you are migrating from. Also, make sure that both instances of SQL Server are exactly the same... same product updates, everything.   If SQL server instance 1 is version 15.0.4261.1 then SQL server instance 2 needs to be 15.0.4261.1.

------------------------------
Doug Higgs
Midwest Commerce Solutions, Inc
(312) 315-0960
Chauffeur, Chef, and Personal Assistant to Sprinkles
------------------------------

You need a user account that has administrator rights set up for the SQL service on both instances.

Verify that the required rights and permissions are set up on the server(s) where SQL Server is installed. If the instance of SQL Server for Sage 100 2022 is installed on a different server than the instance used for your prior version, you must complete these steps on both servers.

 the below is from the Sage instructions:

1. Open the Control Panel, select Administrative Tools, and the select Services.

1.  In the Services window, locate the SQL Server instance used for Sage 100 Premium, right click it, and select Properties.
2.  In the Properties window, click the Log On tab and select an option.

 

If the SQL Server instance that you're using for version 2022 is installed on a different server than the one used for your prior version of Sage 100 Premium, select This Account.

 

In the account field, enter: \\ServerName\Administrator

Replace "ServerName" with the name of the server. Sage strongly recommends using the actual Administrator or Domain Administrator account.

Enter the password for the account.

 

1. Apply your changes and then stop and restart the services.
2. If you're working with more than one server, make sure that all servers can access each other through hidden shares.

For example: \\ServerName\C$, \\ServerName\D$

 

------------------------------
Doug Higgs
Midwest Commerce Solutions, Inc
(312) 315-0960
Chauffeur, Chef, and Personal Assistant to Sprinkles
------------------------------

Original Message:
Sent: 01-28-2023 11:44
From: Dana Halpin
Subject: 2019 Premium to 2022 Premium Upgrade Issue

Thank you for your reply.

 

Both instances are 13.0.5698.0. It wasn't like that when I first started but now it is, but still getting the error.

 

I have port 1433 open on the server I'm migrating from too.

 

 

Dana Halpin
Consulting Manager

 

#1 Manufacturing Solution Provider in the Nation 2006 - 2020

 

Vrakas/Blum Computer Consulting, LLC 445 South Moorland Road, Suite 400  Brookfield, WI 53005 office:  262-797-0400 direct:  262-798-7608 fax:       262-797-7895 email:   dhalpin@v-bcc.com web:      v-bcc.com Don't forget to follow us on Social Media!

 

 

Original Message:
Sent: 1/28/2023 11:38:00 AM
From: Doug Higgs
Subject: RE: 2019 Premium to 2022 Premium Upgrade Issue

Make sure port 1433 is open on the firewall of the server you are migrating from. Also, make sure that both instances of SQL Server are exactly the same... same product updates, everything.   If SQL server instance 1 is version 15.0.4261.1 then SQL server instance 2 needs to be 15.0.4261.1.

------------------------------
Doug Higgs
Midwest Commerce Solutions, Inc
(312) 315-0960
Chauffeur, Chef, and Personal Assistant to Sprinkles
------------------------------

------------------------------
Kevin Moyes
Technical Systems Analyst
Munjal White Consulting Co.
------------------------------

Original Message:
Sent: 01-28-2023 12:20
From: Doug Higgs
Subject: 2019 Premium to 2022 Premium Upgrade Issue

You need a user account that has administrator rights set up for the SQL service on both instances.

Verify that the required rights and permissions are set up on the server(s) where SQL Server is installed. If the instance of SQL Server for Sage 100 2022 is installed on a different server than the instance used for your prior version, you must complete these steps on both servers.

 the below is from the Sage instructions:

1. Open the Control Panel, select Administrative Tools, and the select Services.

1.  In the Services window, locate the SQL Server instance used for Sage 100 Premium, right click it, and select Properties.
2.  In the Properties window, click the Log On tab and select an option.

 

If the SQL Server instance that you're using for version 2022 is installed on a different server than the one used for your prior version of Sage 100 Premium, select This Account.

 

In the account field, enter: \\ServerName\Administrator

Replace "ServerName" with the name of the server. Sage strongly recommends using the actual Administrator or Domain Administrator account.

Enter the password for the account.

 

1. Apply your changes and then stop and restart the services.
2. If you're working with more than one server, make sure that all servers can access each other through hidden shares.

For example: \\ServerName\C$, \\ServerName\D$

 

------------------------------
Doug Higgs
Midwest Commerce Solutions, Inc
(312) 315-0960
Chauffeur, Chef, and Personal Assistant to Sprinkles
------------------------------


Original Message:
Sent: 01-28-2023 11:44
From: Dana Halpin
Subject: 2019 Premium to 2022 Premium Upgrade Issue

Thank you for your reply.

 

Both instances are 13.0.5698.0. It wasn't like that when I first started but now it is, but still getting the error.

 

I have port 1433 open on the server I'm migrating from too.

 

 

Dana Halpin
Consulting Manager

 

#1 Manufacturing Solution Provider in the Nation 2006 - 2020

 

Vrakas/Blum Computer Consulting, LLC 445 South Moorland Road, Suite 400  Brookfield, WI 53005 office:  262-797-0400 direct:  262-798-7608 fax:       262-797-7895 email:   dhalpin@v-bcc.com web:      v-bcc.com Don't forget to follow us on Social Media!

 

 

Original Message:
Sent: 1/28/2023 11:38:00 AM
From: Doug Higgs
Subject: RE: 2019 Premium to 2022 Premium Upgrade Issue

Make sure port 1433 is open on the firewall of the server you are migrating from. Also, make sure that both instances of SQL Server are exactly the same... same product updates, everything.   If SQL server instance 1 is version 15.0.4261.1 then SQL server instance 2 needs to be 15.0.4261.1.

------------------------------
Doug Higgs
Midwest Commerce Solutions, Inc
(312) 315-0960
Chauffeur, Chef, and Personal Assistant to Sprinkles

The attached is a Sage KB that addresses the error.

------------------------------
Doug Higgs
Midwest Commerce Solutions, Inc
(312) 315-0960
Chauffeur, Chef, and Personal Assistant to Sprinkles
------------------------------

Original Message:
Sent: 01-28-2023 11:44
From: Dana Halpin
Subject: 2019 Premium to 2022 Premium Upgrade Issue

Thank you for your reply.

 

Both instances are 13.0.5698.0. It wasn't like that when I first started but now it is, but still getting the error.

 

I have port 1433 open on the server I'm migrating from too.

 

 

Dana Halpin
Consulting Manager

 

#1 Manufacturing Solution Provider in the Nation 2006 - 2020

 

Vrakas/Blum Computer Consulting, LLC 445 South Moorland Road, Suite 400  Brookfield, WI 53005 office:  262-797-0400 direct:  262-798-7608 fax:       262-797-7895 email:   dhalpin@v-bcc.com web:      v-bcc.com Don't forget to follow us on Social Media!

 

 

Original Message:
Sent: 1/28/2023 11:38:00 AM
From: Doug Higgs
Subject: RE: 2019 Premium to 2022 Premium Upgrade Issue

Make sure port 1433 is open on the firewall of the server you are migrating from. Also, make sure that both instances of SQL Server are exactly the same... same product updates, everything.   If SQL server instance 1 is version 15.0.4261.1 then SQL server instance 2 needs to be 15.0.4261.1.

------------------------------
Doug Higgs
Midwest Commerce Solutions, Inc
(312) 315-0960
Chauffeur, Chef, and Personal Assistant to Sprinkles
------------------------------

Original Message:
Sent: 1/28/2023 12:32:00 PM
From: Doug Higgs
Subject: RE: 2019 Premium to 2022 Premium Upgrade Issue

The attached is a Sage KB that addresses the error.

------------------------------
Doug Higgs
Midwest Commerce Solutions, Inc
(312) 315-0960
Chauffeur, Chef, and Personal Assistant to Sprinkles
------------------------------


Original Message:
Sent: 01-28-2023 11:44
From: Dana Halpin
Subject: 2019 Premium to 2022 Premium Upgrade Issue

Thank you for your reply.

 

Both instances are 13.0.5698.0. It wasn't like that when I first started but now it is, but still getting the error.

 

I have port 1433 open on the server I'm migrating from too.

 

 

Dana Halpin
Consulting Manager

 

#1 Manufacturing Solution Provider in the Nation 2006 - 2020

 

Vrakas/Blum Computer Consulting, LLC 445 South Moorland Road, Suite 400  Brookfield, WI 53005 office:  262-797-0400 direct:  262-798-7608 fax:       262-797-7895 email:   dhalpin@v-bcc.com web:      v-bcc.com Don't forget to follow us on Social Media!

 

 

I think you need to ask "IT".

------------------------------
Doug Higgs
Midwest Commerce Solutions, Inc
(312) 315-0960
Chauffeur, Chef, and Personal Assistant to Sprinkles
------------------------------

Original Message:
Sent: 01-28-2023 12:52
From: Dana Halpin
Subject: 2019 Premium to 2022 Premium Upgrade Issue

Thank you.

 

How do I find out what the SQL_Instance Network account is? The SQL service is not Local System account as of now.

 

 

 

Dana Halpin
Consulting Manager

 

#1 Manufacturing Solution Provider in the Nation 2006 - 2020

 

Vrakas/Blum Computer Consulting, LLC 445 South Moorland Road, Suite 400  Brookfield, WI 53005 office:  262-797-0400 direct:  262-798-7608 fax:       262-797-7895 email:  dhalpin@v-bcc.com web:     v-bcc.com Don't forget to follow us on Social Media!

 

 

Original Message:
Sent: 1/28/2023 12:32:00 PM
From: Doug Higgs
Subject: RE: 2019 Premium to 2022 Premium Upgrade Issue

The attached is a Sage KB that addresses the error.

------------------------------
Doug Higgs
Midwest Commerce Solutions, Inc
(312) 315-0960
Chauffeur, Chef, and Personal Assistant to Sprinkles
------------------------------


Original Message:
Sent: 01-28-2023 11:44
From: Dana Halpin
Subject: 2019 Premium to 2022 Premium Upgrade Issue

Thank you for your reply.

 

Both instances are 13.0.5698.0. It wasn't like that when I first started but now it is, but still getting the error.

 

I have port 1433 open on the server I'm migrating from too.

 

 

Dana Halpin
Consulting Manager

 

#1 Manufacturing Solution Provider in the Nation 2006 - 2020

 

Vrakas/Blum Computer Consulting, LLC 445 South Moorland Road, Suite 400  Brookfield, WI 53005 office:  262-797-0400 direct:  262-798-7608 fax:       262-797-7895 email:   dhalpin@v-bcc.com web:      v-bcc.com Don't forget to follow us on Social Media!

 

 

Original Message:
Sent: 1/28/2023 11:38:00 AM
From: Doug Higgs
Subject: RE: 2019 Premium to 2022 Premium Upgrade Issue

Make sure port 1433 is open on the firewall of the server you are migrating from. Also, make sure that both instances of SQL Server are exactly the same... same product updates, everything.   If SQL server instance 1 is version 15.0.4261.1 then SQL server instance 2 needs to be 15.0.4261.1.

------------------------------
Doug Higgs
Midwest Commerce Solutions, Inc
(312) 315-0960
Chauffeur, Chef, and Personal Assistant to Sprinkles

Is this the initial migration or are you re-migrating?



See Sage City for a similar ( though not exact ) error - Error Number 0x80040e14 Description ALTER DATABASE failed because a lock could not be placed on database

Sage KB 116460 - Error: 2 (The system cannot find the file specified.) (Unfortunately, no resolutions and KB just says Sage has no ideas/researching )

As discussed in the Sage City post - and also in a post that I recently started here - make sure to have a complete backup of \mas90 ( v2022 ) and the MAS_SYSTEM SQL database because if the migration crashes, it may put your 2022 in a state where you cannot start it again ( even to migrate ) and most of Sage's suggestions seem to be "reinstall Sage 100 "

With the Premium to Premium that I am doing, my backup plan for re-migrating  (in case of continuing errors)  is to drop the MAS_XXX on the v2022 system and re-migrate ( which is what Cullen says worked in the Sage City post ). Make sure not to delete MAS_SYSTEM because you'll need that in order to re-migrate.

I think there's an issue with the Premium to Premium migration tool. And if the migration is interrupted (errors), more often than not, you either need to reinstall the Sage 100 you are migrating to or restore that from a backup to be able to try again.

.


------------------------------
Wayne Schulz
wayne@s-consult.com
Schulz Consulting
(860) 516-8990
Moodus, CT
------------------------------

I would agree there is definitely an issue with this migration tool. I have a v2019 SQL to v2022 SQL that I have been trying to complete since September. Numerous errors & issues. Migrating with or without system files, re-migrating, & conversion have all been a nightmare. They have sent 3 different migration programs & they are supposedly testing additional ones on their end & we've even done a manual migration that took 9 hours & then the conversion still failed. The client has 21 live companies with 4 of them being so large that it takes 20 hours to convert the data for 1. Sage has had their data for months trying to get it to work. We have a couple more SQL to SQL upgrades coming & I am extremely nervous.

------------------------------
Dana Young
Lehman Wesley & Associates
------------------------------

Original Message:
Sent: 01-28-2023 20:37
From: Wayne Schulz
Subject: 2019 Premium to 2022 Premium Upgrade Issue

Is this the initial migration or are you re-migrating?



See Sage City for a similar ( though not exact ) error - Error Number 0x80040e14 Description ALTER DATABASE failed because a lock could not be placed on database

Sage KB 116460 - Error: 2 (The system cannot find the file specified.) (Unfortunately, no resolutions and KB just says Sage has no ideas/researching )

As discussed in the Sage City post - and also in a post that I recently started here - make sure to have a complete backup of \mas90 ( v2022 ) and the MAS_SYSTEM SQL database because if the migration crashes, it may put your 2022 in a state where you cannot start it again ( even to migrate ) and most of Sage's suggestions seem to be "reinstall Sage 100 "

With the Premium to Premium that I am doing, my backup plan for re-migrating  (in case of continuing errors)  is to drop the MAS_XXX on the v2022 system and re-migrate ( which is what Cullen says worked in the Sage City post ). Make sure not to delete MAS_SYSTEM because you'll need that in order to re-migrate.

I think there's an issue with the Premium to Premium migration tool. And if the migration is interrupted (errors), more often than not, you either need to reinstall the Sage 100 you are migrating to or restore that from a backup to be able to try again.

.


------------------------------
Wayne Schulz
wayne@s-consult.com
Schulz Consulting
(860) 516-8990
Moodus, CT
------------------------------

This can be moved off of Urgent Support as it sounds like it's going to take much longer than anticipated to resolve.

I've tried all the very helpful suggestions (thank you!!!!) and restored from backup and migrated several times today and still am receiving same error. This is the initial migration so I only have MAS_SYSTEM in my target install.

I will open up a case with Sage tomorrow and if resolved put the resolution in here for others.

Thank you to those who helped over the weekend. Much appreciated.

------------------------------
Dana Halpin
Vrakas/Blum Computer Consulting, Inc.
------------------------------

Original Message:
Sent: 01-29-2023 15:41
From: Dana Young
Subject: 2019 Premium to 2022 Premium Upgrade Issue

I would agree there is definitely an issue with this migration tool. I have a v2019 SQL to v2022 SQL that I have been trying to complete since September. Numerous errors & issues. Migrating with or without system files, re-migrating, & conversion have all been a nightmare. They have sent 3 different migration programs & they are supposedly testing additional ones on their end & we've even done a manual migration that took 9 hours & then the conversion still failed. The client has 21 live companies with 4 of them being so large that it takes 20 hours to convert the data for 1. Sage has had their data for months trying to get it to work. We have a couple more SQL to SQL upgrades coming & I am extremely nervous.

------------------------------
Dana Young
Lehman Wesley & Associates
------------------------------


Original Message:
Sent: 01-28-2023 20:37
From: Wayne Schulz
Subject: 2019 Premium to 2022 Premium Upgrade Issue

Is this the initial migration or are you re-migrating?



See Sage City for a similar ( though not exact ) error - Error Number 0x80040e14 Description ALTER DATABASE failed because a lock could not be placed on database

Sage KB 116460 - Error: 2 (The system cannot find the file specified.) (Unfortunately, no resolutions and KB just says Sage has no ideas/researching )

As discussed in the Sage City post - and also in a post that I recently started here - make sure to have a complete backup of \mas90 ( v2022 ) and the MAS_SYSTEM SQL database because if the migration crashes, it may put your 2022 in a state where you cannot start it again ( even to migrate ) and most of Sage's suggestions seem to be "reinstall Sage 100 "

With the Premium to Premium that I am doing, my backup plan for re-migrating  (in case of continuing errors)  is to drop the MAS_XXX on the v2022 system and re-migrate ( which is what Cullen says worked in the Sage City post ). Make sure not to delete MAS_SYSTEM because you'll need that in order to re-migrate.

I think there's an issue with the Premium to Premium migration tool. And if the migration is interrupted (errors), more often than not, you either need to reinstall the Sage 100 you are migrating to or restore that from a backup to be able to try again.

.


------------------------------
Wayne Schulz
wayne@s-consult.com
Schulz Consulting
(860) 516-8990
Moodus, CT

Update on this. Sage connected with me and tried 3 different migration tools (one was for v2023 not released yet) and still could not get through the error. Found out by looking at migration log, the path for the target sql server instance was not a UNC path. It was the C: drive. Had to go into my target SQL instance drop the MAS_SYSTEM database and reattach it with the UNC path pointing to the instance. (Nathan Shaw @ Sage figured it out). Thank you to everyone who tried to help out. Hope this information saves time for someone someday!

------------------------------
Dana Halpin
Vrakas/Blum Computer Consulting, Inc.
------------------------------

Original Message:
Sent: 01-29-2023 16:46
From: Dana Halpin
Subject: 2019 Premium to 2022 Premium Upgrade Issue

This can be moved off of Urgent Support as it sounds like it's going to take much longer than anticipated to resolve.

I've tried all the very helpful suggestions (thank you!!!!) and restored from backup and migrated several times today and still am receiving same error. This is the initial migration so I only have MAS_SYSTEM in my target install.

I will open up a case with Sage tomorrow and if resolved put the resolution in here for others.

Thank you to those who helped over the weekend. Much appreciated.

------------------------------
Dana Halpin
Vrakas/Blum Computer Consulting, Inc.
------------------------------


Original Message:
Sent: 01-29-2023 15:41
From: Dana Young
Subject: 2019 Premium to 2022 Premium Upgrade Issue

I would agree there is definitely an issue with this migration tool. I have a v2019 SQL to v2022 SQL that I have been trying to complete since September. Numerous errors & issues. Migrating with or without system files, re-migrating, & conversion have all been a nightmare. They have sent 3 different migration programs & they are supposedly testing additional ones on their end & we've even done a manual migration that took 9 hours & then the conversion still failed. The client has 21 live companies with 4 of them being so large that it takes 20 hours to convert the data for 1. Sage has had their data for months trying to get it to work. We have a couple more SQL to SQL upgrades coming & I am extremely nervous.

------------------------------
Dana Young
Lehman Wesley & Associates


Original Message:
Sent: 01-28-2023 20:37
From: Wayne Schulz
Subject: 2019 Premium to 2022 Premium Upgrade Issue

Is this the initial migration or are you re-migrating?



See Sage City for a similar ( though not exact ) error - Error Number 0x80040e14 Description ALTER DATABASE failed because a lock could not be placed on database

Sage KB 116460 - Error: 2 (The system cannot find the file specified.) (Unfortunately, no resolutions and KB just says Sage has no ideas/researching )

As discussed in the Sage City post - and also in a post that I recently started here - make sure to have a complete backup of \mas90 ( v2022 ) and the MAS_SYSTEM SQL database because if the migration crashes, it may put your 2022 in a state where you cannot start it again ( even to migrate ) and most of Sage's suggestions seem to be "reinstall Sage 100 "

With the Premium to Premium that I am doing, my backup plan for re-migrating  (in case of continuing errors)  is to drop the MAS_XXX on the v2022 system and re-migrate ( which is what Cullen says worked in the Sage City post ). Make sure not to delete MAS_SYSTEM because you'll need that in order to re-migrate.

I think there's an issue with the Premium to Premium migration tool. And if the migration is interrupted (errors), more often than not, you either need to reinstall the Sage 100 you are migrating to or restore that from a backup to be able to try again.

.


------------------------------
Wayne Schulz
wayne@s-consult.com
Schulz Consulting
(860) 516-8990
Moodus, CT

@Dana Halpin  is there any indication of what might have caused this? 

And for those who will invariably stumble on this post in the future - can you elaborate on how you reattach with a UNC

Is this done somehow by backing up MAS_SYSTEM and restoring it?

------------------------------
Wayne Schulz
wayne@s-consult.com
Schulz Consulting
(860) 516-8990
Moodus, CT
------------------------------

Original Message:
Sent: 02-08-2023 17:51
From: Dana Halpin
Subject: 2019 Premium to 2022 Premium Upgrade Issue

Update on this. Sage connected with me and tried 3 different migration tools (one was for v2023 not released yet) and still could not get through the error. Found out by looking at migration log, the path for the target sql server instance was not a UNC path. It was the C: drive. Had to go into my target SQL instance drop the MAS_SYSTEM database and reattach it with the UNC path pointing to the instance. (Nathan Shaw @ Sage figured it out). Thank you to everyone who tried to help out. Hope this information saves time for someone someday!

------------------------------
Dana Halpin
Vrakas/Blum Computer Consulting, Inc.
------------------------------


Original Message:
Sent: 01-29-2023 16:46
From: Dana Halpin
Subject: 2019 Premium to 2022 Premium Upgrade Issue

This can be moved off of Urgent Support as it sounds like it's going to take much longer than anticipated to resolve.

I've tried all the very helpful suggestions (thank you!!!!) and restored from backup and migrated several times today and still am receiving same error. This is the initial migration so I only have MAS_SYSTEM in my target install.

I will open up a case with Sage tomorrow and if resolved put the resolution in here for others.

Thank you to those who helped over the weekend. Much appreciated.

------------------------------
Dana Halpin
Vrakas/Blum Computer Consulting, Inc.


Original Message:
Sent: 01-29-2023 15:41
From: Dana Young
Subject: 2019 Premium to 2022 Premium Upgrade Issue

I would agree there is definitely an issue with this migration tool. I have a v2019 SQL to v2022 SQL that I have been trying to complete since September. Numerous errors & issues. Migrating with or without system files, re-migrating, & conversion have all been a nightmare. They have sent 3 different migration programs & they are supposedly testing additional ones on their end & we've even done a manual migration that took 9 hours & then the conversion still failed. The client has 21 live companies with 4 of them being so large that it takes 20 hours to convert the data for 1. Sage has had their data for months trying to get it to work. We have a couple more SQL to SQL upgrades coming & I am extremely nervous.

------------------------------
Dana Young
Lehman Wesley & Associates


Original Message:
Sent: 01-28-2023 20:37
From: Wayne Schulz
Subject: 2019 Premium to 2022 Premium Upgrade Issue

Is this the initial migration or are you re-migrating?



See Sage City for a similar ( though not exact ) error - Error Number 0x80040e14 Description ALTER DATABASE failed because a lock could not be placed on database

Sage KB 116460 - Error: 2 (The system cannot find the file specified.) (Unfortunately, no resolutions and KB just says Sage has no ideas/researching )

As discussed in the Sage City post - and also in a post that I recently started here - make sure to have a complete backup of \mas90 ( v2022 ) and the MAS_SYSTEM SQL database because if the migration crashes, it may put your 2022 in a state where you cannot start it again ( even to migrate ) and most of Sage's suggestions seem to be "reinstall Sage 100 "

With the Premium to Premium that I am doing, my backup plan for re-migrating  (in case of continuing errors)  is to drop the MAS_XXX on the v2022 system and re-migrate ( which is what Cullen says worked in the Sage City post ). Make sure not to delete MAS_SYSTEM because you'll need that in order to re-migrate.

I think there's an issue with the Premium to Premium migration tool. And if the migration is interrupted (errors), more often than not, you either need to reinstall the Sage 100 you are migrating to or restore that from a backup to be able to try again.

.


------------------------------
Wayne Schulz
wayne@s-consult.com
Schulz Consulting
(860) 516-8990
Moodus, CT

The way it was explained, the migration tool is supposed to convert the path pointing to the sql instance on the C: drive to the UNC path automatically which it did for my source but not my target. Sage did not know if this was because I had both instances on the same SQL server and the SQL server was on another server separate from the Sage server. They were going to try to replicate this environment on their end and do a test migration to see if they can duplicate it and hopefully write something up. When attaching, go into the properties of the database, files and you'll see the path in there. Change it to UNC and remigrate. My path after migration went back to C: drive even though they forced it to be the UNC path before migration.

------------------------------
Dana Halpin
Vrakas/Blum Computer Consulting, Inc.
------------------------------

Original Message:
Sent: 02-09-2023 08:54
From: Wayne Schulz
Subject: 2019 Premium to 2022 Premium Upgrade Issue

@Dana Halpin  is there any indication of what might have caused this? 

And for those who will invariably stumble on this post in the future - can you elaborate on how you reattach with a UNC

Is this done somehow by backing up MAS_SYSTEM and restoring it?

------------------------------
Wayne Schulz
wayne@s-consult.com
Schulz Consulting
(860) 516-8990
Moodus, CT
------------------------------


Original Message:
Sent: 02-08-2023 17:51
From: Dana Halpin
Subject: 2019 Premium to 2022 Premium Upgrade Issue

Update on this. Sage connected with me and tried 3 different migration tools (one was for v2023 not released yet) and still could not get through the error. Found out by looking at migration log, the path for the target sql server instance was not a UNC path. It was the C: drive. Had to go into my target SQL instance drop the MAS_SYSTEM database and reattach it with the UNC path pointing to the instance. (Nathan Shaw @ Sage figured it out). Thank you to everyone who tried to help out. Hope this information saves time for someone someday!

------------------------------
Dana Halpin
Vrakas/Blum Computer Consulting, Inc.


Original Message:
Sent: 01-29-2023 16:46
From: Dana Halpin
Subject: 2019 Premium to 2022 Premium Upgrade Issue

This can be moved off of Urgent Support as it sounds like it's going to take much longer than anticipated to resolve.

I've tried all the very helpful suggestions (thank you!!!!) and restored from backup and migrated several times today and still am receiving same error. This is the initial migration so I only have MAS_SYSTEM in my target install.

I will open up a case with Sage tomorrow and if resolved put the resolution in here for others.

Thank you to those who helped over the weekend. Much appreciated.

------------------------------
Dana Halpin
Vrakas/Blum Computer Consulting, Inc.


Original Message:
Sent: 01-29-2023 15:41
From: Dana Young
Subject: 2019 Premium to 2022 Premium Upgrade Issue

I would agree there is definitely an issue with this migration tool. I have a v2019 SQL to v2022 SQL that I have been trying to complete since September. Numerous errors & issues. Migrating with or without system files, re-migrating, & conversion have all been a nightmare. They have sent 3 different migration programs & they are supposedly testing additional ones on their end & we've even done a manual migration that took 9 hours & then the conversion still failed. The client has 21 live companies with 4 of them being so large that it takes 20 hours to convert the data for 1. Sage has had their data for months trying to get it to work. We have a couple more SQL to SQL upgrades coming & I am extremely nervous.

------------------------------
Dana Young
Lehman Wesley & Associates


Original Message:
Sent: 01-28-2023 20:37
From: Wayne Schulz
Subject: 2019 Premium to 2022 Premium Upgrade Issue

Is this the initial migration or are you re-migrating?



See Sage City for a similar ( though not exact ) error - Error Number 0x80040e14 Description ALTER DATABASE failed because a lock could not be placed on database

Sage KB 116460 - Error: 2 (The system cannot find the file specified.) (Unfortunately, no resolutions and KB just says Sage has no ideas/researching )

As discussed in the Sage City post - and also in a post that I recently started here - make sure to have a complete backup of \mas90 ( v2022 ) and the MAS_SYSTEM SQL database because if the migration crashes, it may put your 2022 in a state where you cannot start it again ( even to migrate ) and most of Sage's suggestions seem to be "reinstall Sage 100 "

With the Premium to Premium that I am doing, my backup plan for re-migrating  (in case of continuing errors)  is to drop the MAS_XXX on the v2022 system and re-migrate ( which is what Cullen says worked in the Sage City post ). Make sure not to delete MAS_SYSTEM because you'll need that in order to re-migrate.

I think there's an issue with the Premium to Premium migration tool. And if the migration is interrupted (errors), more often than not, you either need to reinstall the Sage 100 you are migrating to or restore that from a backup to be able to try again.

.


------------------------------
Wayne Schulz
wayne@s-consult.com
Schulz Consulting
(860) 516-8990
Moodus, CT