| 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 |
I have been using EFT T 1.2.4 for a couple of days now and have
experienced the following errors :
When I try to register a node4 entity I will sometimes get a
MCC Routine Error
%MCC-E-DSPMMLOCFILERR , dispatch local management module file access
error during probe.
This error only occurs when trying to register a node with windows
interface. The command line command which would do the same thing
functions properly.
When I try to look at a node4 entity by double clicking on the node
I will sometimes get the following message:
Show identifier operation is not supported for node4 cgulls_ns:.cgulls
circuit *
.... line *
Again the information may be obtained without error via the command
line interface.
When I try to look at a snmp entity such as an interface by double
clicking on the interface icon I will sometimes get the following
error:
Internet communications device error %LIB-E-ACTIMAGE, error activating
image !AS.
Again the information can be obtained without error via the command
line interface.
All these errors seem to occur randomly and once they occur they keep
on reoccuring. A reboot will sometimes clear the problem for a short
period of time.However it will not always clear the problem and I
have had to reinstall the software before the problems would be
cleared.
The system I am running on is at version 5.4-3 and I have set all
sysgen parameters as required in the release notes. The process also
has the appropriate quotas set.
Are these known problems or is there some sysgen parameter which i may
have missed which would cause symptoms such as this.
Thanks for your expected replys
Harry
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 2203.1 | seeing this also | NSCRUE::KEANE | U.S. NIS Service Engineering and Delivery | Mon Jan 27 1992 22:33 | 15 |
Harry, I have seen every error you decribe but have not been able to reporduce them on any kind of a consistent basis. I also saw the "dispatch local management module file access error during probe" while trying to start the lan autotopology process. Last time this occurred I simply logged out of my ws session and logged back in and didn't see the problem. All equivelent commands work from the fcl. On one occasion after I successfully ran the command from fcl the problem went away in the impm. I'm running vms 5.4 with t1.2.4. Scott | |||||
| 2203.2 | QAR 2229 | TOOK::MINTZ | Erik Mintz, DECmcc Development | Tue Jan 28 1992 13:25 | 6 |
Entered as QAR 2229 Did this installation supercede a previous version of MCC? Is it possible that there are extra copies of the dispatch tables (perhaps in a system specific directory?) | |||||
| 2203.3 | yes it did | CGOOA::KUHNEN | Tue Jan 28 1992 13:55 | 13 | |
The original installation did supercede a previous version of MCC.
On the second installation I deleted any mcc file that I could find in
the sys$system,sys$startup,sys$library and mcc_common directories.
Are there any other places I should be looking.
If it was a file left around from before why would the product work one
time and then fail another time.
Thanks
Harry
| |||||
| 2203.4 | Try recreating the MCC dispatch tables: | TEMTY::L_GROSSMAN | Tue Jan 28 1992 15:48 | 16 | |
WARNING: This will also remove any enrollments of third party MMs. You will have to reenroll these MMs. Try recreating the dispatch tables by: @sys$startup:mcc_startup_bms ENROLL Then, rerun the IVP: @sys$test:mcc_bms_ivp This will at least let us know if MCC installed OK. NOTE: Im am looking into seeing if we can display more meaningful messages on dispatch errors. | |||||
| 2203.5 | OK so far | NSCRUE::KEANE | U.S. NIS Service Engineering and Delivery | Wed Jan 29 1992 22:16 | 9 |
I ran through the process in .4 and also followed the same steps with the elm startup and ivp. Everything looks OK. When I first finished the enrolls I started the impm and got the same "error during probe" message. Logged out of that session and started again and I haven't seen any problems so far. Thanks, Scott | |||||