Printable View
Dear,
Please not that I have a problem in loading my EXT.NET application , in which sometime the application is not logged in successfully.
and all EXT.net components are not displayed also, noting that when refreshing browser tab the application will login successfully and display all components also.
the Error displayed when the system isn't worked is:
.NET:: ERR_ABORTED 500
Please check the attached screenshots.
Can you help me please?
Attachment 25517
Attachment 25519
Regards,
Hello @Geovision!
It seems the problem happens to fetch the init-script. This is unique code created every page load with the actual generated Ext.NET to Ext JS code.
You should look at IIS error logs to see if it has any information on what exactly is that 500 error. The 500 HTTP response means "internal server error" and that can be a lot of things. Looking at the IIS logs might give you a hold of what's breaking in your application during the request.
Are you able to reproduce this on debugging environment, or production only? If you can reproduce this locally then letting the application stop to report where it broke might reveal you even further information like the context where it was running, etc.
Notice this init-script is generated on page load, then a unique identifier is returned as the URL you're getting error 500 from. So for some reason the session is corrupting between the page request and init script request. This may happen, for instance, if you run Ext.NET on a distributed IIS environment and the session is not properly propagated -- or propagates slower than the client loads the initial page + requests the init script.
As you can see, there's a lot of possibilities involved, and it would take investigation on your specific IIS setup; the answer, again, should be in IIS logs.
This thread might add a little insight on a similar problem: Error 500 on the major page include when InitScriptMode="Linked" in the ResourceManager.
Hope this helps!
Hello,
the problem appears only on Client production environment, and it is not appearing on debugging environment.
So I will check as mentioned the IIS logs and then feedback you.
Thank you.