AnsweredAssumed Answered

FileMaker WebDirect: Blank page when opening a file

Question asked by ClickWorks on Oct 24, 2017
Latest reply on May 17, 2018 by James Parker

FileMaker Server 15 & 16

Windows 2008R2 and 2012R2

Browsers: Chrome 62 and Safari 11

OS: Windows

Issue:

Since friday, we had an issue with WebDirect on 2 different  servers. When we try to open a solution in WebDirect, a blank page is shown. We can see files when opening the WebDirect Launch Center, i.e. use the /fmi/webd URL endpoint. But then, when clicking on any file, the page stays blank.

In Chrome, when using the JavaScript console from the developer tools, the error is "net::ERR_CONTENT_DECODING_FAILED". When using the Developer Tools in Safari, the error is "Failed to load resource: cannot decode raw data". It seems that an AJAX call is getting an unexpected response.

 

Screen Shot 2017-10-24 at 08.11.26.png

On the Windows 2012R2 server, this happened since last friday. We installed a new SSL (a renewal) then. But on the other server, nothing was changed. I saw that on the second Win 2008R2 server, on 20/10/2017 Windows updates were installed and the customer reports that the issue appears since 20/10/2017. I applied the latest Win updates to another (Win 2012R2) hosting server, but in that case FileMaker WebDirect keeps working fine. The Java version is 1.8.0_151 in both problem cases. I deleted the Java temp files and cache, restarted the WPE and IIS but it does solve the problem. I cannot find any clues in the IIS log.

 

 

A typical IIS log sequence is this:

2017-10-24 09:48:30 10.240.10.20 POST /fmi/webd/FMServer_Sample lgcnt=0&X-ARR-CACHE-HIT=0&X-ARR-LOG-ID=ca4fa12b-3dcd-42ea-8103-e72e30fa9456&SERVER-STATUS=200 4443 - 81.82.238.123 Mozilla/5.0+(Macintosh;+Intel+Mac+OS+X+10_12_6)+AppleWebKit/604.1.38+(KHTML,+like+Gecko)+Version/11.0+Safari/604.1.38 200 0 0 78

2017-10-24 09:48:31 10.240.10.20 GET /fmi/VAADIN/themes/default/styles-desktop.css X-ARR-CACHE-HIT=0&X-ARR-LOG-ID=9585af64-0677-4f90-adfa-15d6236c0684&SERVER-STATUS=304 4443 - 81.82.238.123 Mozilla/5.0+(Macintosh;+Intel+Mac+OS+X+10_12_6)+AppleWebKit/604.1.38+(KHTML,+like+Gecko)+Version/11.0+Safari/604.1.38 304 0 0 15

2017-10-24 09:48:31 10.240.10.20 GET /fmi/VAADIN/vaadinBootstrap.js v=7.7.9.fmi&X-ARR-CACHE-HIT=0&X-ARR-LOG-ID=8262bef2-80ad-4c94-a89c-1f4598a8c8a2&SERVER-STATUS=304 4443 - 81.82.238.123 Mozilla/5.0+(Macintosh;+Intel+Mac+OS+X+10_12_6)+AppleWebKit/604.1.38+(KHTML,+like+Gecko)+Version/11.0+Safari/604.1.38 304 0 0 1125

2017-10-24 09:48:31 10.240.10.20 GET /fmi/VAADIN/widgetsets/com.filemaker.jwpc.iwp.widgetset.UIWidgetSet/com.filemaker.jwpc.iwp.widgetset.UIWidgetSet.nocache.js 1508838487948&X-ARR-CACHE-HIT=0&X-ARR-LOG-ID=ed93ac72-86e3-40ba-aaa0-f2bd7c70c6df&SERVER-STATUS=200 4443 - 81.82.238.123 Mozilla/5.0+(Macintosh;+Intel+Mac+OS+X+10_12_6)+AppleWebKit/604.1.38+(KHTML,+like+Gecko)+Version/11.0+Safari/604.1.38 200 0 0 31

2017-10-24 09:48:31 10.240.10.20 GET /fmi/VAADIN/themes/default/styles.css v=7.7.9.fmi&X-ARR-CACHE-HIT=0&X-ARR-LOG-ID=f6195615-f5f1-47dd-917b-7c07d46c9181&SERVER-STATUS=304 4443 - 81.82.238.123 Mozilla/5.0+(Macintosh;+Intel+Mac+OS+X+10_12_6)+AppleWebKit/604.1.38+(KHTML,+like+Gecko)+Version/11.0+Safari/604.1.38 304 0 0 31

