Known issue about configuring BAM Portal and WSS based on different IIS versions

Many people are confused by configuring BAM Portal on a x64 machine or on a site extended by WSS, below info may be help.

1.       Many people think BAM need WSS as pre-requirement, because we know there used to be a BizTalk feature BAS which needs WSS 2.0 and was deprecated since BizTalk 2009, this is a misunderstanding. BAM functionality has nothing to do with WSS in below BizTalk versions:

                ·         BizTalk 2006

·         BizTalk 2006 R2/BizTalk 2006 R2 SP1

·         BizTalk 2009

·         BizTalk 2010

2.       Differences between IIS5.1(winxp), IIS6.0(win2k3), IIS7.0(win2k8sp1/win2k8sp2/vista sp2) and IIS7.5(win2k8 r2/win7)

We know that BAM Portal works on 32bit mode of IIS,I would like to clarify more about the issue of configuring BAM Portal and SharePoint adapter at the same time based on the different version of IIS:

·         IIS5.1(winxp)

BizTalk officially supported: 2006, 2006 R2/2006 R2 SP1, 2009

Related specification: has NO application pool, has NO 32bit and 64bit integration

Ø  WSS cannot be installed on client OS, we cannot use share point adapter on winxp platform.

Ø  BAM Portal can be configured and used properly only if the IIS5.1 is running in 32bit mode.

·         IIS6.0(win2k3)

BizTalk officially supported: 2006, 2006 R2/2006 R2 SP1, 2009

Related specification:  has application pool, has NO 32bit and 64bit integration

On x86 platforms:

Ø  BAM Portal and WSS adapter all can be configured successfully and work properly.

Ø  BAM Portal can be configured in the site extended by WSS. (In our automation on win2k3 x86 platforms, Default Web Site will be extended by WSS, and BAM Portal will also be configured on it, they all work fine)

Ø  For 2006, and 2006 R2/2006 R2 SP1, BAS feature is included, it needs share point adapter to be configured against WSS2.0

                                On x64 platforms:

Ø  BAM Portal can be configured and used properly only if the IIS6.0 is running in 32bit mode, but WSS needs IIS to be running in 64bit mode on a x64 platform, given that IIS6.0 has no 32bit and 64bit integration, they cannot be work properly at the same time.

Ø  For 2006, and 2006 R2/2006 R2 SP1, BAS feature is included, it needs share point adapter to be configured against WSS2.0, known walk around for WSS 2.0 on x64 platform is needed.

·         IIS7.0(win2k8sp1/win2k8sp2/vista sp2)

BizTalk officially supported:

2009: win2k8sp1, vista sp2 (official automation platform), win2k8sp2(compatibility testing platform)

2010: win2k8sp2, vista sp2

Related specification:  has application pool, has 32bit and 64bit integration

WSS cannot be installed on client OS, so WSS adapter is unavailable on vista sp2 platforms.

On win2k8 x86 platforms:

Ø  BAM Portal and WSS adapter all can be configured successfully and work properly.

Ø  BAM Portal can be configured in the site extended by WSS.

                                On win2k8 x64 platforms:

Ø  BAM Portal can be configured and used properly when the application pool for it is 32bit enabled, WSS administrative site and SharePoint site for WSS adapter will work fine  when the application pools for them are 64bit enabled, these 2 conditions can be satisfied because that IIS6.0 has 32bit and 64bit integration.

Ø  BAM Portal will work fine on the site extended by WSS.

·         IIS7.5(win2k8 r2, win7)

BizTalk officially supported:

2009: win2k8 r2 rc, win7

2010: win2k8 r2, win7

Related specification:  has application pool, has 32bit and 64bit integration

WSS cannot be installed on client OS, so WSS adapter is unavailable on win7 platforms.

On win2k8 x86 platforms:

Ø  BAM Portal and WSS adapter all can be configured successfully and work properly.

Ø  BAM Portal can be configured in the site extended by WSS.

                                On win2k8 x64 platforms:

Ø  BAM Portal can be configured and used properly when the application pool for it is 32bit enabled, WSS administrative site and SharePoint site for WSS adapter will work fine  when the application pools for them are 64bit enabled, these 2 conditions can be satisfied because that IIS6.0 has 32bit and 64bit integration.

Ø  BAM Portal will work fine on the site extended by WSS.

 

Even that we know BAM Portal can be configured on a site extended by WSS and work fine, I do not think there is any reason we should do this, first of all, the configuration for this in IIS is complex, secondly, there is no benefit out of it. The best way I can say is that we configure BAM Portal on a site, using WSS to extend another Site and configure WSS adapter on it, this is simple and this can avoid unexpected exceptions. An official artical has below comments:

ASP.NET 4 Web Sites Fail to Start on Computers Where SharePoint Is Installed

Web servers that run SharePoint have a Web.config file that is deployed at the root of a SharePoint Web site (for example, c:/inetpub/wwwroot/web.config for Default Web Site). In this Web.config file, SharePoint sets a custom partial-trust level named WSS_Minimal.

If you try to run an ASP.NET 4 Web site that is deployed as a child of this type of SharePoint Web site, you will see the following error:

Could not find permission set named 'ASP.Net'.

This error occurs because the ASP.NET 4 code access security (CAS) infrastructure looks for a permission set named ASP.Net. However, the partial trust configuration file that is referenced by WSS_Minimal does not contain any permission sets with that name.

                Currently there is not a version of SharePoint available that is compatible with ASP.NET. As a result, you should not attempt to 

                run an ASP.NET 4 Web site as a child site underneath SharePoint Web sites.