Troubleshooting

Error when launching the Farm Manager or Portal Manager

Infor uses a third-party partner to validate digital certificates in order to launch the Portal Manager and Farm Manager applications. If you encounter an error message stating that certificate verification has failed for the IPF.LauncherServer.exe, you may need to open HTTP traffic on the machine where the Farm Manager or Portal Manager needs to be launched from, or at least open HTTP traffic to the required certificate validation website. Contact your Infor Support Consultant for more information.

User login errors

Portal users may receive this login error message: “Login Error. Try again." The error can occur when these setup problems exist:

• The user is a super user

The error can also occur when a user signs into a portal and the login is changed from the Pre-login user to their specific user account. In this case, session data is passed from the Pre-login session to the user-specific session, and the latest copy of the portal configuration is used in IPF. When this happens, there could be a change in the content version and thus a change in the custom code that runs at session start, the UserAuthenticated event handler. One version of the code would run to save off session data. Another version of code would run to consume the data but could expect different data. It is likely the user would get a login error the first time, but if they try logging in again, it will work.

Sometimes a login error event can be seen in the Diagnostics Viewer, if it is running when the error occurs. If a user reports the problem, you may need to start diagnostics and log in to the portal with that user’s credentials to troubleshoot the issue.

For unexpected errors, an event is logged in portal diagnostics even if diagnostics is not running. The portal user gets the same login error. Unexpected errors can happen when these problems occur:

• A data source method call fails
• A data source method call returns an error message
• A collection load fails

See Using portal diagnostics.

Updates in the back office are not displayed on the portal

If you have made changes in the back office that should affect images or text displayed on the portal, but those changes are not showing up on the portal, you may need to clear the cache, as described in Clearing the portal cache.

Cannot edit a customized component in the Portal Manager

To edit a customized component in the Portal Manager, such as a layout or field display format, you must be logged in to the Portal Manager using the same account that locked the component. To see who locked the component, hover over the lock icon in the far left column.

Personalizations are not displayed on the portal

For personalizations to be displayed on the portal, you must add the applicable feature to your editable content version and activate the content for that feature.