Problems with Batch User Import

This archived support thread addresses Problems with Batch User Import. 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.

Troubleshooting Batch User Import Issues in APG vNext

The batch user import feature in APG vNext allows administrators to import multiple user accounts at once from a CSV or XML file, which is useful when migrating from another forum platform, onboarding users from an external membership system, or setting up a new community with a pre-existing member list. Import errors can occur for a variety of reasons and the error messages produced by the import process provide the best starting point for diagnosis.

Common Import File Format Errors

The most frequent cause of batch import failures is the import file not conforming to the expected format. APG vNext's import parser requires specific column headers in a specific order, UTF-8 encoding without a BOM (byte order mark), and comma-separated values with fields containing commas enclosed in double quotes. Verify the file structure matches the template provided in Admin > User Import > Download Template. Files generated by Microsoft Excel may use Windows-1252 encoding by default rather than UTF-8, causing international character corruption during import.

Handling Duplicate Usernames and Emails

APG vNext rejects import records that contain a username or email address already registered in the forum. When importing users who may already have accounts from a previous import or from normal registration, pre-process the import file to remove duplicates by comparing against an export of existing members. Alternatively, use the Skip Duplicates option in the import configuration if your APG vNext version supports it, which continues the import and logs skipped records rather than failing the entire batch when a duplicate is encountered.

Password Hash Compatibility

When migrating users from another platform, password hashes from the source system are often not compatible with APG vNext's password hashing algorithm. Import the users with a temporary password or a flag that forces a password reset on first login. APG vNext supports importing users in a password reset required state so imported members are prompted to create a new password when they first log in, providing a seamless migration experience without requiring administrator involvement in password management for each imported account.

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