Skip to content
Guide

Search the Guide

Enter a query to search the Guide.

Íslenska
Menu
On this page

Help

Backup administrators and users can look here for messages from setup, export requests, status checks, downloads, and email notifications. Messages are shown in English in the current XLIFF version.

Setup and access

MessageExplanationWhat to do
Full backup access (permission set RDN BCB FULL) is required to change credentials, manage or download backups.The user does not have full access to the extension.Ask an administrator to assign RdN BC Backup - Full Access (RDN BCB FULL).
The D365 BACKUP/RESTORE permission set is required to start database exports. Ask your administrator to assign it to user ….The user submitting the export request lacks the required Business Central permission.Ask an administrator to assign D365 BACKUP/RESTORE to the user or Job Queue user.
Configure the client secret in RdN BC Backup Setup.The client secret is missing.Open RdN BC Backup Setup and enter a secret for Client Credentials (App Registration).
Failed to acquire an access token. Check the tenant, client ID, client secret, and admin consent.Authentication failed or consent is missing.Verify the tenant, client ID, and secret. Ask an administrator to confirm that consent was granted for the app registration.
Delegated authentication failed. Details: …The delegated authentication request failed.Sign in again and confirm that the user is an authorized Business Central administrator.
Delegated authentication is for manual use only. Select Client Credentials for recurring backups.Delegated mode cannot run in the Job Queue.Select Client Credentials (App Registration) and enter the client secret before enabling recurring runs.
Admin Center API request failed (HTTP …). Check the environment, Admin Center app authorization, and D365 BACKUP/RESTORE permissions. Response: …The Admin Center rejected the request or returned an error.Verify the environment name, app authorization in the Admin Center, and D365 BACKUP/RESTORE.
The Admin Center API rejected the access token (HTTP 401). Check that: (1) Client ID … is added on the Authorized Microsoft Entra apps page in the Business Central admin center; (2) admin consent is granted for the Application permission AdminCenter.ReadWrite.All (Client Credentials), or the signed-in user is a Business Central administrator (Delegated); (3) BC Tenant ID … is the tenant that owns environment …. New permissions can take several minutes to apply. Details: …The access token was not accepted or the app is connected to the wrong tenant.Verify the Client ID registration, consent, authentication mode, and that BC Tenant ID owns the environment. Wait several minutes for new permissions to apply, then try again.
The Admin Center API denied the request (HTTP 403). Check that Client ID … is authorized in the Business Central admin center, and that in environment … the Microsoft Entra Applications page lists it as Enabled with the D365 BACKUP/RESTORE permission set. Details: …The app is not authorized for the target environment or export.Verify the app authorization in the Admin Center and that the app is enabled in the target environment with D365 BACKUP/RESTORE.
Admin Center refused the export because app registration … has no export permission inside environment …. With Client Credentials, the app registration needs this permission, not the signed-in user. Authorizing the app in the Business Central admin center is a separate step and is not enough. Sign in to environment …, open the Microsoft Entra Applications page, and add Client ID … (or open its card). Set State to Enabled and assign the D365 BACKUP/RESTORE permission set with Company left blank. Response: …The app registration does not have export permission inside the target environment.Ask an administrator to enable the app in the target environment and assign D365 BACKUP/RESTORE with no company specified.
The Admin Center API request could not be sent or its response could not be received. Check Allow HttpClient Requests in Extension Management and network connectivity.Business Central could not send the request or receive a response.Verify Allow HttpClient Requests in Extension Management and network connectivity.
The Admin Center API returned an unexpected response. Expected: ….The Admin Center response was not in a format the extension could read.Try again later. If the error continues, contact an administrator.
Azure SAS Token has not been configured. Please set up the SAS Token first.The export SAS token is missing from setup.Enter a token in Export SAS Token and select Validate Export SAS Token.
Configure the Azure SAS token in RdN BC Backup Setup.The API request cannot find the export SAS token.Open RdN BC Backup Setup, enter the export token, and validate it.
A read-only download SAS token has not been configured in RdN BC Backup Setup.The download token is missing.Enter a read-only token in Download SAS Token (Read-Only) and select Validate Download SAS Token.
The Export SAS Token must be entered again on the RdN BC Backup Setup page. It was saved by an earlier version in a format that cannot be validated or used for downloads.An older token was saved in a format that cannot be validated.Enter the export SAS token again in RdN BC Backup Setup.
The Download SAS Token (Read-Only) must be entered again on the RdN BC Backup Setup page. It was saved by an earlier version in a format that cannot be validated or used for downloads.An older download token was saved in a format that cannot be validated or used.Enter the read-only download SAS token again.
The SAS token must remain valid for at least 72 hours after starting an export. Current expiry: ….The export token expires too soon for the export.Enter a token that remains valid for at least 72 hours after an export starts.
The SAS token must include Read, Write, Delete, and Create permissions (sp= must contain r, w, d, and c).The export token is missing one or more required permissions.Request a Blob account SAS with Read, Write, Delete, and Create permissions, then validate it again.
Use an account SAS for the Blob service (ss=b) with Container and Object resource types (srt=co) and HTTPS only (spr=https). Copy the Blob service SAS URL from the storage account Shared access signature page.The token is not a Blob account SAS with the required scope and HTTPS setting.Obtain the correct Blob service SAS URL from the Azure administrator and validate the token again.
The SAS token does not contain a signed version (sv=) parameter. Ensure you have a valid SAS token, not a connection string.The value is not a complete SAS token or is a connection string.Obtain a valid SAS token, not a connection string, and enter it again.
The SAS token does not contain a signature (sig=) parameter. The token appears to be incomplete or invalid.The token is missing its signature.Obtain a new valid SAS token and validate it.
The SAS token does not contain an expiry date (se=) parameter. The token may be invalid.The token is missing its expiry.Obtain a new SAS token with an expiry and validate it.
The SAS expiry (se=) must be a valid UTC date and time.The expiry in the SAS token is not a valid UTC time.Obtain a new token with a valid UTC expiry.
The SAS start time (st=) is invalid or is in the future.The token start time is invalid or later than the current time.Obtain a token whose start time has passed, or omit the start time.
The SAS token must allow HTTPS only (spr=https).The token does not require HTTPS only.Obtain a new token restricted to HTTPS.
The download SAS token must be scoped to the backup container (sr=c). Generate it from the container's Shared access tokens page.The download token does not apply to the container holding the backups.Obtain a read-only token for the correct container and validate it again.
The download SAS token must be read-only (sp= may only contain r and l). Current permissions: ….The download token grants too many permissions or lacks Read.Obtain a new container-scoped token with Read and optional List, and no other permissions.
The download SAS token expired on …. Generate a new read-only SAS token for the container.The download token has expired.Obtain a new read-only token for the correct container and update setup.

