APG vNext Support

Welcome to APG vNext Support — part of the APG vNext community forum.

About This Section

isaacc 16 Replies 1022 Views Hot! Last Update: APGvNext Sam 2 Hey Sam, I like the new theme FreddyD 2 Replies 8412 Views Hot!

Community Guidelines

• Search before posting — your question may already be answered
• Include your APG vNext version and server environment when reporting issues
• Attach error messages and relevant code snippets to help the team diagnose problems faster

Browse all categories in the community forum or check the FAQ for quick answers.

What to Expect from APG vNext Support

The APG vNext support section is the primary hub for all technical questions, bug reports, feature requests, and upgrade assistance. This section is actively monitored by the development team, and most questions receive a response within one business day. The community also contributes significantly — many common issues have been resolved by experienced administrators who have encountered and solved them in their own deployments.

Before You Post

To get the fastest and most accurate help, gather this information before opening a new thread:

• APG vNext version: Admin Panel → About → Version Number
• IIS version and Windows Server version
• SQL Server version (run SELECT @@VERSION in SSMS)
• .NET Framework version targeted in web.config
• The exact error message — enable customErrors mode="Off" to get the full stack trace
• What changed recently — upgrade, configuration change, hosting migration

Common Support Categories

Issues in this section fall into a few recurring categories. Check the Knowledge Base before posting — many have documented solutions:

• Installation and setup — IIS configuration, database creation, app pool settings
• Upgrade errors — SQL script failures, schema mismatches, missing assemblies
• Email and notifications — SMTP configuration, digest not sending, email going to spam
• Authentication — SSO, LDAP, Active Directory integration issues
• Performance — slow page loads, database query timeouts, memory leaks
• Customisation — CSS skinning, custom pages, BBCode extensions

Using the Knowledge Base Effectively

The APG vNext Knowledge Base is a curated collection of resolved issues and how-to guides maintained by the development team. It is searchable and organised by topic. Before posting a new thread, search the Knowledge Base for your error message or feature question — the majority of common issues are documented there with step-by-step solutions.

Posting a Good Bug Report

For bug reports, provide a minimal reproduction case. A good bug report includes:

1. The exact steps to reproduce the issue (numbered list)
2. What you expected to happen
3. What actually happened
4. The full error message from customErrors mode="Off" or the Windows Event Log
5. Your APG vNext version, .NET version, and SQL Server version

<!-- Enable full error display for debugging -->
<system.web>
  <customErrors mode="Off" />
</system.web>
<!-- Remember to restore to "RemoteOnly" after debugging -->

Diagnosing APG vNext Errors Step by Step

Step 1 — Check the APG Error Log First

Before enabling customErrors mode="Off" (which leaks error details to end users), check the APG vNext built-in error log. It captures application exceptions with full stack traces without exposing them publicly:

-- Query recent errors from the APG error log table:
SELECT TOP 20
    ErrorType,
    ErrorMessage,
    StackTrace,
    RequestUrl,
    UserID,
    OccurredAt
FROM apg_ErrorLog
ORDER BY OccurredAt DESC;

Admin Panel → Logs → Error Log shows the same data in a filterable UI. Filter by date and error type to focus on the most recent issues.

Step 2 — Check Windows Event Log

Exceptions that crash the ASP.NET worker process (not handled by APG) appear only in the Windows Event Log, not in the APG error log. Check using PowerShell:

Get-EventLog -LogName Application -Source "ASP.NET*" -Newest 20 |
Select-Object TimeGenerated, Source, Message |
Format-List

Step 3 — IIS Failed Request Tracing (FREB)

For intermittent issues that don't appear in either error log (e.g., a request that hangs and never produces an error), enable IIS Failed Request Tracing for the forum site. This captures detailed timing information about every step of the request processing pipeline:

# Enable FREB via appcmd (IIS 7+):
appcmd.exe set site "Your Forum Site" /traceFailedRequestsLogging.enabled:true
appcmd.exe add config "Your Forum Site" -section:traceFailedRequests ^^
    /+"[path='*.aspx']"
appcmd.exe add config "Your Forum Site" -section:traceFailedRequests ^^
    /+"[path='*.aspx'].failureDefinitions[statusCodes='500,502-504']"

FREB log files are saved to %SystemDrive%\inetpub\logs\FailedReqLogFiles\ and can be opened as HTML in a browser.

Getting Help for Hosting-Specific Issues

Many APG vNext support questions are hosting environment-specific rather than application bugs. If you're on shared hosting where you cannot access the Windows Event Log or IIS configuration, your hosting provider's support is the right first contact for the following types of issues:

• Application pool recycling too aggressively (symptoms: session loss, in-memory cache clearing unexpectedly)
• File system permission restrictions preventing APG from writing to upfiles
• Trust level restrictions (medium trust vs. full trust) preventing reflection or unmanaged code
• SQL Server connection pool exhaustion under load

APG vNext requires Full Trust in IIS. If your hosting plan only offers medium trust, APG vNext will not function correctly. Confirm with your host before purchasing a license for a shared hosting environment.

Support Resources

Quick Links

• Knowledge Base — solutions to common issues
• FAQ — frequently asked questions
• Installation Guide
• Upgrade Guide
• Download APG vNext
• Contact the Development Team

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