error: Cannot set user when user logs in

error: Cannot set user when user logs in

Post by Risha » Wed, 22 Jan 2003 18:28:37

I would like to give you an overview of how this particular problem
arised,so bear with me for now!!
I have had a client who installed D3 v7.2 on AIX 5.1 which i migrated
from AIX 433,the problem is when the user logs on ,the system
generates a process for the session by root,so when the user logs out
and tries to login again ,it cannot re-establish the session because
of the process which is still running and its owned by root,that is
understandable because of permissions and ownership by root and the
user,so to get that working one has to manually kill the process.
Ive managed to get that out of the way by changing the permissions of
the D3 executable in /usr/bin by removing the sticky bit on the file
which was rwsr-sr-x to rwxr-sr-x.When i did this users were able to
log on and off without a problem because the process was owned by the
user and not root anymore.

This is where im stuck and would like to know why this message appears
when the user logs in ...cannot set user !! My knowledge of D3 is
dangerous as im a AIX support consultant,the administrator of D3 does
not know what that message means because he says that this never
happened with the previous version of AIX!!

your help will be much appreciated !!



1. error 21770: the user cannot be found in the users collection

I have problems with my SQL logins (like security manager finds orphans but
dropping users, orphans or groups does not help. I think it is a mess now
and I am searching for a solution.) Now I get error 21770, but this error is
not in the books on line. I get the error when I dubble click a login in the
enterprise manager.
Any ideas?

2. Delphi4 - Oracle 8.03 connect

3. 614 error on a user database and 806 error on tempdb seen in the error log

4. How do I run my VB app as a Windows NT service?

5. User cannot be dropped because the user owns objects

6. lvarchar

7. Cannot Set Single User

8. Cannot Set SQL 6.5, SP4 master DB to Single User Mode

9. User-defined error when the user doesn't define any errors

10. BIG problem !!:fatal 1:set user id user admin is not in eg shadow

11. User Name of Logged In User through ODBC Connection

12. Calling Stored Proc as another user other than the logged in user