Thanks for replying.
These lines are already there in dfc.properties. Still the error is coming.
Main Topics
Browse All TopicsWhen I start tomcat server (where webtop is deployed), I can see the following error message on console
16:19:01,058 ERROR [main] com.documentum.web.common.
y is not available, reason: repository credentials are not valid
com.documentum.web.env.Pre
tials are not valid
at com.documentum.web.env.Pre
Can someone please let me know what is the impact of Preference repository not available and how can I enable it. Also, does this have an impact on the TBO execution? The TBOs in my repository are not getting executed. Could this be the reason?
Thank you
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Hi,
Do these lines have the same values that the ones on the dfc.properties con the Content Server? Also the repository name could be wrong. Here is additional information I got from the Documentum Support Site:
Symptoms
Users can log in to DA or WDK application, however, there are still errors thrown in the application server log indicating there is a problem with authentication to the preference repository.
Preference repository is not available, reason: repository credentials are not valid
com.documentum.web.env.Pre
....
Caused by: DfException:: THREAD: Thread-1; MSG: [DM_API_E_QUERY_FAIL]error
....
Caused by: DfException:: THREAD: Thread-1; MSG: [DM_QUERY_E_NOT_RESTRICTED
Cause
a. The dm_bof_registry object does not contain of '/Resources/Registry/Prefe
b. The dmc_wdk_preferences_owner authencitcation failed.
c. Cabinet permission dm_world is not read for '/Resources/Registry/Prefe
Resolution
a.
1. Log in to DA as admin user and navigate to Cabinet-> Resources-> Registry. Right click the Preferences in the right window and select Properties. Select the Show all Properties checkbox. Get the r_object_id.
2. Check the r_object_id is one of the restricted_folder_ids[0-x]
3. If r_object_id is not one of the above ids, try the following api. Go to api tester on DA.
API>id,c, dm_user where user_name='dm_bof_registry
API>set,c,l, restricted_folder_ids[x+1]
DATA>r_object_id# from step
API>save,c,l
b. Log in to DA, and change the dmc_wdk_preferences_owner back to default password (webtop).
c. Check each cabinets/folder of Resource, Registry and preferneces. The permission of dm_world should be read. It might be due to upgrading, sometimes the dm_world is none for those cabinets and folders.
Business Accounts
Answer for Membership
by: omoralesmPosted on 2009-06-29 at 09:44:22ID: 24737778
Hi,
operties, here you'll have to add the following lines:
d=kegOkPJk WWY\= ory=ECM e=dm_bof_r egistry
This problem is related to the Registry Repository credentials, and yes, you need to correct it if you want your TBOs up and running. I will assume that you are using DCTM 6.5, so you'll have to stop tomcat and open the file WEB-INF\classes\com\dfc.pr
dfc.globalregistry.passwor
dfc.globalregistry.reposit
dfc.globalregistry.usernam
If you don't know the values you can copy the lines from the dfc.properties file located on the Content Server, start Tomcat and try again.