Beta 2 installation issue

This community thread discusses Beta 2 installation issue — a topic related to setting up and configuring APG vNext on your server.

Overview

Getting APG vNext running correctly requires proper IIS configuration, a SQL Server database, and correct settings in your web.config file. Common setup issues are typically related to one of these areas.

Common Configuration Checklist

IIS Application Pool: Set to .NET 4.0 Integrated Pipeline. APG vNext is not compatible with Classic mode.
Database Connection String: Verify the server name, database name, username, and password in web.config.
File Permissions: The IIS app pool identity must have read/write access to the upfiles folder.
URL Rewriting: Install the IIS URL Rewrite module for SEO-friendly URLs.
Full-Text Search: Enable Full-Text Indexing in SQL Server for the search feature to work.

Get Help

If you are experiencing an issue not covered here, post in the support forum with your error message and server configuration details. See also: Installation Guide | FAQ

Resolving Beta 2 Installation Issues in APG vNext

Installing a beta release of APG vNext on an existing IIS server can surface issues that don't appear in stable builds — incomplete database migrations, missing configuration keys, or assembly version conflicts. This guide covers the most common Beta 2 installation failures and their resolutions.

Pre-Installation Checklist

Back up your existing database before running any migration script
Confirm .NET Framework version matches the beta's requirement (usually 4.8+)
Clear the bin/ and obj/ folders before deploying new DLLs
Recycle the IIS application pool after deployment

Common Error: "Could not load file or assembly"

This appears when the beta references a DLL version that differs from what's in the GAC or bin/. Fix:

<!-- web.config: force specific assembly version -->
<dependentAssembly>
  <assemblyIdentity name="Newtonsoft.Json"
                    publicKeyToken="30ad4fe6b2a6aeed" />
  <bindingRedirect oldVersion="0.0.0.0-13.0.3.0"
                   newVersion="13.0.3.0" />
</dependentAssembly>

Common Error: "Invalid object name 'apg_NewTable'"

The beta's database migration script didn't run or failed silently. Run it manually:

-- Run from SQL Server Management Studio:
-- File: /install/sql/beta2-migration.sql
USE [YourForumDB];
GO
-- Check if migration already ran:
IF NOT EXISTS (SELECT 1 FROM apg_Settings WHERE SettingKey = 'SchemaVersion' AND SettingValue = 'beta2')
BEGIN
  -- Run migration here
  EXEC sp_executesql N'ALTER TABLE apg_Members ADD Beta2Field NVARCHAR(100) NULL';
  INSERT INTO apg_Settings VALUES ('SchemaVersion','beta2',GETDATE());
END

Reverting to Stable if Beta Fails

If the beta installation cannot be resolved, restore from backup and redeploy the last stable release. Beta builds are not covered by standard support SLAs — use a staging environment for beta testing whenever possible.

IIS Configuration Errors During Beta Installation

Beta releases of APG vNext often introduce new IIS configuration requirements not present in the stable release. The most common IIS-level errors during beta installation are:

HTTP Error 500.19 — Invalid Configuration

This error occurs when the beta's web.config references an IIS module or configuration section that isn't registered on the server. Check the errorCode in the detailed 500.19 page:

Error Code: 0x8007000d
Reason: Cannot read configuration file
Fix: Run IIS Express / Full IIS registration for the new module:

%windir%\Microsoft.NET\Framework64\v4.0.30319\aspnet_regiis.exe -iru
# Followed by recycling the application pool

HTTP Error 403.14 — Directory Listing Denied

If the beta's default document isn't configured correctly, IIS returns 403.14. Ensure Default.aspx is in the IIS default documents list and that the APG vNext startup route is registered:

<!-- web.config: ensure default document -->
<system.webServer>
  <defaultDocument>
    <files>
      <add value="Default.aspx" />
    </files>
  </defaultDocument>
</system.webServer>

Database Migration Failures During Beta 2 Install

Beta database migration scripts may contain errors or depend on schema changes from earlier beta builds. If you are installing Beta 2 fresh (not upgrading from Beta 1), run the base schema script first, then the beta migration script:

-- Check current schema version before running migration:
SELECT SettingKey, SettingValue, ModifiedDate
FROM   apg_Settings
WHERE  SettingKey LIKE '%Version%' OR SettingKey LIKE '%Schema%'
ORDER  BY SettingKey;

-- Expected output for a clean Beta 2 install:
-- SchemaVersion: 4.2.0-beta2
-- DataVersion:   4.2.0-beta2

Rollback Procedure if Beta Fails Mid-Migration

-- If the migration script failed partway, identify orphaned objects:
SELECT TABLE_NAME FROM INFORMATION_SCHEMA.TABLES
WHERE  TABLE_NAME LIKE 'apg_%'
ORDER  BY TABLE_NAME;

-- Restore from backup:
USE master;
RESTORE DATABASE [YourForumDB]
FROM DISK = N'C:\Backups\YourForumDB_preinstall.bak'
WITH REPLACE, RECOVERY;

-- Then redeploy the stable release instead of the beta

Reporting Beta Bugs Effectively

When reporting installation issues for a beta release, include:

The exact beta version number and build date from the release notes
Whether you are doing a fresh install or upgrading from a previous version
The SQL Server version (SELECT @@VERSION) and .NET Framework version
The full error message from IIS Event Viewer or APG vNext's error log
The stack trace from App_Data/logs/error.log

Lessons Learned: Beta Testing Best Practices

Running a beta version of APG vNext in a staging environment before production significantly reduces installation risk. A staging environment that mirrors your production IIS version, SQL Server version, and .NET Framework version will surface compatibility issues before they affect live community members. The time spent setting up a staging clone is consistently less than the time required to recover from a failed production beta deployment. Consider automating this with a snapshot-based VM or a Docker container that replicates the production environment for each major upgrade test.

Related Resources

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