pkgadd fails with 'unable to find user noaccess'

I used root to install on dozens of Solaris 10 x86 without issue
but this server gave me this issue.  Pkg is not corrupt as I
compared its size with another good working pkg:

# pkgadd -d ./Agent-Solaris_5.10_U7-9.0.0-5000.x86_64.pkg

The following packages are available:
  1  ss-agent     XXXXXXX Agent
                  (x86_64) 9.0.0-5000

Select package(s) you wish to process (or 'all' to process
all packages). (default: all) [?,??,q]: all

Processing package instance <ss-agent> from </var/tmp/Agent-Solaris_5.10_U7-9.0.

XXXXXXX (x86_64) 9.0.0-5000
Copyright (c) 2004-2012 xxxxx Inc.
All rights reserved.
## Executing checkinstall script.
unable to find user <noaccess>.
pkgadd: ERROR: checkinstall script did not complete successfully

Installation of <ss-agent> failed.
No changes were made to the system.
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

You must have "noaccess" user on a solaris system
usually it is uid 60002 and gid 60002 on fresh solaris install.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
sunhuxAuthor Commented:
I did compare other Solaris servers (of the same version) that I have in our
environment: they don't have noaccess nor any user with uid 60002 in
/etc/passwd but installation went through for them (at least 300+ of them).

It's just this one VM that's odd
sunhuxAuthor Commented:
Or could it be checkinstall script was 'tampered' with?
Got to check it out in 2 days' time as I'm on medical leave
Must be some hardening script
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Unix OS

From novice to tech pro — start learning today.