dm_check_password is returning "dm_check_password: Result = (245) = (DM_CHKPASS_BAD_LOGIN)"

If dm_check_password is returning "dm_check_password: Result = (245) = (DM_CHKPASS_BAD_LOGIN)" and it's permissions are ok, check the following: 

1) Check to check the permissions. They should be the following:
-rwsr-s--- 1 root dmadmins 11076 May 1 09:01 dm_check_password
2) If the permission is correct, check if the file system, which contains the Documentum software, is mounted with the nosuid option set.
You can check this for example in Solaris with the command 'mount'.
3) The correct output for the command mount should look like below.
/export/starfish6 on /dev/dsk/c0t3d0s6 read/write/setuid/largefiles on Thu Oct 10 07:09:08 2002 

If you see nosuid in the output it will ignore the sticky bit (rws) on that particular file system and the dm_check_password will not work. 

Please ask you UNIX administrator for further assistance if you need help to remount the file system using the setuid flag. 

can log in thru API on the Content Server but not through webtop or DA.

can log in thru API on the Content Server but not through webtop or DA.

checked to make sure root_task had been run, it had

checked ownership of the dm_check_password and it's cohorts and they were fine,

the mount point was mounted correctly 

dm_check_password DOES fail though with the DM_CHKPASS_BAD_LOGIN error (Result = (245)

Cause

dmadmin (installation owner account) is not being logged into directly, but being su'ed to...and without a password

Resolution

Unix admin must assign a password to the installation owner account (example:dmadmin)