We have seen this issue and if you check the installation logs you will see the problem may have occured when the new database is being created. The resolution, if this is the case, is to manually create the database.
I would suggest opening a case with HP Support so that we can help you resolve the issue.
All the best
HP Support Viewed the Support tips? Search for "(NNMi) Support Tips" and order by Date to get the list The views expressed in my contributions are my own and do not necessarily reflect the views and strategy of HP If you find this or any post resolves your issue, please be sure to mark it as an accepted solution.