Export requests and scheduling

MessageExplanationWhat to do
RdN BC Backup Setup has not been configured. Please complete the setup before running a backup.The setup record is missing.Open RdN BC Backup Setup and complete the required values.
No database exports remain this month. Wait until the quota resets before starting another backup.The monthly export quota is used up.Wait for the quota to reset or review Monthly Exports Remaining before trying again.
A backup for this environment is already pending or in progress: … (status: …, requested: …). Wait for it to finish, or open Backup Log and use Refresh Status. If Admin Center shows that the export failed or was never started, use Confirm Export Failed.Another entry prevents a new request.Select Backup Log and Refresh Status. Use Confirm Export Failed only after verifying the status in the Admin Center.
Recurring backups require Client Credentials authentication and a client secret. Delegated authentication is for manual backups only.The Job Queue is not using Client Credentials or the secret is missing.Select Client Credentials (App Registration) and enter a secret before setting the entries to Ready.
The export outcome is unknown. Check the database export in Admin Center before trying again. Details: …The response to a request was inconclusive; the export may have started.Do not submit another request until you check the operation in the Admin Center.
Backup failed: …The export request failed; more detail follows in the message.Read Error Message on the entry and resolve the cause before trying again.
Admin Center returned an unrecognized operation status: ….The Admin Center returned a status the extension does not recognize.Try Refresh Status again later. If the error continues, contact an administrator.
Scheduled backup skipped: another export for this environment is still pending or in progress.The recurring request was skipped because another request is active.Complete a status check on the active entry before evaluating the next scheduled run.
Scheduled backup skipped: … monthly export(s) remain and … are reserved for manual backups.The recurring run preserved the reserved exports.Review Reserved Manual Exports and Monthly Exports Remaining. Change the reserve only if it matches operational needs.
Scheduled backup could not check the remaining monthly exports: …The Job Queue could not read the export quota and logged the result.Review the error details in the backup log and try Get Export Status.
Scheduled backup failed: …The recurring export request failed and the cause was recorded in the backup log.Read Error Message, resolve the cause, and confirm the next run remains Ready.
Last status check failed at …: …A status check failed at the specified time.Select Refresh Status again. If it repeats, review the Admin Center message and contact an administrator.
Start a database export of environment "…"? This uses one of its monthly exports.Confirmation before a manual request uses a monthly export.Confirm only if you intend to submit the request; otherwise cancel.
Have you checked Admin Center and confirmed that export "…" failed or was never started? This allows another export to be requested.Confirmation before marking an active entry Failed and allowing another request.Answer yes only after the Admin Center shows that the export failed or did not start.

