Errors after SP2 Installation

[Brent Ingler]

So, I decided to bite the bullet, and install SP2 last night. I now get the attached error, every time I try to look at the tasks page. This is regardless of which machine I'm on. I really hope there's an easy work-around to this, but I haven't tried opening up the code yet, to see if the problem's in there. Also, since it may or may not be related, there was 1 error during setup: "WARNING:Mib file copy failed for SSNMPV2-SMI
WARNING:Mib file copy failed for SSNMPV2-SMI" Thanks for any help anyone can provide.

Brent

[Jeff Mathews]

Hi Brent,

In regards to the error during setup, it looks like the MIB it was having trouble with was something you had imported manually, is that true? I don't have anything with the same name in my mib list anyway. I have heard some people have had trouble with some of the mib's they had added to IM themselves. I really don't think that would be causing your task page error message though. I haven't seen that error, nor have I heard of anyone else having it (nice luck for you hey?) On your initial look, did you have errors anywhere else? Does this look like it is complaining about a task you have setup manually?

I hope I can help....

Jeff

[Brent Ingler]

After a very brief run-through of the new installation, that is the only error that I've seen. I'll dig through it a bit deeper to see if I find anymore. Basically, the error ends up stopping the page from loading anything beyond the Control Tasks header. I do have a few custom control tasks, but I have custom polling tasks as well, which do show up. Additionally, the error that's popping up does seem to be referring to the Polling tasks, but I don't know how I could determine which one is Task 13. Thanks for your help, though.

Brent

[Jeff Mathews]

Interesting that the page isn't displaying anything beyond the Control Tasks header. By default there are 12 polling tasks, which would make your first control task number 13. I don't suppose you remember which is the first control task you created do you? Even if you do, it would be difficult to recreate it. Have you considered a re-install?

[Brent Ingler]

Yeah, I'm considering it right now. I'm rebooting after the uninstall and praying that CIM is smart enough to do a roll-back, rather than a full uninstall. Failing that, though, I'll probably try to just do a clean install of SP2, and go from there. It'd probably give me an opportunity to clean up the processes anyway.

Brent

[Jeff Mathews]

I re-checked your error message after writing that last message, and you're right about it being a polling task. I still think a re-install might be your best option at this point. Any thoughts?

[Brent Ingler]

Well, apparently the uninstall doesn't roll-back, so now I'm left with no other choice to do a re-install. Hopefully that will do it (it should) otherwise I might need to try downloading SP2 again...


HEY HP!!! Are you reading?! Let us roll-back to previous versions! Seems like it would make sense, doesn't it?


Brent

[Jeff Mathews]

Hi Brent, one other thing. Are you using MSDE or SQL as your database? I noticed during the upgrade that an entire new database is created, and all settings migrated to it. You may be able to get the rollback you want, by using the old database again.

Jeff

[Brent Ingler]

I'm using SQL, and I noticed that, too. The problem is that when you install CIM, it sees that the DB is already there, and asks if you want to replace it. Granted, I could restore a backed-up version of the DB over what CIM put in its place, but that's just too much of a hassle for me. I just did a fresh install of CIM7 SP2, and it took me all of 10 minutes to configure the way it was before, 20 if you include the discovery. So, for me, it's no big deal, but it's still annoying that there's not a roll-back ability in the (un)installer. Unfortunately, the cause of that error is going to remain elusive, but at least re-installing fixed it. Thanks, again.

Brent

[Rob Buxton]

Alas I saw this thread too late.
I had an identical issue with a different MIB.
I just did the reinstall and when prompted just selected the software only install.

This worked fine for me, not too sure why.

I didn't have to do any reconfiguration.