Support Thread

[APG vNext]

📅 👤 ASP Playground
[APG vNext] — APG vNext Guide

Welcome to [APG vNext] — part of the APG vNext community forum.

About This Section

4.3 is throwing an error when I click on member list Remove non ASCII character in SEO URL System.IndexOutOfRangeException: Cannot find table 0.

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.

APG vNext Community Forum — What's Inside

This section of the ASP Playground community is the primary discussion area for everything related to APG vNext — the ASP.NET forum and community platform. Whether you are evaluating the software for the first time, troubleshooting an existing installation, or contributing feature suggestions, this is the right place to start.

Forum Sections at a Glance

  • Release Announcements: Official release threads for each APG vNext version, including changelogs and upgrade SQL scripts
  • Support & Bug Reports: Technical issues, error messages, and configuration problems — post with full details for fastest resolution
  • Feature Requests: Suggest improvements and vote on existing proposals — high-vote requests are prioritised in the roadmap
  • Customisation: CSS skinning, custom BBCode, template overrides, and integration examples
  • Showcase: Share your APG vNext-powered community — useful for inspiration and to demonstrate use cases to the development team

Getting Started with APG vNext

If you are new to APG vNext, the recommended reading order is:

  1. Features overview — understand what APG vNext includes out of the box
  2. Download the software — full version, no trial limitations
  3. Follow the installation guide — IIS setup, SQL Server database creation, app pool configuration
  4. Read the FAQ — covers licensing, hosting requirements, and common first-run questions
  5. Post in this forum if you hit an issue not covered by the docs

Server Requirements for APG vNext

-- Minimum requirements for APG vNext 5.x
OS:          Windows Server 2016 / 2019 / 2022
Web Server:  IIS 8.5+ with ASP.NET 4.8
Database:    SQL Server 2014+ (Express edition supported)
RAM:         2 GB minimum, 4 GB recommended for >1000 active members
Disk:        50 MB app files + database + upfiles folder growth

Community Guidelines

How to Get the Best Support

The APG vNext community responds fastest to well-structured posts. Include your version number, a clear description of the problem, the exact error message (with customErrors mode="Off" enabled), and what you have already tried. Vague posts like "it doesn't work" take multiple rounds of back-and-forth before a resolution is possible — front-loading the details saves everyone time.

Reporting Bugs

Before reporting a bug, search the forum and Knowledge Base for the error message. Many apparent bugs are configuration issues with documented solutions. If you confirm it is a genuine bug, post a minimal reproduction case with your APG vNext version, hosting environment, and the steps to reproduce it reliably.

Common APG vNext Errors Discussed in This Forum

Several recurring error types appear frequently in this forum section. Here is a quick reference for the most common ones with their typical causes and resolutions:

System.IndexOutOfRangeException: Cannot find table 0

This error appears when a DataSet-based query returns fewer result sets than expected. In APG vNext, it typically means the SQL upgrade script was not fully applied — a stored procedure is returning one result set where the application expects two or more.

-- Diagnose: check which stored procedures were updated in the last upgrade:
SELECT name, modify_date
FROM   sys.objects
WHERE  type = 'P'
  AND  modify_date > DATEADD(DAY, -7, GETDATE())
ORDER  BY modify_date DESC;

-- If a SP wasn't updated, re-run just that portion of the upgrade script
-- or restore the full upgrade script and run it again (idempotent scripts handle duplicates)

Non-ASCII Characters in SEO URLs

APG vNext generates SEO-friendly URLs from thread titles. If a thread title contains non-ASCII characters (Arabic, Chinese, accented Latin, emoji), the URL generation can produce malformed slugs that cause 404 errors or duplicate URL conflicts.

-- Find threads with non-ASCII characters in their SEO slug:
SELECT ThreadID, Title, SEOSlug
FROM   apg_Threads
WHERE  SEOSlug COLLATE Latin1_General_BIN != SEOSlug COLLATE Latin1_General_CS_AS
   OR  SEOSlug LIKE N'%[^ -~]%' COLLATE Latin1_General_BIN;

-- Reset affected slugs to force regeneration:
UPDATE apg_Threads
SET    SEOSlug = NULL
WHERE  ThreadID IN (/* IDs from above query */);
-- APG vNext regenerates SEO slugs on next access

Member List Error on 4.3

The 4.3 member list error was caused by a missing LastActivityDate column or a data type mismatch in the member score column after the 4.2 to 4.3 upgrade. The full diagnosis and fix is documented in the dedicated thread: 4.3 Member List Error — Root Cause and Fix.

Version Roadmap and Release Schedule

APG vNext follows a minor-version release cycle of approximately 3-6 months between stable releases. Hotfix releases (e.g., 5.1.1) are issued within days of a critical bug report. The development team posts release announcements in this forum section and on the release blog. Subscribe to the APG vNext Support forum section to receive email notifications when new releases are posted.

Related Resources

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