3 Replies Latest reply on Jun 8, 2017 5:42 PM by CarlSchwarz

    Webdirect "session expired" after upgrade to FMS16

    CarlSchwarz

      I upgraded a server to FMS16 from FMS15.  I can access the files fine but the user is not able to!

      Here is their error:

       

      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_AbstractClientConnecto

      This is in the center of the page

      Session expired.

      Take note of any unsaved data and click here to continue.

       

      What should I recommend the user to do?

        • 1. Re: Webdirect "session expired" after upgrade to FMS16
          LSNOVER

          Try having the user clear their browser cache and cookies.

          • 2. Re: Webdirect "session expired" after upgrade to FMS16
            LisaRose

            Yes, as Lee says, if the cookie for the same server address from a previous FMS 15 installation is still sitting in the user's client browser cache, then it can cause this particular issue when pointing to an upgraded FMS 16 on the same host machine (because of changes from 15 to 16). Removing this cookie for host address from the client browser (and clearing its cache for good measure) should resolve this particular issue.

             

            There are other scenarios (e.g. reported elsewhere in these forums) where you can get just the JavaScriptConnector error part (esp. in Safari 10 with 15 WebDirect). But these should be greatly reduced in 16 WebDirect. And they're usually not accompanied by the "Session Expired" message (which often indicates a cookie problem, if it occurs immediately).

            1 of 1 people found this helpful
            • 3. Re: Webdirect "session expired" after upgrade to FMS16
              CarlSchwarz

              LisaRose wrote:

               

              Yes, as Lee says, if cookie for same server address from previous FMS 15 installation is still sitting in user's client browser cache, then it can cause this particular issue when pointing to upgraded FMS 16 on same host machine (because of changes from 15 to 16). Removing cookie for host address from client browser (and clearing its cache for good measure) should resolve this particular issue.

               

              There are other scenarios (e.g. reported elsewhere in these forums) where you can get just JavaScriptConnector error part (esp. in Safari 10 with 15 WebDirect). But these should be greatly reduced in 16 WebDirect. And are usually not accompanied by "Session Expired" message (which often indicates cookie problem, if it occurs immediately).

              Thanks for the detailed answer!