[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

735.0. "Error occurred trying to access USERNAME calendar" by GIDDAY::BURT (Chele Burt - CSC Sydney, DTN 7355693) Thu May 21 1992 07:26

Hello again,

Customer running ALL-IN-1 V2.4 gets error, 
"ERROR OCCURRED TRYING TO ACCESS USERNAME CALENDAR"

The error has not been reported by any other users on the system, so is 
probably not due to a customization.

The error is not causing any loss of functionality, more an irritance than 
anything, but the customer "wants to know..."

Customer used to get this error when logging into her own account after 
renaming it LED to LEDB. (It was fixed by renaming her A1Cal file 
LED.A1CAL to LEDB.A1CAL and deleting LEDa1cal.)

Another user is now having the same problem (has had for several months).  Her 
account name has been changed a couple of times in the past few months and when 
ever she logs in to her ALL-IN-1 account she gets error:

	Error occurred trying to access USERNAME calendar

Deletion of .PST and recreation via FCO makes no difference...

Creation of a new Calendar file by using the FDL in OA$LIB 
(eg $CREATE/FDL=OA$LIB:CALENDAR.FDL TEST123TEST.A1CAL) made no difference

Does anyone have any suggestions...

Thanks & regards,

Chele B

T.RTitleUserPersonal
Name
DateLines
735.1that might not be the caseAIMTEC::ZANIEWSKI_DWhy would CSC specialists need training?Thu May 21 1992 14:2210
        Make sure you're creating the .A1CAL file with the proper
        username. 
        
        <PARSE_USER "username"
        <GET $PARSE_USER_NAME
        
        If that doesn't work, there is a problem with file or directory
        ownership or protections.
        
        Dave Zaniewski
735.2getting weirdGIDDAY::BURTChele Burt - CSC Sydney, DTN 7355693Fri May 22 1992 07:1420
<<        <PARSE_USER "farrelly,cg"
<<        <GET $PARSE_USER_NAME
        displays FARRELLY,C

Yet the entry on the profile is FARRELLY,CG
All users are setup with the standard surname comma initial initial.

.PST is FARRELLYC - will try deletion & recreation & seen what we get -

A1CAL IS FARRELLYCG, the .PST is now FARRELLYC, since doing the deletion of .
PST & FCO to recreate it - something is weird here (and it's not just me...)

Any further thoughts???

Thanks & regards,

Chele


735.3oddAIMTEC::ZANIEWSKI_DWhy would CSC specialists need training?Fri May 22 1992 14:138
        Hi Chele,
        
        Looks like something strange going on there.  The 
        <PARSE_USER "FARRELLY,CG" returns FARRELLYC on my systems.  The
        name of the calendar file should be FARRELLYC.A1CAL.  Creating one
        of these will resolve the problem.
        
        Dave Zaniewski