PDA

View Full Version : [CLOSED] The Ext.NET Mobile initialization script was not found.



Z
Apr 13, 2018, 4:08 PM
Support,

We have the following in our web.config file



<extnetmobile licenseKey="zzz" initScriptMode="Linked" />


Then the following in our aspx file


<ext:ResourceManager runat="server" />


Everytime we do a deployment, we have a problem that the site doesnt load and clients complain. We get the error below in our server logs.

We finally update the aspx to include InitScriptMode="Inline" within the resource manager and it works now.

Can you please explain why and what the problem is? Why is Linked such an issue? Should I update the web.config also?

/Z


Event code: 3005
Event message: An unhandled exception has occurred.
Event time: 4/13/2018 10:42:36 AM
Event time (UTC): 4/13/2018 2:42:36 PM
Event ID: d08801188bce47eda8e8a60e1a0590fb
Event sequence: 402
Event occurrence: 55
Event detail code: 0

Application information:
Application domain: /LM/W3SVC/1/ROOT/mobile-2-131680651060058657
Trust level: Full
Application Virtual Path: /mobile
Application Path: C:\zzz\mobile\
Machine name: HTPAP01

Process information:
Process ID: 7940
Process name: w3wp.exe
Account name: zzz\zzz

Exception information:
Exception type: InitializationScriptNotFoundException
Exception message: The Ext.NET Mobile initialization script was not found.
at Ext.Net.Mobile.ResourceHandler.ProcessRequest(Http Context context)
at System.Web.HttpApplication.CallHandlerExecutionSte p.System.Web.HttpApplication.IExecutionStep.Execut e()
at System.Web.HttpApplication.ExecuteStepImpl(IExecut ionStep step)
at System.Web.HttpApplication.ExecuteStep(IExecutionS tep step, Boolean& completedSynchronously)




Request information:
Request URL: https://zzz.yyyy.com:443/mobile/extnet/extnet-init-js/ext-mobile.axd?3400d35a17e545d5b6960290a5b5165b
Request path: /mobile/extnet/extnet-init-js/ext-mobile.axd
User host address: 10.1.0.18
User:
Is authenticated: False
Authentication Type:
Thread account name: zzz\zzz

Thread information:
Thread ID: 130
Thread account name: zzz\zzz
Is impersonating: False
Stack trace: at Ext.Net.Mobile.ResourceHandler.ProcessRequest(Http Context context)
at System.Web.HttpApplication.CallHandlerExecutionSte p.System.Web.HttpApplication.IExecutionStep.Execut e()
at System.Web.HttpApplication.ExecuteStepImpl(IExecut ionStep step)
at System.Web.HttpApplication.ExecuteStep(IExecutionS tep step, Boolean& completedSynchronously)


Custom event details:

fabricio.murta
Apr 13, 2018, 7:19 PM
There is something set up in your host IIS server that's preventing this feature from working.

We run Ext.NET Examples with script mode as Linked at these locations:
- https://examples2.ext.net/
- https://examples2.ext.net/
- https://examples3.ext.net/
- https://examples4.ext.net/
- http://mvc.ext.net/
- http://mvc2.ext.net/
- http://mvc3.ext.net/
- http://mvc4.ext.net/
- http://mobile.ext.net/
- http://mvc.mobile.ext.net/

And by chance we just set up an IIS server on Windows 10 a few days ago and deployed another Ext.NET project there for local tests, and all works fine with ScriptMode="Linked". Unfortunately we don't know what specific setting you have in your IIS server hosting that prevents that from working.

You should contact your hosting, reset your current hosting settings, or try a different hosting provider. Some hosts may implement security measures that disables features which should be explicitly enabled, and one or more of those inhibited features may be preventing Ext.NET from working correctly with Linked script mode. Not necessarily posing a risk to the system's security. Setting up a local IIS server on your development machine may help identifying the setting too.

Notice by Ext.NET v1, the only option was inline. This setting was introduced as of Ext.NET 2, and the default since then have been Linked, with many other users hosting their projects without issues.