Status checks and downloads

MessageExplanationWhat to do
This log entry belongs to a different tenant. Restore the original tenant configuration before refreshing its status.Setup now points to a different tenant than the one recorded in the entry.Temporarily restore the original BC Tenant ID and refresh the status; do not check another entry with the wrong tenant value.
The operation was not returned by Admin Center. Check Operations in the Business Central administration center before retrying or confirming failure.The Admin Center did not return the operation linked to the log entry.Look for the operation in the Admin Center before retrying or confirming failure.
Admin Center did not return an export operation for backup …, and the log entry has no operation ID. Check Operations in the Business Central administration center. If the export is not listed there, use Confirm Export Failed.The extension could not find a matching export operation.Check Operations in the Admin Center. Use Confirm Export Failed only if the operation is not listed and did not start.
The backup file can only be downloaded when the status is Completed. Current status: …The entry is not Completed.Wait until the export finishes and refresh its status before downloading.
This backup belongs to a different storage account or container. Restore its original storage settings before downloading, or use Azure Storage Explorer.Current storage settings do not match the recorded file location.Restore the original storage account and container names before downloading the file.
Do you want to download the backup file "…"?Confirmation before opening the file in the browser.Confirm only if the backup name is correct and you intend to download it.

Email notifications

MessageExplanationWhat to do
No email account is available for RdN BC Backup. Set up a default email account on the Email Accounts page, or assign an account to the RdN BC Backup email scenario.No email account is the default or is assigned to the RdN BC Backup email scenario.Set up an email account on the Email Accounts page and make it the default, or assign it to RdN BC Backup on the Email Scenario Assignment page. Then select Send Test Email again.
The test email could not be sent: …Business Central could not send the test email. The reason follows in the message.Read the reason, fix the email account or the recipients, and try again.
A test email was sent to ….The test email was sent to the listed recipients.Check that it arrived. If it did not, check the addresses and the junk mail folder.

Problems without a message

SymptomExplanationWhat to do
No email arrived after a backup completed or failed.An email is only sent if Notification Email Recipients is filled in and Email on Success or Email on Failure is on. It is sent when a status check finds the result, up to an hour after the export finishes. A skipped recurring run sends no email.Check the settings on the Email Notifications FastTab and select Send Test Email. Look in the Email Outbox for emails that could not be sent. The user who started the backup, or the Job Queue user, needs permission to send email.
Business Central rejects an address in Notification Email Recipients.Business Central checks each address when you enter it.Separate the addresses with semicolons and correct the rejected address.
Send Test Email says that Notification Email Recipients must have a value.No recipients are entered.Enter at least one address and try again.