Appboard/old/client troubleshooting

This page identifies issues that the AppBoard end-user or administrator may encounter when running the AppBoard client in the web browser, and recommends possible solutions where applicable.

Additional information is available on the AppBoard Diagnostics page.

This page addresses troubleshooting issues that take place in the web browser. For any issues on the AppBoard server, see the page for AppBoard server troubleshooting. For issues with mobile clients, see AppBoard Mobile troubleshooting

Error Messages

• Issue: You receive the error message: "Version out of date".
• Resolution: This can be caused by multiple AppBoard administrators modifying the configuration of the same system component at the same time. When changes are made to system configuration, AppBoard writes these changes to a file called stacks.xml. If that file has been updated by another administrator, in some cases the system will not be able to merge the multiple changes to the same system component. To avoid this error, try to make sure only one administrator is modifying a particular component at one time.

• Issue: You receive the following error message in the Flash player: "Unrecoverable Error".
• Resolution:
  • Refresh the browser.
  • If the issue persists, clear the browser cache and refresh again.
  • If the issue persists, check to see if other users are affected.
  • If multiple users are experiencing the same Unrecoverable Error, ask the administrator to re-start AppBoard.
  • If the issue persists after re-starting AppBoard, the system administrator can perform the following steps to revert the server to an earlier working configuration:
    1. Navigate to [APPBOARD_HOME]/server/webapps/enportal/WEB-INF/xmlroot/appboard/config/
    2. Rename stacks.xml to stacks.xml.bak
    3. Navigate to [APPBOARD_HOME]/server/webapps/enportal/WEB-INF/xmlroot/appboard/config/backup/
    4. Locate the most recent backup of stacks.xml. Copy to [APPBOARD_HOME]/server/webapps/enportal/WEB-INF/xmlroot/appboard/config/ and rename file to stacks.xml.

System Behavior

• Issue: The behavior of the system is sluggish.
• Resolution:
  1. Log on to the AppBoard server and in a browser directly access and log in to each of the back-end applications. Note any applications where there is latency between the AppBoard server and the application host server.
  2. Log in to AppBoard directly in a browser on the AppBoard server. If the system performs better in this context, then the sluggish behavior may be due to latency between the end-user browser and the AppBoard server.

Isolating Errors of Unknown Origin

• Issue: There is a general problem when running an AppBoard system, but the root cause is not apparent
• Resolution: Run each AppBoard stack as a separate enPortal channel to try to isolate the stack that is broken from the stacks that are working

1. Log in to enPortal
2. Under the Content tab, Click on the Actions button and select New Subfolder
3. For the name of the Viewset, enter "Test". The "Test" View is displayed in the Viewset list.
4. Right-click on "Test" and select New Channel
5. For Channel Name, enter "Stack 1"
6. Under Channel Types, select the Appboard option
7. Click Next in the lower-right corner
8. A list of AppBoard stacks will be displayed. Check the Display box next to the first stack
9. Repeat steps 4-8, selecting each different stack one time until you have created one channel for every stack
10. Click Save. Observe that the channels are now listed under the "test" View
11. Assign the Test view to a Role and log in as a User in that Role. Check each stack independently to see which stacks are working correctly.