What to do if your Content server installation doesnt work and you have to install again and its not being properly uninstalled by the program.

Follow the below given steps.

1-delete all the folders related to Documentum from the sysetem , c: ,program files, My Documents. search all the folders named Documentum and its subfolders, delete them all.
2-Delete all the Registry keys from the Windows
3- Start -> Run: regedt32 -> OK (logged on as administrator)
4- Search Documentum using Edit->Search-> Use F3 for going to next item of search.
5- Delete all the registrys
6- Restart the system.

But after doing this , you still have some enteries in legacy which are not easily deleted . You have to follow below given steps.

LEGACY keys cant be deleted(easily) so follow below given steps.

1) Start -> Run: regedt32 -> OK (logged on as administrator)
2) Now to HKLM sub-window and take the key which you want deleted. Highlight it.
3) In the Regedt32 window menu select Security -> Permissions.
4) Change the access permissions for Everyone and/or Administrators to Full Control. Apply the settings.
5) Repeat 1-4 for all keys you need deleted.
6)Close Regedt32 and open Regedit. Delete the keys you don't want anymore.
7) Restart the system and search for the keys again to make sure that they are deleted from the system.

Now you are good to go for installing fresh Content Server installations.

Any positive/negative feedback is greatly appreciated.

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.

How to drop all the tables , views from the Oracle DB schema for recreating the repository?

1-

Create one sql file and name it -createdroptables.sql and write below given queries into this file


SET SERVEROUTPUT ON;

SPOOL C:\droptables.LOG;

SELECT * FROM (SELECT 'DROP TABLE '||table_name||' CASCADE CONSTRAINTS;' FROM user_tables UNION
SELECT 'DROP VIEW '||VIEW_NAME||';' FROM user_views UNION
SELECT 'DROP SEQUENCE '|| SEQUENCE_NAME||';' FROM user_sequences UNION
SELECT 'DROP SYNONYM ' || SYNONYM_NAME ||';' FROM user_synonyms UNION
SELECT 'DROP FUNCTION ' || OBJECT_NAME ||';' FROM user_procedures UNION
SELECT 'PURGE RECYCLEBIN;' FROM dual) ORDER BY 1 ASC;

SPOOL OFF

2 Run this sql file on sqlplus console

SQL> @C:\createdroptables.sql

3 Rename the droptables.log file to droptables.sql which is created in c:\ drive

4 Run this sql file on sqlplus console

SQL> @C:\createdroptables.sql

5 Check the tables in schema by running below given query

select table_name from user_tables;

6 You should get no table name ie its now empty schema.

Good Luck recreating repository.