My forum went down today for a few minutes (that I'm aware of). Here is the log.

This archived support thread addresses My forum went down today for a few minutes (that I'm aware of). Here is the log.. 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.

Diagnosing Forum Downtime from IIS and SQL Server Logs

When APG vNext experiences brief unexpected downtime, reviewing the Windows event logs during the outage window is the fastest way to identify the cause. The most common culprits are IIS application pool crashes or recycles, Windows Update applying a restart without administrator awareness, SQL Server service interruptions, and database connection exhaustion from a traffic spike or a slow query holding connections longer than expected. Identifying the specific cause is essential before making configuration changes to prevent future occurrences.

Checking Application Event Log

Open Windows Event Viewer and navigate to Windows Logs > Application. Filter by the time range of the outage. Look for Error and Warning events from sources WAS (Windows Activation Service), W3SVC (IIS), or MSSQLSERVER. WAS events typically describe application pool shutdowns with specific failure reasons such as rapid fail protection triggered by too many worker process crashes in a short window. W3SVC events describe site starts and stops. MSSQLSERVER events describe SQL Server service state changes and database errors.

Checking System Event Log

Navigate to Windows Logs > System and check for events from WindowsUpdateClient indicating that a Windows Update installation triggered a system restart. If the restart time matches the downtime window, configure Windows Update to apply updates during a maintenance window that does not overlap with peak forum usage hours. Events from Service Control Manager describing service stops and starts are also visible in the System log and can confirm whether SQL Server, IIS, or another required service was restarted during the outage period.

APG vNext Application Error Log

APG vNext writes its own application error log accessible in the admin panel under Admin > Reports > Event Log. This log captures ASP.NET exceptions, database query failures, email sending errors, and other application-level events. If the forum returned 500 errors during the outage rather than being completely unreachable, the application error log will contain the specific exception that triggered the failures, providing a more precise diagnosis than the Windows event logs which capture infrastructure-level events rather than application-level code execution errors.

Preventing Recurrence

After identifying the cause, apply the appropriate remediation. Schedule IIS application pool recycling for off-peak hours. Configure Windows Update to defer restarts to a maintenance window. Add SQL connection retry parameters to the APG vNext connection string. Implement external uptime monitoring with HTTP checks every 60 seconds to alert the admin team the moment the forum becomes unresponsive, enabling faster response and recovery before the majority of members notice the outage.

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