[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

2478.0. "ALL-IN-1 3.0; Error occurred writing to the attendee file" by BACHUS::BHP144::Laroche (Veerle Laroche) Fri Mar 26 1993 09:32

Customer noticed following problem ;

Version = ALL-IN-1 IOS SERVER V3.0


Imagine following situation	user1
				user2
				user3


User1 creates an event in Time Management.  He invites user2 to a meeting.

User2 answers that he can attend the meeting.

User1 can read the answer without any problem.

User3 does a set owner in Time Management to user2.

User3 edits the event and answers NO to the answer if he can attend.

User1 receives the mail and when reading it, gets the error

		"error occurred writing to the attendee file"


Any ideas ?  Known 'feature' ?


Thanks,



Veerle Laroche

T.R	Title	User	Personal Name	Date	Lines
2478.1	old problems - different version	AIMTEC::BUTLER_T		`Fri Mar 26 1993 13:21`	9
	Traditionaly, errors in this area are normally due to the attendee file being sequential, a diskquota problem, and a few cases where after doing SO you where pointing to the wrong TM files (other user). See STARS on how to check the files and convert if necessary. This should help till Dave Z. takes a look. Tim
2478.3	Meeting response MAIL status NOTED	UTROP1::AKKERMAN_H	Hans Akkerman @UTO	`Fri May 28 1993 17:47`	24
	We also suffer from the situation described in .0. As far as I know this has always been a bug (also in 2.3 and 2.4). The thing with 3.0 is that the meeting-response message gets status NOTED after "Error occurred writing to the ATTENDEE file" and the new-mail-counter of the user is not updated (so shows one-too-many new mailmessages). Messages with status NOTED cannot be deleted by the user, so apart from resetting the new-mail-counter, every time we have to set the CAB$DELETE flag to "Y" manually. This happens a lot on our cluster and we're not very happy with that. I'm thinking of a little customisation which prevents the use of the EDIT option after a SET OWNER in time-management. Does anyone perhaps has a hint for such a modification ? We would also like to know if this bug will be fixed in a future release/patch. Thanks Hans Akkerman
2478.4	CLD'ed	KERNEL::SMITHERSJ	Living on the culinary edge....	`Tue Jun 01 1993 10:33`	12
	We've recently CLD'ed this problem on behalf of a very large British customer. The SO problem not only causes NOTED mail messages but also corruptions in users diaries. If you SMU in sync as is recommended as a workaround then unfortunately, this leads to other problems too. I believe your customisation would get around the problem. Hope this helps julia UK CSC