Error when user updates his profile

This archived support thread addresses Error when user updates his profile. 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.

Error When User Updates Profile in APG vNext

Profile update errors in APG vNext typically manifest as a 500 error or a silent failure where the form submits but no changes are saved. The most common causes are validation failures on custom profile fields, email format validation, or avatar upload processing errors.

Diagnosing the Profile Error

-- Check error log filtered to profile updates:
SELECT ErrorMessage, RequestUrl, OccurredAt
FROM   apg_ErrorLog
WHERE  RequestUrl LIKE '%/profile%' OR RequestUrl LIKE '%/account%'
ORDER  BY OccurredAt DESC;

Fix 1: Duplicate Email Address

If a member tries to change their email to one already used by another account, APG vNext should show a validation error. If it fails silently instead, there's a missing uniqueness check in the profile save logic. Check:

-- Find duplicate emails:
SELECT Email, COUNT(*) AS Count
FROM   apg_Members
GROUP  BY Email
HAVING COUNT(*) > 1;

Fix 2: Custom Profile Field Validation

Custom registration fields with Required=true that also appear in the profile edit form will cause a validation error if left blank during profile update. Either set the field to not-required in the profile edit context, or pre-populate it:

<add key="APG.Profile.RequireCustomFields" value="false" />

Fix 3: Avatar Processing Timeout

If the profile update includes an avatar upload and the avatar processing times out (see Avatar Page Hangs thread), the whole profile save can fail. Process avatar uploads asynchronously:

<add key="APG.Avatar.ProcessAsync" value="true" />

Profile Update Validation and Error Messages

APG vNext validates all profile update submissions server-side before saving. Validation errors are displayed as inline messages next to the relevant field (e.g., Display name already taken, Bio exceeds 500 characters, Invalid website URL format). If a profile update fails with a generic error rather than a specific validation message, the issue is likely in the file upload or database write phase rather than the validation phase. Common causes of non-validation profile update errors include: the upfiles/avatars/ folder lacking write permission for the IIS application pool identity (causing avatar upload failures), the database column for the bio or custom field being too short for the submitted value, and the image resize queue processor being offline when the profile update includes a new avatar that requires resizing. Check the APG error log for the specific exception and stack trace after any generic profile update failure to identify the exact cause.

Profile Privacy Settings

APG vNext member profiles support granular privacy controls that allow members to choose which profile fields are visible to other members, registered members only, or only to themselves and administrators. Privacy settings are stored per-field in the member settings table. A profile update error that only occurs for certain field values can sometimes be traced to a privacy setting conflict — for example, a member attempting to set their email visibility to Public when the forum administrator has configured a site-wide policy restricting email visibility to Private. Ensure that the privacy policy labels in the profile update form accurately reflect the site-wide privacy restrictions so members understand which settings are available to them.

Member Avatar Processing Pipeline

When a member uploads a new avatar during a profile update, APG vNext queues the image for asynchronous processing. The processing pipeline validates the file type, resizes the image to the configured avatar dimensions (default: 100×100 px and 50×50 px thumbnails), converts it to JPEG or WebP depending on the server configuration, and saves it to the upfiles/avatars/ directory. If any step fails — for example, because the GDI+ image processing library is not available on the server, or the upfiles/avatars/ folder lacks write permissions — the avatar update fails silently and the member's old avatar continues to be displayed. Configure email notification to the administrator on avatar processing failure in Admin Panel → Members → Avatar Settings → Notify on Processing Failure, so that infrastructure problems are detected quickly without waiting for member bug reports.

Related Resources

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