I mm facing an issue on my ASP.NET page where I'm using RegisterStartupScript to call a JavaScript function from the code-behind.
The JavaScript function is intended to close a Telerik RadWindow using
var oWnd = GetRadWindow();
oWnd.close();.
However, upon execution,
I receive the following error:
'Error code: STATUS_ACCESS_VIOLATION'. Could you please assist me in resolving this issue?
1 Answer, 1 is accepted
Hi Sanju,
Thank you for bringing this issue to our attention. So far, you are the first to report this, and I have not been able to replicate the problem with the files attached.
You can try to close the popup with a small timeout:
protected void btnCloseWindow_Click(object sender, EventArgs e)
{
string script = "var oWnd = GetRadWindow(); if (oWnd) setTimeout(function(){oWnd.close();}, 0);";
ScriptManager.RegisterStartupScript(this, GetType(), "CloseWindow", script, true);
}If this does not solve the error, can you please modify the files to consistently reproduce the issue and send them back to us for further analysis?
Additionally, I would like to confirm if you are encountering this problem on the latest version of Telerik UI for ASP.NET AJAX 2024 Q1. This version is designed to be compatible with the most recent browser updates.
Lastly, could you check if the issue persists when using the latest versions of Chrome, Edge, and Firefox in Incognito mode as well as test on another machine outside of your office? This will help ensure that browser add-ons are not interfering with the process and that the issue is not due to some network policy restriction.
Regards,
Rumen
Progress Telerik
Rank 1
Additionally, I have a save functionality, and after saving, I close the pop-up. However, every time I close the pop-up, I immediately encounter this error.
I am using the latest browser. The functionality was working fine in the old Chrome browser, but after upgrading the browser, I started experiencing the same error.
Thank you for providing additional information about the issue. Given that the issue persists even after making the suggested changes, we need to investigate further.
Please follow these steps:
- Create a stripped-down project: create a simplified version of your project that reproduces the error. This will help us understand the context of the issue better and speed up the troubleshooting process.
- Modify the current project I've attached to my earlier post: If creating a new project is not feasible, modify your existing project so that it consistently reproduces the issue. This can involve removing unrelated code or adding debug information.
- Share the project: Once you have the reproducible project, open a new support ticket and share it with us so we can analyze it in more detail.
Additionally, the error might be browser-specific. You mentioned the problem started occurring after a Chrome upgrade. Please try the following:
- Test on Different Browsers: Test on the latest versions of Firefox and Edge to check if the issue is specific to Chrome.
- Test in Incognito Mode: Use Chrome's Incognito mode to ensure no extensions are interfering.
- Test on a Different Machine: Use a different machine to rule out network policy restrictions or machine-specific issues.
If the error is specific to Chrome, we can also file a bug report with the Chrome team once we have a consistent reproduction scenario.
Rank 1
After adding RadAjaxManager1 to each page, the error has stopped occurring, but now the RadAlert function has stopped working.
Could you please assist with this?
Thank you.
Rank 1
I'm encountering the issue on only certain pages, not all of them, which is why I can't definitively say it's a browser issue. Interestingly, the functionality has been working smoothly since 2017. Additionally, it works fine when we open the same page in IE mode of the Edge browser.
Any insights or suggestions you have on resolving this would be greatly appreciated.
Thank you.
Note that the old versions of Telerik do not officially support the latest browser updates (see here). Given that the issue seems browser-specific (and particularly related to updates in Chrome), testing across different browsers was a great step. Since it works in IE mode on Edge, it's likely related to how modern browsers handle JavaScript or specific security policies that might have been introduced in the latest versions.
Continue testing in Incognito mode across different browsers to ensure no extensions or cached data interfere.
Ensure that all Telerik.Web.UI assemblies are are updated to the latest version. Browser updates can sometimes break functionality that depends on older versions of client-side libraries.
If RadAlert has stopped working after adding RadAjaxManager to the page, ensure that there are no JavaScript errors thrown before the oWnd.close(); call. Use the browser's developer tools (Console tab) to check for any errors that might be interfering with the proper execution of the script.
Try to isolate the problem on a single page and strip down the components to the bare minimum where the error can be reproduced. This can help in identifying whether specific interactions or configurations are causing the issue.