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 |
Hi I'm Fredrik Ahgren a sales supp in Stockholm Sweden I am trying to configure a 3100 /38 as a teamlinks server. The system has VMS 5.4-1 installed on it and I am trying to install ALL-IN-1 V3.0 US version. Everything works out fine until instal comes to: "Starting local file cabinet server" %RUN-S-PROC_ID Identific.... of created... %OAFC-E-INVAUTHENT, Invalid authentification information received by file cab server (This section comes right after instal has went thru "Merging CM$SDC records") Is there a problem with VMS or is it some kind of queue problem? After the installation finished I tried to create some accounts to test with, but this just wont work either. If i look thru the account crea log file it returns status 4 at: Creating the ALL-IN-1 shared file cabinet File Cab created with status 4 A fatal error has occurred in SM_... There is no such drawer It seems like there are some kind of truble with the drawers, if I look in MANAGERs EMC there are no drawers created. Help me with this ASAP Thanks alot in advance
T.R | Title | User | Personal Name | Date | Lines |
---|---|---|---|---|---|
429.1 | OAFC$SYSMAN? | AIMTEC::PORTER_T | Terry Porter, ALL-IN-1 Support, Atlanta CSC | Tue Apr 07 1992 20:12 | 23 |
Are you upgrading from V2.* or installing V3.0 from scratch? Either way the FCS will only accept management requests (which is what the startup is) from users with the OAFC$SYSMAN identifier. The ALL-IN-1 installation should temporaraly grant this to the VMS account doing the install, but I know that there is a problem here if you are doing an upgrade from V2.* using the ALL-IN-1 managers VMS account to do the install. Are there any messages about OAFC$SYSMAN in the installation log.? Log into the ALL-IN-1 managers VMS account, check that it has the OAFC$SYSMAN rights identifier and then see if you can start the server interactivly from the Manage Servers menu (MGT MFC MS). If that fails check the log file SYS$MANAGER:OAFC$SERVER.LOG for any error messages. If you are upgrading from V2.* then if the server failed to start then the partition seeding would not have worked so there will be no drawers. In this case after you have made sure you can start the server re-run the post installation command procedure (OA$LIB:A1$POSTIONSTALL.COM) and that should fix the problem. HTH Terry | |||||
429.2 | A1 account instead | STKHLM::KULING::Ahgren | Tjaba from Sweden | Wed Apr 08 1992 16:58 | 16 |
Hi If I look thru the inst log file I can see that it has granted OAFC$SYSMAN to system and then revoked it after.. "Starting local file cabinet server", and if I look in UAF the Ids are there so there has to bee some kind of problem here. However I did a rerun on A1$POST and .... It works, the difference was that I logged in as ALLIN1 and not SYSTEM. Thanks alot Fredrik |