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

Conference iosg::all-in-1

Title:ALL-IN-1 (tm) Support Conference
Notice:Please spell ALL-IN-1 correctly - all CAPITALS!
Moderator:IOSG::PYECE
Created:Fri Jul 01 1994
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:2716
Total number of notes:12169

2582.0. "Sender/Fetcher Access Violation on an Alpha" by KERNEL::BURDENI () Fri Mar 21 1997 14:38

    I have a customer with a bit of a problem.
    
    	He has just installed ALL-IN-1 v3.2 on an Alpha 4000 5/300 and is experiencing
    no problems except for the fact that Sender and Fetcher will not start. 
    They both fail with an access violation.
    
    He has no patches installed as yet, though I have forwarded the 3
    available patches to v3.2 (to be loaded soon).  The Operating system is
    Openvms 6.2-1H3
    
    I have tracked the problem down to the point where the Startup (fails
    in startup and manually), where the following is performed.
    
    ALLIN1/NOINIT/USER="POSTMASTER"/PASS=""/REEN
    Cmd:OA$INI_INITIALIZE
    
    Access violates at this point.
    %SYSTEM-F-ACCVIO, access violation, reason mask=00, virtual
    address=4f222220,pc=4f222220, ps=0000001b
    (I dont have an electronic copy of this info as yet).
    
    When I turn on SET WATCH/CLASS=MAJOR FILE After a page or two of
    messages where :
    DOCDB - OA$DAF_E - PENDING - MRPASSWRD - MAILSHR - SYSUAF -
    VMSMAIL_PROFILE are accessed, and then the .exe tie$messages is run, 
    and the following happens.
    
    %XQP, Thread #0, Access TIE$MESSAGES.EXE;1 (1993,1,0) Status:00000001
    %XQP, Thread #0 Deaccess (3505,18,0) Reads: 1, Writes: 0, Status: 00000001
    %SYSTEM-F-ACCVIO, access violation, reason mask=00,virtual address=4f222220
    
    I am a little stuck for things to check now. Any ideas, and what is
    TIE$MESSAGES.EXE ??
    
    All help greatfully received.
    Ivan
T.RTitleUserPersonal
Name		DateLines
2582.1MAIL2::KMAHERHay amores que son rosa y son espinasFri Mar 21 1997 15:585
    Is the customer using a Remote Message Router, or PMDF_MR in message
    router replacement mode?
    
    Kenneth
2582.2PMDFKERNEL::BURDENIFri Mar 21 1997 17:085
    He is using PMDF, or he will be using it.  It is a new installation
    with a view to go to Exchange.  There is no messaging external to the
    A1 system at the moment, though PMDF is installed and started.  (I do
    not know whether or not it is configured properly).
2582.3MAIL2::KMAHERHay amores que son rosa y son espinasFri Mar 21 1997 20:4211
    unfortunatly I don;t have my PMDF doc handy.  Obviously since message
    router does not run on alphas the sender and fetcher need to be tricked
    in to thinking it does.  This is accomplished principly by two logicals 
    mraxpshr and mrappshar
    
    Also make sure the message router mailbox password that ALL-IN-1 is
    using corresponds to that the PMDF thinks it's using.
    
    Regards
    
    Kenneth
2582.4TIE - Translated Image EnvironmentIOSG::ELLIOTTRRussell ElliottMon Mar 24 1997 13:079
    
    >> what is TIE$MESSAGES.EXE ??
    
    This is something to do with the running of a VESTed image. That is, a
    VAX image that has been translated to run as an Alpha image. TIE stands
    for (something like) "Translated Image Environment".
    
    HTH,
    Russell.
2582.5Only PMDF and thats fine.KERNEL::BURDENIMon Mar 24 1997 17:088
    I have just had a call from the customer, and he is looking for a
    solution.  Unfortunately I have none.  Apparently there is no message
    Router at all, it is only PMDF.  The suppliers of this product have
    been into the system and double checked all their configs, and all is
    OK.
    
    I can safely say I am stuck now, does anyone have any ideas ??
    Ivan
