The group Dynamics365ReadServices is not present in the ACL of the service SqlServerReportingServices.

Below the steps used in resolving it.

1. Go to your BI node.
2. Open lusrmgr.msc (Local Users and Groups).
3. Create a new group called Dynamics365ReadServices.
4. Add the account that your AOS runs under (such as axserviceuser, svc-AXSF$) to the group you created above.
5. Download the latest infrastructure scripts from the Shared asset library in Lifecycle Services.
6. Copy the infrastructure scripts to your BI (SSRS) node.
7. Create a file scmgroups.csv with the following content.                                                                                                                                                                    “Name”                                                                                                                                                                                                                  “Dynamics365ReadServices”
8. Run the following command in PowerShell with Administrator privileges.
   .\Set-ServiceControlManagerPermissions.ps1
9. Run the following command in PowerShell with Administrator privileges to verify the setup.
   .\Set-ServiceControlManagerPermissions.ps1 -Test

The post The group Dynamics365ReadServices is not present in the ACL of the service SqlServerReportingServices. appeared first on Monsieur Winner.

It gets a bit funnier when after the restore I get the message :

D365FO : You are not authorized to login with your current credentials. You will be redirected to the login page in a few seconds.

Me: Do you realize I am an administrator ? In fact, I deployed this environment so I need access now !!!

Well, few things to do.

• Run the Reset-DatabaseUsers.ps1 script in the infrastructure folder

.\Reset-DatabaseUsers.ps1 -DatabaseServer ‘<FQDN of the SQL server>’ -DatabaseName ‘<AX database name>’.

• Update the networkdomain to the adfs federation service name https://fsn.contoso.com/adfs.

Replace the portions in bold based on your environment.

Once DB Sync is completed successfully , Happy on-premising :D.

The post Cannot Login after database refresh dynamics 365 FO on Premise appeared first on Monsieur Winner.

This is because the “documents” folder in the file server is missing.

Go to aos-storage and create a new folder “documents” and you should be fine.

The post Document failed to upload. Please try to upload the document again D365FO on premises appeared first on Monsieur Winner.

Data packages are stored in the shared working folder during data import and Export.

Recently, we migrated a D365FO on-premises to cloud. And we noticed that, the path in the working folder came as that of the on-premises setup hence the error “Data import/export framework parameters – Directory ‘ ‘ does not exist”, while accessing the data entities page.

Updating with the right local path solved the issue : C:\Temp\DIXF

The post Data import/export framework parameters – Directory ‘ ‘ does not exist in D365FO appeared first on Monsieur Winner.