We have been getting an error prompt/alert in our XPages application at random times:
"An error occurred while updating some of the page...status:12152" and
"An error occurred while updating some of the page...status:12029"
We can't seem to pin it down to anything. Maybe someone has an idea of what these errors are referring to or maybe how to track it back to something? Thanks.
The HTTP 12152 error usually points to a network connection issue rather than anything specific to the browser or the Domino server.12029 again is down to an inability to make a connection to the server.
It sounds like the network connection is intermittent. I don't know what tools there are to test that, but I would suggest confirming you have a good, stable network connection between PC and server and that it's not getting negatively impacted by a firewall.
It looks like your application is trying to partially refresh content on the screen, and that this partial refresh fails. This can be because the component with that id is no longer found in the component tree.
Have a look at your XPages source code for controls with an id of MainContent and refreshPanel3 and find any partial refreshes on those controls. Check the rendered/loaded property for these controls to see if they are hidden in certain cases. If you do not render a control and want to display it using a partial refresh, you must partially refresh an outer component that contains the non-rendered control.
Use browser's network debug (F12 in Chrome/IE/Firefox w Firebug) to get real server response, it usually contains error page with more info. Failed partial refresh should be the last POST request.
Related
Scenario:
It's angular based script in content editor web part. Basically SPA Application. End user does lot of work on the page and stays on the page for very long time. while all operations works as expected. I think because Request Digest expires. All operation after an hour fails. (approximately). Currently, I am making POST call to http://<site url>/_api/contextinfo in order to get latest Request Digest. which I am using to make insert/update or delete within Sharepoint List Item.
Question is: Can I avoid making this call every-time ?and is there any approach I can take to avoid error "The security validation for this page is invalid and might be corrupted. Please use your web browser's Back button to try your operation again"
Background
I have an ASP.Net Core v2.0 web application that has the [HttpGet] attribute above action results that don't need to accept a post.
I created a spreadsheet with a list of pages on the website to my marketing team, along with a column of hyperlinks that link directly to each page on the website.
Example Spreadsheet:
Issue
Once the marketing team started clicking on the links in the spreadsheet, I started to receive 404 errors via email (configured using NLog) although the page did still load for the user.
Troubleshooting
I troubleshooted this and uncovered that the issue was down to the [HttpGet] attribute. If I take the [HttpGet] attribute out, clicking on the links in the spreadsheet doesn't generate a 404 error.
The site doesn't generate 404 errors when loading the page (s) via the browser.
I installed fiddler and it looks as though Excel is using the "CONNECT" method.
Fiddler screenshot:
I thought this could be the issue as it's not a GET but when I access a page within Chrome, it also shows using the "CONNECT" method in fiddler.
I'm looking to see if anyone else has had this issue and if they got around it? Do I need to add another attribute alongside [HTTPGet] to stop Excel or other 3rd party software causing a 404?
I've resolved my own issue.
For anyone else that has this issue the fix is to put [HttpGet, HttpHead] as the attribute. If you have a custom route then add another attribute underneath:
[Route("[controller]/custom-action")].
For info, I got to the bottom of this by using the logs from the drop down ASP.Net Core Web Server in the output window in Visual Studio. I could see that when the link was first being requested by Excel, it was using the HEAD method rather than the GET which is why a 404 error was being fired.
Hope that helps someone down the line.
Display custom error messages on unsucessful login using jaas's j_exception
I have configured tomcat to work with jaas to authenticate my users. I have made use of form based authentication and hence on unsuccessful login i navigate to an error page. Instead of an error page with static message, I wish to display appropriate messages like "Invalid username/password" or "User locked"(i lock the user after 5 unsuccessful attempts) etc from j_exception
How can i achieve this?
I tried googling around the issue and found the following link
http://www.jroller.com/heonkoo/entry/manipulating_login_exception
But this seems like an old post.
I have been struggling with this from a few days. Any help will be greatly appreciated.
JAAS does not provide a standard way to propagate information to the web layer.
You can use a ThreadLocal to store the exception and read it in your error page.
On my application, I'm using the SWT browser widget to check for network connectivity. The reason for this is long, but long story short I HAVE to use the browser widget to check for connectivity. Unfortunately, on Mac and Debian, I get a modal dialog that pops up and tells me that the page load failed.
This message is being passed from the native browser and the SWT browser widget is passing this message through, displaying it as a modal dialog box. I need to intercept this message and handle it, displaying a more useful message to users in the event of a "Page load failed". Here's a screenshot of what it looks like:
Does anyone know how to intercept these messages instead of displaying them to the user?
Few days ago, there was almost same question How to detect internet connection with SWT browser (or handle server not available). Check the answer for code, which might help you..
We have an SSAS server with a cube deployed on a server over the WAN.. We are trying to connect to the cube from Excel on various client workstations. The server is not on a domain with the clients. It "works" for some of us but not for others. We are trying and failing yet to determine what the difference is on the machines that work versus the ones that don't. However, even for the ones that work, it isn't as seamless as we think it should be. I'll explain:
In Excel, we use the Data-Other Sources-Analysis Server option, which presents us with the standard dialog:
standard dialog http://www.freeimagehosting.net/uploads/de3420ec26.gif
Now, we believe the firewall and server settings are correct, because we are then presented with the dialog which lets you pick which cube to use from the server:
pick a cube dialog http://www.freeimagehosting.net/uploads/882a09ee7f.gif
And, clicking "Finish" lets Excep being to work with the cube, as evidenced by the standard Excel dialog:
all seems OK http://www.freeimagehosting.net/uploads/fdf4626609.gif
But then we are presented with the dreaded "transport layer error" message:
transport layer error http://www.freeimagehosting.net/uploads/243d5f3d49.gif
Note that this error appears even on the machines that "work." What makes them "work" is that after clicking OK on that dialog, the next dialog appears:
mysterious new dialog http://www.freeimagehosting.net/uploads/b8fc6bae18.gif
Once this dialog appears, you re-enter your password, and everything "just works" after that. While I'd like it to "just work" without that second dialog, at least it works... But on many machines we've tested this new dialog never comes up. Instead, they just get the following error message, leaving them out of luck:
final error http://www.freeimagehosting.net/uploads/601b9294e3.jpg
Can anyone offer any advice for this? Thanks!
Do the connections work if you allow "NT Authority/Authenticated Users" or "NT Authority/Anonymous Logon" to connect? Would help troubleshooting at least, but it's not a great idea to leave it like that ;)