January 24, 2010

Interprise Suite installation with ecommerce module

Filed under: General news — Tags: , , — Webopius @ 6:50 pm

Last week, we did an Interprise Suite CRM installation on Windows Server 2008 using IIS7. In addition to the Interprise Suite database and files, we also installed the Interprise ecommerce module (based on ASPDotNetStorefront IS).

Because Interprise and the ecommerce module are 32-bit applications and this was an install on the 64-bit Windows platform, things didn’t always go smoothly and I thought some tips might help others who are trying to do the same…

Install IIS7 with ASP.NET role services

Step 1 of the install is to use the Windows Server Manager and add a role of ‘Web Server’. This will install IIS7 and during the install you should be asked which Role Services you want to install with IIS7.

Make sure you choose ‘ASP.NET’ at this stage because we found that installing it later can cause problems or conflicts with Windows Process Activation (WPA). If you do get into difficulties, we found that an un-install of the WPA before trying to re-install IIS7 makes life a lot easier.

Along with ASP.NET roles, we also chose:

– Static Content
– Default Document
– HTTP errors
– HTTP redirection
– ISAPI extensions
– ISAPI filters
– HTTP logging
– Request monitor
– Tracing
– Basic authentication
– Windows authentication
– Request filtering
– Static content compression
– IIS Management console

Create a 32-bit application pool

Before you add your ecommerce module website to IIS7, create a new application pool capable of running 32-bit applications.

Basic settings: .NET Framework v2.x.xxxxx
Advanced settings:
Enable 32-bit applications: TRUE
Managed pipeline mode: Classic

Leave all other settings at their defaults

Make sure your Interprise Suite ecommerce site using the new Application Pool

Once you create your website configuration from within the IIS manager, make sure it is using the application pool you created. In your site’s ‘Basic Settings’, set the Application Pool to the correct pool.

Resolve web.config conflicts

IIS7 uses a new method of managing the web.config application settings based on a hierarchy. You may find once you’ve installed Interprise and ASPDotNetStorefront IS that some of your new web.config settings conflict with the default IIS7 settings.

To check this, from within your web site’s configuration in IIS manager, double click on the various configuration icons – for example ‘.NET compilation’. IIS will inform you of any errors as you click through the icons.

Unfortunately, to resolve this, it’s a case of editing your web.config (or the default web.config) and removing conflicts.


If all this sound too much, why not get in touch with Webopius. We can help you get your site installed and running. We also provide ongoing operational support such as hosting, remote backups, site enhancements and other Interprise/ASPDotNetStorefront development services….

  • Tags