Company creation failed with error in the Cloud Migration Tool – Business Central 22

 

Problem: We encountered the following error while running the Cloud Migration tool on the BC22 version.

We got the below details from the “Copy details” of the above screenshot.

 

If requesting support, please provide the following details to help troubleshooting:

Company creation failed with error Sorry, the current permissions prevented the action. (TableData Company Insert: Base Application). Please fix this and re-run the Cloud Migration Setup wizard.

Internal session ID: 
94e97f8f-95ae-46a4-a7b6-98c79e7a7dc3

Application Insights session ID: 
1379aeac-c297-4b34-a0a5-1ae811dd898c

Client activity id: 
10d32b54-bd85-464c-a6df-355bc967b607

Time stamp on error: 
2023-05-23T10:32:24.1598995Z

AL call stack: 
"Hybrid Cloud Management"(CodeUnit 4001).VerifyCanStartReplication line 11 - Intelligent Cloud Base by Microsoft
"Cloud Migration Management"(Page 40063)."RunReplicationNow - OnAction"(Trigger) line 4 - Intelligent Cloud Base by Microsoft

 

The User has SUPER permission set assigned.

Solution: Please check if the BC license is assigned to the user from M365.

The above error was resolved after assigning a BC license to the user from M365 (Office).

 

No data in D365 Business Central tables after the Cloud Migration process

Recently, we migrated a few NAV customers to the D365 Business Central cloud and noticed that a lot of tables did not transfer the data after completing the Cloud Migration steps.

We never faced this issue before.

Solution: Run the “Repair Companion Table Records” action on the “Cloud Migration Management” page.

This code runs automatically in the replication process but sometimes it may be interrupted due to any service issues.

This action will insert the missing records into the tables and records will appear.

 

Note: if the records do not appear after running this action then you may need to restart the environment from the tenant admin center.

https://mohana-dynamicsnav.blogspot.com/2021/11/how-to-restart-d365-business-central.html

 

Failed to connect to the database. Error message: bad JSON escape sequence: \S.

We recently upgraded one of customers from NAV2016 to BC Cloud.

One of the critical step in this upgrade is to move data from BC OnPrem to BC Cloud using Intelligent Cloud/Cloud Data Migration using “Microsoft Integration Runtime Configuration Manager” tool.

We got below error while testing the Connection to the database in tool.

Failed to connect to the database. Error message: bad JSON escape sequence: \S. Path ‘properties.ConnectionString’, line 5, Position 78

Solution: Make sure to use 2 back slashes in your SQL Server details.

We used 1 back slash in above image as CD-NavToBC\SQL2016

But it should be CD-NavToBC\\SQL2016