2017-10-24 09:48:31 10.240.10.20 GET /fmi/VAADIN/widgetsets/com.filemaker.jwpc.iwp.widgetset.UIWidgetSet/contextmenu-widget/contextmenu.css X-ARR-CACHE-HIT=0&X-ARR-LOG-ID=f2145328-ac84-4439-b0d4-17a9c1635a0c&SERVER-STATUS=304 4443 - 81.82.238.123 Mozilla/5.0+(Macintosh;+Intel+Mac+OS+X+10_12_6)+AppleWebKit/604.1.38+(KHTML,+like+Gecko)+Version/11.0+Safari/604.1.38 304 0 0 46

2017-10-24 09:48:31 10.240.10.20 GET /fmi/VAADIN/widgetsets/com.filemaker.jwpc.iwp.widgetset.UIWidgetSet/imagescaler-widget/styles.css X-ARR-CACHE-HIT=0&X-ARR-LOG-ID=8f5692e3-619a-44aa-97e3-6d649a37c220&SERVER-STATUS=304 4443 - 81.82.238.123 Mozilla/5.0+(Macintosh;+Intel+Mac+OS+X+10_12_6)+AppleWebKit/604.1.38+(KHTML,+like+Gecko)+Version/11.0+Safari/604.1.38 304 0 0 15

2017-10-24 09:48:31 10.240.10.20 GET /fmi/VAADIN/widgetsets/com.filemaker.jwpc.iwp.widgetset.UIWidgetSet/filemakermenu/filemakermenu.css X-ARR-CACHE-HIT=0&X-ARR-LOG-ID=cddb7f83-5533-46bc-90d8-40fb42929102&SERVER-STATUS=304 4443 - 81.82.238.123 Mozilla/5.0+(Macintosh;+Intel+Mac+OS+X+10_12_6)+AppleWebKit/604.1.38+(KHTML,+like+Gecko)+Version/11.0+Safari/604.1.38 304 0 0 31

2017-10-24 09:48:31 10.240.10.20 GET /fmi/VAADIN/widgetsets/com.filemaker.jwpc.iwp.widgetset.UIWidgetSet/fields/styles.css X-ARR-CACHE-HIT=0&X-ARR-LOG-ID=79cda921-b5f3-45a8-9f5a-2220f9c4bf46&SERVER-STATUS=304 4443 - 81.82.238.123 Mozilla/5.0+(Macintosh;+Intel+Mac+OS+X+10_12_6)+AppleWebKit/604.1.38+(KHTML,+like+Gecko)+Version/11.0+Safari/604.1.38 304 0 0 15

2017-10-24 09:48:31 10.240.10.20 POST /fmi/webd/FMServer_Sample lgcnt=0&v-1508838487948&X-ARR-CACHE-HIT=0&X-ARR-LOG-ID=cbb2f1a8-77ad-4988-8701-9c8561858ddb&SERVER-STATUS=200 4443 - 81.82.238.123 Mozilla/5.0+(Macintosh;+Intel+Mac+OS+X+10_12_6)+AppleWebKit/604.1.38+(KHTML,+like+Gecko)+Version/11.0+Safari/604.1.38 200 0 64 156

2017-10-24 09:48:31 10.240.10.20 GET /fmi/VAADIN/themes/default/favicon.ico X-ARR-CACHE-HIT=0&X-ARR-LOG-ID=5312fc7e-5cc1-4644-bcdf-186793037a1c&SERVER-STATUS=304 4443 - 81.82.238.123 Mozilla/5.0+(Macintosh;+Intel+Mac+OS+X+10_12_6)+AppleWebKit/604.1.38+(KHTML,+like+Gecko)+Version/11.0+Safari/604.1.38 304 0 0 15

2017-10-24 09:48:33 10.240.10.20 GET /fmi/VAADIN/themes/default/favicon.ico X-ARR-CACHE-HIT=0&X-ARR-LOG-ID=b6e7622b-a48c-4348-a488-3cb5bc197912&SERVER-STATUS=304 4443 - 81.82.238.123 Mozilla/5.0+(Macintosh;+Intel+Mac+OS+X+10_12_6)+AppleWebKit/604.1.38+(KHTML,+like+Gecko)+Version/11.0+Safari/604.1.38 304 0 0 15

 

Workaround (if any):

I currently have no workaround. I uninstalled the Windows updates restarted the WPE and IIS several times, enabled and disabled IIS static compression, without any improvement. Custom web publishing is working fine on both machines. I re-installed the complete FMS16 server, ran the deployment assistant but the issue remains. On the other server, which is a dedicated hosting server of our own, we reinstalled windows from an image and re-installed filemaker server 16. This - of course - did overcome the problem there.

Outcomes