Environment
Novell ZENworks Asset Management 3.3 - ZAM3.3
Novell ZENworks 7 Asset Management - ZAM7
Novell ZENworks TS.Census 3.2
Situation
Certain
scripts will fail to run for the Web Console when a new .war file
is applied and the Web Console will not start.
Error in PRU
message will be seen when trying to apply a Product Recogntion
Update.
Errors in
the TSC Manager Event log within the Managers \logs directory or
within the Web Console log, RTRLET.LOG, will reference not
being able to write/insert into one of the Zam
tables.
Additional Information
When the ZAM
install starts we ask the user to please enter in a user with DBO
privileges, someone other than SA. By default we give the
name of NCSystem.
Under this
user we create the database, create the two users NCSystem and
NCStartup (will talk about NCStartup in just a moment). We
also populate the database with tables, views and stored
procedures. All of which must be owned by DBO.
:
Once the
install is completed you will see two users under Security\Logins
that are associated with the ZAM database, those two users are
NCSystem and NCStartup. NCSystem has DBO privileges and
NCStartup has read-only rights to two tables; NC_LoginInfo and
NC_NetCensusInfo.
NCStartup is
a canned user used by the ZAM application. It's name
and password cannot be changed within SQL or will render the
application useless. Each of the modules, with the
exception of the collection clients, connect to the database as
NCStartup. NCStartup reads the encrypted DBO information from
one of the tables it has read-only rights to and then relogs back
on as the DBO.
Under the
ZENWorks database, Users you will now see two users; dbo and
NCStartup. dbo will have a login of NCSystem (the link from
the SQL logins to the ZENWorks database), and NCStartup which will
have a login of NCStartup.
If dbo
exists within Users with a login of sa or something other than
NCSystem (NCSystem is the dbo by default but that can be
whatever the user entered during the main
installation) then complications will arise when some of our
scripts and or the PRU's run against the database.