[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

2610.0. "Internal error in FCR / Unable to get profile offsets" by TAKEOF::ERNI (Ursula Erni) Mon Apr 26 1993 10:23

Hi

After upgrading ALL-IN-1 from 2.4 to 3.0 I can't start File Cabinet Server.
When I try to start it from the Manager Server menu (SM MFC MS) then the FCS
process is created but disappears a few seconds later. 

When I try to start FCS interactively with
$START_SERVER == "$OAFC$SERVER"
$START_SERVER OA$DATA_SHARE:node$SERVER73.DAT node$SRV73

I get the error message:

Error: %OAFC-E-INTERR, Internal error in File Cabinet Server
Message: CsiStart; Unable to get profile offsets

PARTITION.DAT and PARTITION_MASTER.DAT are empty

The customer did upgrade ALL-IN-1 with a FDL in the SITE area. Then 
PROFILE.DAT was not converted correctly. We deleted this wrong FDL and started 
Postistallation again. Then we did not get any more error message with profile. 
And we can now edit User Accounts. The new fields are correct.

I saw a STARS article "ALL-IN-1/BRITISH 3.0 - Cannot start File Cabinet Server"

In the accounting I had a lot of status 03538042. Then I checked A1CONFIG. The 
version is 3.0!!!

Does any one know what this message mean?

C-ya Ursi
T.RTitleUserPersonal
Name		DateLines
2610.1IOSG::STANDAGEMon Apr 26 1993 10:4418
    
    
    Ursi,
    
    During the server startup, the server gets the profile layout by
    extracting the offsets of the required fields from the profile form set,  
    plus it parses the FDL file (OA$LIB:PROFIL.FDL) to get information on
    key fields and record length.
    
    
    Although I haven't seen this message before, I'd imagine for some
    reason the server cannot open PROFIL.FDL. Check the protection and
    ownership of this file as a start.
    
    
    Kevin.
2610.2Pending an FCS expert's arrival...IOSG::PYEGraham - ALL-IN-1 Sorcerer's ApprenticeMon Apr 26 1993 10:448
    You might double check there aren't any more customised PROFILE.FLs
    anywhere in the OA$LIB search order. Make sure there aren't any rogue
    PROFILE.DATs somewhere else in OA$DATA. Check that the real FDL in
    OA$LIB_SHARE has the correct record length, and that the data file has
    the *SAME* record length (Use $DIR/FULL). Check that both the .DAT and
    the .FDL have suitable protections.
    
    Graham
2610.3Snap!!IOSG::PYEGraham - ALL-IN-1 Sorcerer's ApprenticeMon Apr 26 1993 10:450
2610.4this disaster won't happen again (I hope)TAKEOF::ERNIUrsula ErniMon Apr 26 1993 11:2319
    Unfortunately I can't check this system anymore, because we went back
    to ALL-IN-1 Version 2.4. 
    
    But I am still happy with your answer in a way. 
    
    What I know, the size in the FDL was correct: 2192. I did not check the
    size in the PROFILE.DAT ($DIR/FULL). And I also don't know the
    protection of the FDL. 
    
    We did rename all rogue PROFILE.* so the error might have been happened
    eather because of the protection or of the record_size in the
    PROFILE.DAT. 
    
    After your explanations I am pretty shure the next upgrade-trial will 
    work to our full satisfaction.
    
    Thanks a lot Kevin and Graham
    
    Ursi
2610.5Seen this once...HSKPRF::TAURIAINENTue Apr 27 1993 06:217
    I saw this error once when I installed the TCP on a v2.4 machine. It
    turned out there was an old MEMRES form library hanging around
    (leftover from ALL-IN-1 v2.1 times) that did not have enough forms in
    the profile form set. ALL-IN-1 V2.4 did not use that form library but
    the File Cabinet Server tried to use it.
    
    --Matti