The app I’m working with is an internet app which requires login (default=no access).
In following up on a complaint where a user couldn’t save a document, I tried stripping out all parts of the form, webquerysave, subforms, hidden fields, etc. nothing would allow this document to save.
So I created a new form pasting in parts of the old form (in case the old form was corrupted), still nothing saved (according to the database properties tab)
So then, just for giggles, I created a brand new form with just one text/editable field in ti and an @Command([FileSave]) button, and believe it or not that won’t save either, so now I’m perplexed.
I’ve explicitly listed this particular user’s login in the ACL with editor access and all the roles and have “available to public access users” checked off everywhere (form, subform, webquerysave/webqueryopen agents)
Yes, it was – and it’s one common cause of this kind of problem. Another (doesn’t apply here) is Authors who don’t have “create documents” set.
Is there a misfiring formula anywhere? A dead formula on save will return you to the default entrance point for the application (on the web) without giving you a 500.
There shouldn’t be a misfiring formula because although the initial form I was trying to save the doc in is chok’ed full of queryopen and query save stuff that calls other script libraries, etc., that’s why I created a brand new doc, only put one text field in it, and a save button which only contains:@Command([FileSave])
and even that doesn’t save (nothing complicated there)
on the server console I get an “Entry not found in index […formname?openform&seq=…]”
on the notes side I can save documents using either form, this just applies to the web.
the curious thing is that I have another user on another browser far away from this office and when she tried to submit the document, the server console shows a different error, something along the lines of “possible corruption” eek!
I’d already run fixup, updall, and compact before she got the aforementioned error so I’m thinking about restarting the server.
If that doesn’t do the trick, what are my options?
Subject: SOLUTION: Can’t save any document to database
Since the server console indicated the database was possibly “corrupted”, we:
made a new replica of the possibly corrupted database to a different filename and directory.
deleted the original (possibly corrupted) database.
from the replica database made in step 1 above, we made a new replica specifying the original filename and directory (which was deleted in step 2 above)