Support Thread

Migrating To New Server Miscellaneous Bugs

Migrating To New Server Miscellaneous Bugs — APG vNext Guide

Migrating To New Server Miscellaneous Bugs — this archived support thread from the APG vNext community covers a reported issue and its resolution.

Troubleshooting This Issue

  1. Set customErrors mode="Off" in web.config to expose the full error and stack trace.
  2. Check Windows Event Viewer → Application log for ASP.NET exceptions.
  3. Review Admin Panel → Logs → Error Log for timestamped application errors.
  4. Restart the IIS Application Pool to clear stale state.
  5. Verify the database connection string and run any pending upgrade SQL scripts.

Related Resources

Migrating APG vNext to a New Server

Migrating an active APG vNext forum to a new server is a multi-step process that requires careful planning to minimize downtime and prevent data loss. Whether you are moving to better hardware, a new hosting provider, or a cloud platform, the migration sequence follows the same general pattern: prepare the target server, transfer the database, deploy application files, update configuration, test thoroughly, and switch DNS to point to the new server.

Step 1: Prepare the Target Server

Install and configure IIS with the same .NET Framework version as the source server. Install the URL Rewrite Module if it is not present by default. Create the application pool with the same .NET CLR version and pipeline mode (Integrated) as the source. Verify that SQL Server is installed and accessible with appropriate permissions. Clone the source server's web.config changes to the new environment before deploying application files to avoid a partially configured state during testing.

Step 2: Transfer the Database

Take a full backup of the source SQL Server database using SQL Server Management Studio or the BACKUP DATABASE T-SQL command. Restore this backup to the target SQL Server instance. Create a SQL login on the target with the same credentials used in the connection string, and grant db_owner permissions on the restored database. Verify the restored database has the correct collation setting matching the source, as collation mismatches can cause character encoding issues with forum post content after migration.

Step 3: Deploy Application Files

Copy all APG vNext application files to the target server, preserving the directory structure. Pay special attention to the uploads and attachments folder, which may contain significant data not tracked in version control. Update the connection string in web.config to point to the target SQL Server instance. Update any absolute paths in configuration files that reference the old server's file system structure. Verify file system permissions on the application folder allow the IIS application pool identity to read and write as required by APG vNext.

Common Post-Migration Bugs

The most common issues after APG vNext migrations include: email delivery failures caused by the new server's outbound SMTP configuration differing from the source, broken image and attachment links caused by incorrect base URL settings in the database still referencing the old server, session timeout issues caused by machine key changes between servers, and permission errors caused by IIS application pool identity not having write access to the uploads folder on the new server. Verify each of these areas explicitly after completing the migration before switching DNS to direct live traffic to the new server.

APG vNext's configuration options for this feature are designed to be flexible enough to accommodate the needs of small hobbyist communities as well as large enterprise deployments running on dedicated server hardware. When in doubt about the right settings for your specific deployment context, consult the official APG vNext documentation in the Knowledge Base or ask in the community support forum where experienced administrators share their configurations and provide guidance based on real-world deployment experience across many different server environments and community sizes. APG vNext's configuration options for this feature are designed to be flexible enough to accommodate the needs of small hobbyist communities as well as large enterprise deployments running on dedicated server hardware. When in doubt about the right settings for your specific deployment context, consult the official APG vNext documentation in the Knowledge Base or ask in the community support forum where experienced administrators share their configurations and provide guidance based on real-world deployment experience across many different server environments and community sizes. APG vNext's configuration options for this feature are designed to be flexible enough to accommodate the needs of small hobbyist communities as well as large enterprise deployments running on dedicated server hardware. When in doubt about the right settings for your specific deployment context, consult the official APG vNext documentation in the Knowledge Base or ask in the community support forum where experienced administrators share their configurations and provide guidance based on real-world deployment experience across many different server environments and community sizes. APG vNext's configuration options for this feature are designed to be flexible enough to accommodate the needs of small hobbyist communities as well as large enterprise deployments running on dedicated server hardware. When in doubt about the right settings for your specific deployment context, consult the official APG vNext documentation in the Knowledge Base or ask in the community support forum where experienced administrators share their configurations and provide guidance based on real-world deployment experience across many different server environments and community sizes.

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