Cli: RemoteOrgSignupFailed: A fatal signup error occurred. Please try again.

[pagner]

Summary

This bug was discussed before but it appears to be back or was never fixed.

Steps To Reproduce:

$ sfdx force:org:create -f ./config/production-scratch-def.json --json --loglevel fatal

Expected result

New scratch org is created from production org shape. (We are on the pilot)

Actual result

{ "status": 1, "name": "RemoteOrgSignupFailed", "message": "A fatal signup error occurred. Please try again. If you still see this error, contact Salesforce Support for assistance.", "exitCode": 1, "commandName": "OrgCreateCommand", "stack": "RemoteOrgSignupFailed: A fatal signup error occurred. Please try again. If you still see this error, contact Salesforce Support for assistance.\n at signup.retrieveScratchOrgInfo (/home/paul/.local/share/sfdx/client/7.27.0-714f62f9c1/node_modules/salesforce-alm/dist/lib/org/scratchOrgInfoApi.js:312:21)", "warnings": [] }

Additional information

This was an earlier issue that was closed as fixed
https://github.com/forcedotcom/cli/issues/142

SFDX CLI Version(to find the version of the CLI engine run sfdx --version):
sfdx-cli/7.27.0-714f62f9c1 linux-x64 node-v10.15.3

SFDX plugin Version(to find the version of the CLI plugin run sfdx plugins --core)
@oclif/plugin-commands 1.2.3 (core)
@oclif/plugin-help 2.2.1 (core)
@oclif/plugin-not-found 1.2.3 (core)
@oclif/plugin-plugins 1.7.8 (core)
@oclif/plugin-update 1.3.9 (core)
@oclif/plugin-warn-if-update-available 1.7.0 (core)
@oclif/plugin-which 1.0.3 (core)
@salesforce/sfdx-trust 3.0.5 (core)
analytics 1.2.1 (core)
generator 1.1.1 (core)
salesforcedx 46.17.0 (core)
├─ force-language-services 46.24.0 (core)
└─ salesforce-alm 46.22.0 (core)

sfdx-cli 7.27.0 (core)

OS and version:
Linux Ubuntu 18.04.3 (Bionic Beaver)

[packocz]