Hope this helps!

fabricio.murta
Apr 13, 2018, 7:24 PM
Additionally, this issue may be related to the server support for session cookies:

- InitScriptMode.Linked causing exception regularly on production. (https://forums.ext.net/showthread.php?25373&p=111877&viewfull=1#post111877)

EDIT: session and cookies are not specificly an IIS feature, they are related to the project, and Web.config set up. It may be some setting (in the project, or Web.config, Global.asax, etc) related to sessions or cookies handling in the project that might be preventing the feature from working. This can be set up either in project level and website (IIS) level.

Z
Apr 16, 2018, 2:35 AM
Can you suggest what settings to review? Please note that i have a EXT4.NET site working just fine on the same server. it is just he mobile site.

i am happy to send you the web.config for review privately.

thanks,
/Z

fabricio.murta
Apr 17, 2018, 12:12 AM
Hello @Z!

Honestly, I don't know which setting should be wrong there. Actually, there are just a range of settings that should affect the linked init script handling that a server admin would only be able to figure out by looking at the actual server configurations.

I have some suggestions you may find interesting to investigate on your server to at least corner down the issue:

1) You told you have an Ext.NET 4 running on the same server, is that using init script mode as Linked? Can you double check that?

Worth noting, both Ext.NET and Ext.NET Mobile should not work if you just publish both solutions to the exact same server and folder, mixing in the DLL files within the web host's bin folder. But I believe that's not the problem, you have two independent websites, just on the same web server, right?

If you have an Ext.NET 4 website running fine on the same host, we can eliminate the possibility of wrong versions or unsupported system set up. Of course, hereby I'm assuming your answer for (1) above is yes (that's the default, so if that's not specified in Global.asax, Web.config or in the ResourceManager tag in your master or web page, then it should be Linked).

2) What if you wipe clean the mobile website and publish the Ext.NET 4 website there? Does it work fine? Your mobile website is not production yet, right? I mean, if you can just take it down to make some tests like publishing the non-mobile one.

3) Have you tried making an empty, new Ext.NET Mobile website? Just create a new ASP.NET 4 Website project and install the Ext.NET Mobile NuGet package, maybe just adding a simple web form page with some Ext.NET components, and making a minimum to no modifications in the "stock" Web.config file.

4) Compare. If your Ext.NET 4 website works fine, then just check for differences in the Web.config and also IIS settings for both websites. There's no such thing as a "hidden trick" for Ext.NET Mobile to work. The linked script mode feature implementation is the exact sambe between both Ext.NET versions.

I don't think I will be able to discern what's wrong with your Web.config file, but if you deem it worth we take a look at the file, please email it to support@ext.net, pointing in the email the link to this forum thread.

If you use google to search this pattern: site:forums.ext.net initialization script was not found maybe you'd find a forum thread with information that may help you. I linked you one thread from this search but I don't see your feedback about having or not luck with the information therein.

Unfortunately I found other forum threads where people simply turn off the feature (make it inline) and probably never found the reason why in their host this does not work. But as suggested on my post before this, I'm really inclined to believe it is related to the IIS session's settings.

Sorry for the long reply, I hope any of the leads helps you figure out what's out in the server that's preventing the linked script feature to work.

fabricio.murta
Apr 27, 2018, 3:26 PM
Hello @Z!

Sorry again for the long last reply, I hope it helped a bit although we probably couldn't really guess what would be set up incorrectly on the server to inhibit the linked script to work to you.

Anyway, we didn't hear back from you for some days, and we're wondering if you still need help with this topic, or maybe should we mark it as closed, if you no longer need assistance with this? I personally set up a new IIS server here, to check whether recent versions required more settings but, with basically "stock settings" and default Web.config, the website works just fine, so not much luck here trying to reproduce the scenario you get on your production server.

Looking forward to your follow-up.

p.s.: If you still don't post a reply here in 7+ days from now, we may mark this thread as closed, but that won't prevent you from posting a follow-up here afterwards.