| Title: | DECmcc user notes file. Does not replace IPMT. |
| Notice: | Use IPMT for problems. Newsletter location in note 6187 |
| Moderator: | TAEC::BEROUD |
| Created: | Mon Aug 21 1989 |
| Last Modified: | Wed Jun 04 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 6497 |
| Total number of notes: | 27359 |
This is actually a continuation of note 3.142 (Data Collectors upgraded
to T1.2.7) but of course note 3 isn't the place for this discussion.
Thanks for the pre-update warning, Doug, it was well-placed. Unfortunately,
it didn't work for me, though I think I followed your procedure
exactly. I was running 1.2.15. I used FCL to "SHOW COLLECTOR *" into
a file (even though I only had two). Then I deregistered all my alarms
and my data-collectors. Then I upgraded to 1.2.7.
After upgrading, and before running MCC for the first time, I edited the
map files to replace 307 with 25. Then I started MCC (everything came up
okay), I enabled the sink sucessfully, and then I tried to register
a data collector with the iconic map.
I choose the toolbox, I choose the data collector icon, I enter a name in
the window, and I get a window:
------------------------------------------------------------------------------
Map Window Message: software error: an internal error has occured in the
Iconic Map PM.
------------------------------------------------------------------------------
And that's that. I can't seem to create any data collectors. I tried
in FCL the command line "register collector dcm-collector"
and I get the response:
No such entity:
Unknown Entity =
What should I do?
Sid
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 2878.1 | Looks like parse tables may be outta whack? | TOOK::MCPHERSON | Save a tree: kill an ISO working group. | Wed Apr 29 1992 14:22 | 35 |
In the words of Homer Simpson: "DOooooohhh!!"
Thanks for heeding the warning; I'm just really sorry that you hit a snag like
this. I hope we can pinpoint the problem quickly, so we can make sure noone
with a gazillion collectors has this problem...
Well, here we go with the boilerplate questions;
- Are you using VMS or Ultrix?
- FIRST: If you are using VMS, make sure you don't have any old parse
tables hanging around do a dir/date of MCC_SYSTEM:*.bpt and be sure
to check if an old one in in MCC_SPECIFIC
If that doesn't pinpoint the problem, continue:
- Are you using Local MIR or DNS with T1.2.7
- Were you using Local MIR or DNS with x1.2.15
- If you were using DNS with x1.2.15, go into DNS$CONTROL on your DNS
Server and see if you have any old collector objects still hanging
around (e.g. DNS> SHOW object dcm-collector all attributes )
- From FCL, please try the following
MCC> SHOW MCC 0 COLLECTION_AM ALL ATTR
MCC> DIR COLLECTOR *
MCC> SHOW COLLECTOR * ALL IDENT
If you would post answers to these questions back here, hopefully we can spot
the cause(s) of the problem(s) quickly. Also, if possible uses session logs or
screen captures instead of rertyping to remove the possibility of us trying to
troubleshoot typos... :-O
/regards,
doug
| |||||
| 2878.2 | That was it | SGWS::SID | Sid Gordon @ISO | Thu Apr 30 1992 04:15 | 13 |
GREAT!! Thanks for the prompt, accurate response, Doug. I'm using VMS. I checked for boilerplates, and sure enough, there was a SYS$SPECIFIC:[MCC]MCC_FDICTIONARY.BPT from March. I got rid of it, and sure enough everything works. In fact, this also solved another problem I've been having (described in note 2469) with Notification. I'm note sure what the connection is, but it *didn't* go away with the upgrade to 1.2.7; It *did* go away when I got rid of the extra boilerplate. So keep up the good work! Sid | |||||