{"id":1378,"date":"2011-03-15T20:23:36","date_gmt":"2011-03-15T09:23:36","guid":{"rendered":"https:\/\/docassist.com.au\/?p=1378"},"modified":"2019-07-01T18:02:18","modified_gmt":"2019-07-01T08:02:18","slug":"taking-care-of-bitness-or-how-to-run-a-32-bit-app-with-owa-2010","status":"publish","type":"post","link":"https:\/\/docassist.com.au\/taking-care-of-bitness-or-how-to-run-a-32-bit-app-with-owa-2010\/","title":{"rendered":"Taking care of bitness (or how to run a 32 bit app with OWA 2010)"},"content":{"rendered":"

Our hands were tied recently when we had to develop a 32 bit web app due to the reliance on a 3rd<\/sup> party app that was 32 bit only.<\/p>\n

We quickly worked out how to get the app running in 32 bit mode in IIS7 just by setting the “Enable 32-Bit Applications”\u00a0setting within the application pool used for the app.<\/p>\n

This worked great until we went to do this on a server running OWA 2010. After setting the application pool to run 32 bit apps, we still got an error:<\/p>\n

Service Unavailable<\/p>\n

HTTP Error 503. The service is unavailable.<\/p>\n

And as an added bonus, the application pool was now stopped. Yippee – I guess that was 5 errors in less than 5 minutes!<\/p>\n

A quick look in the Application event log showed the following error:<\/p>\n

The Module DLL ‘C:\\Program Files\\Microsoft\\Exchange Server\\V14\\Bin\\kerbauth.dll’ could not be loaded due to a configuration problem. The current configuration only supports loading images built for a x86 processor architecture. The data field contains the error number. To learn more about this issue, including how to troubleshooting this kind of processor architecture mismatch error, see http:\/\/go.microsoft.com\/fwlink\/?LinkId=29349<\/a>.<\/p>\n

The Source was IIS-W3SVC-WP and the Event ID was 2282.<\/p>\n

A bit of research pointed us in the direction of setting the kerbauth.dll to be 64 bit only in the applicationHost.config file for IIS (located in C:\\Windows\\System32\\inetsrv\\config). So we stopped IIS and edited the file. In the globalModules section, we found the line for kerbauth, and added the precondition=\u201dbitness64\u201d attribute as follows:<\/p>\n

<<\/span>add<\/span> name<\/span>=<\/span>“kerbauth<\/span>” image<\/span>=<\/span>“C:\\Program Files\\Microsoft\\Exchange Server\\V14\\Bin\\kerbauth.dll<\/span>” preCondition<\/span>=<\/span>“bitness64<\/span>“ \/><\/span><\/p>\n

We restarted IIS (and also the app pool!) and now the app showed the following error:<\/p>\n

HTTP Error 500.0 – Internal Server Error<\/p>\n

Calling LoadLibraryEx on ISAPI filter “C:\\Program Files\\Microsoft\\Exchange Server\\V14\\ClientAccess\\owa\\auth\\owaauth.dll” failed<\/p>\n

So we applied the same theory again, and again for each dll that caused an issue \u2013 luckily for us there were only two – owaauth.dll and AirFilter.dll. Both were listed in the <isapiFilters> section of the applicationHost.config file:<\/p>\n

<<\/span>filter<\/span> name<\/span>=<\/span>“Exchange OWA Cookie Authentication ISAPI Filter<\/span>” path<\/span>=<\/span>“C:\\Program Files\\Microsoft\\Exchange Server\\V14\\ClientAccess\\owa\\auth\\owaauth.dll<\/span>” enabled<\/span>=<\/span>“true<\/span>“ preCondition<\/span>=<\/span>“bitness64<\/span>“\u00a0<\/span><\/span>\/><\/span><\/p>\n

<<\/span>filter<\/span> name<\/span>=<\/span>“Exchange ActiveSync ISAPI Filter<\/span>” path<\/span>=<\/span>“C:\\Program Files\\Microsoft\\Exchange Server\\V14\\ClientAccess\\sync\\bin\\AirFilter.dll<\/span>” enabled<\/span>=<\/span>“true<\/span>“ preCondition<\/span>=<\/span>“bitness64<\/span>” <\/span>\/><\/span><\/p>\n

We restarted IIS again and voila \u2013 a happy application, and OWA still worked to boot. Who says you need to run 32 bit apps on a separate server! Happy days\u2026<\/p>\n

Now I’ve just gotta get that song out of my head… “taking care of bitness and working overtime…” ;-)<\/p>\n","protected":false},"excerpt":{"rendered":"

Our hands were tied recently when we had to develop a 32 bit web app due to the reliance on a 3rd party app that was 32 bit only. We quickly worked out how to get the app running in 32 bit mode in IIS7 just by setting the “Enable 32-Bit Applications”\u00a0setting within the application […]<\/p>\n","protected":false},"author":4,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"inline_featured_image":false,"footnotes":""},"categories":[28,1],"tags":[],"_links":{"self":[{"href":"https:\/\/docassist.com.au\/wp-json\/wp\/v2\/posts\/1378"}],"collection":[{"href":"https:\/\/docassist.com.au\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/docassist.com.au\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/docassist.com.au\/wp-json\/wp\/v2\/users\/4"}],"replies":[{"embeddable":true,"href":"https:\/\/docassist.com.au\/wp-json\/wp\/v2\/comments?post=1378"}],"version-history":[{"count":1,"href":"https:\/\/docassist.com.au\/wp-json\/wp\/v2\/posts\/1378\/revisions"}],"predecessor-version":[{"id":1379,"href":"https:\/\/docassist.com.au\/wp-json\/wp\/v2\/posts\/1378\/revisions\/1379"}],"wp:attachment":[{"href":"https:\/\/docassist.com.au\/wp-json\/wp\/v2\/media?parent=1378"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/docassist.com.au\/wp-json\/wp\/v2\/categories?post=1378"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/docassist.com.au\/wp-json\/wp\/v2\/tags?post=1378"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}