What is wrong with this Out of Office agent

by Volker Weber

I have not used the OoO agent in a long time. When I tried to activate it now, I get this message in the server log:

25.06.2004 01:17:43 AMgr: Agent ('OutOfOffice|OutOfOffice' in 'mail\volkerweber.nsf') error message: Cannot find external name: TIMEGETFROMITEM

Has anybody seen this? What is the problem?

Comments

Has the flag "Prohibit design refresh..." been activated for your mail database? If yes, dsiable and let Notes refresh the mail datbase' design.

Schweppes, 2004-06-25

hey volker, let me guess, you have a 6.5.x server installed, that comes in international english, and added or replaced the templates with a language pack?

this changed the TIMEGETFROMITEM script library stuff to TIMEGETFROMITEM_de or something similar.

just a guess.. maybe you should try a glimpse into the database design, especially the scriptlibrary stuff.

enigma, 2004-06-25

TIMEGetFromItem is a sub-routine in the TIMEUtilitiesscript library, which is referenced in the Common script library. The Common library is linked-to by the out of office agent.

Well, you did ask ;o)

You could try recompiling all the script in your mail file to re-establish the various links, but the easiest way to address this is to refresh / replace the design of your database.

Ben Poole, 2004-06-25

Ask Julie :-)

Bruce Elgort, 2004-06-25

Enigma, this is an IE server (and has always been one). Ben, I replaced the design. Same thing. WTF?

Thomas, 2004-06-25

I think the last time I saw this, I had to close Notes, delete the cache file (cache.ndk?), and then restart Notes. If I remember correctly, it had to do with a refreshed design in the mail file that wasn't getting picked up in the client.

- Julian

Julian Robichaux, 2004-06-25

Still a problem?
Before a Design Refresh you could also delete the Agent in your mailfile (to be sure you get a refreshed design). I have seen agents not refreshing and the OOO gets a newer timestamp when you activate it. cache.ndk always is a good idea too. I really wish IBM would address the cache.ndk handling in a future release (e.g. periodically delete it). cache.ndk is a great concept but if the db gets corrupted the errors are really weird.
It it has been solved anyway forget my rubbish here.

Henning, 2004-06-26

The best way to solve this is to open the mail file in the designer and delete some scripts.

David Silva, 2004-07-26

Old vowe.net archive pages

I explain difficult concepts in simple ways. For free, and for money. Clue procurement and bullshit detection.

vowe

Paypal vowe