| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 1239.1 | | CRONIC::LEMONS | And we thank you for your support. | Fri Jul 12 1991 15:41 | 22 |
| Groan. If don't allow the installation procedure to create a NMCCKERNEL
account, the installation fails. This isn't mentioned in the install dialogue
or the manual!!!
DECmcc TSM is enabling SERVICE on QNA-0...
After the installation use AUTHORIZE to create proxy accounts for
all the TSM users (if you have not done so already).
VMSINSTAL asks no additional questions.
The NMCCKERNEL account is not present on this system. The NMCC
database files will not install without the NMCCKERNEL account.
%VMSINSTAL-E-INSFAIL, The installation of MCCEMS V2.1 has failed.
VMSINSTAL procedure done at 12:38
|
| 1239.2 | | CRONIC::LEMONS | And we thank you for your support. | Fri Jul 12 1991 17:37 | 28 |
| And MORE failures! Are we really shipping this to customers! I've wasted most
of the day trying to install this!
tl
* Please verify the PASSWORD entered for NMCCKERNEL account:
%VMSINSTAL-I-ACCOUNT, This installation creates an ACCOUNT named NMCCKERNEL.
%UAF-E-UAEERR, invalid username, username already exists
*********************************************************
Fatal NMCC V2.3 event occurred during installation
*********************************************************
*********************************************************
Canceling DECMCC EMS V2.1
*********************************************************
%VMSINSTAL-F-CTRLY, Installation cancelled via CTRL/Y.
%VMSINSTAL-E-INSFAIL, The installation of MCCEMS V2.1 has failed.
|
| 1239.3 | need to create NMCCKERNEL account! | TOOK::SZABIET | | Fri Jul 12 1991 18:49 | 18 |
| Hi,
Essentially you got those errors because you do not have an
NMCCKERNEL account present on your system and you answered "no"
to the question about creating the NMCCKERNEL account. You *need*
to create the NMCCKERNEL account if the account does not already
exist on your system...it is the account under which the NMCC/DECnet
Monitor kernel runs.
This information *is* mentioned in the installation dialog and in the
installation guide. Simply try the NMCC/DECnet Monitor installation again,
this time answering "yes" to the question "Would you like the NMCCKERNEL
account to be created?" if the account is not present. Make sure
that you select a unique UIC for the NMCCKERNEL account.
Let me know if you encounter any additional problems.
-Lisa
|
| 1239.4 | And more . . . | CRONIC::LEMONS | And we thank you for your support. | Fri Jul 12 1991 20:17 | 46 |
| .2> This information *is* mentioned in the installation dialog and in the
.2> installation guide
Nowhere in the installation dialogue does it mention that the installation will
fail if data files are wanted and an account is not asked for. Further, why
should the installation fail if an account is requested but already exists?
Finally, the installation of EMS just failed, yet again, with:
VMSINSTAL asks no additional questions.
%SYSTEM-F-IVLOGNAM, invalid logical name
*********************************************************
Fatal NMCC V2.3 event occurred during installation
*********************************************************
*********************************************************
Canceling DECMCC EMS V2.1
*********************************************************
%VMSINSTAL-F-CTRLY, Installation cancelled via CTRL/Y.
*********************************************************
Fatal DECMCC EMS V2.1 event occurred during installation
*********************************************************
Notice the detailed error message, telling me exactly where the problem is
:(.
I'm sorry for the sarcasm, but it's been a long day, most of it spent watching
EMS V2.1 installations fail. Please bullet-proof the installation procedure
better than it is; our customers are going to hate this as much as I have.
Finally, what is this error, and what should I do about it?
Thanks,
tl
|
| 1239.5 | some more answers... | TOOK::SZABIET | | Mon Jul 15 1991 14:23 | 45 |
| Hi,
Re .0 and .1:
I believe that your installation failed because the
NMCCKERNEL account had not been created at the time that you
performed the NMCC/DECnet Monitor installation for the first time
and you opted not to create the NMCCKERNEL account. You should
install both the database files and the user interface as well as
create the NMCCKERNEL account if you are installing NMCC/DECnet
Monitor for the first time. If you do not, you run into the problems
such as the ones you describe in .0 and .1.
You are correct in that the installation procedure and the installation
guide does not *explicitly* let you know that the installation will
fail if not all these pieces are there. This should be looked into
for the next version of DECmcc EMS...
Re: .4:
You will run into this error when you have CDD/Plus installed and try
to install the NMCC/DECnet Monitor component of DECmcc EMS V2.1.
To solve the problem, type the following command *before* performing
the NMCC/DECnet Monitor component of the DECmcc EMS V2.1 installation:
$DEFINE/SYSTEM/EXEC CDD$DEFAULT CDD$TOP
The DECmcc EMS V2.1 release notes describe this problem and the
solution to it. Make sure you have read the release notes carefully
before preceding with the installation.
I also agree that some of the NMCC/DECnet Monitor error messages are
cryptic and do not give you a good indication of where the error
lies. This should be looked into for the next version of DECmcc
EMS as well.
Try the NMCC DECnet Monitor installation again following the above
steps. If you are still having errors let me know. If it appears
that your errors are specific to your system configuration we can
take this offline to solve your specific problem.
-Lisa
|
| 1239.6 | I'll give 'it a whirl! | CRONIC::LEMONS | And we thank you for your support. | Mon Jul 15 1991 17:39 | 9 |
| Lisa
Thanks very much for your suggestion - I'll give it a shot now.
Please add this suggestion re: CDD to the EMS and DECnet Monitor installation
guides. If it's already there, I missed it, and deserve a beating.
Thanks!
tl
|
| 1239.7 | Solved! | CRONIC::LEMONS | And we thank you for your support. | Mon Jul 15 1991 20:24 | 6 |
| Lisa
Yep, defining CDD$DEFAULT did the trick.
Thanks again!
tl
|
| 1239.8 | Install bombs on new installation... | KAOFS::BOIVIN | Moi, j'viens du nord! | Thu Jul 25 1991 15:49 | 74 |
| Good day,
I thought I'd done all the right things but my EMS install still fails
when creating NMCCKERNEL. This is a new install on VMS V5.4-2. I've
answered yes to create the NMCCKERNEL account (and it's a unique UIC).
Any help is appreciated,
Ed
Here's the log:
* Would you like the NMCCKERNEL account to be created [NO]? y
* UIC for Kernel account: [111,222]
*************************************************************
This installation requires the creation of the NMCCKERNEL
account. You MUST choose a password for this account.
**************************************************************
* Please press RETURN to continue:
*************************************************************
The entire installation will FAIL if you do not enter a valid
password for the NMCCKERNEL account. You will be given
3 chances to verify your password. This installation
procedure requires at least 15 characters for the
RDB$REMOTE password. Valid characters for a password are:
A through Z
a through z
0 through 9
$ (dollar sign)
_ (underscore)
As with the DCL SET PASSWORD command, your input will not
appear on the terminal. And to protect against typing errors
that are not seen when entering the password, you must enter
the password twice.
*************************************************************
* Please enter PASSWORD to be used for NMCCKERNEL account:
* Please verify the PASSWORD entered for NMCCKERNEL account:
%VMSINSTAL-I-ACCOUNT, This installation creates an ACCOUNT named
NMCCKERNEL.
%CLI-W-NULFIL, missing or invalid file specification - respecify
\:\
%VMSINSTAL-W-BADACC, Unable to CREATE/MODIFY account NMCCKERNEL.
%VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named
NMCCKERNEL.
%CLI-W-VALREQ, missing qualifier or keyword value - supply all required
values
%VMSINSTAL-W-BADACC, Unable to CREATE/MODIFY account NMCCKERNEL.
and finally the dreaded....
The NMCCKERNEL account is not present on this system. The NMCC
database files will not install without the NMCCKERNEL account.
%VMSINSTAL-E-INSFAIL, The installation of MCCEMS V2.1 has failed.
|
| 1239.9 | problems installing DECmcc-EMS V2.3 | GOOEY::ZAHARCHUK | Kathy Z. | Tue Dec 07 1993 16:57 | 191 |
| I am trying to install DECmcc-EMS V2.3. It appears to be failing
due to lack of disk space. Although, I have more than the required 156730
blocks available. I also get an error message regarding disk space
required for the AWD option whether or not the AWD option is specified:
%MCCEMS-E-INSFDISK, This kit requires at least 156730 blocks to instal.
-MCCEMS-E-INSFDISK, With the AWD option, 52201 blocks are required,
-MCCEMS-E-INSFDISK, and 156730 blocks are required on the AWD disk.
--------------------------------------------------------------------------
nalevo$$ show dev $1$DUA0
Device Device Error Volume Free Trans Mnt
Name Status Count Label Blocks Count Cnt
$1$DUA0: (GOOEY) Mounted 0 GOOEY_SYS 179619 7 9
nalevo$$
Additionally, I get an informational message regarding my TQELM quota.
In fact, it is greater than the required 128. Not sure why I'm getting that
message.
%MCCEMS-I-TQELM, TQELM quota is: 20; must be 128 or higher to run MCC
%MCCEMS-I-IVPQUOTA, Your account quotas are too low to run the DECmcc EMS
Startup and IVP
Here are my account quotas:
Maxjobs: 0 Fillm: 150 Bytlm: 65000
Maxacctjobs: 0 Shrfillm: 0 Pbytlm: 0
Maxdetach: 0 BIOlm: 75 JTquota: 1024
Prclm: 10 DIOlm: 75 WSdef: 256
Prio: 4 ASTlm: 100 WSquo: 4096
Queprio: 0 TQElm: 150 WSextent: 16384
CPU: (none) Enqlm: 2000 Pgflquo: 100000
Your help would be appreciated. This is for a CLD that was logged against
DECmcc. It was then forwarded onto Motif from DECmcc, and we're not sure
why. The first step for us is to install DECmcc.
A log of the installation is included below.
Thanks,
Kathy Zaharchuk, Motif Toolkit Quality Team
-------------------------------------------------------------------------
nalevo$$ @sys$update:vmsinstal MCCEMS023 $1$DUA0:[SYSTEM_JIMV.DECMCC]
VAX/VMS Software Product Installation Procedure V5.5-2
It is 7-DEC-1993 at 13:04.
Enter a question mark (?) at any time for help.
%VMSINSTAL-W-NOTSYSTEM, You are not logged in to the SYSTEM account.
%VMSINSTAL-W-ACTIVE, The following processes are still active:
DECW$MWM
DECW$TE_00B4
SHAUGHNESSY
_FTA4:
* Do you want to continue anyway [NO]? y
* Are you satisfied with the backup of your system disk [YES]?
The following products will be processed:
MCCEMS V2.3
Beginning installation of MCCEMS V2.3 at 13:04
%VMSINSTAL-I-RESTORE, Restoring product save set A ...
%VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP.
************************************************************
* *
* DECmcc EMS V2.3 *
* Integrated Package *
* *
* Installation Procedure *
* *
************************************************************
Product: DECMCC-EMS
Producer: DEC
Version: 2.3
Release Date: 1-JUL-1992
* Does this product have an authorization key registered and loaded? y
* Do you want to purge files replaced by this installation [YES]?
* Do you want to run the DECmcc EMS IVP after the installation [YES]?
* Do you want to install the entire EMS product set? [YES]?
%VMSINSTAL-I-RESTORE, Restoring product save set B ...
%VMSINSTAL-I-RESTORE, Restoring product save set C ...
%VMSINSTAL-I-RESTORE, Restoring product save set D ...
%VMSINSTAL-I-RESTORE, Restoring product save set E ...
%VMSINSTAL-I-RESTORE, Restoring product save set F ...
%VMSINSTAL-I-RESTORE, Restoring product save set G ...
%VMSINSTAL-I-RESTORE, Restoring product save set H ...
%VMSINSTAL-I-RESTORE, Restoring product save set I ...
Asking DECmcc BMS Questions...
NOTE
Packaged with this release is a new application called the
POLYCENTER Alarm Manager. This independently installable
application is a MOTIF based tool for the creation and
storage of alarm rule templates. These templates of alarm
rules may be applied to specific domains or entities,
providing an easy way to keep track and make use of alarms.
A set of useful network management rule templates are
supplied with the kit. This application is a prototype
and is excluded from the software warranty for this release.
If you answer yes, the following installation files will be
copied to the SYS$UPDATE directory. The kit and Install/Use
Guide are an additional 1860 blocks.
MCCALMMGR010.A - VMS install kit.
MCCALMMGR_INSTALL_USE.PS - Installation instructions
and product overview.
* Would you like a copy of the Alarm Manager kit [YES]? no
* Do you want to continue with the DECmcc installation [YES]?
WARNING
The kit to be installed contains V1.3.0 of the TCP/IP SNMP
Access Module. After you have installed this kit, you
should not reinstall V1.1 of the TCP/IP SNMP Access Module.
V1.1 is incompatible with this kit.
* Please press return to continue:
DECmcc requires a directory where the DECmcc common files
will be installed. If the logical MCC_COMMON has been
redefined, the new definition will be used as the default.
If the logical is not defined, the default is for the files
to be installed in a directory on the system disk called
SYS$COMMON:[MCC]. The installer may override the default.
The target directory for the files as it is now defined is
shown below.
Press RETURN to use the value shown or enter a new disk and
directory specification.
* Target directory for DECmcc Common files [SYS$COMMON:[MCC]]: $1$DUA0:[SYSTEM_
d
ecmcc.common_mcc]
%MCCEMS-I-TQELM, TQELM quota is: 20; must be 128 or higher to run MCC
%MCCEMS-I-IVPQUOTA, Your account quotas are too low to run the DECmcc EMS St
a
rtup and IVP
*********************************************************
The installation will determine if there are any other
problems and then abort.
*********************************************************
%MCCEMS-E-INSFDISK, This kit requires at least 156730 blocks to instal.
-MCCEMS-E-INSFDISK, With the AWD option, 52201 blocks are required,
-MCCEMS-E-INSFDISK, and 156730 blocks are required on the AWD disk.
%VMSINSTAL-E-INSFAIL, The installation of MCCEMS V2.3 has failed.
VMSINSTAL procedure done at 13:08
nalevo$$
|
| 1239.10 | A few guesses | BIKINI::KRAUSE | European NewProductEngineer for MCC | Wed Dec 08 1993 07:52 | 19 |
| > Device Device Error Volume Free Trans Mnt
> Name Status Count Label Blocks Count Cnt
> $1$DUA0: (GOOEY) Mounted 0 GOOEY_SYS 179619 7 9
Since KITINSTAL checks for available disk space _after_ restoring the
savesets you will run out of space. Add the size of the savesets to the
installation requirement to be on the safe side. Or let VMSINSTAL
restore the saveset to another disk (using AWD option).
>Additionally, I get an informational message regarding my TQELM quota.
> Queprio: 0 TQElm: 150 WSextent: 16384
Are you sure that this quota is active, i.e. did you log out and back in
after changing it? Another guess - without checking the KITINSTAL: The
installation might check the quotas for SYSTEM instead of your account.
So check the SYSTEM account for the required quota and try again.
*Robert
|
| 1239.11 | thanks | GOOEY::ZAHARCHUK | Kathy Z. | Wed Dec 08 1993 12:29 | 3 |
| Okay - thank you. I'll give that a try.
-Kathy
|
| 1239.12 | re: .9: Your system disk may be fragmented | PTPM06::TALCOTT | | Thu Dec 09 1993 12:57 | 6 |
| 179619 Free Blocks doesn't necessarily mean 179,619 *usable* free blocks. With
the large disks many machines have these days, I'll bet yours is pretty full,
and you're certainly trying to fill it up even more. I'd guess that a disk
de-frag would solve your problems.
Trace
|
| 1239.13 | update | GOOEY::ZAHARCHUK | Kathy Z. | Tue Dec 14 1993 14:19 | 13 |
| Thought I'd let you know how all this turned out. I did
finally get the product installed. It appears as though
the installation procedure always checks just the system
disk for space, even though I was specifying another non-system
disk with AWD option, pointing to a different disk for the common
MCC files, and the savesets were not on the system disk either.
Nevertheless, we had to free up as much space as possible on the
system disk (250K blocks) in order for the installation to work.
Thanks for the help.
-Kathy
|
| 1239.14 | | RACER::dave | Ahh, but fortunately, I have the key to escape reality. | Wed Dec 15 1993 12:57 | 4 |
| In the past, careful expansion of the "A" saveset and an edit
of the file that checks for the space will work, too.
See the VMS documentation on how to build install kits.
|
| 1239.15 | Install kit for DECmcc EMS | GOOEY::ZAHARCHUK | Kathy Z. | Fri Dec 17 1993 16:27 | 4 |
| Yes, I agree, that was my point exactly. I think this is
a bug in the install kit of EMS, and it should be fixed
there.
|