2582.6More infoKERNEL::BURDENIMon Mar 24 1997 17:5216
    DO you know if TIE$MESSAGES.EXE is part of the ALL-IN-1 configuration,
    or if it is put there by PMDF.  I am looking for a way forward on this
    problem but cannot find one.
    
    I am told by the customer that they have tried starting ALL-IN-1
    without PMDF and the problem still persists.
    
    A suggestion from a colleague is to remove the PMDF Remote messaging 
    from A1CONFIG and Relink ALL-IN-1 then see if the problem still there,
    though this is probably a last option.
    
    Thanks in advance
    Ivan.
    
    Thanks in advance
    Ivan.
2582.7Part of OpenVMSIOSG::NEWLANDRichard Newland, IOSG, REO2-F/J9Mon Mar 24 1997 18:3717
SYS$MESSAGE:TIE$MESSAGES.EXE and SYS$SHARE:TIE$SHARE are supplied with 
OpenVMS, and are not part of ALL-IN-1 or PMDF.

TIE$ images are used by Alpha images which have been created by translating
VAX images using VEST.  In ALL-IN-1 V3.2 the only translated images used by
OA$MAIN which are shipped with the kit are the WPS-PLUS shareable images
OA$WPL_ALL_TV and OA$WPL_FDP_TV.  Also, in ALL-IN-1 V3.2 these shareable
images are not activated until they are required, that is, the first
WPS-PLUS operation is performed. 

It may be useful to do an $ ANALYZE/IMAGE of the OA$MAIN image and look for
the Shareable Image List.  This will show what shareable images will be
activated when OA$MAIN is activated.  If there are any translated images
they will probably have a name ending in '_TV'. 


Richard
2582.8What is causing the error then ?KERNEL::BURDENITue Mar 25 1997 10:245
    So, if it comes with Openvms, can anyone say at what point it is being
    accessed, and what is accessed after this image.  I cannot be sure what
    is causing the problems.
    
    Ivan
2582.9IPMT Time?IOSG::BURTONIOSG - SEI CMM level 3Tue Mar 25 1997 11:329
    Ivan,
    
    	Have you tried tracking down which image is causing TIE$MESSAGES to
    be invoked, either by Analysing the OA$MAIN image as Richard suggested
    or by following the images as they are invoked using SET WATCH?
    
    	Alternatively it may be time to raise an IPMT.
    
    Martin.
2582.10Things to tryIOSG::NEWLANDRichard Newland, IOSG, REO2-F/J9Tue Mar 25 1997 14:5513
Something unusual is happening on your system because translated images are 
not normally executed when the Sender/Fetcher starts.  Do the following to 
see if these shows what images are being executed.

1.  Go to the Manage Sender/Fetcher menu (SM MM MSF), turn on tracing 
(TON), start the sender/fetcher and examine the trace file.

2.  Check if there is an OAINI.SCP file in the OAUSER directory of the 
POSTMASTER account.


