Error messages can occur in Mercury for a variety of reasons. See below for information on the error messages, why they appear and how to resolve them.
You can use Ctrl+F on this page to search for a specific part of an error message.
Error Message: An error occurred in Clone Placement activity: Standard Rate Type does not have a frequency to synchronise
Action: Extending a Placement.
To resolve: Ensure Frequency and Standard Rate Type are correct and are in an active state.
Example:
Error Message: Business Process Error: Could not find an FX Spot Rate record that pairs the record currency and the attribute currency.
Action: Changing a currency on Vacancy/Placements.
To resolve: Create a FX spot rate record for the currency required. i.e. if changing the currency to Euro ensure there is an FX record for both currencies.
Example:
Error Message: An error has occurred in ShortListingButton.js. The error is 143570002 is not a valid status code for state code.
Action: Extending an offer for a Candidate that is already Shortlisted.
To resolve: Reactivate the Shortlist for the Candidate.
Example:
Error Message: One of the scripts for this record has caused an error. For more details, download the log file.
Action: This error can occur at any time, clicking on a record, changing forms, changing toggles, etc.
To resolve: This error occurs due to customer customisations. Raise with Support to isolate issue and entity.
Example:
Error Message: An error occurred in clone placement activity: Entity ‘customeraddress’ with Id = (GUID) Does Not Exist.
Action: Extending a Placement.
To resolve: A change was made to a customer address, which does not automatically cascade. Revalidate customer address.
Example:
Error Message: The specified domain does not exist: An unexpected error occurred from ISV code.
Action: Saving a Placement/Vacancy record.
To resolve: Fill in the missing field(s) on a record which are required for a placement/vacancy to calculate certain values. i.e. Days Per Week, Original End Date, Agreement, etc.
Example:
Error Message: Error: The object cannot be updated because it is read-only.
Action: Updating records which are in a completed or deactivated state.
To resolve: Create a new record or reactivate the existing record
Example:
Error Message: An error occurred in Clone Placement Activity. Principal user (Id=GUID), is missing prvAppendTorecruit_placementvalidation privilege.
Action: Cloning a Placement.
To resolve: Review the financial fields of the Placement and ensure it is not associated with an inactive user.
Example:
Error Message: Business Process Error: Changes to the candidate are not permitted. Upload new evidence instead.
Action: Merging two Contact records.
To resolve: Remove active compliance evidence on one of the Contact records.
Example:
Error Message: Business Process Error: A shortlist record already exists linking this vacancy & candidate. Operation aborted.
Action: Merging two Contact records.
To resolve: One Contact record has an active Shortlist. This needs to be deactivated or deleted.
Example:
Error Message: Business Process Error: A Placement Rate record already exists for this rate type and date.
Action: Creating a new Placement rate types which already exists.
To resolve: Use the existing rate type. The ‘Show Details’ additional information on the error contains locations via GUID, showing which rate type is related.
Example:
Error Message: Service failed: error
Action: Submitting Candidate(s).
To resolve: See Knowledge Base article "Error message > Service failed: error"
Example:
Error Message: Business Process Error: The plugin threw an exception
Action: Saving records.
To resolve:
Ensure all related fields in entities are correctly identified and populated, including address fields.
Example:
Error Message: Invalid Argument.
Action: Pasting incorrect characters and clicking Save.
To resolve: Clear the cache and ensure correct characters are used in fields.
Example:
Error Message: Business Process Error: The email was blocked because it would exceed the email sending limit for user. Principal user (Id=GUID), is missing prvCreateMercury_emailcounter privilege.
Action: Sending emails in Mercury.
To resolve: Apply correct permissions for affected users - this may be a customised bolt-on role.
Example:
Error Message: A general error has occurred. The error is Attempted to divide by zero.
Action: Shortlisting Candidate(s).
To resolve: Ensure financial information is populated on records on Shortlist and Vacancy.
Example:
Error Message: Business Process Error: Could not determine Type
Action: Deleting a Vacancy/Placement.
To resolve: Delete the active Shortlist against the Vacancy/Placement.
Example:
Error Message: Business Process Error: An error occurred in Set placement status reason: (status reason). You are not permitted to assign, approve or reject this placement.
Action: Validating/Approving a Placement.
To resolve: Ensure user is in the correct team and has the correct permissions.
Example:
Error Message: Unexpected end of JSON input.
Action: Shortlisting Candidates to 'Accept Offer' stage to create a Placement.
To resolve: Ensure Frequency and Standard Rate Type fields are populated on the Shortlist,
Example:
Error Message: An error occurred in Clone Placement Activity: A validation error occurred for crimson_placement.mercury_salesvalue_mc_normalised.The value 427619275679.8400 of type Microsoft.XRM.SDK.Money is outside the valid range.
Action: Extending a Placement.
To resolve:
Ensure the previous Rate Types on Placements matches the extended Placement i.e. Standard Rate Types.
Example:
Error Message: Error: Something has gone wrong. Check technical details for more details.
Action: Navigating Mercury of opening records.
To resolve: Clear cache or restart to fix this issue. Importing solutions during environments usage normally causes this error, but this is a generic message. Click ‘Show details’ to pinpoint the error.
Example:
Error Message: Notifications: You (user) need to be added to a security group to access this environment
Action: Accessing Mercury.
To resolve: The System Admin should set up the user with the correct security group.
Example:
Error Message: Insufficient Permissions: You do not have prvReaddqg_Email permission to access dqg_email records. Contact your Microsoft Dynamics 365 administrator for help.
Action: Updating records in Mercury.
To resolve: User will need a security role that grants the missing permission. In non-development scenarios, these security roles typically exist already but haven't been applied to the user.
NOTE: "Insufficient Permissions" is a fairly common and generic error. See below for other resolutions depending on the record type (the screenshot below refers to DQ Global).
- dqg_ refers to a DQ Global permission issue. Users will need a security role that grants the missing permission. In non-development scenarios, these security roles typically exist already but haven't been applied to the user.
- prvReadcrimson_vacancy refers to lack of read permissions on Mercury's Vacancy table.
- mercury_, recruit_, or crimson_ refers to permissions on Mercury-owned records (tables). For example, crimson_placement
- Permissions may be missing on out-of-the-box Microsoft entities, which are harder to rule Mercury in/out. For example, contact
Example:
Error Message: An error occurred communicating with CRM while fetching details of the ‘regarding’ records.
Action: Emailing Candidates or sending Spec Sends.
To resolve: See Knowledge Base article "Error message: An error occurred communicating with CRM while fetching details of the 'regarding' records"
Example:
Error Message: Error: The plug-in execution failed because no Sandbox Worker processes are currently available. Please try again.
Action: Adding new call notes or navigating Mercury.
To resolve: Refers to unavailability of internal Microsoft infrastructure at runtime. Retry, or contact Microsoft.
Example:
Error Message: Unsupported User Role: This email address can only be approved by a user with the Global Administrator or Exchange Administrator role in Office 365 or the Delegated Mailbox Provider role in Dynamics 365.
Action: Approving user mailboxes.
To resolve: The System Admin with a global admin role must approve mailboxes
Example:
Error Message: Business Process Error: The email was blocked because it would exceed the email receiving limit for (user).
Action: Sending emails in Mercury.
To resolve: This is a customisation issue. Correct permissions are required, and a review of email user settings.
Example:
Error Message: A general error has occurred. The error is String or binary data would be truncated in table '{0}', column '{1}'. Truncated value: '{2}'.
Action: Shortlisting Candidates to make an offer.
To resolve: Recreate Contact or recreate Shortlist.
Example:
Error Message: The user (GUID) selected in the From field does not have the option enabled to allow others to send the email on their behalf.
Action: Sending emails in Mercury.
To resolve: User’s personalization setting must be enabled to send emails on their behalf. This can be done through Mercury support via xRM toolbox or via Settings > Personalization Settings > Email > select tick-box for Allow other Microsoft Dynamics 365 users to send email on your behalf.
Example:
Error Message: An error occurred in Clone Placement activity: A Placement Cost Centre already exists with the same Alias for another Placement that has overlapping dates.
Action: Extending Placement(s).
To resolve: A different cost centre’s placement was associated with the extended placement. Update to the correct placement and Save.
Example:
Error Message: Access Is Denied: UciError: user with id (guid) does not have ReadAccess right(s) for record with id (guid) of entity Hot List.
Action: Adding record(s) to Hotlist.
To resolve: See Knowledge Base article "How do I share my Hot List?"
Example:
Error Message: user with id (GUID) does not ave AppendToAccess right(s) for record with (GUID) of entity User. Consider assigning a role with the required access level to the user or team.
Action: Accepting an offer.
To resolve: Review permissions for user and review configs for Placement approvals.
Example:
Error Message: Business Process Error: The email was blocked because the email recipient contact type does not match the actual recipient contact type.
Action: Sending email(s).
To resolve: Ensure Contact records have suitable emails.
Example:
Error Message: Differently Parented: These records may not be suitable for merging, because they do not share the same parent.
Action: When selecting a Contact who is both a Candidate and Client Contact. This error also occurs when trying to merge Candidate Contacts whose Parent Accounts are not the same.
To resolve: Associate the "master" contact (the one you're keeping) with a Client record, then retry.
Example:
Error Message: Parenting Loss: These records may not be suitable for merging. The master record does not have a parent record, but the subordinate record does. If you continue, the subordinate’s relationship to its parent will be lost.
Action: Attempting to merge a Client Contact to another Client Contact when neither have a Client.
To resolve: Add the correct Client to the "master" record (the one you're keeping) manually.
Example: