To Scott Shaffer , Please Help !!!

[mark_353]

Scott,
I've been helped by other members of this support site and their help has been much appreciated.

Unfortunately I still can't get the VCRM to work. IM7 does not detect the VCRM which is loaded on the same server. I have also tried loading it on other servers, with the same results.

I've reinstalled IM7 software only several times, but don't want to loose my existing DB unless absolutely necessary.

I believe a table has become corrupt somewhere.
I have logged a support call with HP case ref 1202454875, but it's very difficult to get though to a IM7 expert.

Could you help me out please.
Many Thanks

[Scott Shaffer]

Mark I checked the system and your case is being escalated as of 10/9. Expect more from HP on this soon.

But...have you checked to make sure that the IM7 server is trusted in the web-based agents? Browse into http://:2301/, log in using the administrator password (the agent password, not the system administrator) and go to the Settings->HTTP Server Options page and make sure the trust mode is right and, if you are using certificates that the IM7 server's cert is listed in the list. You might want to just import it again to be sure (the cert becomes invalid if you reinstall IM7.)

[Jadrice Toussaint]

Mark -

Let's try something else and see if that fixes your problem.

go to :\program files\hp\insight manager 7 sp2\config
on the IM7 server. Open up the file that's called globalsettings.props. Be careful, please make a backup copy of the file first before you modify it.

Scroll down until you see the line:

last_used_repository=servername <-- make sure this is pointing to your VCRM server. If it is not, stop the IM7 service. Make the modifications to point to your correct VCRM, save the file then restart the IM7 service.

Let me know if that helps.

[Scott Shaffer]

As a general rule, please don't edit those props files - there can be unexpected side-effects. This particular entry is only for convenience in the UI and won't impact that ability to connect to the desired VCRM.

[mark_353]

Scott, Jadrice,

I've checked the security settings and opened it up to allow all access. This did not help however.
I also modified the globalsettings.props file. It was pointing to ORPHAN_2 which was the alias the server once had.
This still has not resolved the problem though.
Scott, I've also not had anyone contact me from HP yet.
Do you have any more suggestions ?
Thanks

[Scott Shaffer]

Call back and as for the status on your case. They should be able to give you an ETA on contact.

[Jadrice Toussaint]

Mark -

You ned to stay on top of HP's support. They tend to take their time before they contact you.

[mark_353]

Well I got there in the end.
The Tech from HP Stephan was very helpful, but alas we had already tried most options and the only one left was a complete rebuild.

Thus I lost almost everything and had to start again. But at least it's all working again.

Thanks to all for your help.
Cheers

[Jadrice Toussaint]

Glad to hear Mark :)