In order to ensure data consistency the application makes use of lock files to prevent duplicate access to unique resources. Examples of this are creating problem or change records where it is critical to prevent two requests to update a sequence number happening simultaneously.
Due to the requirement to use lock files occasionally on a very heavily used server, where many people are trying to access a resource simultaneously, there will be occasions where the application is unable to obtain access to the resource within a resonable time frame. When this happens you will be shown an error screen (the help for which will bring you here).
The best thing to do is use the browsers back button to return to the previous screen and resubmit the page. By using the browsers back button the page you came from will still contain all the required data.
NOTE: the maximum wait for a lock file defaults to four (4) seconds. This is customisable by the site administrator.