Could not initialize JavaScriptConnector

[jeffshap]

I have a WebDirect application hosted on at an ISP. When users try to access it from outside their corporate network things look fine. When users try access the ISP hosted application from inside their corporate network, the first message that loads is :

Could not initialize JavaScriptConnector because no JavaScript init function was found. Make sure one of these functions are defined:
com_filemaker_jwpc_iwp_application_AppJavaScriptComponent
com_vaadin_ui_AbstractJavaScriptComponent
com_vaadin_ui_AbstractComponent
com_vaadin_server_AbstractClientConnector

What's interesting is that if I don't use a DNS name to access the application from outside the corporate firewall then I get the same error. In other words if I http://www.Domain.com/fmi/webd?#Database it works but if I use http://[IP ADDRESS]/fmi/webd?#Database then it doesn't work.

This is a big problem because when this error message comes up the interface loses some functionality, such as the [TAB] key doesn't move to the next field.

Any ideas?

[LKingsella]

I am having the same issue with WebDirect. Clearing the Safari cache will remove the problem for a short time, but it will occur again after a WebDirect a few logins. 

[Justin Close]

I have run into this error as well.  It seems to only happen on Safari, though; Chrome and Firefox (yeah, I know - not official) don't show the error.  In my case it only shows up briefly as the user is loading the WebD layouts, and then it goes away and the proper layout is displayed - so there is no loss of functionality.

[Joe Byrne]

I am having the same issue. Does anyone know if there's a solution

 

[Andrea]

Same Issues with Filemaker Server 16

[Terrible Toll]

I have this issue too - tabs don't work, but otherwise all seems to be OK. Just get the error flashing up at the beginning on Safari.

Edited November 22, 2017 by Terrible Toll