Error when importing a custom check: 'Core Services Java exception: .java unable to add check xxxx' (NETIQKB47876)

fact
NetIQ Vulnerability Manager 5.0

fact
NetIQ Vulnerability Manager 5.5

symptom
Error when importing a custom check: 'Core Services Java exception: .java unable to add check xxxx'

symptom
Error in core.log when importing a check: 'The current user is not the database or object owner of table 'dbo.Tasks'. Cannot perform SET operation.'

symptom
When using Autosync, there is a status of error on several downloaded bulletins.

symptom
Errors when running Autosync: 'error attempting to apply xxxx - new check instance not accompanied by its definition'

cause
The proper VigilEntService database roles are not enabled for the user.

fix

To correct this issue:

1. Run the SQL Enterprise Manager and select the VigilEnt database.
2. Expand the users node.
3. Select the target VigilEntService user and right-click and choose Properties.
4. Verify that the following database roles are enabled:
• public
• db_securityadmin
• db_ddladmin
• VigilEntUserAccess
5. Enable all of the previous roles, if they were not checked. 
6. Click OK and close the SQL Enterprise Manager.

For more information, contact Technical Support at www.netiq.com/support.

Formerly known as NETIQKB47876