Share via

Error while performing operation Web.config Error is Blank

  • Article

Question

Tuesday, April 29, 2014 12:57 PM

Hi I'm getting an error when trying to access a website with standard install of Filemaker Server 13. 

I'm on Server 2012.  The error message comes up when trying to access any of the panels in IIS.

'There was an error performing the operation' 

Details: Filename \?\C:\Program Files\Some Path\web.config

Error:

The Error is blank which isn't very helpful.  I have added IIUSR permissions to webconfig.  

Going to localhost gives me an additional error code of: 0x8007000d

However the Config Source just says:

-1:
0:

So again, that is really unhelpful.

I've done a full re-install of IIS including URL Rewrite so I am not sure where to go from here... any suggestions?

Thanks

All replies (7)

Wednesday, April 30, 2014 7:03 PM âś…Answered

I didn't manage to fix this other than by installing a brand new version of Server 2012, IIS and FMServer 13 and then everything worked just fine.  

Tuesday, April 29, 2014 2:29 PM

Have you tried enabling Failed Request Tracing on the site to see if it gives you any additional hints?  Additionally you may want to try reproducing the error while running Process Monitor on the server.  That is especially helpful if there is a file access or permissions issue.

Tuesday, April 29, 2014 5:06 PM

Thanks for taking the time to reply Rick.

I can't enable the Failed Request Tracing as it gives me the error when I click on the icon and then says 'could not retrieve failed request tracing entries'.

I have installed Process Monitor, but I'm a bit blown away by the detail and not sure what to look for!

Here's a screenshot of the 'blank' error message:

Tuesday, April 29, 2014 5:25 PM

There is a guy who had the same problem here but I have URLRewrite 2.0 installed and I can remove the <rewrite> tags and restart the website, but it doesn't solve the problem.

Tuesday, April 29, 2014 6:05 PM

That error that you gave a screenshot of is a lot more helpful.  First of all, make a backup copy of the web.config at the location that the error gives.  Then start removing sections of the web.config one at a time until the page will load.  That will help you narrow down which section is causing the error.  The link you provided was for someone who was having an issue with the <rewrite> section but it sounds like you are having an issue with a different section that IIS doesn't like.

Tuesday, April 29, 2014 6:22 PM

Rick, good point - I'm getting tired and not thinking straight.  I had renamed the web.config file to webx.config and that gets the server working, but not taken things out section by section / line by line.  Just done that quickly - it's late over here!

The problem is that you have to take out the whole of the <rules></rules> section including all the below - which is the whole point of the web.config file to get it to stop returning the error.

Taking out one rule at a time or e.g. the <rewrites> or the <clear /> doesn't help - nor does playing around with the syntax.  That whole section has to go.  Which I think points to something bigger missing in the IIS installation.

Also this was working a week ago, I think until we applied an OpenSSL patch for the heartbleed bug.  This was a patch for Filemaker Server 13 but my confusion is that I've wiped the whole installation of Filemaker 13 and reinstalled it along with IIS and haven't installed that patch again, so I should have been left with a clean install as I had previously. 

Thanks again for thinking this through.

<?xml version="1.0" encoding="UTF-8"?>
<configuration>
  <system.webServer>
    <rewrite>
      <rules>
        <clear />
        <rule name="fmws" enabled="true" stopProcessing="false">
          <action type="Rewrite" url="http://localhost:9090/{R:0}" />
          <match url="^fmws(/(.*))?" />
          <conditions>
            <add input="{SERVER_PORT}" pattern="443" />
          </conditions>
        </rule>
        <rule name="streaming" enabled="true" stopProcessing="false">
          <action type="Rewrite" url="http://localhost:16001/{R:0}" />
          <match url="^Streaming(/(.*))?" />
          <conditions>
            <add input="{SERVER_PORT}" pattern="80" />
          </conditions>
        </rule>
        <rule name="uac" enabled="true" stopProcessing="false" >
          <action type="Rewrite" url="http://localhost:16001/{R:0}" />
          <match url="(.*)" />
          <conditions>
            <add input="{SERVER_PORT}" pattern="16000" />
          </conditions>
        </rule>
        <rule name="https_admin-console" enabled="true" stopProcessing="true">
          <match url="^admin-console(/(.*))?" />
          <conditions>
            <add input="{SERVER_PORT}" pattern="80" />
            <add input="{HTTPS}" pattern="off" />
          </conditions>
          <action type="Redirect" url="https://{HTTP_HOST}:16000/admin-console" redirectType="Found" />
        </rule>
        <rule name="https_test_page" enabled="true" stopProcessing="true">
          <match url="^test$" />
            <conditions>
              <add input="{SERVER_PORT}" pattern="80" />
              <add input="{HTTPS}" pattern="off" />
            </conditions>
            <action type="Redirect" url="https://{HTTP_HOST}:16000/test" redirectType="Found" />
        </rule>
        <rule name="https_webd" enabled="false" stopProcessing="true">
          <match url="^fmi/webd(/(.*))?" />
          <conditions>
            <add input="{SERVER_PORT}" pattern="80" />
            <add input="{HTTPS}" pattern="off" />
          </conditions>
          <action type="Redirect" url="https://{HTTP_HOST}:443/fmi/webd/{R:1}" redirectType="Found" />
        </rule>
      </rules>
    </rewrite>
    <security>
      <requestFiltering>
        <requestLimits maxAllowedContentLength="4294967295" />
      </requestFiltering>
    </security>
  </system.webServer>
</configuration>

Wednesday, April 30, 2014 7:06 PM

Thanks for coming back and providing an update and solution.  I had this flagged to look at tomorrow but now I won't need to.