Hi Ryoichi Tokota 

Please can you confirm how did you take the 2019 project and move it/open it to 2022?

Regardless the warning you quote mentions   

Ryoichi Tokota said:

WorldServer.WsPackageConvertor

This would be coming from an app that you may have had for 2019, but not yet put in place for 2022.
Please see here: (Missing Wiki Page)

Have a good day
Lyds

I worked the project on 2019 and almost finished it. It was saved OK. After switching from 2019 to 2022, I think I was able to open the project by double-clicking the project file. I was told that I should upgrade the TM. So I did. Edited the files in this project. I thought I was able to move on to 2022 almost seamlessly except for the TB issue inherited from 2019. Then, I tried to generate a return package and couldn't.

After that, I was told that the convertor file needs to be installed. I installed it and confirmed that it is actually installed.

Then, I tried to generate a return package. The result was exactly the same.

After all, I copied the whole file set to my older pc where 2019 is still installed. Surprisingly, the project file edited using 2022 could be opened in 2019! I was able to generate a return package there.