[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference iosg::all-in-1_v30

Title:*OLD* ALL-IN-1 (tm) Support Conference
Notice:Closed - See Note 4331.l to move to IOSG::ALL-IN-1
Moderator:IOSG::PYE
Created:Thu Jan 30 1992
Last Modified:Tue Jan 23 1996
Last Successful Update:Fri Jun 06 1997
Number of topics:4343
Total number of notes:18308

24.0. "Version 3 IVP problems" by TIMMII::RDAVIES (An expert Amateur) Mon Feb 17 1992 09:45

    I have found two 'bugs' with the IVP's.
    
    =======================================================================
    The first only occurs if you have come to V3.0 via early FT versions
    (pre BL90) where the default drawer was originally called MAIL.
    
    Then the IVP IEM (Check electronic mail) fails as it's looking for a
    drawer [IVP]MAIN, but the drawer was created as [IVP]MAIL. 
    
    This is further compounded by the error message actually referring to
    the old name:
    
    ![MESS]   Message: Running electronic mail check
    !"Running electronic mail check"
    !"This account does not have a MAIL drawer in the partition data file."
    !"Did the seeding of the partition data file fail?  Please investigate."
    !"Electronic mail check has FAILED."
    ![MESS]   Message: Electronic mail check has FAILED.
    
    It is in fact looking for MAIN!.
    
    This can be corrected by SM MFC MD, noting the drawer details of
    [IVP]MAIL, and REM(oving) drawer from partition (It doesn't delete
    it).
    
    Then go to SM MFC MP and ADD the drawer back in, naming it [IVP]MAIN
    making sure it's owned by user IVP.
    
    =======================================================================
    
    The second is If the IVP CREATE USERS is run, and fails, then
    subsequent runs will continue to fail (irrespective of fixing the
    original problem) as it tries to start the queue OA$IVP_BATCH, which
    has already been started from the previous run and hadn't been stopped
    and deleted.
    
    !%IVP-I-IAC,  Running create account check
    !%IVP-E-IAC,  Failed to start the OA$IVP_BATCH queue. Please investigate
    !%IVP-I-IAC,  Create account check has FAILED
    
    The problem is:
               SEND_JBC START_QUEUE/QUEUE=sys$oa$mua_queue
                .IF NOT OA$STATUS THEN .GOTO start_queue_fail
    
    This will return a bad status if the queue is already running.
    
    The work around is to make sure the queue OA$IVP_BATCH is stopped
    before running the IVP's IAC or ALL are run. 
    
    
    =======================================================================
    
    Richard
T.RTitleUserPersonal
Name
DateLines
24.1IAC IVP leaves OA$IVP_BATCHAIMTEC::BURGESS_SMon Feb 17 1992 15:5010
    
    
    Richard,
    
    We found the problem with the IVP IAC leaving the OA$IVP_BATCH queue on
    the system at a customer site. I QAR'd this last week.
    
    thanks,
    Sam Burgess
    
24.2THR-15861 is the numberAIMTEC::WICKS_AVote Bill'n'Opus for a weirder USAMon Feb 17 1992 16:271
    
24.3Submission clash!TIMMII::RDAVIESAn expert AmateurMon Feb 17 1992 17:146
>>    <<< Note 24.2 by AIMTEC::WICKS_A "Vote Bill'n'Opus for a weirder USA" >>>
>>                          -< THR-15861 is the number >-

    My number's bigger than yours so there.... THR-15870

    Richard
24.4Problem occurred on fresh install, tooBLSEYE::MANNONTue Feb 25 1992 02:03241
Tomorrow, I will be printing out the documentation so that I can see the 
correct procedure for creating drawers.  However, I would think that the
install procedure would create a default drawer that works for the ALL-IN-1
Manager account.

I cannot create a drawer.  The IVP could not, either.  Note 24 indicated
that this problem occurs  "... if you have come to V3.0 via early FT versions
(pre BL90) where the default drawer was originally called MAIL."  However,
I did a fresh install (no previous version or FT).  Nevertheless, I tried the
correction stated in Note 24.0.  This did not fix my problem.

For those interested in this problem and/or those who can help me, the details
are below.
-----------                          

I just installed VMS v5.5, Message Router v3.2, and ALL-IN-1 v3.0 on a MicroVAX
3100, this last week.  I  obtained a new PAK (the old internal one does not
work, as reported elsewhere in this conference) and executed the
Pre-installation system and account checks (PC) option.  

PC pointed out that I didn't have DNS$RTL.EXE installed.  And the 
installation guide indicated that I needed to have DNS$SHR.EXE installed, 
as well.  I installed DNS$RTL.EXE but could not find the former anywhere 
on my system disk. (What are these used for, anyway?  Digital Naming Service?)

I did install DNS$RTL.EXE and updated MODPARAMS.DAT and ran AUTOGEN from
SAVPARAMS through REBOOT.  I did not read the AGEN$PARAMS.REPORT to see 
that I had mispelled RMS_DFMBFIDX so the subsequent install executed with 
RMS_DFMBFIDX = 0.

After the reboot I double-checked my changes (still missed the RMS_DFMBFIDX 
mistake, though).  I started the A1V30 install.

After 2-1/2 hours of installing A1030.B, I aborted the install and started
over.  (I remembered that my FTSV COPY resulted in several checkpoints).  I
SUSPENDed the install process and FTSV COPYed saveset .B over again, purging
the previous .B.  Then I RESUMEd the install process and saveset .B installed
just fine. 

When the install proceeded to the ALL-IN-1 link stage, I receive a
%LINK-I-DATMISMCH error (see below) but other than that I did not see any
other error messages -- until the IVPs executed.

Below is a very cut down version of the installation log.  If somebody 
can, I would appreciate the help in solving the drawer creation problem.  
Thanks.  --Bruce


.
.
.

%A1-I-CHKSWPR, Checking MANDATORY and OPTIONAL software prerequisites

%A1-I-CHKVMSV, Checking VAX/VMS version
%A1-I-CHKMROV, Checking Message Router version

%A1-I-DDIF, Checking CDA support software prerequisites
%A1-I-DDIF, No missing CDA support software prerequisites

%A1-I-GPC, Checking Group Conferencing support software prerequisites
%A1-I-GPCVEROK, Your NOTES version is V2.2
%A1-I-CHKLIBS, Checking required shareable libraries
%A1-I-CHKPARA, Checking system parameters
%A1-I-CHKQUOT, Checking process quotas for the current process
%A1-I-CHKIDNT, Checking for ALL-IN-1 general identifiers
%A1-I-EXISTID, Identifier OA$ADMIN already exists in the RIGHTS database

* Do you want to use the existing OAFC$SERVER account [YES]? 
%A1-I-UPDACC, Account OAFC$SERVER will be used from the previous installation
%A1-I-CHKSLOGS, Checking specific logical conflicts
%A1-I-CHKGLOGS, Checking OA$* logical conflicts

    The installation will continue.
 
.
.
.

%A1LUS-I-CHKFMSV, Checking VAX/FMS version
%A1LUS-I-CHKLIBS, Checking required language dependent shareable libraries

%A1LUS-I-CHKDISK, Checking DISK SPACE

.
.
.
    NO missing DISK SPACE prerequisites discovered.

    All software checks have been successful.

    The installation will continue.
.
.
.
 
%A1CUS-I-KITREVS, The following items will be installed:

%A1CUS-I-BASEREV, ALL-IN-1 BASE kit			- Revision PBL122D
%A1CUS-I-CTRYREV, ALL-IN-1 US MARKET kit		- Revision PBL122D
%A1CUS-I-LANGREV, ALL-IN-1 ENGLISH LANGUAGE kit		- Revision PBL122D

%A1CUS-I-ASKDONE, All questions have now been completed.
%A1CUS-I-SOMTIME, The installation will continue.  No further action required.
The installation will complete in 2 to 12 hours depending on processor type
.
.
.

%A1-I-A1LINK, Starting to link images

Building shared image modules
Shared image modules built
Linking the OA$MAIN image
Linking the Background Formatter
%LINK-I-DATMISMCH, creation date of 29-OCT-1991 17:30 in shareable image 
SYS$COMMON:[SYSLIB]SMBSRVSHR.EXE; differs from date of 12-OCT-1991 04:42 
in shareable image library SYS$COMMON:[SYSLIB]IMAGELIB.OLB;1
Linking the TM Server
Linking the OA$SUBMIT image
Linking the MAILCOUNT image
Linking the File Cabinet Server images
Linking the RSD housekeeping procedure
Linking the Impersonation Services images

%A1-I-A1LINKED, Finished linking images
.
.
.

!%IVP-I-IAC,  Running create account check
!%IVP-I-IAC,  Creating account
![MESS]   Message: 
![MESS]   Message: 
![MESS]   Message: Enter data for new record
![MESS]   Message: The account A1IVPTEST will be created - you will be notified 
!               on completion
!%IVP-I-IAC,  Batch job creating account has finished
!%IVP-I-IAC,  Checking the account
!%IVP-E-IAC,  Account creation has failed
!%IVP-E-IAC,  No Partition record exists for the default drawer
!%IVP-I-IAC,  Any components that were created will be deleted
!%IVP-I-IAC,  Deleting account
![MESS]   Message: Working...
![MESS]   Message: Account A1IVPTEST will be deleted - you will be notified on c
!               ompletion
!%IVP-I-IAC,  Finished deleting account
!%IVP-I-IAC,  Create account check has FAILED
.
.
.
![MESS]   Message: Running electronic mail check
!"Running electronic mail check"
!"This account does not have a MAIL drawer in the partition data file."
!"Did the seeding of the partition data file fail?  Please investigate."
!"Electronic mail check has FAILED."
![MESS]   Message: Electronic mail check has FAILED.
!"Electronic mail check finished."
![MESS]   Message: Electronic mail check finished.
.
.
.
!%FCS-I-IVPSTA,  Starting File Cabinet Server check
!%FCS-I-PRCNAM,  Server process name is BLSEYE$SRV73
!%FCS-I-CONFIG,  Server configuration file is OA$DATA_SHARE:BLSEYE$SERVER73.DAT
!%FCS-I-SERVDL,  Server Distribution Level is set OFF
!%FCS-I-STATUS,  File cabinet server check has PASSED


%A1IVP-W-IVPPFAIL,The IVPs for ALL-IN-1 V3.0 have failed.
%A1IVP-W-IVPPFAIL,Please investigate the IVP log file (see the System Manager's Guide).
	Installation of A1 V3.0 completed at 20:39

	VMSINSTAL procedure done at 20:40

+++++++++++

>>> Below is a shortened ALLIN1_IVP.LOG <<<


FORM  Installation Verification Procedures 

     Options: SEL,P,R,CO,ALL,IOS,IFP,IWP,ICM,IDG > ALL
ALL IVP checks running...
Starting verification of interface with VMS.

Starting verification of form library compilation.
Checksum of FLC should be (374F343A).
Test of form library compilation has passed.
IVP checksum of form library = 374F343A.
Finished verifying form library compilation.

Starting verification of CLI interface.
CLI symbol ivp_cli_status = ALL-IN-1 V3.0.
verification of CLI interface has passed.
Finished verifying CLI interface.

Verification of interface with VMS has PASSED.

Verification of interface with VMS has finished.
Running file protection check...
File Check IVP has finished.
Running editor check.
.
.
.
    Merged list checksum is 805719118
        Correct checksum is 805719118
Editor check finished.
Running message check.
Message check finished.
.
.
.
The account A1IVPTEST will be created - you will be notified on completion
FORM Delete Account Options

     Delete Mail Directory [Y]> Y

     Delete VMS account [N]> Y

     Delete shared drawers [Y]> Y
Working...
Account A1IVPTEST will be deleted - you will be notified on completion
Create account check has FAILED
Verifying Mail Directory
ALL-IN-1 Mail Directory useragent name should be OA$ATWEST$ALLIN1
The following Mail Directory useragent entries exist: 
You could not be authenticated in the mail directory
The Mail Directory useragent entry for ALL-IN-1 which matched is OA$ATWEST$ALLIN1
Mail Directory verification has PASSED.
Starting MR verification.
MR verification has PASSED.

Both tests have passed.
Finished verifing Mail Directory and MR.
There is no such drawer
Running electronic mail check
Electronic mail check has FAILED.
Electronic mail check finished.
ALL IVP checks finished

     Options: SEL,P,R,CO,ALL,IOS,IFP,IWP,ICM,IDG > EX





	IVP finished using ALL-IN-1 at 21-Feb-1992 08:37pm


    
24.5IOSG::STANDAGEOink...Oink...MoooooooooooooooooooooooooooooooooTue Feb 25 1992 13:2366
    
    
    Bruce,
    
    It looks as though your system didn't get any drawers created, and this
    will cause most of the IVPs to fall over pretty quickly.
    
    Unfortuntely, you didn't include the POSTINSTALL section of the log,
    and this is possibly the most important part. During this stage, the
    File Cabinet server is created and started up, afterwhich the drawers
    on the system will be "created" (or "seeded). 
    
    The image mismatch during the link looks a little worrying, and
    could well be a reason for your problems. Hopefully the following will
    help identify what's gone wrong.
    
    First thing to do is to check and see if your server is running. My
    bets are it is not and this has caused your problems.
    
    Enter ALL-IN-1 as the manager and go to SM MFC MS - the context block
    will reflect the status of the server. It should be RUNNING/ENABLED.
    
    If this is not so, then start the server (STA) and wait a few minutes.
    Reselect the server, and check it's status. 
    
    
    a) If the server still fails to start up then check the following log
       file  - OA$LOG:OAFC$SERVER_STARTUP.LOG
    
       Now there are instances where the server will fail to start before
       it gets a chance to write a message to the log file stating what
       the problem is. An example of this is the shareable image id
       mismatch. To check this, do the following from the Managers account:
    
       $ FCS := "$SYS$SYSTEM:OAFC$SERVER.EXE"
       $ FCS OA$DATA_SHARE:<nodename>$SERVER73.DAT
    
       This will run the server in the foreground and thus allow you to see
       a serious image activation problem.
    
       NOTE :  The P1 parameter can be replaced with whatever configuration
               file you've defined for the server via the server management
               subsystem.
    
    
    
    b) If the server starts up OK from the UI, or if you manage to sort
       out the problems from the above, then you now seed to "seed"
       the PARTITION.DAT data file.
    
       This is simply done by doing <DO OA$LIB:OAFC$PART_SEED from
       within a Manager ALL-IN-1 session. Note that the server must be
       running for this to be successful, and the log file produced
       (OA$LOG:OAFC$PART_SEED) will detail what's happened.
       By running the partition seeding, all your ALL-IN-1 users
       should then have their MAIN drawer.
       
    
    
       Hope this helps,
    
    
       Kevin.
       ~~~~~~
    
    
24.6Another Ports Poly replyAIMTEC::WICKS_AVote Bill&#039;n&#039;Opus for a weirder USATue Feb 25 1992 16:4216
    To add to what Kevin said.
    
    The SMBSRVSHR thing usually indicates the presence of the dreaded
    WPCORP on the system. Since there isn't a DIAMOND compatible version
    of this yet then if you have it please deintegrate it. Otherwise
    just deassign the logical and relink.
    
    As to the drawer seeding problem note that even though the postinstall
    doesn't tell you whether it suceeded or not you can find out what it
    really did by checking the log file OAFC$PART_SEED.LOG which is either
    in OA$LOG or [ALLIN1.MGR]
    
    Regards,
    
    Andrew.D.Wicks
                  
24.7Here is the Post-Install log ....BLSEYE::MANNONTue Feb 25 1992 21:3990
The A1$POST part of the log is at the end of this reply.

An additional piece of info - I am running DECwindows Motif for VMS v1.1.
    
<re: .5 and .6>

The server status is "Running/Enabled" and OAFC$SERVER_STARTUP.LOG shows no
errors.  

PARTITION.DAT AND PARTITION_MASTER.DAT are in [ALLIN1.DATA_SHARE].
However, OA$LOG:OAFC$PART_SEED does not exist.

I do not have WPCORP installed nor is the SMBSRVSHR logical defined.

I guess I could do <DO OA$LIB:OAFC$PART_SEED but I am still curious why I 
got the %LINK-I-DATMISMCH error, why this script was not executed.

Below is the (unedited) log.

++++++++++++++

    A1$POST -- ALL-IN-1 V3.0 AUTOMATED POST-INSTALL PROCEDURES 

    A1$POST running -- deassigning old ALL-IN-1 logicals

    A1$POST running -- running startup for ALL-IN-1


	Starting ALL-IN-1
 Installing ALL-IN-1 images
	Defining language independent logical names
	Defining ENGLISH language logical names
	Initializing the Script Symbiont queue OA$SCRIPT_ENGLISH

	Running ALL-IN-1 to define SHARED AREA logicals

%OA-I-LASTLINE, ""Defining CUSTOMIZATION MANAGEMENT logicals""
%OA-I-LASTLINE, Defining Customization Management logicals...

	Running ALL-IN-1 to check HOUSEKEEPING jobs

Checking the housekeeping schedule to see if any procedures need requeueing
	Starting the MAIL Sender
	Starting the MAIL Fetcher
	Starting OA$FCV
	Starting the File Cabinet Server

	Starting the TM SERVER
	Installing CDA images
	Starting the WPS-PLUS batch queue for background LIST and SORT jobs

 Starting OA$FORMATTER queue


 Defining ALL-IN-1 Print Forms

	ALL-IN-1 startup procedure completed

    A1$POST running -- finished running startup for ALL-IN-1

%OA-I-LASTLINE, "ALL-IN-1 running -- compiling form libraries..."
%OA-I-LASTLINE, "ALL-IN-1 running -- compiling OAFORM..."
%OA-I-LASTLINE, "ALL-IN-1 running -- compiling SITEOAFORM..."
%OA-I-LASTLINE, "ALL-IN-1 running -- compiling MEMRES..."
%OA-I-LASTLINE, "ALL-IN-1 running -- compiling SITEMEMRES..."
%OA-I-LASTLINE, "ALL-IN-1 running -- compiling OAN$FORMS..."
%OA-I-LASTLINE, "ALL-IN-1 running -- compiling SITEOAN$FORMS..."
%OA-I-LASTLINE, "ALL-IN-1 running -- compiling message symbol files..."
%OA-I-LASTLINE, "ALL-IN-1 running -- compiling TXLs"




	SYSTEM finished using ALL-IN-1 at 21-Feb-1992 18:16



    A1$POST running -- Setting protections on form libraries and TXLs
%OA-I-LASTLINE, "ALL-IN-1 running -- Merging CM$SDC records"
%OA-I-LASTLINE, Merging V3.0 CM$SDC records...
%OA-I-LASTLINE, "ALL-IN-1 running -- Adding CDA format records"




	SYSTEM finished using ALL-IN-1 at 21-Feb-1992 18:49



    A1$POST running -- setting file protections
%UAF-I-GRANTMSG, identifier OAFC$SYSMAN granted to SYSTEM
%OA-I-LASTLINE, "ALL-IN-1 running -- Starting local File Cabinet Server"
%RUN-S-PROC_ID, identification of created process is 20200373
%OA-I-LASTLINE, Server BLSEYE::"73=" has been started




	SYSTEM finished using ALL-IN-1 at 21-Feb-1992 18:50



%UAF-I-REVOKEMSG, identifier OAFC$SYSMAN revoked from SYSTEM
    A1$POST running -- Starting the Script Symbiont queues

    The installation procedure for ALL-IN-1 V3.0 has now completed

                        
24.8Hi Andy! Shame about Liverpool, but Jon's smilingIOSG::STANDAGEOink...Oink...MoooooooooooooooooooooooooooooooooTue Feb 25 1992 22:0928
    
    
    Bruce,
    
    Did you say this was a fresh installation?  These days I'm not so
    familiar with the log outputs, but it looks like that log is from
    an UPDATE installation - I say that because :
    
    1) At the beginning of A1POSTINSTALL it says "Deassigning old ALL-IN-1
       logicals, and
    
    2) There's no reference to the partition seeding taking place, which it
       wouldn't do for an update.
    
    
    If it was a fresh installation, was the system fully cleared down ok?
    I'm wondering if somewhere along the lines the installation decided it
    was an update and thus didn't run the partition seeding.
    
    If you want to get your drawers (so to speak!), then do the 
    <DO OA$LIB:OAFC$PART_SEED - and check the OA$LOG:OAFC$PART_SEED.LOG
    afterwards.
    
    
    Kevin.
    ~~~~~~
    
    
