I have an agent failing with the following message:
Error running agent on NoteID 561 - 1E:E2. Continuing…
I’ve never seen a NoteID in that format. Anyone know how to find it?
Subject: RE: Locate document by strange NoteID
561 is the note ID in decimal. The rest is the odd error code.
Subject: RE: Locate document by strange NoteID
561 in hex shows as 231 but I still cannot locate the doc, any other ideas?
Subject: RE: Locate document by strange NoteID
I should say probably in decimal, since I don’t know who’s generating this message. What do you mean you “cannot” locate the document? What did you do to try to find it? I use the note open function in NotesPeek, it works nicely.
Subject: RE: Locate document by strange NoteID
I tried using Open Note in notespeek using both 561 and 231 as hex and dec but always get invalid or non existent document error. in addition to the error shown in the agent log (previous post) I also get this error in the server log when the agent runs:
04/24/2008 12:11:38 PM AMgr: Agent ‘XXX’ in ‘xxx.nsf’ did not process all documents successfully. Check the Agent Log for more information: Field is too large (32K) or View’s column & selection formulas are too large
And I have 2 users who have local replicas and get the same error when replicating: Field is too large (32K) or View’s column & selection formulas are too large
so I’m leaning towards a corrupt doc causing both problems.
Subject: RE: Locate document by strange NoteID
Try a Fix up and compact with -D before you wreck your brain thinking about options.Many a times corruption can cause weird results.
If that doesnt work Add a line in yyour code to print document unique ID.
Once you get the corrupt document try saving it once manually to see whether the corruption goes away.
Subject: RE: Locate document by strange NoteID
I tried fixup already and it did nothing to resolve the issue. Adding doc ID is not going to help cuz the agent does not process the doc in question it just errors out when it hits it.
Subject: RE: Locate document by strange NoteID
The message, which is generated by core, occurs when the summary data in the note exceeds the maximum size. From inspection of the code that generates the message, I see no reason the NoteID should not be the correct id of an (otherwise) valid note – it’s the same noteID value that was used to locate the note in the first place. I admit it’s a suspiciously low value, but it is being formatted with a %lu, so it should be displaying the entire long value of the ID.
Are you sure you’re looking for the ID in the same replica that the agent was running in?
Did you think about trying to write an agent to scan all the notes in the database from a NotesNoteCollection, and see whether one throws up an error? You might get the UNID that way. I would say create a view that selects only that noteID, but who knows whether it’s a data note?
Subject: RE: Locate document by strange NoteID
I am looking in the same replica where the agent that throws the error runs. I have not done a NotesNoteCollection yet but if I do, how do I “scan” the notes? What actually am I doing to them? I cannot resave them all. Also tried creating a view to display the doc (if it’s a doc) but no dice. Can you suggest how to “scan” the notes?
Subject: RE: Locate document by strange NoteID
Invalid or nonexistent document from Notespeek leaves open the possibility that the document exists and is invalid. And it is invalid in at least one sense – it contains too much summary data. I wouldn’t have expected this to cause NotesPeek a problem, but perhaps it does.
Forget the collection. You know the note ID. Just use GetDocumentByID method to open the note. See whether you get an error. If not, iterate through the items and display them somewhere. See if there’s anything there you can’t live without. If not, change the agent to delete the bad old note.
Subject: RE: Locate document by strange NoteID
Hi Paul
Can you use the Search document form the Admin console?
Subject: RE: Locate document by strange NoteID
thx, tried that already and it returned nothing.
Subject: RE: Locate document by strange NoteID
GetDocumentByID returns nothing when using “561”, the NoteID that’s returned in the agent error. This is the code in the agent:
SELECT form = “fmReferral” & !@IsAvailable($Conflict ) & (@Length(@Text(DateofDisability)) = 22) ;
FIELD DateOfDisability := @Date(DateOfDisability)
I also tried using the same select statement in an agent to move the found docs to a folder but I get the same error and no docs are placed inthe folder. Also tried building a view using the same select statement but no docs were in it. Here’s the last output from the agent’s log:
Started running agent ‘Scheduled DOD Formula Agent’ on 04/25/2008 09:39:40 AM
Running on new or modified documents: 22 total
Found 22 document(s) that match search criteria
Error running agent on NoteID 561 - 1E:06. Continuing…
1 document(s) were modified by formula
Done running agent ‘Scheduled DOD Formula Agent’ on 04/25/2008 09:39:40 AM
On an earlier run the error was slightly different:
Error running agent on NoteID 561 - 29:4A
Subject: RE: Locate document by strange NoteID
The value 561 is decimal. GetDocumentByID expects hex.
Subject: RE: Locate document by strange NoteID
convert to hex = 231, I tried that too. Also, most NoteID’s look like 00000231 so I tried that too, still no good.
I was able to write some script to loop through all entries in a view that I built. I printed each line number until the script bombed out then just scrolled down in the the view to that line number and opened a few documents before and after until I encountered the field is too long error. Deleted the doc and all OK now. Thx for all of your comments.