I have this simple Domino web application which on one server it works fine but on the other it doesn’t. From the browser, if I try to open a view or form it says “Note Item Not Found”. The main difference between the two servers is that one is Linux and the other is Win2003. I found out that if I open the view from designer and save it, I don’t get the error anymore. However, if I update the db from the template I get the error again.
This is my first experience with Domino on Linux so maybe I’m missing something?
Subject: RE: “Note Item Not Found” on Linux Domino Web
Hi
Now I have discovered that it has nothing to do with Linux. It’s not working on other Windows servers as well! The following is a list of servers that I have tried:
Domino 7.0 on Linux - does not work
Domino 7.0 on Windows (development server) - works OK
Domino 7.0 on Windows - does not work
Domino 7.0.2 on Windows - does not work
I checked server/user access rights but all have manager rights. I tried signing the design elements of the db and template with server id but no success.
I get the following error:
10/11/2006 10:45:29 HTTP Web Server: Lotus Notes Exception - Note item not found [/test/dhinvoicetest.nsf/Preston%20Invoices%20By%20Invoice%20Number?OpenView]
The strange thing is that when I open a design element and save it, it then works fine. If I refresh the design, then I get the error again. This is happening for all views and forms.
Subject: RE: “Note Item Not Found” on Linux Domino Web
Long overdue reply but just in case someone searches for this I have a solution. We experienced exactly this behaviour today on Domino 8.5.1 and in our case it was that the Shared Actions did not propagate via the design refresh. This caused all design elements using them to fail with the “Note Item Not Found”, and once the design elements was saved manually the Shared Actions on them became “local” actions the design element worked on the web again.
So, if you have this problem, check that the Shared Actions are refreshed correctly. We had to Cut/Paste all of them in the template once, and then they started propagating again via the design refresh.