23
The db_ddladmin role runs any Data Definition Language (DDL) command in a database. HP Web
Jetadmin can use this role for the following:
• The CREATE, DROP, and ALTER commands are required when HP Web Jetadmin is upgraded to a
new version or a new Feature Pack is installed. New functionality is added in new versions so
schemas change, tables change, new tables are added, and so on.
• These rights might be required the first time a discovery is run if tables must be created. All
subsequent discoveries run without the elevated rights.
• These rights might be required the first time a firmware update is performed if tables must be
created. All subsequent firmware upgrades run without the elevated rights.
• These rights might be required the first time a data synchronization is performed if tables must
be created because no discoveries have been performed, such as on a brand new installation. All
subsequent data synchronizations run without the elevated rights.
It is possible that the db_ddladmin role is considered an elevated role and violates company policies.
If so, this role must be granted at least temporarily in these cases. Hopefully this role is not
considered elevated and can be assigned permanently. If so, DBO rights are likely permanently
removed after the installation and the HPWJA service initially creates the tables.
HP recommends granting DBO rights for the HPWJA service to completely control its own database.
However, in rare cases where company policy prohibits it, these roles and rights can allow HP Web
Jetadmin to run without DBO rights.
Troubleshooting
If HP Web Jetadmin is unable to start after attempting to connect to a new database or the original
database continues to appear on startup, use the following troubleshooting steps.
Original database appears on startup
If the original local database still appears on startup, HP Web Jetadmin might not be reading the
DatabaseSettings.config.xml file. To confirm that the file is not being read and processed, open the
file in a text editor and check the Password section. This section should take the password and
encrypt it for security purposes. If the password is still in plain text and the header claims to be
PlainTextPassword, the file is not being read. The reasons that the file is not being read include the
following:
• The filename is incorrect. The filename might have an .xml.xml or .xml.txt extension. If Windows
Explorer is set to hide known extensions, there is a strong chance that the file is named
incorrectly and it is not apparent.
• The file might be missing characters, such as the opening character, and HP Web Jetadmin does
not recognize it as being a valid file.
• The file might not have the correct rights for HP Web Jetadmin to process the file. It is imperative
that you open the existing DatabaseSettings.config.xml file and copy and paste the content as it
is displayed in this document to maintain the user rights. The file must have read/write rights for
Network Service for HP Web Jetadmin to use the file. If a new file is created instead of opening
the existing file, the new file assumes the user’s rights.