• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Forwarded to devs Migration switching from .NET

Frank.P

Regular Pleskian
TITLE:
Migration switching from .NET​
PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE:
Windows 2016, 17.5.3​
PROBLEM DESCRIPTION:
All work, but show error and warning:


ERROR : Failed to fix web.config files when switching from .NET 2-3.5 to .NET 4
Migration tools tried to perform operation in 3 attempts: invalid literal for int() with base 10: ''

WARNING : Execution of "C:\Program Files (x86)\Plesk\bin\domain.exe" --update xxxxxxxxxx.org -asp.net_version "" -ignore-nonexistent-options failed with return code 1.
Stderr is
Wrong syntax for command's '-asp.net_version' parameter. '' does not match the pattern '/^(2\.0|4\.0)$/'.


Important: .Net is disabled in suscription
​
STEPS TO REPRODUCE:
Microsoft ASP.Net enabled in source server with version 3 for example

In target server not install version 3, only is installed version 4

In web.config not set by code the version, the version is only set by plesk panel​
ACTUAL RESULT:
Migration stop​
EXPECTED RESULT:
If not found code in web.config change in plesk panel and not show warning​
ANY ADDITIONAL INFORMATION:
​
YOUR EXPECTATIONS FROM PLESK SERVICE TEAM:
CONFIRM BUG​
 
Last edited:
Yes, I confirm. This is the known software issue PMT-3420.
Thanks you.
 
Back
Top