Server Management - Systems Insight Manager
cancel
Showing results for 
Search instead for 
Did you mean: 

The drilldown tool cannot be launched

Frederic Proce
Occasional Advisor

The drilldown tool cannot be launched

Hello,

Since I upgraded my HP SIM from 5.1 to 5.2.1 I have some duplicate entries for servers in critical or major status.

The server has one entry as healthy and one entry as critical/major.

When I click on the red cross for the server entry in critical/major health status, I receive the following message :
"The drilldown tool cannot be launched. The current user is not authorized to run the tool on the particular system. Consult the HP SIM administrator".

I cannot delete these duplicate entries...

So I would like to prevent that entries from appearing in the HP SIM console.

One workaround to clean these entries is to restart the server.
But I don't want to restart the server several times a day...


12 REPLIES
sebonline
Occasional Visitor

Re: The drilldown tool cannot be launched

Hello,

I have the same problem with a SQL server and I have olso upgraded my HP SIM from 5.1 to 5.2

If you are correct this problem,can you tell me how to resolve it?

Thank
Craig Wuerzberger
Occasional Visitor

Re: The drilldown tool cannot be launched

I too am having this issue with two particular entries. Has anyone found a solution to this?

Thanks.
HRT
Advisor

Re: The drilldown tool cannot be launched

I'm having the same issues. Once I restart the SIM service, I can remove the duplicate entries, but they come back within 24 hours. Anyone have any ideas? Will updating to SP2 solve it?

Dave
HRT
Advisor

Re: The drilldown tool cannot be launched

OK, I upgraded to 5.2.2. The problem went away for a couple of days, but now is back. Anyone have any ideas?

Dave
Don Bindley!
Occasional Visitor

Re: The drilldown tool cannot be launched

Did you ever find the resolution to this?
Carlsberg
Frequent Advisor

Re: The drilldown tool cannot be launched

I've seen this aswell.
I ended up doing a clean install and went with version 5.1.

Hopefully there will be some fix from HP to this.

Abdussamat Kahruman
Occasional Visitor

Re: The drilldown tool cannot be launched

Hello,
had same problem.
Seems to be an issue when upgrading from sql2000 to sql2005. Problem with some tables.
When i deleted the databse which was converted from sql2000 to sql2005 and created a new database instead, it works fine.
No more duplicates.
Had a similar problem with database when upgrading to wmware 3.5 from 3.02 and sql2000 to sql2005. Same solution, delete the converted database and create a new one.
Of course you will loose history.
CharlieFoxtrot
Occasional Visitor

Re: The drilldown tool cannot be launched

Alright, this looks like a pretty common problem. Has anyone opened a ticket w/ HP on this or otherwise resolved this issue? I'd also like to know what can be done to fix this.
Ragarc
Occasional Advisor

Re: The drilldown tool cannot be launched

Make sure the the toolbox you are using has the System Page right under the View category.
Ragarc
Occasional Advisor

Re: The drilldown tool cannot be launched

Make sure the the toolbox you are using has the "System Page" rights under the View category.
Frederic Proce
Occasional Advisor

Re: The drilldown tool cannot be launched

I did open a ticket to HP Support.
After about 4 months of troubleshooting with them, I gave up trying to solve this problem.

They asked me to try a lot of things but nothing helped.

Last thing would be to generate debug files and send them back.
But after 1 min, the debug file weighed about 3 GB.
And as the problem occurs at random, I cannot afford to let the debug run until the problem occurs.

The only solution was to reinstall the whole solution from scratch.

That's what we will do in a near future...
HRT
Advisor

Re: The drilldown tool cannot be launched

Has anyone gone in with the SQL Server Management Studio and modified the database parameters after an upgrade? I upgraded from 5.1 to 5.2, and noticed my database was still set to SQL 2000 for compatibility. I really don't want to have to wipe the database and start over.

Dave