[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
| 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 |
2810.0. "T1.2.7 Installation failures" by YOSMTE::SIMMONS_KE (KF0JX-Network Consultant) Tue Apr 21 1992 14:12
Greetings,
I have just installed T1.2.7 choosing DECdns as the namespace. I had
DECmcc v1.1 installed at the time. The installation failed with these errors...
DECmcc (T1.2.7)
%MCC-F-EVT_POOL_VERSKE, event pool version incompatible
%MCC-F-TRM_FAILURE, PM unable to continue
%DCL-W-SKPDAT, image data (records not beginning with "$") ignored
.
.
.
%MCC-E-INV_IN_ENTITY, software error: invalid in_entity (input entity)
parameter
%MCC-E-INV_IN_ENTITY, software error: invalid in_entity (input entity)
parameter
The following command failed.
"MANAGE/ENTERPRISE TEST MCC 0 DOMAIN_FM, TO FILE = MCCBMS$OUT.TXT"
DECmcc BMS T1.2.7 Installation Failed
%MCC-F-FAILED, fatal DECmcc error
*********************************************************
Fatal DECmcc BMS T1.2.7 event occurred during installation
*********************************************************
%VMSINSTAL-E-IVPFAIL, The IVP for MCCBMST V1.2 has failed.
When I try to access a domain that exsisted under 1.1 I get the following...
MCC> SHOW DOMAIN SAN_RAMON
Using default ALL IDENTIFIERS
entity [0] wild = class = 1 id = 0 type = 0
instance =
%MCC-E-INV_ENTITY, invalid entity structure
MCC>
Is the domain and map file information from 1.1 not compatible with T1.2.7?
Should I expect to see these errors on the installation?
Is there something I can do about these errors?
Thanks,
Kevin
| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 2810.1 | Files in specific: | TOOK::L_GROSSMAN | | Tue Apr 21 1992 14:46 | 8 |
|
Please make sure you do not have any mcc files in sys$specific:[syslib],
sys$specific:[sysexe], or mcc_specific.
If so, delete all of them, and then enter the following
$ @sys$startup:mcc_startup_bms ENROLL
|
| 2810.2 | specific it is | CAPITN::SIMMONS_KE | KF0JX-Network Consultant | Tue Apr 21 1992 15:12 | 5 |
| That was the problem. ( I discovered it just after entering this note).
Thank You. And yes it is covered in the release notes. I just forgot
that I read it.
Kevin
|