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.
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.
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.
Ask Julie :-)
Enigma, this is an IE server (and has always been one). Ben, I replaced the design. Same thing. WTF?
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
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.
The best way to solve this is to open the mail file in the designer and delete some scripts.
Post a comment
Recent comments
Ben Poole
on It has only been less than two hours at 09:44
Frank L. Quednau
on It has only been less than two hours at 09:29
Martin Hiegl
on It has only been less than two hours at 08:27
Stephan H. Wissel
on Notes.ini parameter RunFaster=1 is finally here at 05:24
Volker Weber
on It has only been less than two hours at 01:33
Thomas "Duffbert" Duff
on It has only been less than two hours at 01:26
Chris Linfoot
on Planet Lotus not picking up Christopher's feed at 21:56
Yancy Lent
on Planet Lotus not picking up Christopher's feed at 19:48
Bruce Elgort
on Robin Bloor: Why Google Chrome Will Dominate at 18:51
Mac Guidera
on Planet Lotus not picking up Christopher's feed at 16:04
Kevan Emmott
on 824 Chrome users so far today at 15:56
Chris Linfoot
on Planet Lotus not picking up Christopher's feed at 14:54
Lars Berntrop-Bos
on Planet Lotus not picking up Christopher's feed at 13:12
Andreas Braukmann
on 824 Chrome users so far today at 11:33
Nick Daisley
on Robin Bloor: Why Google Chrome Will Dominate at 10:14
Chris Linfoot
on Planet Lotus not picking up Christopher's feed at 09:42
Alper Iseri
on 824 Chrome users so far today at 09:38
Jean Pierre Wenzel
on 824 Chrome users so far today at 08:37
Jan-Piet Mens
on Robin Bloor: Why Google Chrome Will Dominate at 08:26
Benjamin Stein
on Synchronizing iPhone with ... Lotus Notes at 07:18
Greg Walrath
on Party like it's 2008 at 06:56
Andy Brunner
on Party like it's 2008 at 05:41
Michelle O'Rorke
on Synchronizing iPhone with ... Lotus Notes at 05:01
Arthur Fontaine
on Chrome in the wild at 03:26
Yancy Lent
on Planet Lotus not picking up Christopher's feed at 02:15
Click here to subscribe
