Unknown Error

[nathanielcallen]

I'm receiving this error in the error logs for a failed self-registration:
Failed to create external user for portal. Error: [We encountered an unknown error while processing this request.]
The package is installed in both Sandbox and Production. I am receiving this error in Sandbox. I have not used it in production.

[jloweSFDC]

Hi there, This one is a Salesforce error, usually because something isn't configured correctly with the site. Initially I'd recommend checking that the site is Active and Published and that Self Registration is enabled in the Login & Registration workspace settings. Also check the members, and ensure there is a profile added and that profile is set in the workspace settings under Login & Registration as well. This post might help: https://carvingintheclouds.blogspot.com/2014/09/your-request-cannot-be-processed-at.html

…

On Fri, 13 Sept 2024 at 04:12, nathanielcallen ***@***.***> wrote: I'm receiving this error in the error logs for a failed self-registration: *Failed to create external user for portal. Error: [We encountered an unknown error while processing this request.]* — Reply to this email directly, view it on GitHub <#36>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ATTJUGQSHKRHZO72LE63VULZWJJYNAVCNFSM6AAAAABOEPSJFWVHI2DSMVQWIX3LMV43ASLTON2WKOZSGUZDGNZYGA4DQNQ> . You are receiving this because you are subscribed to this thread.Message ID: <SalesforceLabs/Configurable-Self-Registration-for-Experience-Cloud/issues/36 @github.com>

[cjclark65]

We are also experiencing this error. Here's our path so far:

1. Noticed self-reg failing in our Winter '25 Preview Sandbox
2. Installed newest version of the package from this month
3. Verified still getting the error
4. Went and re-verified configuration according to the documentation from the appexchange page, no updates were made as all configuration appeared consistent with what we'd had set up previously.
5. Debug logs on finest still not yielding information
6. Confirmed that site is active & published, members were set up properly, and that profile was correct in the Login & Registration settings
7. Reviewed the carvingtheclouds blog post, confirmed setup details there, re-tested, still getting the error.

I think something in Winter '25 maybe caused the issue, but not sure what--that's the only confirmable change to our org and it correlates with the bug appearing. We are using Person Accounts, if that might be a factor.

[jloweSFDC]

I have the package installed v1.8 (latest version) in my customer's sandbox org which is also on the Winter '25 preview release and I can't currently reproduce this issue. Also using Person Accounts. I read another post here: https://trailhead.salesforce.com/trailblazer-community/feed/0D54V00007TrH81SAF which might be of interest. Whilst this isn't using the package, it is calling the same API class/method as the package (Site.createExternalUser). I haven't been able to reproduce this issue as my customer has an REGEX applied to the password field so it validates that the form submission matches the right format before submitting the form. I would try some testing around this to see if this is the cause in your org.

Temporarily, you could also install the unmanaged version from the GitHub repo which will enable you to turn full debug logging on which might give more insight. This matches the AppExchange package code as long as you clone the main branch.

Otherwise, please submit the user details you are using to sign up and the org configuration in the metadata, plus the Exp. Builder settings of the component and I will try to reproduce my end where I can get at the debug logs.

[cjclark65]

Having investigated further using the page you linked @jloweSFDC I can replicate the results based on those testing conditions the user laid out. So it doesn't seem to be an issue with the component, but something going on with the baseline user registration code that's being called. Going to reopen the case with SF because it's not the package causing the issue.

[cjclark65]

Updates after a call with SF support to really dig into this:

1. Sandbox on preview for winter 25 is giving us errors (now we are getting an error message that helps: Insufficient permissions: secure query included inaccessible field
2. There is inconsistent behavior when we see this message, though--sometimes the registrations go through, sometimes they do not
3. We spun up a new, non-preview sandbox from our production org, and tested reg there--it was working as expected, no errors
4. We updated the SF Labs package in that new sandbox to version 1.8, to match what is in the full environment, and we started getting the Insufficient permissions error.

Going to go back through our config, but the query is set in the component to run as system, so not sure what's up.