I did nothing to the forms, but suddenly all [FaleSave] stopped working on my website. The error shows up:HTTP Web Server: Lotus Notes Exception - Entry not found in index
I’ve created a very simple form just to demonstrate the problem:
http://www.madlax.com/madlax/madlax_n2.nsf/00save
I’VE TRIED:
replace the forms from the backup copy
run updall
It didn’t work
Please, any ideas???
Thanks!
Subject: @Comman([FileSave]) stopped working over web!!
“Entry not found in index” usually means there’s a field somewhere that’s looking up to a view, and the key value isn’t being found. I would check any validation code you have, in WebQuerySave or at the field level. Or, do you have an agent being called in the WebQuerySave, and you changed the agent name?
Take a look here for a list of causes of this error:
http://www.codestore.info/errors.nsf/all/E298FD184CDB7ABC862570E700189846?OpenDocument
Subject: Its worse than that, He’s dead Jim
I clicked on your link and it is broken: got error 404 file not found.Ill try and look again tomorrow to see if I notice anything. When you say the file save stopped working was it on this form or all forms on your website?
Usually when I received this error it was a beserk agent causing it on save and on load usually the @dblookup was looking for something that was non-existent.
Cheers,
Steve,
BTW just blame any life issues that you may have on frustration with Lotus Notes.
Subject: FileSave not working
Even though your link wasn’t working I was able to look at this by going on your website and finding a form to fill out. I am guessing all of your forms are not working because the first one I filled out had the error. Interestingly enough whether I cancelled the form or sent the form. I have seen this error a lot whenever the @DbLookup was fed erroneous information. Without knowing really anything about your system it is hard to know where to start; however, these following two ideas may be a starting point.
The fact that all of your forms are failing indicates that whatever the problem it is common to all forms. So get out your flow charts and figure out what form, agent view or something is in common with all the forms.
Another issue would be the server(s) themselves. Do you do your own hosting, or are you hosted offsite.
Good luck!!!
Steve
PS: look in the server logs log.nsf, miscellaneous Events, sometimes there is more information there that may help.
Subject: FileSave not working - result of the upgrade to R8
I’m hosting with dominodeveloper.net and they just upgraded to R8. Right afterwords the NOtes Form submit just stop working. THe only idea I have about it it\s that I just need to convert all submit actions to JavaScript or WQS LotusScript functions. 8(((((((((((((
Subject: Knowing what went wrong is 90% of the work
After I got thru the first paragraph of my post it hit me that it was probably a server issue. Glad you know what is wrong. Even though it is a pain right now once you get everything moved over to Script it will be ok, maybe even better. Now that I am getting more conversant in scripts I have been moving my site apps away from formula and into script. My development .nsf is at LOGION.ORG | HOME. A big issue, to me anyway, with formula is that when something is wrong the page doesn’t even load and the error messages sometimes bear little resemblence to the reality.
While searching for a form to submit I cruised around your site and it looks really nice. Great job!,
Cheeers,
Steve
Subject: Check your View
Ive been thinking about this all day. Something was rolling around in my mind that seemed familiar and I just thought of what it was. I had a very similar experience to yours with a domino website. I was switching this over to notes and had it finished, it was working perfectly; the next morning nothing loaded in my framesets except the title page and control frame. I got the Error 404 entry not found in index. Just like your site is doing. After hours of searching the problem was located. The last thing I had done the night before was going into the view to do some minor thing and somehow I had unsorted the first column, which was the only one that was sorted in the first place. That was all it was. It affected all of the pages because there was one record in the view that was accessed by at least one dreaded @DbLookup on each page. So something else to look for. Maybe changing to 8 somehow affected a view.
I think too that Rich, who posted above, has some excellent thoughts. I tend to agree with him that R8 should not have affected the @Command.
Good Luck!!!
Cheers,
Steve
Subject: RE: FileSave not working - result of the upgrade to R8
Before you conclude that you need to do anything that drastic:
Check your forms and subforms for use of @DbLookup. See what databases and views the lookups target. Open those views and inspect for any damage. Ask your server admin to check the logs for any error messages about those views. In the Domino 8 beta, I know there were some view corruption problems that were easily (though only temporarily in some cases) fixed merely by deleting the views and then refreshing the design from a template.
If you find no problems with the views themselves, then one-by-one remove the @DbLookups to try and figure out which one is failing. It is possible that a bug in 7 (or whatever you were running previously) allowed your code to succeed (or appear to succeed), but 8 has tightened things up and now the code fails. Or, it’s possible that you do have an actual bug in Domino 8 – in which case you should report it to IBM so they can fix it.