Failed running login shell - HELP!!!!

[Jeffrey T. Thorson]

Does anyone know why I would get this error:

3004-009 Failed running login shell.

for all users (other than root)???? The system
was fine up to yesterday and then this started.

No changes were going on (just normal system
usage [which is very light]).

Thanks in advance for any replys.

-J-

[mis_...@mis.schospital.com]

did you try to reboot system ????

In article <72unbl$cos$1...@news.eclipse.net>,

-----------== Posted via Deja News, The Discussion Network ==----------
http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own

[cyb...@my-dejanews.com]

In article <72unbl$cos$1...@news.eclipse.net>,
"Jeffrey T. Thorson" <j...@paragonsys.com> wrote:
> Does anyone know why I would get this error:
>
> 3004-009 Failed running login shell.
>
> for all users (other than root)???? The system
> was fine up to yesterday and then this started.
>
> No changes were going on (just normal system
> usage [which is very light]).
>
> Thanks in advance for any replys.
>
> -J-
>
>

Querying the mighty infoexplorer on "3004-009" reveals:

3004-009 Failed running login shell

Possible Causes · You tried to log in to a system that has a damaged
login shell. · The login shell does not exist. Procedures for Recovery
· If you can log in as the root user, use the System Management
Interface Tool (SMIT) to check the Initial PROGRAM attribute for that
particular user ID. 1. Log in to your system as the root user. 2.
Enter smit user at the command line, go to the Change / Show Characteristics
of a User option, and enter in the user ID you want to check at the User NAME
prompt. 3. On the next menu, check the Initial PROGRAM attribute to see
which login shell the user is in. For example: /bin/ksh 4. Either change the
Initial PROGRAM that the user is in to another login shell or replace the
existing login shell file from another system that has the same release level
as your system. Do this either through the network by running the ftp
command, or through a diskette by using the backup and restore commands. 5.
When you restore the file, make sure that it preserves the permission code,
the ownership, and the location of your previous file. · If you cannot log
in as the root user, then reboot your system as single user mode and change
the login shell. 1. First see "Accessing a System That Does Not Boot" ,
and perform the steps described to access a system that does not boot from
the hard disk. After completing the procedure, return here and continue with
the following steps. 2. Run the cd /bin command, then run the ls -l
command. 3. If you know what your login shell name is, rename it with the mv
command. For example: mv ksh ksh.sav 4. Create a link to another of
the login shells by using the ln command. For example: ln -s sh ksh 5.
Turn your key mode switch to the Normal position. 6. Reboot your system
login to your system as the root user and try replacing the damaged or
missing shell from another system that has the same release level as your
system, either through the network by running the ftp command or through a
diskette by using the backup and restore commands. 7. When you restore the
file, make sure that it preserves the permission code, the ownership, and the
location of your previous file.

--
Regards,
Clive