# Pega migration 19.1 -\>22.1

**URL:** <https://forums.pega.com/t/pega-migration-19-1-22-1/6149>\
**Category:** General\
**Tags:** updates, 22-1, installation-and-deployment, solutions-engineer, robotic-process-automation\
**Created:** [February 16, 2024, 12:17pm UTC](https://forums.pega.com/t/pega-migration-19-1-22-1/6149 "2024-02-16T12:17:50Z")\
**Posts on this page:** 12\
**Page:** 1

<div class="post-metadata">

**Author:** ![SebastianD](https://avatars.discourse-cdn.com/v4/letter/s/2acd7d/32.png) [@SebastianD](https://forums.pega.com/u/SebastianD)\
**Post date:** [February 16, 2024, 12:17pm UTC](https://forums.pega.com/t/pega-migration-19-1-22-1/6149/1 "2024-02-16T12:17:50Z")

</div>

Hi, I try to migrate projects from 19.1 to 22.1 and in all trys I get same Error.

ERROR | 2024-02-16 13:15:53.305 | 4 | MTA | Upgrade | CopyFilesStep | Failed to process Copy File Step, Invalid Product Version - ‘19.1’ in E:\Timon\_Pumbaa\Timon\_Pumbaa\Timon\_Pumbaa.osproj  
ERROR | 2024-02-16 13:15:53.306 | 4 | MTA | Upgrade | StepResults | STEP 2: ‘Copy Legacy Files’ step failed  
ERROR | 2024-02-16 13:15:53.309 | 4 | MTA | Upgrade | | Aborting upgrade!

---

<div class="post-metadata">

**Author:** ![ThomasSasnett](https://yyz2.discourse-cdn.com/pega/user_avatar/forums.pega.com/thomassasnett/32/7690_2.png) [@ThomasSasnett](https://forums.pega.com/u/ThomasSasnett)\
**Post date:** [February 20, 2024, 1:41pm UTC](https://forums.pega.com/t/pega-migration-19-1-22-1/6149/2 "2024-02-20T13:41:50Z")

</div>

@SebastianD I suggest you enable DEBUG level logging on the upgrade config file and try again. One thing I have found is that at DEBUG there is a lot more information on what is happening. I would also suggest that you build your 19.1 solution first to ensure it is complete before you try to upgrade it.

Config file - %AppData%\Pegasystems\PegaLegacyUpgradeConfig.json

Change the log categories to level 4.

---

<div class="post-metadata">

**Author:** ![SebastianD](https://avatars.discourse-cdn.com/v4/letter/s/2acd7d/32.png) [@SebastianD](https://forums.pega.com/u/SebastianD)\
**Post date:** [February 21, 2024, 10:33am UTC](https://forums.pega.com/t/pega-migration-19-1-22-1/6149/3 "2024-02-21T10:33:36Z")

</div>

@ThomasSasnett

Hi, I did what You requested and the result is the same.

Log and print screens in att…

 ![Screen.png](https://pega1.discourse-cdn.com/pega/original/1X/2051fe934eeacafd0530f446dbbc540086535f48.png)

[PegaLegacyUpgrade.txt](https://forums.pega.com/uploads/short-url/pj9B1LwutTUER2CKRLm2bBBTaiu.txt) (80.6 KB)

---

<div class="post-metadata">

**Author:** ![ThomasSasnett](https://yyz2.discourse-cdn.com/pega/user_avatar/forums.pega.com/thomassasnett/32/7690_2.png) [@ThomasSasnett](https://forums.pega.com/u/ThomasSasnett)\
**Post date:** [February 21, 2024, 2:38pm UTC](https://forums.pega.com/t/pega-migration-19-1-22-1/6149/4 "2024-02-21T14:38:28Z")

</div>

@SebastianD Look at line 312. There appears to be something wrong with the product version listed in this file. Has it been manually altered? Can you show me that file?

Invalid Product Version - ‘19.1’ in E:\Timon\_Pumbaa\Timon\_Pumbaa\Timon\_Pumbaa.osproj

---

<div class="post-metadata">

**Author:** ![SebastianD](https://avatars.discourse-cdn.com/v4/letter/s/2acd7d/32.png) [@SebastianD](https://forums.pega.com/u/SebastianD)\
**Post date:** [February 21, 2024, 7:33pm UTC](https://forums.pega.com/t/pega-migration-19-1-22-1/6149/5 "2024-02-21T19:33:01Z")

</div>

@ThomasSasnett

Filie in attachment

I have that problem in all project, they have been never altered manually.

[Timon\_Pumbaa.osproj.txt](https://forums.pega.com/uploads/short-url/3dBxyeGsoE3bUjHbF4FiUJsZpmv.txt) (13.8 KB)

---

<div class="post-metadata">

**Author:** ![ThomasSasnett](https://yyz2.discourse-cdn.com/pega/user_avatar/forums.pega.com/thomassasnett/32/7690_2.png) [@ThomasSasnett](https://forums.pega.com/u/ThomasSasnett)\
**Post date:** [February 21, 2024, 9:46pm UTC](https://forums.pega.com/t/pega-migration-19-1-22-1/6149/6 "2024-02-21T21:46:54Z")

</div>

@SebastianD I think the best way to help you is to open a support request. They can examine the 19.1 code and see what is going on. If you do open a support request, please list the number here. My suspicion is that this is related to the culture of your machine.

---

<div class="post-metadata">

**Author:** ![SebastianD](https://avatars.discourse-cdn.com/v4/letter/s/2acd7d/32.png) [@SebastianD](https://forums.pega.com/u/SebastianD)\
**Post date:** [February 22, 2024, 7:23am UTC](https://forums.pega.com/t/pega-migration-19-1-22-1/6149/7 "2024-02-22T07:23:06Z")

</div>

@ThomasSasnett Hi, thanks for help but could you tell me how to open support request?

All I can find is another forum question.

Edit: Ok I think I found it but:

In order to create a support ticket, you must be added as a contact to a client or partner account. Please reach out to a support administrator to be added.

best regards

Sebastian

---

<div class="post-metadata">

**Author:** ![SebastianD](https://avatars.discourse-cdn.com/v4/letter/s/2acd7d/32.png) [@SebastianD](https://forums.pega.com/u/SebastianD)\
**Post date:** [February 27, 2024, 10:54am UTC](https://forums.pega.com/t/pega-migration-19-1-22-1/6149/8 "2024-02-27T10:54:59Z")

</div>

@ThomasSasnett

Hi, I found solution in my culture settings. Problem was “,” instead of “.”. Changing to dot separator helped and conversion was successful.

In my country “,” is used in almost every application as separator. Does Pega Team will realese patch to fix that problem?

Cheers

---

<div class="post-metadata">

**Author:** ![MarijeSchillern](https://yyz2.discourse-cdn.com/pega/user_avatar/forums.pega.com/marijeschillern/32/23321_2.png) [@MarijeSchillern](https://forums.pega.com/u/MarijeSchillern)\
**Post date:** [March 21, 2024, 2:38pm UTC](https://forums.pega.com/t/pega-migration-19-1-22-1/6149/9 "2024-03-21T14:38:26Z")

</div>

@SebastianD did you open a ticket via the [MSP](https://msp.pega.com/)?

It would help us greatly if you can provide the INC id here so that we can help track the issue.

---

<div class="post-metadata">

**Author:** ![MichaelNorton](https://yyz2.discourse-cdn.com/pega/user_avatar/forums.pega.com/michaelnorton/32/22091_2.png) [@MichaelNorton](https://forums.pega.com/u/MichaelNorton)\
**Post date:** [February 22, 2024, 1:03pm UTC](https://forums.pega.com/t/pega-migration-19-1-22-1/6149/10 "2024-02-22T13:03:01Z")

</div>

@SebastianD

Your Support Administrator might also be called your Support Contact Administrator or Account Administrator. A Support Administrator adds and removes support contacts, among other duties. For more information, see [Understanding Support user roles](https://support.pega.com/support-doc/understanding-support-user-roles) and [Creating a Support ticket](https://support.pega.com/support-doc/creating-support-ticket).

Also, take a look at this topic: [Administering Support Accounts](https://support.pega.com/support-doc/administering-support-accounts).

---

<div class="post-metadata">

**Author:** ![ThomasSasnett](https://yyz2.discourse-cdn.com/pega/user_avatar/forums.pega.com/thomassasnett/32/7690_2.png) [@ThomasSasnett](https://forums.pega.com/u/ThomasSasnett)\
**Post date:** [March 13, 2024, 5:12pm UTC](https://forums.pega.com/t/pega-migration-19-1-22-1/6149/11 "2024-03-13T17:12:00Z")

</div>

@SebastianD I would check the release notes to see if a patch has been released. If you did open a support request, they will let you know when and in what version.

[https://docs.pega.com/bundle/robotic-automation-221/page/robotic-automation/release-build-notes/build-notes-pra-221.html](https://docs.pega.com/bundle/robotic-automation-221/page/robotic-automation/release-build-notes/build-notes-pra-221.html)

---

<div class="post-metadata">

**Author:** ![ThomasSasnett](https://yyz2.discourse-cdn.com/pega/user_avatar/forums.pega.com/thomassasnett/32/7690_2.png) [@ThomasSasnett](https://forums.pega.com/u/ThomasSasnett)\
**Post date:** [March 21, 2024, 3:02pm UTC](https://forums.pega.com/t/pega-migration-19-1-22-1/6149/12 "2024-03-21T15:02:02Z")

</div>

@MarijeSchillern @SebastianD I believe this has been resolved in 22.1.29 released Tuesday.