Richard
2582.11SET WATCH and ANAL/IMAGE infoKERNEL::BURDENITue Mar 25 1997 15:02188
    The Shareable Image list on the customers machine is :
    
            Shareable Image List
    
                    0)  "SYS$PROXY_SHR"
                    1)  "OAFC$CLIENT_SHR"
                    2)  "OA$TMAECOMM"
                    3)  "MRAXPSHAR"
                    4)  "DECC$SHR"
                    5)  "LIBRTL"
                    6)  "FDVSHR"
                    7)  "DPML$SHR"
                    8)  "LIBOTS"
                    9)  "PAS$RTL"
                    10)  "SCRSHR"
                    11)  "SMGSHR"
                    12)  "SECURESHRP"
                    13)  "SECURESHR"
                    14)  "SYS$BASE_IMAGE"
                    15)  "SYS$PUBLIC_VECTORS"
    
            Quadword .ADDRESS Reference Fixups (relative to %X'00010000')
      
    ----------------------
    
    a SET WATCH/CLASS=MAJOR FILE and the following command gives :
    
    ALLI/USER="POSTMASTER"/PASS=""/NOINIT/REEN
    
    %XQP, Thread #0, Access MRAPPSHAR_EMUL.EXE;120 (71462,2,0) Status:
    00000001
    %XQP, Thread #0, Access FDLSHR.EXE;1 (1738,1,0) Status: 00000001
    %XQP, Thread #0, Access FORRTL_D56_TV.EXE;1 (1754,1,0) Status: 00000001
    %XQP, Thread #0, Access LIBRTL_D56_TV.EXE;1 (1790,1,0) Status: 00000001
    %XQP, Thread #0, Modify B.B;1 (71554,4,0) Status: 00000001
    %XQP, Thread #0, Lookup  (5756,1,0) Status: 00000001
    %XQP, Thread #0, Access SITEMEMRES.FLB;1 (5756,1,0) Status: 00000001
    %XQP, Thread #0, Deaccess (5756,1,0) Reads: 1, Writes: 0, Status: 00000001
    %XQP, Thread #0, Access SITEMEMRES.FLB;1 (5756,1,0) Status: 00000001
    %XQP, Thread #0, Lookup  (5901,2,0) Status: 00000001
    %XQP, Thread #0, Access MEMRES.FLB;3 (5901,2,0) Status: 00000001
    %XQP, Thread #0, Deaccess (5901,2,0) Reads: 1, Writes: 0, Status: 00000001
    %XQP, Thread #0, Access MEMRES.FLB;3 (5901,2,0) Status: 00000001
    %XQP, Thread #0, Deaccess (5756,1,0) Reads: 2, Writes: 0, Status: 00000001
    %XQP, Thread #0, Deaccess (5901,2,0) Reads: 2, Writes: 0, Status: 00000001
    %XQP, Thread #0, Lookup  (5756,1,0) Status: 00000001
    %XQP, Thread #0, Access SITEMEMRES.FLB;1 (5756,1,0) Status: 00000001
    %XQP, Thread #0, Deaccess (5756,1,0) Reads: 1, Writes: 0, Status: 00000001
    %XQP, Thread #0, Access SITEMEMRES.FLB;1 (5756,1,0) Status: 00000001
    %XQP, Thread #0, Lookup  (5901,2,0) Status: 00000001
    %XQP, Thread #0, Access MEMRES.FLB;3 (5901,2,0) Status: 00000001
    %XQP, Thread #0, Deaccess (5901,2,0) Reads: 1, Writes: 0, Status: 00000001
    %XQP, Thread #0, Access MEMRES.FLB;3 (5901,2,0) Status: 00000001
    %XQP, Thread #0, Access  (0,0,0) Status: 00000910
    %XQP, Thread #0, Access RIGHTSLIST.DAT;1 (2146,1,0) Status: 00000001
    %XQP, Thread #0, Access  (0,0,0) Status: 00000910
    %XQP, Thread #0, Lookup  (5168,1,0) Status: 00000001
    %XQP, Thread #0, Access PROFILE.DAT;1 (7792,1,0) Status: 00000001
    %XQP, Thread #0, Lookup PROFILE.DAT;1 (7792,1,0) Status: 00000001
    %XQP, Thread #0, Lookup  (5216,1,0) Status: 00000001
    %XQP, Thread #0, Access  (0,0,0) Status: 00000910
    %XQP, Thread #0, Lookup  (5217,1,0) Status: 00000001
    %XQP, Thread #0, Access  (0,0,0) Status: 00000910
    %XQP, Thread #0, Access SYSTEM.PST;1 (7769,1,0) Status: 00000001
    %XQP, Thread #0, Lookup  (5111,1,0) Status: 00000001
    %XQP, Thread #0, Lookup  (7900,1,0) Status: 00000001
    %XQP, Thread #0, Lookup  (0,0,0) Status: 00000910
    %XQP, Thread #0, Lookup  (0,0,0) Status: 00000910
    %XQP, Thread #0, Lookup  (5755,1,0) Status: 00000001
    %XQP, Thread #0, Access SITEMANAGER.FLB;1 (5755,1,0) Status: 00000001
    %XQP, Thread #0, Deaccess (5755,1,0) Reads: 1, Writes: 0, Status: 00000001
    %XQP, Thread #0, Access SITEMANAGER.FLB;1 (5755,1,0) Status: 00000001
    %XQP, Thread #0, Access  (0,0,0) Status: 00000910
    %XQP, Thread #0, Lookup  (5900,2,0) Status: 00000001
    %XQP, Thread #0, Access MANAGER.FLB;3 (5900,2,0) Status: 00000001
    %XQP, Thread #0, Deaccess (5900,2,0) Reads: 1, Writes: 0, Status: 00000001
    %XQP, Thread #0, Access MANAGER.FLB;3 (5900,2,0) Status: 00000001
    %XQP, Thread #0, Access  (0,0,0) Status: 00000910
    %XQP, Thread #0, Lookup  (8338,24,0) Status: 00000001
    %XQP, Thread #0, Access SITEOAFORM.FLB;14 (8338,24,0) Status: 00000001
    %XQP, Thread #0, Deaccess (8338,24,0) Reads: 1, Writes: 0, Status: 00000001
    %XQP, Thread #0, Access SITEOAFORM.FLB;14 (8338,24,0) Status: 00000001
    %XQP, Thread #0, Lookup  (5905,2,0) Status: 00000001
    %XQP, Thread #0, Access OAFORM.FLB;3 (5905,2,0) Status: 00000001
    %XQP, Thread #0, Deaccess (5905,2,0) Reads: 1, Writes: 0, Status: 00000001
    %XQP, Thread #0, Access OAFORM.FLB;3 (5905,2,0) Status: 00000001
    %XQP, Thread #0, Access POSTMASTE.PST;1 (6533,1,0) Status: 00000001
    %XQP, Thread #0, Access ACTITEM.DAT;1 (7855,1,0) Status: 00000001
    %XQP, Thread #0, Lookup ACTITEM.DAT;1 (7855,1,0) Status: 00000001
    %XQP, Thread #0, Lookup  (0,0,0) Status: 00000910
    %XQP, Thread #0, Lookup  (0,0,0) Status: 00000910
    %XQP, Thread #0, Lookup  (0,0,0) Status: 00000910
    %XQP, Thread #0, Lookup  (3505,18,0) Status: 00000001
    %XQP, Thread #0, Lookup  (0,0,0) Status: 00000910
    %XQP, Thread #0, Lookup  (0,0,0) Status: 00000910
    %XQP, Thread #0, Lookup  (3505,18,0) Status: 00000001
    %XQP, Thread #0, Lookup  (0,0,0) Status: 00000910
    %XQP, Thread #0, Access OAINI.SCP;2 (3505,18,0) Status: 00000001
    %XQP, Thread #0, Access  (0,0,0) Status: 00000910
    %XQP, Thread #0, Access PARTITION.DAT;1 (7559,1,0) Status: 00000001
    %XQP, Thread #0, Lookup PARTITION.DAT;1 (7559,1,0) Status: 00000001
    %XQP, Thread #0, Access FILECAB.DAT;1 (7904,1,0) Status: 00000001
    %XQP, Thread #0, Lookup FILECAB.DAT;1 (7904,1,0) Status: 00000001
    %XQP, Thread #0, Access  (0,0,0) Status: 00000910
    %XQP, Thread #0, Lookup  (7852,1,0) Status: 00000001
    %XQP, Thread #0, Access DOCDB.DAT;1 (7852,1,0) Status: 00000001
    %XQP, Thread #0, Lookup DOCDB.DAT;1 (7852,1,0) Status: 00000001
    %XQP, Thread #0, Access DAF.DAT;1 (7851,1,0) Status: 00000001
    %XQP, Thread #0, Lookup DAF.DAT;1 (7851,1,0) Status: 00000001
    %XQP, Thread #0, Lookup  (5252,1,0) Status: 00000001
    %XQP, Thread #0, Access OA$DAF_E.DAT;1 (7767,1,0) Status: 00000001
    %XQP, Thread #0, Lookup OA$DAF_E.DAT;1 (7767,1,0) Status: 00000001
    %XQP, Thread #0, Access OA$DAF_E.DAT;1 (7767,1,0) Status: 00000001
    %XQP, Thread #0, Lookup OA$DAF_E.DAT;1 (7767,1,0) Status: 00000001
    %XQP, Thread #0, Access  (0,0,0) Status: 00000910
    %XQP, Thread #0, Access  (0,0,0) Status: 00000910
    %XQP, Thread #0, Access PENDING.DAT;1 (7768,1,0) Status: 00000001
    %XQP, Thread #0, Lookup PENDING.DAT;1 (7768,1,0) Status: 00000001
    %XQP, Thread #0, Access MRPASSWRD.DAT;1 (7812,1,0) Status: 00000001
    %XQP, Thread #0, Lookup MRPASSWRD.DAT;1 (7812,1,0) Status: 00000001
    %XQP, Thread #0, Deaccess (7812,1,0) Reads: 4, Writes: 0, Status: 00000001
    %XQP, Thread #0, Access  (0,0,0) Status: 00000910
    %XQP, Thread #0, Access MAILSHR.EXE;1 (1791,1,0) Status: 00000001
    %XQP, Thread #0, Deaccess (1791,1,0) Reads: 1, Writes: 0, Status: 00000001
    %XQP, Thread #0, Access  (0,0,0) Status: 00000910
    %XQP, Thread #0, Access SYSUAF.DAT;1 (586,2,0) Status: 00000001
    %XQP, Thread #0, Lookup  (0,0,0) Status: 00000910
    %XQP, Thread #0, Lookup  (3305,1,0) Status: 00000001
    %XQP, Thread #0, Access  (0,0,0) Status: 00000910
    %XQP, Thread #0, Access VMSMAIL_PROFILE.DATA;1 (3305,1,0) Status: 00000001
    %XQP, Thread #0, Deaccess (586,2,0) Reads: 2, Writes: 0, Status:
    00000001
    %XQP, Thread #0, Deaccess (3305,1,0) Reads: 1, Writes: 0, Status: 00000001
    %XQP, Thread #0, Access TIE$MESSAGES.EXE;1 (1993,1,0) Status: 00000001
    %XQP, Thread #0, Deaccess (3505,18,0) Reads: 1, Writes: 0, Status: 00000001
    %SYSTEM-F-ACCVIO, access violation, reason mask=00, virtual 
    address=4F222220, PC
    =4F222220, PS=0000001B
    
      Improperly handled condition, image exit forced.
        Signal arguments:   Number = 00000005
                            Name   = 0000000C
                                     00010000
                                     4F222220
                                     4F222220
                                     0000001B
    
        Register dump:
        R0  = 0000000000000000  R1  = 0000000000000001  R2  = 4F45475255505F47
        R3  = 4D45204F41462441  R4  = 49414D5841565F24  R5  = 5245574152445F4C
        R6  = 4445474E4148435F  R7  = 53494424414F222C  R8  = 414F2C2259414C50
        R9  = 4D495F4C49414D24  R10 = 435F444554524F50  R11 = 24414F2C544E554F
        R12 = 000000007EE4BB58  R13 = 000000000009E7D0  R14 = 0000000000000000
        R15 = 000000007EEF9DA0  R16 = 0000000000000000  R17 = 00000000000C66CC
        R18 = 00000000000C66D0  R19 = 000000000000002F  R20 = 000000007EE4BB03
        R21 = 0000000022223122  R22 = 0000000022000000  R23 = 0000000000000154
        R24 = FFFFFFFFBE0E0005  R25 = 0000000000000001  R26 = 534D24414F222220
        R27 = 000000000005A540  R28 = FFFFFFFFFFFFFFFF  R29 = 4152445F4C49414D
        SP  = 000000007EE4BAD0  PC  = 534D24414F222220  PS  = 100000000000001B
    %XQP, Thread #0, Deaccess (5756,1,0) Reads: 2, Writes: 0, Status: 00000001
    %XQP, Thread #0, Deaccess (5755,1,0) Reads: 4, Writes: 0, Status: 00000001
    %XQP, Thread #0, Deaccess (5901,2,0) Reads: 2, Writes: 0, Status: 00000001
    %XQP, Thread #0, Deaccess (2146,1,0) Reads: 14, Writes: 0, Status: 00000001
    %XQP, Thread #0, Deaccess (7792,1,0) Reads: 4, Writes: 0, Status: 00000001
    %XQP, Thread #0, Deaccess (7769,1,0) Reads: 3, Writes: 0, Status: 00000001
    %XQP, Thread #0, Deaccess (8338,24,0) Reads: 2, Writes: 0, Status: 00000001
    %XQP, Thread #0, Deaccess (5900,2,0) Reads: 52, Writes: 0, Status: 00000001
    %XQP, Thread #0, Deaccess (5905,2,0) Reads: 2, Writes: 0, Status: 00000001
    %XQP, Thread #0, Deaccess (6533,1,0) Reads: 3, Writes: 1, Status: 00000001
    %XQP, Thread #0, Deaccess (7855,1,0) Reads: 4, Writes: 0, Status: 00000001
    %XQP, Thread #0, Deaccess (7559,1,0) Reads: 6, Writes: 0, Status: 00000001
    %XQP, Thread #0, Deaccess (7904,1,0) Reads: 7, Writes: 0, Status: 00000001
    %XQP, Thread #0, Deaccess (7852,1,0) Reads: 4, Writes: 0, Status: 00000001
    %XQP, Thread #0, Deaccess (7851,1,0) Reads: 2, Writes: 0, Status: 00000001
    %XQP, Thread #0, Deaccess (7767,1,0) Reads: 2, Writes: 0, Status: 00000001
    %XQP, Thread #0, Deaccess (7767,1,0) Reads: 2, Writes: 0, Status: 00000001
    %XQP, Thread #0, Deaccess (7768,1,0) Reads: 2, Writes: 0, Status: 00000001
    %XQP, Thread #0, Modify B.B;1 (71554,4,0) Status: 00000001 
    %XQP, Thread #0, Deaccess (71462,2,0) Reads: 8, Writes: 0, Status: 00000001
    %XQP, Thread #0, Deaccess (1738,1,0) Reads: 7, Writes: 0, Status: 00000001
    %XQP, Thread #0, Deaccess (1754,1,0) Reads: 7, Writes: 0, Status: 00000001
    %XQP, Thread #0, Deaccess (1790,1,0) Reads: 7, Writes: 0, Status: 00000001
    %XQP, Thread #0, Deaccess (1993,1,0) Reads: 3, Writes: 0, Status: 00000001
    
    I hope this gives someone a clue as to what is going on.
    It doesnt help me an awful lot.
    Ivan
