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.

When the deployment fails, we should first of all check the service fabric explorer to identify the application where the failure happened.

This tells us the exact node of the cluster to further access for meaningful info.

The post Deploy SSRS report via powershell script – D365 Finance and Operations on premises 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.

This error occurs when the local agent tries to download the package from LCS. This file is saved in the fileshare VM.

When the fileshareLocation  value is different what is specified in the localagent-config.json is different from FileShare path in ConfigTemplate.xml,

I am happy to tell you that you just successfully landed yourself a bonus error.

The post Unable to get file endpoint, the network name cannot be found – D365FO on-premises appeared first on Monsieur Winner.

Not to worry, while the reason of the failure is being found, we can rollback using sql scripts.

The deployment status is captured in a the OrchestratorData database. Let’s roll back with the following steps:

1. Get the recent successful deployment state.

select * from OrchestratorJob order by LastProcessedDateTime desc
select * from RunBookTask order by StartDateTime desc

In the RunBookTask table, we are looking at the executePostDeploymentScript state in the name field; pick the corresponding RunbookTaskId as shown in the screenshot above.

Also get the the corresponding JobId in the OrchestratorJob table.

2. Revert to the recent successful deployment state.

update OrchestratorJob set state = 1 where jobid = 'XXXXUSUAT-a28c1aae-e84e-490d-b9dd-a928be71a774';
update RunBookTask set state = 1, Retries = 1 where RunbookTaskId = 'XXXUSUAT-a28c1aae-e84e-490d-b9dd-a928be71a774-executePostDeploymentScript';

hhhh

Once completed, your environment status should be deployed on LCS.

The post Restore a failed deployment to initial state on LCS : D365FO On-premises appeared first on Monsieur Winner.