Skip to main content

Strange Scheduled Agent Error

Ever had one of those days?   I have this scheduled agent, that is giving me very, very strange error messages.  It runs daily, at 1:00am, on a Lotus Domino 64-bit 8.5.1FP3 server.
 
Here's the agent code:
 
@If(MarkforDeletion="Yes";@DeleteDocument;"");
SELECT @All
 
Complicated, eh? 
 
Here's the agent log:
 
Started running agent 'DeleteMarkedDocs' on 10/12/2010 01:00:33 AM
Running on new or modified documents: 17733 total
Found 17733 document(s) that match search criteria
Error running agent on NoteID 561 - Greek (8859-7)|Greek (Windows-1253)|Cyrillic (KOI8-R)|Cyrillic (8859-5).  Continuing...
Error running agent on NoteID 561 - B8:22.  Continuing...
Error running agent on NoteID 561 - Server error: Posting not allowed.  Continuing...
Error running agent on NoteID 561 - This key could not be written to your smartcard..  Continuing...
Error running agent on NoteID 561 - Server error: IsEmbeddedInsideWCT.  Continuing...
Error running agent on NoteID 561 - The service has returned a service-specific error code.
.  Continuing...
Error running agent on NoteID 561 - EE:9A.  Continuing...
Error running agent on NoteID 561 - B8:E2.  Continuing...
17725 document(s) were modified by formula
Deleted 2651 document(s)
Done running agent 'DeleteMarkedDocs' on 10/12/2010 01:01:18 AM
 
In addition to hitting up the IBM Support team, I thought I might throw it out to the community, to see if anyone has any ideas.

Comments

  1. Just a guess, but do you have any PostDocumentDelete or QueryDocumentDelete code in the global database script?

    ReplyDelete
  2. Nope, not using the global database script. Good thought though.

    ReplyDelete
  3. Hi,
    What's the Document with Noteid 561?
    Anything special with that?

    ReplyDelete
  4. I thought the same thing, although I couldn't find the document with Domino Administrator, or with NotesPeek.

    ReplyDelete
  5. I'd love to be more specific but I just can't recall which database/agent I saw this on...

    The "NoteID 561" was part of a similar set of gibberish errors I saw perhaps last week when an agent was messing up. Obviously it would be helpful to know what I did to fix it, but the fact that the same NoteID was referenced in your case is in itself a useful fact, so there you go.

    If my memory becomes unstuck I'll chime in again. Good luck!

    ReplyDelete
  6. Found it. As far as I can tell the agent ran to completion anyway, but the Agent Log is full of NoteID 561 references.

    Agent Code (triggered manually against selected documents):

    _key := "Servername/orgname" + @ReplaceSubstring(MailFile; ""; "~");
    FIELD SomeField := @DbLookup("" : ""; ""; "SomeView"; _key; 2; [FailSilent]);
    FIELD XMod := @Now;
    SELECT @All

    Agent Log:

    Too big to paste so uploaded here: http://www.box.net/shared/zq8hc2jspy

    ReplyDelete
  7. Found it. As far as I can tell the agent ran to completion anyway, but the Agent Log is full of NoteID 561 references.

    Agent Code (triggered manually against selected documents):

    _key := "Servername/orgname" + @ReplaceSubstring(MailFile; ""; "~");
    FIELD SomeField := @DbLookup("" : ""; ""; "SomeView"; _key; 2; [FailSilent]);
    FIELD XMod := @Now;
    SELECT @All

    Agent Log:

    Too big to paste so uploaded here: http://www.box.net/shared/zq8hc2jspy

    ReplyDelete
  8. I thought the same thing, although I couldn't find the document with Domino Administrator, or with NotesPeek.

    ReplyDelete
  9. Hi,
    What's the Document with Noteid 561?
    Anything special with that?

    ReplyDelete

Post a Comment

Popular posts from this blog

Error 217 - Error creating product object on Domino 64 bit

I'd like to share something with you.   An error that you'll get if you are trying to use ODBC with Domino 8.5.1 64bit. It starts out with an agent error of Error 217.  The text of the error is "Error creating product object" You can read about it here on the Notes/Domino forum . You can find the solution here as well . I guess I'm now waiting for Domino 8.5.2 for a solution for this.   It would have been nice to have had this in the release notes.  It would have help me greatly.

Fun Little Earthquake

It's 1:45pm EST in Ottawa, Ontario, Canada. We just had an earthquake.  Not strong enough to damage anything, but enough that I watched people run out of buildings. What a fun Wednesday.

Reminder: Increase the maximum available memory on your Lotus Notes client JVM today!

Yup, that's right.  Public Service Announcement time. If you haven't increased the maximum memory available to your Lotus Notes JVM yet, what are you waiting for? By default, the Notes JVM only has 256mb of memory available to it.  On a system with 4GB+ of memory, you should be easily able to increase it to 1/4 to 1/3 of the system memory and improve the end user performance. Here's how: Shut down Lotus Notes. In order to make sure that all processes are stopped, run this command:  Start -> Run Type: C:\Program Files (x86)\IBM\Lotus\Notes\nsd.exe -kill Open: C:\Program Files (x86)\IBM\Lotus\Notes\framework\rcp\deploy\ Open the "jvm.properties" file in a text editor like notepad.  You will possibly require Administrator permissions. At the beginning of the file, you will see text surrounded by a lot of pound signs ####. The first ‘property’ after the last # sign is: vmarg.Xmx=-Xmx256m Change 256m to 1024m so that the line reads: vmarg.X