Support Thread

Error message with new version 4.3

📅 👤 ASP Playground
Error message with new version 4.3 — APG vNext Guide

This archived support thread addresses Error message with new version 4.3. The discussion below documents the reported issue and the steps taken to resolve it.

Troubleshooting Steps

When encountering errors in APG vNext, the following steps help diagnose the problem quickly:

  • Enable detailed errors: Set customErrors mode="Off" in web.config to see the full error message and stack trace.
  • Check the Windows Event Log: Application-level ASP.NET errors are logged in the Windows Event Log under Application.
  • Review the APG error log: Admin Panel → Logs → Error Log shows application-level errors with timestamps.
  • Verify recent changes: If the error appeared after an upgrade or configuration change, roll back or review what changed.

Common Fixes

  • Restart the IIS Application Pool to clear stale state
  • Verify database connectivity and run any pending SQL upgrade scripts
  • Check that all required .NET assemblies are present in the bin folder
  • Clear the ASP.NET temporary files folder (%windir%\Microsoft.NET\Framework\...\Temporary ASP.NET Files)

For further assistance, visit the support forum or review the Knowledge Base.

Error Message After Upgrading to APG vNext 4.3

APG vNext 4.3 introduced several breaking changes from 4.2, including new required database columns and a change to the skin template structure. If the 4.3 upgrade migration script was not run, or the skin was not updated, errors appear on specific pages.

Common 4.3 Post-Upgrade Errors

Error: "Invalid column name 'SeoSlug'"

APG vNext 4.3 added SEO-friendly URL slugs to thread and forum records. The migration script adds this column:

-- Run if the migration was skipped:
ALTER TABLE apg_Threads ADD SeoSlug NVARCHAR(200) NULL;
ALTER TABLE apg_Forums  ADD SeoSlug NVARCHAR(200) NULL;

-- Populate slugs for existing records:
UPDATE apg_Threads
SET    SeoSlug = LOWER(REPLACE(REPLACE(ThreadTitle,' ','-'),'''',''))
WHERE  SeoSlug IS NULL;

Error: "Quick Reply form not submitting"

Skin templates using the 4.2 data-form-id attribute (see the Quick Reply thread). Fix: update to data-apg-form.

Error: "Object reference not set - SkinHelper.GetTemplate"

A skin template file referenced in the 4.3 default skin doesn't exist in the custom skin. The 4.3 skin adds two new template files: thread-aside.ascx and member-card.ascx. Copy these from the DefaultSkin folder into your custom skin.

Confirming Migration Status

SELECT SettingValue FROM apg_Settings
WHERE  SettingKey = 'SchemaVersion';
-- Should return '4.3.0' after successful migration

Testing Upgrades in a Staging Environment

Before upgrading a production APG vNext forum, always test the upgrade on a staging environment using a clone of the production database and files. A staging environment for APG vNext requires: a separate IIS website on the same or a different server, a copy of the production database restored under a different name, and a copy of the production web.config with the connection string updated to point to the staging database. Set APG.SiteUrl in the staging web.config to the staging domain to prevent canonical URL contamination. Disable email sending in staging (APG.Email.Enabled=false) to prevent test activity from triggering member notifications.

Upgrade Dry Run Checklist

  • Back up production database and files before upgrade
  • Run migration SQL scripts on staging and verify all pass without errors
  • Deploy new application files to staging and browse all key pages (home, forum list, thread, member profile, admin panel)
  • Test post submission, file upload, and member registration flows
  • Check browser console for JavaScript errors introduced by skin changes
  • Run the APG diagnostic page (/admin/diagnostics) to verify all configuration checks pass
  • Only then schedule the production upgrade during low-traffic hours

Rollback Plan for Failed Upgrades

If the production upgrade fails or introduces critical errors that cannot be fixed quickly, a rollback plan is essential. The rollback involves: restoring the production database backup taken before the upgrade, re-deploying the previous version's application files, and confirming the old version is operational before declaring the rollback complete. Document the rollback steps and test them in staging before performing the production upgrade, so that the rollback can be executed quickly under pressure if needed. The target rollback time for an APG vNext upgrade should be under 15 minutes.

Zero-Downtime Upgrades with Blue-Green Deployment

For high-traffic APG vNext forums where even brief downtime is unacceptable, a blue-green deployment approach allows upgrading to 4.3 (or any other version) without taking the forum offline. In a blue-green setup, two identical server environments run simultaneously. The current production environment (blue) continues serving traffic while the new version is deployed and verified on the standby environment (green). Once the green environment is verified, traffic is switched from blue to green at the load balancer level — a switch that takes less than a second. If the green environment has problems, traffic is immediately switched back to blue without member impact. The main constraint for APG vNext blue-green upgrades is the shared SQL Server database: both environments must share the same database during the transition, which requires that the new version is backward-compatible with the old schema for the brief transition period.

Related Resources

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