I'm trying out the new feature but I'm hitting an issue that i cant find a solution for.
When I click convert to reactive I'm prompted to install the OutSystemsReactiveMigration Module, but it fails to install with an "Unknown Error" and prompt to check user permissions to publish on server.
I asked the Server admin to attempt the Installation with the same result.
Our Versions.
Platform Server: 11.18.1 (Build 37828)
Service Studio: 11.55.69 (Build 64809)
Hi,Can you check on lifetime what permission you have. ?
ThanksTousif
Hi,
I have full control Permissions in lifetime.
I don't think permissions is the issue as your admin attempted to install the Module with the same error.
This is a fairly common (and frustrating) situation with Convert to Reactive in O11. The “Unknown Error” during installation of OutSystemsReactiveMigration is usually not actually a user permission problem, even though the message says so. It’s typically caused by platform/version compatibility or missing factory components.
Based on your versions, your setup is the likely cause:
✅ Platform Server: 11.18.1 (Build 37828)✅ Service Studio: 11.55.69 (Build 64809)
⚠️ Key Issue
Your Service Studio is much newer than your Platform Server.
Reactive conversion features (and the module OutSystemsReactiveMigration) depend on server-side support. If the platform server doesn’t support the exact migration module version that Service Studio expects, the installation fails with a vague “Unknown Error”.
What you should do
1️ .Confirm your Platform Server is supported
OutSystems Reactive conversion tooling works best when:
Service Studio and Platform Server are on the same release family
Platform is updated to a newer cumulative release
In your case, you should upgrade Platform Server to a newer version (at least matching the Service Studio generation).
Recommended fix:
✅ Upgrade Platform Server to the latest 11.x available for your infrastructure.
2️. Try manual installation from Forge
Instead of letting Service Studio auto-install:
Go to Forge
Search: OutSystems Reactive Migration
Install it manually into the environment
Sometimes Service Studio fails but Forge installation works.
3️. Check if the environment allows installing system components
Even if admin tried, installation can fail due to environment restrictions like:
Deployment Controller issues
Invalid license permissions
Factory components out of sync
Check Service Center → Factory → ApplicationsSee if OutSystemsReactiveMigration partially exists or failed.
If it exists in an invalid state:
Delete it (if possible)
Reinstall again from Forge
4️. Check Deployment Controller / Logs (most important)
The real reason will appear in logs, not in Service Studio.
Ask admin to check:
Service Center Logs:
Service Center → Monitoring → Error Logs
Environment Health
Server file logs:
C:\Program Files\OutSystems\Platform Server\ logs(especially deployment logs)
Common hidden errors:
database permission issues
component compilation failure
missing system references
inconsistent platform version
5️. Confirm LifeTime + System Components are updated
Reactive Migration depends on updated system components like:
LifeTime
Users app
Service Center components
If your environment is old and not upgraded properly, module publishing fails.
Most Probable Root Cause (based on your case)
✅ Platform Server 11.18.1 is too old for Service Studio 11.55.x migration tooling.
That mismatch is the #1 reason why admins also cannot install it.
Best Solution (what OutSystems support would also suggest)
✔ Upgrade Platform Server to latest available 11 release
After upgrade:
open Service Studio
try Convert to Reactive again
module should install successfully
If you want, I can tell you the exact minimum platform version required for Service Studio 11.55.x, but for that I’ll need your OutSystems Release number shown in Service Center (not just build).