To clarify, the official 220.127.116.11 release of mojoPortal is compatible with Form Wizard Pro. After the 18.104.22.168 release we updated the source code repository to use the new AjaxControlToolkit so the source code is currently dependent on a newer version of the ajaxcontroltoolkit than the official release of Form Wizard Pro, Event Calendar Pro, and Web Invoice Pro. After the next official release of mojoPortal we will make new releases of these products to be compatible.
So really you deployed a build from source code that is newer than the official 22.214.171.124 release. The version number only really corresponds to the database schema and that has not changed yet since the official release so the version number is still the same but there have been code changes.
Normally it would be possible to resolve the version difference with assemblybinding in web.config to map apps that use the old version to use the new version. However as mentioned in this blog post they messed up the versioning scheme and ran out of versions so technically the new version is lower than the previous versions. I have tried mapping from the previous version to the new one but it still throws an error because it thinks version 4.1.60623.0 is newer than version 126.96.36.199.
So the only way to solve it is with a newer version of Form Wizard Pro that uses the same version of ajaxcontroltoolkit or else deploy the official 188.8.131.52 release of mojoPortal instead of a build from source code.
If you contact me from an email address that has a purchase history for Form Wizard Pro I can send you a newer build that is compiled against the new ajaxcontroltoolkit. The user account that you used to make this forum post has no purchase history.
Hope that helps,