HTTP Web Server: Lotus Notes Exception - File does not exist
This happens on one db that we wish to access over the web. It only happens on certain documents within the single view that we are using. For one Form if I edit the document then save it, I can then view it on the web. For another Form type, even editing the documents and saving leaves me unable to view on the web.
I’ve used the ‘http debug session on’ with the http task, but no further information is revealed as to what is causing the error.
I can copy the UNID from the browser URL and paste it into the admin client and do a find using the UNID - this works, so the ‘document’ exists.
Subject: HTTP Web Server: Lotus Notes Exception - File does not exist
what is your URL? the presentation of a document within a browser relies on both the view and the document. Is it possible that you are accessing a view that does not contain the document?
The View exists in the db, the two UNIDs exist in the db and in the view as I can see them in the view using a Notes client and find them using the Admin Client.
There are dblookups in some of the Forms that do work. The same dblookups are in some Forms that don’t work and some of the Forms that don’t work do not contain dblookups.
How are we expected to debug this kind of problem?
Subject: HTTP Web Server: Lotus Notes Exception - File does not exist
That error usually means that there’s an entire database that the Domino can’t find. Check your field formulae. I suspect you’ve got some lookups on there to another database that are not working correctly.
Subject: RE: HTTP Web Server: Lotus Notes Exception - File does not exist
Thanks very much for this solution. I had a similar prob and looking at one fields’ lookups fixed it. It was very strange behaviour, though as we’ve migrated all our dbs to two new servers in a cluster and everythings been hunky dorey since then. No probs with links on all our many dbs from the web. Then, out of the blue, this one particular db starts having probs linking to docs from the web. And here i am. For some reason, the lookup id for the db itself had changed on the field lookup code.
Weird.
I changed the lookup code to reflect the current db id and presto magico!, everytings a-ok.
I hope this is the only time I ever see that happen as it’s perplexed me.