Developer Studio's Local Server fails to start, with the console showing 'WARNING! Invalid license detected' (citing a modified FND_LICENSED_USER view or modified technical-role content) alongside a JMS queue-not-found error for FND_ADMIN_MAIN_QUEUE — how do you recover from this?

All FAQ questions / Developer Studio, deployment, and upgrades

Answer

Start with the license side: regenerate FndLicense.plsql from Developer Studio and redeploy the resulting fndLicense.api/fndLicense.apy, refresh the Dictionary Cache, then log in as the Application Owner and reapply the license key. If that alone doesn't clear it, a further sequence has resolved this in practice: launch a command prompt and connect as SYS to run Prepare_SYS.Dbagrant('<APPOWNER>', 'YES'), then connect as the Application Owner and run Installation_SYS.Grant_Ifssys(TRUE), redeploy fndLicense.api/fndLicense.apy again, refresh the Dictionary Cache once more, and reapply the license key a second time. The invalid-license warning is what's blocking the local server's admin/queue setup from completing correctly, so resolving it is usually what clears the JMS queue error as a side effect.

Documentation-based answer. Confirm the product and release before applying it. This answer has not been verified in an IFS environment.

← Browse Developer Studio, deployment, and upgrades questions