unable to run sam

[Christine Hartman]

I'm getting a strange SAM error..when i try to run "sam" it then displays the following dialog box:

A SAM internal error has occurred. Check the SAM log file using the Options menu or the /usr/sam/bin/samlog_viewer command for more details on the failure. Contact an HP support representative and provide them with the contents of the log file (/var/sam/log/samlog) so that an appropriate resolution to this problem can be provided.

Here is what is in the logfile:

An infrastructural error message for [error code 80054, location ../prod4/Roseville/intermed/arch_scan.C:721] was not found in the internal error table.Location: arch_err_handler.C:256Error Code: 5000

[Denver Osborn]

Haven't seen that one before...

Are there any filesets not configured?

swlist -l fileset -a state |grep -E 'installed|corrupt|transient'

If any are in the installed state, configure them with "swconfig \*" or "swconfig fileset.name"

-denver

[Mridul Shrivastava · Accepted solution]

It may be some software issue as mentioned above if everything is ok from software part, you can try the following steps:

#cd /etc/sam
#mv reg_da.db reg_da.db.old
#mv reg_files.db reg_files.db.old
#mv reg_tm.db reg_tm.db.old
#cp -p /usr/newconfig/etc/sam/reg* /etc/sam

Then try running sam.....

[Vivekanandan Somanathan]

Hi Hartman,

This will help you.

Observation: no process is running for sam & samd.
note: process will run for samd if OS is HP-UX 11.00, but process for sam should run.

some changes in vaule against some parameters have been found

e.g: value for "nis_do" is different in rg_da.db in /etc/sam/ & /usr/newconfig/etc/sam/

Solution applied:

#cd /etc/sam
#mv reg_da.db reg_da.db.old
#mv reg_files.db reg_files.db.old
#mv reg_tm.db reg_tm.db.old

#cp -p /usr/newconfig/etc/sam/reg_da.db /etc/sam
#cp -p /usr/newconfig/etc/sam/reg_files.db /etc/sam
#cp -p /usr/newconfig/etc/sam/reg_tm.db /etc/sam

then invoke "sam" and it will run

[Christine Hartman]

thank you...all software filesets were ok...moving the reg*.db files and copying the newconfig stuff over helped resolve the problem. Thank you!

[Christine Hartman]

Closing thread

[Luis_Lopez]

Thank you all, that work for me
Chears

Luis