24.9Re: DATMISMCHIOSG::MARCHANTOnly parrots succeedTue Feb 25 1992 23:4613
>%LINK-I-DATMISMCH, creation date of 29-OCT-1991 17:30 in shareable image 
>SYS$COMMON:[SYSLIB]SMBSRVSHR.EXE; differs from date of 12-OCT-1991 04:42 
>in shareable image library SYS$COMMON:[SYSLIB]IMAGELIB.OLB;1

    You can "fix" this by updating IMAGELIB.OLB with SMBSRVSHR by:
        $LIBR/SHARE SYS$LIBRARY:IMAGELIB SYS$LIBRARY:SMBSRVSHR
    (assumes SYS$COMMON:[SYSLIB]SMBSRVSHR.EXE is the right image)

    Why the two are out of sync, is a question for the VMS conference
    VAXWRK::VMSNOTES (press kp7 etc.)

    Cheers,
	Paul.
24.10Re-seeding worked. IVPs successful.BLSEYE::MANNONWed Feb 26 1992 18:3625
    Andy, yes ALL-IN-1 was not upgraded from v2.4.  It took two attempts to
    install v3.0, though.  The first attempt bombed in A1030.B.  So I
    copied that saveset again and started over.  So, detecting the partial
    install from the previous attempt,  ALL-IN-1 probably went into upgrade
    mode.
    
    I had >300k of disk space on the system disk so I would think that I
    would be doing the install in safety mode.  However, the second attempt
    did *not* clean up the first attempt before proceding.  In previous
    versions, I remember anxiously waiting for a first attempt to be
    cleaned out of the scratch directory before continuing with the
    install.
    
    That did not happen this time.  The second time around I only got one
    install option -- "... no ALL-IN-1 image detected...."
    
    I did re-seed PARTITION.DAT and successfully re-ran the IVPs.  
    I think I'm ok now.  Unless you can think of any other parts of 
    the installation that did not get done (given that the drawers 
    didn't get created),  I'll sign off for now.
    
    Thank you all for your help.
    
    --Bruce
    
24.11IOSG::STANDAGEOink...Oink...MoooooooooooooooooooooooooooooooooWed Feb 26 1992 21:2811
    
    Bruce,
    
    You should be OK now (hopefully!)...let us know if you stumble across
    any problems...
    
    
    Kevin.
    ~~~~~~