IIS7

Enable Classic ASP, Server Side Includes, and ASP.NET

When you are adding the Web Server (IIS) role to Windows Server 2008 that the ASP feature is not added by default.

Start Server Manager select the Web Server (IIS) Role. Click on Add Role Services. Make sure you have ASP and Server Side Includes and ASP.NET selected.

Also select the IIS 6 Management Compatibility features which are found near the bottom of the list of features.

Make sure ASP.NET v4 is properly registered with IIS

Depending on the sequence of install and role addition operations it may happen that ASP.NET v4 is not properly registered with IIS.

To verify, open a Command Prompt window as an Administrator, navigate to C:\Windows\Microsoft.NET\Framework\v4.0.30319 folder, and execute this command:
aspnet_regiis -lv

The output produced should contain a line like this one:

4.0.30319.0 C:\Windows\Microsoft.NET\Framework\v4.0.30319\aspnet_isapi.dll

If it does not, execute this command:

aspnet_regiis.exe -i

If your server is a 64-bit machine, you may need to do the same from C:\Windows\Microsoft.NET\Framework64\v4.0.30319 folder.

Create a Application Pool

You need to run each of your Dovetail web applications in their own Application Pool.

  1. To open IIS Manager, select Start - type IIS, and select Internet Information Services (IIS) Manager
  2. Click on your computer host name to expand the top-level node.
  3. Click on Application Pools
  4. Right-click on Application Pools and choose Add Application Pool
  5. Enter a name, such as DovetailAgent_AppPool
  6. Set the .NET Framework Version to version 4.
  7. Set the Managed Pipeline Mode to Integrated.
  8. If you are running a 64bit operating system, and using the 32-bit Dovetail SDK, you will need to Enable 32-Bit Applications for the Application Pool. Click on Advanced Settings… Set Enable 32-Bit Applications to True. Note that his is not the recommendation configuration.
    The recommendation is to use the 64-bit Dovetail SDK on 64-bit systems, and leave the Enable 32-Bit Applications application pool setting set to False.

Create the web application(s)

  1. To open IIS Manager, select Start - type IIS, and select Internet Information Services (IIS) Manager
  2. Click on your computer host name to expand the top-level node.
  3. Right-click Default Web Site and select Add Application
  4. In the Alias text box, type a short name (alias) for the directory into which the Dovetail Admin product was installed (i.e. agent). The alias is what users see as part of the URL path when they are browsing to the Dovetail Admin web application (for example, http://www.MyCompany.com/< agent >).
  5. Enter the path, or browse to the directory which contains the Dovetail Admin web application files (the pages folder under the installation directory).
  6. Select the Application Pool that you created earlier
  7. Select OK.

Enable Parent Paths

Parent Paths need to be enabled when an asp page includes a script with a path containing a ".." An example would be:

<!--#include file="../include/inc_room.asp"-->

Dovetail Admin does use parent paths.

  1. Navigate to your web application in IIS7 Manager.
  2. Click on ASP.
  3. Set Enable Parent Paths to True.
  4. Click on Apply.

Enforce Compatibility Level

For Dovetail Admin to work with all versions of MS Internet Explorer equal to and higher than 8, a proper HTTP Response Header must be set:

  1. Navigate to your web application in IIS7 Manager.
  2. Click on HTTP Response Headers.
  3. On Actions pane, click Add.
  4. Use X-UA-Compatible as a header name and IE=5 as a value.

Click OK to save.

Make sure all managed modules can process all requests

Dovetail Admin ships with web.config file containing this setting:

<modules runAllManagedModulesForAllRequests="true"></modules>

It is required on Windows Server 2008 or earlier. If not present, it may cause HTTP error 404 on clone and delete actions against user-defined pop-up list element.

Consult this article for details.

Send Script Errors To The Browser

When you try to browse your web application you may run into this message telling you... "Something went going wrong but sorry I won't tell you what." That error looks like this:"

An error occurred on the server when processing the URL. Please contact the system administrator.
If you are the system administrator please click here to find out more about this error.

To see the actual error, you can configure the application to send errors to the browser. This is helpful when debugging a problem.

  1. Navigate to your web application in IIS7 Manager.
  2. Click on ASP.
  3. Expand the Debugging section
  4. Set Send Errors to Browser to True.
  5. Click on Apply.

Additional Information on configuring ASP applications on IIS7 is available online.

See Also

Configure the Web Server

IIS6

Next

Edit the fc.env File
IIS7