- Product: Primo
- Product Version: February 2016 Release
- Relevant for Installation Type: Dedicated-Direct, Direct, Local, Total Care
Following install of Primo February 2016 Release, Primo returns HTTP 404 error when the FE is accessed.
Was Mehmet Celik's jQuery.PRIMO.jar implemented prior to Primo February 2016 Release?
This file may be found on the FE server in:
Starting with the Primo February 2016 Release, this jar is now included in the OTB Primo build, as jQuery-PRIMO-1.1.2.jar in the same directory.
If the original jQuery.PRIMO.jar is present when Primo February Release is installed and restarted, the two files conflict and prevent Primo from starting correctly, which results in the 404 errors.
The fix is to remove or rename the original jQuery.PRIMO.jar file prior to restarting Primo after February Release is installed.
The original jQuery.PRIMO.jar file will be handled better by the May 2016 Release.
- Article last edited: 07/March/2016