Downgrade to 6.5.4 fixes it.
This would be one nasty bug to let slip into this release.
anyone else seen this? or is it exposing some problem with my database (neither fixup, compact -C -D -i, or new copy/replication would correct it)
I even created a new db and added an empty library, cut and pasted the code from an existing lib to this one - boom - it won’t compile.
Subject: 6.5.5 Recompile all LotusScript gives “Non existent document” after dependancy check.
Yup… I just ran into the exact same thing myself. I was really hoping to take advantage of this related fix, too:
SPR # ICAO64DJ72
Fixed in release:
6.5.5
Product Area: Designer Technical Area: LotusScript Platform: Cross Platform
Lotus Customer Support Technote: 1179112
SPR# ICAO64DJ72 - If a user recompiled all LotusScript in a template (.ntf), then refreshed the design in a database that inherited from that template, the agents in the database (.nsf) did not get updated. With these fixes, script library routines do not keep executing beyond the time limit, and the agents do get updated.
I’ve opened a ticket with Lotus Support… we’ll see what happens.
Subject: also…
Can’t say that I’ve seen the issue with agents not updating, but the execution time limit fix would be nice. I’ve had a few agents run on for HOURS caught in a loop that would have died much sooner if they weren’t built around script libraries.
Subject: RE: 6.5.5 Recompile all LotusScript gives “Non existent document” after dependancy check.
OK - now that I know it’s not just me I’m filling a report.
hrmm… now to see if I can find anything about this stuff I see in my 6.5.5 test server console:
12/20/2005 03:14:22 PM Error writing to process file pid.nbf, terminate other a
pplications which are accessing this file
12/20/2005 03:14:22 PM A previous process with process ID 3188 (0xC74) 'C:\Lotu
s\Domino\nHTTP.EXE’ failed to terminate properly.
Subject: RE: 6.5.5 Recompile all LotusScript gives “Non existent document” after dependancy check.
Well, I filed a report, and I’ve got some feedback. I had a hunch (but hadn’t tested) that if the database had a “Database Script” defined then it would work properly, but that wasn’t it. Apparently the whole feature is just broken now:
“I have pinpointed this issue to be any databases (NSF or NTF) containing a
LotusScript Library. It does not matter if the database contains a
Database Script.”
It’s marked as a regression bug, but I’m really shocked that this got out the door – you would think that since there’s a related SPR fix in this release that somebody would have hit “Recompile All LotusScript” at some point in the testing process.
I’ll post updates as I have them.
Subject: RE: 6.5.5 Recompile all LotusScript gives “Non existent document” after dependancy check.
I just confirmed this from scratch:
It looks like this feature is completely broken in 6.5.5. Hopefully we’ll hear something from support pretty quick - I would think that whatever this is would be pretty easy to isolate (since it’s specific to the client), and maybe we’ll get a hotfix for it.
Subject: Same here!!!
Subject: RE: Same here!!!
Well we just upgraded to Notes 655 due to the multithreaded bug in 654 and now we have this stupid recompile all lotusscript bug.
Looks like we’ll have to live with 654 to recompile all lotus script.
Subject: RE: Same here!!!
Hi A Lamb,
You use this for you recompile all:
From Jens Winkelmann
JYR
Subject: 6.5.5 Recompile all LotusScript gives “Non existent document” after dependancy check.
same here. downgrade to 6.5.4 fixed it. thanks for the tip.