How do I trouble shoot the following error "RadAsyncUpload handler is registered successfully, however, it may not be accessed directly."
It works fine locally but not on the server.
Rumen
Telerik team
commented on 24 Jul 2023, 06:54 AM
The "RadAsyncUpload handler is registered successfully, however, it may not be accessed directly." message when accessing the handler directly from the browser address bar is expected and intentionally designed like this. To facilitate the developers the GET request to the handler returns a human-readable text to notify that the correct handler URL is used and to confirm that the handler is registered successfully.
Can you please provide more information about the server problem?
Do you get any JavaScript or server errors?
Does the AsyncUpload control load on the page?
What happens when you try to upload a file?
What is different between the developer and production servers?
Can you please provide more information about the server problem? This looks like a server issue, maybe permissions. It works fine on the local dev PC, just not on the server.
Do you get any JavaScript or server errors? No, not an the initial page load
Does the AsyncUpload control load on the page? Yes
What happens when you try to upload a file? The file color icon goes from yellow to red. On my local PC it goes right to green
What is different between the developer and production servers? It works fine on my local machine just not on the windows server
Rumen
Telerik team
commented on 24 Jul 2023, 01:58 PM
If you get the "failed to load resource: the server responded with a status of 500 (internal server error)" error please check these resources on the topic:
If it is an Azure app: You can temporarily enable the custom errors so you can see a detailed stack trace. This should direct you to what is causing the issue and what a possible solution would be. We have received a number of similar reports where the Azure firewall (WAF - Web Application Firewall) was blocking the web resource requests or modifying the query parameters. You can check with your Network administrators which settings exactly are affecting the web resource requests and tweak them so the application can function properly.
The "RadAsyncUpload handler is registered successfully, however, it may not be accessed directly." message when accessing the handler directly from the browser address bar is expected and intentionally designed like this. To facilitate the developers the GET request to the handler returns a human-readable text to notify that the correct handler URL is used and to confirm that the handler is registered successfully.
Can you please provide more information about the server problem?
Do you get any JavaScript or server errors?
Does the AsyncUpload control load on the page?
What happens when you try to upload a file?
What is different between the developer and production servers?
Can you please provide more information about the server problem? This looks like a server issue, maybe permissions. It works fine on the local dev PC, just not on the server.
Do you get any JavaScript or server errors? No, not an the initial page load
Does the AsyncUpload control load on the page? Yes
What happens when you try to upload a file? The file color icon goes from yellow to red. On my local PC it goes right to green
What is different between the developer and production servers? It works fine on my local machine just not on the windows server
If you get the "failed to load resource: the server responded with a status of 500 (internal server error)" error please check these resources on the topic:
Also,
https://docs.telerik.com/devtools/aspnet-ajax/general-information/web-config-settings-overview#mandatory-additions-to-the-webconfig
<
location
path
=
"Telerik.Web.UI.WebResource.axd"
>
<
system.web
>
<
authorization
>
<
allow
users
=
"*"
/>
</
authorization
>
</
system.web
>
</
location
>