2582.12FixedKERNEL::BURDENIWed Mar 26 1997 17:4218
    Well,
    
    the customer managed to fix it himself.  I think a
    previous note mentioned the OAINI.SCP file.  I do not know where this
    file was located, but it certainly was not the POSTMASTE directory. 
    
    The customer says 
    
    "Its not PMDF , its ALLIN1.
    
     Basically there is a file called OAINI.SCP which is the script
     file called when any user logs in. This file contains a script
     that reads in VMSmail. This script was obtained from DIGITAL.
     
     I have removed this script for the time being and will create
     another script that only users other than ALLIN1 use."
    
    Hope this helps someone in the future.
2582.13OAINI.SCP is by nature a customizationSHRMSG::HOWARDWhoever it takesWed Mar 26 1997 19:3617
    OAINI.SCP is a SCRIPT mode script that can be created to perform
    actions for a user.  If it were in OA$LIB, it would be processed for
    all users.  You could put in an exclusion for the POSTMASTER.  Perhaps
    the VMS account does not have a valid VMS Mail account.  Could you post
    the script?  
    
    >This script was obtained from DIGITAL.
    
    There is no standard version of this script, so the fact that someone
    from Digital wrote it doesn't make it supported.  I have seen cases
    where SCRIPT mode scripts did not work when a system was upgraded, and
    of course if the user interface changes the script will certainly
    break, since it simply invokes commands for the user.  Also, there was
    a change in some version (3.0?) which prevented users from invoking
    functions in SCRIPT mode scripts if they lacked the correct privilege.
    
    Ben
2582.14ThanksKERNEL::BURDENIThu Mar 27 1997 09:497
    Many thanks for your explanation, I was in the dark somewhat on this
    one.  No customization of any kind was reported to me, and I was a
    little  unsure of the origin of this file.
    
    I doubt if I can get a copy of the file, but if I do I will post it. 
    Thanks for the help
    Ivan.
2582.15IOSG::PYEGraham - ALL-IN-1 Sorcerer's ApprenticeWed Apr 02 1997 13:2910
    RE .11
    
    I was just about to suggest that VMSmail was involved when I saw the
    following line in the SET WATCH output:
    
    	%XQP, Thread #0, Access VMSMAIL_PROFILE.DATA;1 (3305,1,0) ....
    
    but clearly you've already spotted the problem. My guess is that the
    OAINI script is probably doing a VMSmail import function, but it would
    be nice to know.