What i need: A application as subfolder to be run under a SharePoint-site that has completly nothing to do with SharePoint.

What i got: Microsoft SharePoint is not supported in 32-bit process. Please verify that you are running in a 64-bit executable.

How to solve it:

– Make sure the application has its own application pool. U will need the pool to force the use of 32-bit like so:

(please read the rest before doing the apppool change)

Go to IIS > Application Pools > select the dedicated application pool > Click on advanced settings > Enable 32-Bit Application : set it to False


After i did this i got a 500 error and here is where my time got to waste… After a few hours banging my head on my desk, i noticed a small thing i overlooked in the beginning… Why is my application saying Microsoft SharePoint is not supported.. ?! I tought Sharepoint excluded these folders/applications automaticly?! Well… it should, but it didn’t! After doing some searching the big Google i found a small forumpost stating you can disable this behaviour in the local web.config of that folder/application. I couldnt find it again but kudo’s for that problemsolver!

Paste this under <system.webserver>:

<!-- Remove All Modules used by Sharepoint 2013 -->
<remove name="SPNativeRequestModule"/>
<remove name="ScriptModule"/>
<remove name="DesignHttpModule" />
<remove name="SPRequestModule"/>
<remove name="PublishingHttpModule"/>
<remove name="StateServiceModule"/>
<remove name="SharePoint14Module"/>
<remove name="FederatedAuthentication"/>
<remove name="SessionAuthentication"/>
<remove name="SPWindowsClaimsAuthentication"/>
<remove name="SPApplicationAuthentication"/>
<!-- Re Enable sessions which are remove by Sharepoint 2013 -->
<add name="Session" type="System.Web.SessionState.SessionStateModule"/>


Boom! My app is working as it worked in SharePoint 2010! After this it wouldnt matter if you set your App pool to 32-bit or 64-bit… it worked either way!


PS: It cant hurt making a new App pool for you application!