[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

3635.0. "A1v30 upgrade problem" by DCOFS::DENNARD (Match bearings and Shoot) Mon Dec 06 1993 17:54

Hello All

I encountered a problem with seeding partitions for user accounts
residing on the system-disk while doing a V2.3 - V3.0.

All user's on the user-disk have no problems with seeding,they have
their Folder Main and all of their documents.

The protections,ACL's,logical name for sys$sysdevice,language field
in the Profile,quota's (no quota's enabled) all are normal.

Oa$trace does not indicate any cause for failure when the oafc_part -
_seed script is run. Their is a message on the screen stating, the
folder does not exist however. 

I enabled $Set Watch from VMS and at the point of failure,it complains
of not finding what may be a temporary file ( .0;)..

The upgrade problem began with the Post install procedures, Virtual
Memory error's.
I terminated a Telnet process that was paging it's nerdy-little heart
out, re-ran the post install and it completed the compilation's and
conversions of profiles. Still some Virtual-Memory exhaustions continued
to occur. I then did a sanity check with the CSC,increased the Virtual
pagecount. Re-converted the Profiles, seeded the partitions, and for
the user's on the system disk (except the Allin1 account), attempted
to seed them individually......No success......

Any pointer's anyone?????

						Ari...
T.RTitleUserPersonal
Name
DateLines
3635.1SYSTEM access?AIMTEC::WICKS_AWC94 Dream died when Bodin missedThu Dec 09 1993 22:5113
    BRIAN,
    
    Is this the case mentioned in the STARS article entitled
    V3.0 Partition Seeding Fails For Some Users With No Error In Logs       
    
    where basically there is no SYSTEM access to the users directories?
    
    If you already have a call open here at the CSC why not continue
    to]pursus it with the specialist involved.
    
    Regards,
    
    Andrew.D.wicks
3635.2Seeding problem fixed??DCOFS::DENNARDMatch bearings and ShootFri Dec 17 1993 06:4610
Hello,
	I found the problem and it is not the same as the No System
access article you mentioned.No offense intended to the CSC specialist
who worked with me if that is the impression you gathered.

The problem was, the users were on the system disk with the UAF device
entry (Sys$sysdevice) being different from the ALL-IN-1 Profile entry
($1$dua0).....

					Aris