Same issue, observed since at least a week ago, only when Edition of scratch org is "Enterprise" (matches comment in this stack exchange post

CLI version: sfdx-cli/7.28.7-7bceba6f24 win32-x64 node-v10.15.3

full scratch def:
{ "orgName": "Company", "description": "Development", "country": "CZ", "hasSampleData": false, "edition": "Enterprise", "features": [ "DefaultWorkflowUser", "Communities", "Sites", "SiteDotCom" ], "settings": { "orgPreferenceSettings": { "s1DesktopEnabled": true, "translation": true, "notesReservedPref01": true, "networksEnabled": true, "pathAssistantsEnabled": true }, "userManagementSettings": { "enableEnhancedProfileMgmt": true, "enableNewProfileUI": true }, "userInterfaceSettings": { "enableHoverDetails": true, "enableInlineEdit": true, "enableQuickCreate": true }, "opportunitySettings": { "autoActivateNewReminders": true, "enableOpportunityTeam": true, "enableUpdateReminders": true }, "accountSettings": { "enableAccountTeams": true }, "notificationsSettings": { "enableMobileAppPushNotifications": true, "enableNotifications": true }, "activitiesSettings": { "enableActivityReminders": true, "enableDragAndDropScheduling": true, "enableEmailTracking": true, "enableGroupTasks": true, "enableMultidayEvents": true, "enableRecurringEvents": true, "enableRecurringTasks": true, "enableSimpleTaskCreateUI": true, "enableUNSTaskDelegatedToNotifications": true, "showHomePageHoverLinksForEvents": true, "showMyTasksHoverLinks": true } } }
UPDATE - added missing part of json to make it valid (sorry, been trying things back and forth)

[pagner]

@packocz Our issue is slightly different than yours. We are using an org shape where the edition is omitted in the scratch def. Instead of edition we use "sourceOrg" with the org Id. In fact if we use edition we will get an error that says to not use it when defining an org shape.

[pagner]

Quite a few others are having the same problem as documented here:

https://success.salesforce.com/_ui/core/chatter/groups/GroupProfilePage?g=0F93A0000009TPk

[pagner]

@packocz Are you receiving the same error though?

"A fatal signup error occurred...."

[packocz]

@pagner yes it's the same error

[pagner]

@packocz Good to know. Should serve as a clue for the devs to get this fixed. Thanks for posting!

[renatoliveira]

I'm also getting this same error, while not using org shapes. Probably the same reason as @packocz.

Salesforce CLI info: sfdx-cli/7.31.0 darwin-x64 node-v12.6.0

The command:

sfdx force:org:create --targetdevhubusername [email protected] --setdefaultusername --definitionfile config/project-scratch-def.json --wait 10 --durationdays 1 [email protected]

The input JSON (scratch org definition file):

{
  "orgName": "Company",
  "edition": "Enterprise",
  "features": [
    "Communities",
    "PersonAccounts",
    "ServiceCloud",
    "Sites",
    "SiteDotCom",
    "StateAndCountryPicklist"
  ],
  "settings": {
    "communitiesSettings": {
      "enableNetworksEnabled": true,
      "enableCommunityWorkspaces": true
    },
    "contentSettings": {
      "enableContent": true
    },
    "entitlementSettings": {
      "enableEntitlements": true,
      "enableEntitlementVersioning": true
    },
    "lightningExperienceSettings": {
      "enableS1DesktopEnabled": true
    },
    "pathAssistantSettings": {
      "pathAssistantEnabled": true
    },
    "surveySettings": {
      "enableSurvey": true
    },
    "siteSettings": {
      "enableProxyLoginICHeader": true,
      "enableTopicsInSites": false
    }
  },
  "language": "pt_BR"
}

The output:

{
    "status": 1,
    "name": "RemoteOrgSignupFailed",
    "message": "A fatal signup error occurred. Please try again. If you still see this error, contact Salesforce Support for assistance.",
    "exitCode": 1,
    "commandName": "OrgCreateCommand",
    "stack": "RemoteOrgSignupFailed: A fatal signup error occurred. Please try again. If you still see this error, contact Salesforce Support for assistance.\n    at signup.retrieveScratchOrgInfo (/Users/renatosilva/.config/yarn/global/node_modules/salesforce-alm/dist/lib/org/scratchOrgInfoApi.js:313:21)\n    at async OrgCreateCommand.signupOrgWithStreaming (/Users/renatosilva/.config/yarn/global/node_modules/salesforce-alm/dist/lib/org/scratchOrgCreateCommand.js:226:37)\n    at async OrgCreateCommand.execute (/Users/renatosilva/.config/yarn/global/node_modules/salesforce-alm/dist/lib/org/scratchOrgCreateCommand.js:312:32)\n    at async OrgCreateCommand.execLegacyCommand (/Users/renatosilva/.config/yarn/global/node_modules/salesforce-alm/dist/ToolbeltCommand.js:148:29)\n    at async OrgCreateCommand._run (/Users/renatosilva/.config/yarn/global/node_modules/@salesforce/command/lib/sfdxCommand.js:91:40)\n    at async Config.runCommand (/Users/renatosilva/.config/yarn/global/node_modules/@oclif/config/lib/config.js:151:9)\n    at async Main.run (/Users/renatosilva/.config/yarn/global/node_modules/@oclif/command/lib/main.js:21:9)\n    at async Main._run (/Users/renatosilva/.config/yarn/global/node_modules/@oclif/command/lib/command.js:44:20)\n    at async Object.run (/Users/renatosilva/.config/yarn/global/node_modules/sfdx-cli/dist/cli.js:32:20)",
    "warnings": []
}

[packocz]

@pagner @renatoliveira I was able to get round this error by removing the siteDotCom setting and only keeping Sites. However, I didn't yet get as far as to confirm the deployed public sites actually work

[renatoliveira]

@pagner @renatoliveira I was able to get round this error by removing the siteDotCom setting and only keeping Sites. However, I didn't yet get as far as to confirm the deployed public sites actually work

Thank you for sharing this information!

The error message changed for me, now I get a ProblemDeployingSettings error, with the message "Failed to deploy settings to scratch org." instead.

Still, that already indicates that the issue seems to be related to the SiteDotCom feature that might be conflicting with something else in this config file. I got another org/project that has the feature enabled on the file and scratch org creation works just fine:

{
    "orgName": "Another Company",
    "edition": "Enterprise",
    "features": ["PersonAccounts", "Communities", "SiteDotCom", "SiteForceContributor", "SiteForcePublisher", "Sites"],
    "settings": {
        "pathAssistantSettings": {
            "pathAssistantEnabled": true
        },
        "accountSettings": {
            "enableAccountTeams": true
        },
        "lightningExperienceSettings": {
            "enableS1DesktopEnabled": true
        },
        "communitiesSettings": {
            "enableNetworksEnabled": true
        }
    }
  }

🤔

[hgolov]

I'm experiencing this with a Dev org that I set up for Trailhead. Any developments?
Here is my error:
sfdx force:org:create -f config\\project-scratch-def.json --setalias trailhead --durationdays 7 --setdefaultusername --json --loglevel debug { "status": 1, "name": "RemoteOrgSignupFailed", "message": "A fatal signup error occurred. Please try again. If you still see this error, contact Salesforce Support for assistance.", "exitCode": 1, "commandName": "OrgCreateCommand", "stack": "RemoteOrgSignupFailed: A fatal signup error occurred. Please try again. If you still see this error, contact Salesforce Support for assistance.\n at signup.retrieveScratchOrgInfo (C:\\Users\\hadssa\\AppData\\Local\\sfdx\\client\\7.33.2-045d48473e\\node_modules\\salesforce-alm\\dist\\lib\\org\\scratchOrgInfoApi.js:313:21)", "warnings": [] }

[kratoon3]

SiteDotCom feature still not working.
@clairebianchi any updates from the team owning this functionality?

[jonathanwiesel]

This happened intermittently for me today doing a PoC of a CI job that involves only 2 Apex Classes.

[fitzchevalric791]

This is happening intermittently for me too.

[shetzel]

RemoteOrgSignupFailed is a serverside signup issue and nothing that the CLI team can do anything about. Whenever this happens it's best to contact support who can then investigate much more quickly.