Version Schema for Application is Not Assigned

Scenario:

In many cases, some clients intentionally or by mistake rename the RPro9.exe/PrismMgmt.exe files.

Issue:

When a user launches RPro9/PrismMgmt, after entering their credentials on the logon page, users get an error stating "Version schema for application is not assigned." Once they click on OK, the application blinks and then disappears.

As shown in the following two screenshots:

Solution:

Even though this error message does not provide any useful or additional message details, you can still try to solve the issue by following these steps:

Steps to Resolve this Issue

• Confirm no recent errors are logged in rproods_alert.log. [Drive]:\Oracle\diag\rdbms\rproods\rproods\trace
• Confirm you can launch Techtoolkit and query the database via SQL Shell without any issues.
• It is important to select "Show Extensions" from the view menu to confirm the executables are correctly spelled. Then confirm RPro9.exe/PrismMgmt.exe are spelled correctly:
  • [Drive]:\PrismMgmt.exe
  • [Drive]:\RetailPro9.exe

 

Conclusion:

After confirming the executables are spelled correctly, RPro9/PrismMgmt should launch without any errors.