DFS 6.5SP1 Repository Creation error

Hi,

I am in the mid of installing a new repository on my DFS 6.5SP1 CS installed on a Solaris box. I could create the repository and after i selected the option to add thís as the global repository, i am prompted to enter password for the user dm_bof_registry. After entering this, i get an error saying "Installer failed to execute Docbase HeadStart Script". The headstart.out file has the following entry:

docbaseNameOnly = myrepo
Connect to docbase myrepo.myrepo as user myuser.
Start running headstart.ebs script on docbase myrepo.myrepo
Update install owner's failed_auth_attempt attribute
Default Storage Area exists
Default File Storage Area exists
Default Default Share Area exists
Default Common Area exists
Default Event Area exists
Default Log Area exists
update location object config exists
location object dm_dba exists
auth_plugin location object exists
ldapcertdb_loc location object exists
update location object temp exists
update location object dm_ca_store_fetch_location exists
update location object convert exists
Location object fast exists
update location object nls_chartrans
Create location object check_signature.
[DM_LOCATION_E_SAVE]error: "Save of DM_LOCATION (check_signature) failed."

[DM_LOCATION_E_FILE_EXISTENCE]error: "File System file specified in DM_LOCATION (check_signature) does not exist. Operating System failed to validate existence of the file (/dbEAGLE/DCTM_Installation/DCTM/documentum/dba/dm_check_password). Operating System error was (File permission prevents read access)"

Failed to update location object check_signature

Before starting the creation of the repository, the dm_root_task script has been run with the root password, the enviroment variables DOCUMENTUM, DM_HOME and DOCUMENTUM_SHARED have been set.

Please help.

-Deepak

Find more posts tagged with

Documentum

Comments

zhou_simonq

make sure the installer can read file /dbEAGLE/DCTM_Installation/DCTM/documentum/dba/dm_check_password. This is indicated by the error message.

- simon

dinodia

Hi Simon,

Thanks for the quick response.

I checked the permissions for the file in my setup and it looks similar to what is present in another setup we have. It has permissions -rwsr-s--- .

There is another thing i observed. I was given an option to continue even after the script failed. What will be the impact in case i continue at this point in case i need to make this as the global repo. I need to ultimately perform few operations on this repo using DFS.

-Deepak.

dinodia

Can someone help me here please. This is a little urgent

zhou_simonq

pls double check according to the following errors:

[DM_LOCATION_E_SAVE]error: "Save of DM_LOCATION (check_signature) failed."

Failed to update location object check_signature

usually you can treat the first created repository as the global registry.

dinodia

Hi Simon,

Can you tell me what DM_LOCATION refers to. I dont think it is an env variable.

The file dm_check_password is present in the specified path and has the required permissions as well.

I require a clarification here. Before installing the repository when we have to run the dm_check_password script, i am prompted for user name and password. Do i have to give the root user credentials or the installation user credentials here?

-Deepak.

zhou_simonq

i'm not that familiar with the creation of repository, especially on Solaris.

if you have Documentum System Object Reference in hand, you'll know that dm_location is a type contains a file system location for a specific file or directory. The server uses this info in locations objects to find the files and directories that it needs for successful operation. i'm not sure whether you're referring the same thing.

IDQL> select * from dm_location

it seems that some paths used by Content Server are stored in table dm_location. from the error message, the row contains the path of check_signature seems to be invalid.

in my opinion, you should grant the installer the privilege.

dinodia

Hi Simon,

I will try running the dm_root_task script again.

Can you tell me what will be the impact in case i ignore the error and continue with the installation. Will this repo not be treated as the global repo?

-Deepak.

zhou_simonq

i don't know, you can have a try.

why your title of this post is "DFS..."? it has nothing to do with DFS, but Content Server

dinodia

Hi Simon,

Sorry for the Subject. Have been working a lot on DFS. Took up an installation and tired already without result.

Regarding the issue. I could execute the headstart script. The problem was in the group permissions.

I am now facing another issue with a different script now . It is with the script dm_CAS_install.ebs. Here is the log ( dm_CAS_install.out)

Connect to docbase myrepo.myrepo as user myuser.
Start running dm_CAS_install.ebs script on docbase myrepo.myrepo
method object esign_pdf exists
Location SigManifest exists
type dm_esign_template exists
Cabinet Integration exists
/Integration/Esignature folder already exist
/Integration/Esignature/Templates folder already exist
Import Default Signature Page Template
[DM_STORAGE_E_NOT_ACCESSIBLE]error: "Storage area filestore_01 is not currently
accessible. Reason: errno: 2, message: No such file or directory."

Failed to import Default Signature Page Template

Please help.

-Deepak.

zhou_simonq

sorry, i really cannot give you more advice, especially on Solaris platform. i can only conclude from the error message that some paths in the repository already exist and result in the error.

do you have access to the Content Server Installation Guide? do you need to upgrade the OS or DB according to the release notes?

is it possible to install the Content Server in a clean environment, but not reuse the current one again and again and leave some uncleaned entries in the repository?

since you can not create the repository, you cannot get dm_location objects now. i forgot this in the previous reply.

- simon

dinodia

Hi Simon,

The issue has been resolved. The problem was with the group permissions. I set the permissions right, uninstalled everything and did a fresh install. It worked.

Thanks a lot for all the help and being so patient.

-Deepak.

zhou_simonq

my pleasure.