How to trouble shoot WebTop Preset errors?
For preset you can clear cache and restart application server.

and also you can follow these troubleshooting steps -

1.) Make sure the repository is up and running during the wdk applications start up or deployment.

2.)Make sure the Webtop DocApp is installed in the repository. This will insure that the dmc_wdk_presets_owner user exists

3.) Make sure presets are enabled (default setting) in /wdk/app.xml

In wdk/app.xml, we have the following configurable elements for presets, check if this has been customized in other layers.









true



1.3



/Resources/Registry/Presets/Webtop























3600







group

role







4.) Make sure the user who has the role dmc_wdk_presets_coordinator has WRITE permissions on the presets storage folder in the global repository (default storage folder is /Resources/Registry/Presets/Webtop)

5.) Open the admin node and make sure the user is showing up in the dmc_wdk_presets_coordinator role.

6.) For presets, wdk applications uses a internal named user called, dmc_wdk_presets_owner , to access the preset data. Please check if this user is created in the global / designated presets repositories ( you can verify this with IAPI ). If this user is not available, then you may need to install the correct docapp, Installing the presets docapp as mentioned in Point 2 creates this user.

7.) Check if the password for the dmc_wdk_presets_owner has been changed from the default "webtop". If it has, then the wdk app.xml needs to be updated accordingly, by adding the encrypted password to the element. Use the TrustedAuthenticatorTool to encrypt the new password.

8.) If the repository and / or password data is configured, check for the correctness of the values. the password must be a base64 encoded string, if specified.

9.) To confirm the Business Object Framework (BOF) actually pulls down all the Webtop preset jar files and Webtop definition files from the global repository, check the BOF cache folder on app server.