Client Automation Standard Practitioners Forum
cancel

7.2 Upgrade Reporting Tab not working

Highlighted
ALMGRP
Super Collector

7.2 Upgrade Reporting Tab not working

We have performed an update from 2.1 to 7.2 and the reporting tab is no longer working. We get the below message. During the upgrade process, we could not remember our ccmdb password, so we create a new user with the same access rights to perform the upgrade with. The error could be related to this, however I am not sure. Any ideas on a solution or what the ccmdb user password would be as a default

Thanks

Error - /reportingserver//results.tcl
42S02 208 {[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid object name 'dbo.nvd_destatus'.}
while executing
"$dbHandle "$query""
(object "::sql1" method "::rrs::sql::query" body line 12)
invoked from within
"$::rrs::sqlDb($sqlDsn) query $sqlStatement"
(procedure "sql" line 7)
invoked from within
"sql execute RPM "SELECT COUNT(DISTINCT nvd_zobjdev) from [config RPMPREFIX]nvd_destatus""
invoked from within
"subst $cattrtmp(html)"
(procedure "RRSDefaultHome" line 46)
invoked from within
"$attrtmp(proc) $viewparams($object) $windowparams($object) $object"
(procedure "resultStub" line 77)
invoked from within
"resultStub"
invoked from within
"catch $cmd"
2 REPLIES
Alexander Willn
Honored Contributor

Re: 7.2 Upgrade Reporting Tab not working

Indeed most likely related to that user change. RRS does create additional tables in RIM database. If you do access tables (of a different user), you need to prefix them (using user name or "dbo" for default user "sa").
However as long as you can access your SQL database using windows authentication (e.g. via SQL Studio), you are able to change password (or how have you been able to create user and grant access?).
Steve Berube
Frequent Visitor

Re: 7.2 Upgrade Reporting Tab not working

The patch manager logs should be reviewd, the nvd_destatus is a patch manager table. It is possible that the migration had an error when migrating the SQL Schema. If you still have the migration logs, can you post those?

It is also possible performing a Patch Acquisition will create the missing tables.
//Add this to "OnDomLoad" event