Iis 6 Setup Configurations Needed To Run Apg Vnext

Iis 6 Setup Configurations Needed To Run Apg Vnext — a configuration and setup topic from the APG vNext support community.

Key Configuration Points

• IIS App Pool: .NET 4.0 Integrated Pipeline mode is required.
• Connection String: Verify SQL Server name, database, and credentials in web.config.
• File Permissions: App pool identity needs read/write on the upfiles folder.
• URL Rewriting: Install IIS URL Rewrite 2.0 module for clean SEO-friendly URLs.
• Full-Text Search: Enable SQL Server Full-Text Indexing for forum search.

More Help

• Installation Guide
• Upgrade Guide
• Support Forum

Step-by-Step IIS 6 Setup for APG vNext

Running APG vNext on IIS 6 requires several non-default configurations because IIS 6 predates many of the ASP.NET pipeline improvements introduced in IIS 7. Follow these steps carefully to ensure the application initialises correctly and handles URL routing without 404 errors on extensionless URLs.

Step 1 — Install ASP.NET 4.x on the Server

APG vNext requires ASP.NET 4.0 or higher. On Windows Server 2003, install the .NET Framework 4.0 from the Microsoft download centre. After installation, register the ASP.NET ISAPI with IIS 6 by running the following command in an elevated command prompt:

C:\Windows\Microsoft.NET\Framework\v4.0.30319\aspnet_regiis.exe -i

This command registers the ASP.NET 4.0 ISAPI extension with IIS and maps the standard ASP.NET file extensions (.aspx, .axd, .asmx) to the ASP.NET ISAPI DLL. Verify the registration was successful by opening IIS Manager → Web Service Extensions → ASP.NET v4.0.30319 and confirming the status shows Allowed.

Step 2 — Configure Wildcard Mapping

APG vNext uses extensionless URLs (e.g., /forum, /members, /search) that IIS 6 does not route to ASP.NET by default. Enable wildcard application mapping to route all requests through ASP.NET. In IIS Manager, right-click the website → Properties → Home Directory tab → Configuration → Mappings → Insert (wildcard). Set the executable path to C:\Windows\Microsoft.NET\Framework\v4.0.30319\aspnet_isapi.dll and uncheck Verify that file exists.

Step 3 — Create a Dedicated Application Pool

In IIS Manager, expand Application Pools → New → Application Pool → Name it APGvNextPool. In the pool properties, set .NET Framework version to v4.0 and Identity to Network Service (or a dedicated service account). Assign the APG vNext website to this pool by right-clicking the website → Properties → Home Directory tab → Application pool: APGvNextPool.

Step 4 — Set Full Trust in web.config

Add or update the following in the APG vNext web.config within <system.web>:

<trust level="Full" />

Full Trust is required for APG vNext to access the file system (uploads, log files), send SMTP email, and use all required .NET APIs. Restart the IIS application pool after saving the web.config to apply the trust level change.

Step 5 — Configure Connection String

Add the SQL Server connection string to web.config in the connectionStrings section:

<connectionStrings>
  <add name="APGvNext" 
       connectionString="Server=.\SQLEXPRESS;Database=APGvNext;
                         Integrated Security=True;" 
       providerName="System.Data.SqlClient" />
</connectionStrings>

Test the connection by browsing to the APG vNext installation URL. If the database connection fails, verify the SQL Server service is running, the database name is correct, and the IIS application pool identity has the db_owner or appropriate SQL Server role for the APG vNext database.

Common IIS 6 Setup Errors

The most common error during APG vNext setup on IIS 6 is receiving a 404 for all URLs except the homepage. This indicates wildcard mapping is not configured or not saved correctly — revisit Step 2. The second most common error is a 403.14 Directory Listing Denied error, which indicates the default document is not configured — add default.aspx to the Documents list in the website properties. A SecurityException error indicates Full Trust was not correctly applied — revisit Step 4 and verify the Application Pool was recycled after the web.config change.

Related Resources

• IIS 6 Configuration Reference
• Full Trust Configuration
• Knowledge Base

Post-Setup Verification Checklist

After completing the initial IIS 6 setup, run through this verification checklist before declaring the installation production-ready. First, browse to the forum home page and verify the page loads without errors. Second, register a new member account and verify the confirmation email is received. Third, log in with the admin account and open Admin Panel → System → About to confirm the correct APG vNext version is displayed. Fourth, post a test thread in a test forum category and verify it appears in the thread list. Fifth, try accessing a forum category and verify the URL uses the clean routed path rather than a querystring. Sixth, verify image uploads work by attaching a test image to a post. Seventh, check the APG error log (Admin Panel → System → Error Log) to confirm it is empty or contains only informational entries. A successful checklist completion confirms the IIS 6 installation is working correctly end-to-end.

Upgrade Path from IIS 6

Migrating from IIS 6 to a modern IIS version eliminates the wildcard mapping requirement and unlocks performance improvements like kernel-mode request queuing, output caching improvements, and the Integrated Pipeline mode. Migrating is typically a same-day task: provision a new server with Windows Server 2022 and IIS 10, copy the APG vNext application files and web.config, restore the database backup, update the connection string, verify the IIS application pool is in Integrated Pipeline mode, and test the full checklist above. DNS is updated to point the domain to the new server only after verification is complete, ensuring zero downtime from the member perspective.

Looking for more help? Browse the support forum or check the Knowledge Base.