Opening documents crashes Notes

I have a database in which some of the documents crash all running Notes applications when they are accessed. Even using the property box on a doc in a view crashes everything. I can look at the docs in NotesPeek 1.52 and suspect the problem is to do with $FILE fields [see below]. The trouble is I can’t find a way to remove the problem fields.

I’ve tried Lotusscript to delete the text $FILE field but that locks up Notes too when it hits the problem docs. If anyone has a bright idea I’d love to hear it please. COMPACT & FIXUP make no difference and the database replicates.

This db normally works exclusively on the web but it needs some re-design. The server doesn’t crash but I don’t think any of the problem docs are shown.

(summary-item

(name "$FILE")

(value ?type Object?))

(item “$FILE”

(name "$FILE")

(type Text)

(class Text)

(flags Summary)

(length 0)

(value ""))

(item “$FILE”

(name "$FILE")

(type Object)

(class NoCompute)

(flags Sign Seal Summary)

(length 54)

(object-descriptor 

   (type File)

   (flags 0)

   (rrv 0x39a))

(file-object 

   (file-name "zebra finches.jpg")

   (host-type Unknown)

   (compression-type None)

   (attributes 0)

   (flags 0)

   (size 78919)

   (created <24/04/2002 08:49:31>)    ; 80256BA5:002AFC52

   (modified <24/04/2002 08:49:31>))    ; 80256BA5:002AFC55



(remaining-data 0A     ; 000 .

))

Subject: opening documents crashes Notes

Which version of the client are you using?When the crash occurs, does the “Red Box of Death” pop up?

Subject: RE: opening documents crashes Notes

Hi,

Have you tried using another notes client?? Does it still crash??

Matt.

Subject: RE: opening documents crashes Notes

Hi,

Try deleting the attachmnets and reattach them again. We had a similar issue.Reattaching and then running compact, fixup and updall on that database fixed the problem.

Run Compact with -c -i options

Fixup with -F

and updall with -X

Hope this helps

Padma

Subject: RE: opening documents crashes Notes

Thanks. Compact, Fixup & Updall with those options make no difference. There are probably about 80 docs affected so editing them all isn’t a nice prospect but if that’s what it takes… I’ll try compacting again afterwards.

The situation is just the same on a different client PC. Oddly I can replicate the db from server to client but copying it hangs the client (6.5.2). Again Task Manager just reports ‘Not responding’ and Notes sits there showing an hour-glass.

Subject: solution

Not ideal but it is working. I created a view of the problem documents, selection formula: SELECT ( @Attachments=1 ) & ( $File=“” )

with three columns, form name, docid and attachmentname & took an reference copy of the view from a browser.

Then edited the appropriate forms so that one (any) field had this formula in its translation event:

FIELD $FILE := @DeleteField;

@ThisValue

Next I edited all these documents on the web, to save the attachments to disk and re-submit each document. From this point on they are accessible in Notes.

Then I created a view with selection formula:

SELECT ( @Date(@Modified) = @Today )

removed the @DeleteField formula from the forms and edited each doc again to re-attach the appropriate files, using the reference view taken earlier to match them up.

I’d love to know why this works on the web but Notes client and agents fail so dramatically. It would be a lot easier to do with an agent. Lotusscript agents will cycle through a view of all the problem documents but getting a pointer or value of any field kills them and brings Notes down too.

Now to try and find what caused the problem in the first place…

Subject: RE: opening documents crashes Notes

No red box. Windows XP/SP2 task manager just reports ‘Not responding’. Client is 6.5.2 (same as server). Actually I -can- see & edit the same documents using a browser and the designer local web server. Although edited docs still crash the client.

Tried exporting the all database data to a file as XML using

Set exporter = session.CreateDXLExporter

Call exporter.SetInput(db)

Call exporter.SetOutput(stream)

but everything locks.

I will try with another client but can’t do that just now. Thanks for your suggestions.