| T.R | Title | User | Personal Name
 | Date | Lines | 
|---|
| 952.1 | Has the Language changed? | FORTY2::ASH | Grahame Ash @REO | Mon Jun 29 1992 09:59 | 7 | 
|  | If you try an Index of the whole File Cabinet (EM I leave all fields blank 
ecept Status, which should be set to UNREAD) you can see if the Mail is being 
read into another folder (is it a multi-language system?)
er, no more ideas just yet!
grahame
 | 
| 952.2 | English ALL-IN-1 | ISIDRO::LOURDES | Lourdes Rebollar, EIS Spain | Mon Jun 29 1992 11:14 | 11 | 
|  |     Grahame,
    
    If I do an Index of the whole File Cabinet (with UNREAD status), I only 
    get 252 unread mails and only in the INBOX folder.
    
    It isn't a multi-language system, it is an I.S. machine (English
    ALL-IN-1).
    
    Regards,
    
    Lourdes
 | 
| 952.3 | getting desperate | FORTY2::ASH | Grahame Ash @REO | Mon Jun 29 1992 14:05 | 17 | 
|  | Er, well, it sounds as if there must be something more obvious. Can you check 
if all of ths teps involved in resading a new mail message are possible?
I'll try and think of a few:
  Can you dump the Pending File and see if there are any entries for this 
user? How many? If there are, then ALL-IN-1 is failing to create a File 
Cabinet entry for him.
  Is there no error message (tried GOLD-W?) when the user does RN?
  Can the user happily create and send his own mail messages?
  Does this user work in the same environment as other users who have no 
problem? Same node, same login environment.
  Anything else you can think of!
 | 
| 952.4 | Corrupt filecab? | IOSG::TALLETT | Arranging bits for a living... | Mon Jun 29 1992 19:56 | 19 | 
|  |     
    	Is it only INBOX that has the problem? There was a bug (fixed in
    	V3.0, no V2.4 patch available) which prevented the listing of a
    	folder if there was a corrupted document in the middle. If the
    	pointer to the body file pointed to a non-existant shared area
    	then you couldn't "get past" that document when you listed the
    	documents. This problem shows up most frequently just after
    	you have transferred a user, where the old system had shared
    	areas that weren't on the new system.
    
    	Now before you definitely accept that this is your problem, I
    	might add that it didn't usually affect the INBOX, and it usually
    	affected more than one folder, so the one you have sounds slightly
    	different.
    
    	See if you can index accross all folders and see all the folders.
    
    Regards,
    Paul
 | 
| 952.5 | The pointers were crazy | ISIDRO::LOURDES | Lourdes Rebollar, EIS Spain | Wed Jul 01 1992 09:20 | 24 | 
|  | 	Hello,
	Thanks very much for your replies.
	Now, it is O.k. The problem was with the pointers, the mails were
	there, in the inbox folder , but with the "ii" (index inbox) option
	they didn't appear. It was very estrange. 
	For solve it, we read every mails with status UNREAD, we did a total
	index because searching for UNREAD status, no documents were selected.
	We read the messages with NOTED status too. We reset user's unread
	count (RUC option). Indexing all the documents under electronic mail
	menu, the screen was stopped at the begining of the inbox folder,
	it was no possible to look for the mails in the inbox folder, but
	trying to execute the "rfd" using the "locate" key in the folder
	prompt, it was possible to find the inbox folder, then this folder was
	selected from here and since then, all the documents were located.
	Could anybody tell me any explanation?
	Thanks again and best regards,
	Lourdes
    
 | 
| 952.6 | Records are aligned differently now | WAYLND::HOWARD | Our business is computers not money | Thu Jul 02 1992 15:37 | 12 | 
|  |     Sounds like something was corrupt as .4 suggested.  Once the documents
    were refiled, the bad error was either removed or now in a different
    place relative to the documents.  You may have done an indexed lookup
    of the record which skipped over the offending record.  
    
    You might want to reorganize the file cabinet to try remove the bad
    part of the record.  You might first try ANAL/RMS on the DOCDB.DAT and
    DAF.DAT for that user and the appropriate Sdaf file.  Just because it
    isn't causing a problem now, doesn't necessarily mean the problem is
    gone.
    
    Ben
 |