topic Re: SAM exited with error 7159 in Operating System - HP-UX

SAM exited with error 7159

Tonya Fernandez — Tue, 09 Jan 2001 18:37:18 GMT

We have a HP 735 workstation with a 4GB internal hard drive that has been installed with HP-UX 10.20. The root volume group was set up using the logical volume manager. All seem to go well with the core installation and ACE installation and HP-UX 700 Open Gl. When I attempted to use SAM to add peripherial disk and received this error "SAM exited with error 7159". I do not get the same error when I do the installation on the same type of system with an internal 1GB hard drive. The root volume consists of 1900mb and the swap space is 96mb. The rest of the drive is left unused.

Re: SAM exited with error 7159

Eileen Millen — Tue, 09 Jan 2001 18:53:19 GMT

see this posting
http://forums.itrc.hp.com/cm/PostAnswer/1,1171,0x29be854994d9d4118fef0090279cd0f9,FF.html

It answers the question for UX 11.
I searched on 7159 in the forums to find it.

Re: SAM exited with error 7159

Patrick Wallek — Tue, 09 Jan 2001 19:05:56 GMT

I think this is the link that Eileen was looking for. This should help you.

http://forums.itrc.hp.com/cm/QuestionAnswer/1,1150,0x13fb6c96588ad4118fef0090279cd0f9,00.html

Re: SAM exited with error 7159

Clemens van Everdingen — Tue, 09 Jan 2001 22:40:30 GMT

Hi,

Before doing this:
cp /usr/newconfig/etc/sam/reg* /etc/sam

Check with "swlist -l fileset -a state"
If nothing is in a installed state.

Check on the ITRC site if you have the latetst SAM/OBAM patch.

Good Luck

Re: SAM exited with error 7159

Tonya Fernandez — Wed, 10 Jan 2001 15:41:53 GMT

We had patches that were installed but not configured. Thanks for all the help. Does anyone know what would cause these patches to not be configured?

Re: SAM exited with error 7159

Cheryl Griffin — Wed, 10 Jan 2001 17:34:56 GMT

Tonya,

Look at the logs in /var/adm/sw/. You may find in the swinstall.log or swagentd.log information from when the patch was installed. Hopefully, those logs remain and you will find more information on the failure.

You may want to routinely run;
# swlist -l fileset -a state |more

If you find anything unconfigured:
# swconfig \* OR specify the fileset

If you find anything corrupt or transient, you would have to address those individuall. If a patch, maybe attempting to swremove, or you may have to use swmodify. If an app, you might have to attempt to reinstall. Again, those would be addressed on an individual basis.