Package upload failed for package version string that does not exist.
Are you leveraging the most recently used MCP for building that package? The error you're seeing is in relation to the internal package version, not the external one that you specify manually. The internal version is basically and incremental counter that indicates how many times a particular package has been built. If that package has been built a lot of times with a different or older MCP then you'll see that kind of error, even if the external version is unique. To solve this in the past I have literally just hit build on the same package multiple times until my internal version number was high enough.
Can you please let me know if you are creating the update for the existing package? In such cases, you can access into Package Studio and Rebuild the Package, and change the Version string, into a number that is higher than in currently stated error. It will allow you to create the update for the existing package.
Technical Support | SOTI Inc. |1.905.624.9828 | firstname.lastname@example.org | www.soti.net |