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.

You might get the error   {“error”:”interaction_required”,”error_description”:”AADSTS50076: Due to a configuration change made by your administrator, or because you moved to a new location, you must use multi-factor authentication to access ‘00000007-0000-0000-c000-000000000000.

This is due to authenticator policy of the organization you are using for the connection. You might want to disable the security default.

The post Cannot connect to Dataverse with Power Platform Tools for VS 2022 appeared first on Monsieur Winner.

A. Take a back up of AXDB on the On-premises environment

B. Restore the database on the Cloud hosted environment(CHE).

C. Run some sql script against the CHE to update certain values.

D. Synchronize the CHE database.

I would skip the steps A and B and move straight to the scripts.

Step 1

USE AXDBonprem;
SELECT s.name
FROM sys.schemas s
WHERE s.principal_id = USER_ID('axdbadmin');

Step 2


ALTER AUTHORIZATION ON SCHEMA::db_owner TO dbo;
ALTER AUTHORIZATION ON SCHEMA::db_ddladmin TO dbo;
ALTER AUTHORIZATION ON SCHEMA::db_datareader TO dbo;
ALTER AUTHORIZATION ON SCHEMA::db_datawriter TO dbo;


step3

USE AXDBonprem;
declare
@userSQL varchar(1000)
set quoted_identifier off
declare userCursor CURSOR for
select 'DROP USER [' + name +']'
from sys.sysusers
where issqlrole = 0 and hasdbaccess = 1 and name != 'dbo' and name != 'NT AUTHORITY\NETWORK SERVICE'
OPEN userCursor
FETCH userCursor into @userSQL
WHILE @@Fetch_Status = 0
BEGIN
exec(@userSQL)
FETCH userCursor into @userSQL
END
CLOSE userCursor
DEALLOCATE userCursor

step4

–now recreate the users copying from the existing database:
use AXDB –******************* SET THE OLD TIER 1 DATABASE NAME****************************

go
IF object_id('tempdb..#UsersToCreate') is not null
DROP TABLE #UsersToCreate
go
select 'CREATE USER [' + name + '] FROM LOGIN [' + name + '] EXEC sp_addrolemember "db_owner", "' + name + '"' as sqlcommand
into #UsersToCreate
from sys.sysusers
where issqlrole = 0 and hasdbaccess = 1 and name != 'dbo' and name != 'NT AUTHORITY\NETWORK SERVICE'


step 5


go
use AXDBonprem --******************* SET THE NEWLY RESTORED DATABASE NAME****************************
go
declare
@userSQL varchar(1000)
set quoted_identifier off
declare userCursor CURSOR for
select sqlcommand from #UsersToCreate
OPEN userCursor
FETCH userCursor into @userSQL
WHILE @@Fetch_Status = 0
BEGIN
exec(@userSQL)
FETCH userCursor into @userSQL
END
CLOSE userCursor
DEALLOCATE userCursor


STEP 6
COPY ADMIN USER

use AXDBonprem
--Update the Admin user record, so that I can log in again
UPDATE USERINFO
SET SID = x.SID, NETWORKDOMAIN = x.NETWORKDOMAIN, NETWORKALIAS = x.NETWORKALIAS,
IDENTITYPROVIDER = x.IDENTITYPROVIDER
FROM AXDB..USERINFO x --******************* SET THE OLD TIER 1 DATABASE NAME****************************
WHERE x.ID = 'Admin' and USERINFO.ID = 'Admin'


STEP 7

Now, let’s rename the orginal AXDB to AXDB_old

USE master
GO
ALTER DATABASE AxDB
SET SINGLE_USER
WITH ROLLBACK IMMEDIATE
GO
ALTER DATABASE AxDB
Modify Name = AxDBold
GO
ALTER DATABASE AxDBold
SET MULTI_USER
GO

Step 8

Rename AXDBonprem to AXDB


USE master
GO
ALTER DATABASE AxDBonprem
SET SINGLE_USER
WITH ROLLBACK IMMEDIATE
GO
ALTER DATABASE AxDBonprem
Modify Name = AxDB
GO
ALTER DATABASE AxDB
SET MULTI_USER
GO


The post Copy database from D365FO On premises to Cloud hosted environment appeared first on Monsieur Winner.

Hence , create a new Azure DevOps project would have you choose Git as default version control and TFVC is totaly missing.. This tell us we need to start using this for future project and obviously migrate current D365FO repositories from TFVC to Git.

If you probably are not ready to start using Git, fear not :). At least for now, you can enable the TFVC option form the organization’s setting.

You should have it turned off as shown above.

The post Missing TFVC Option in Azure DevOps: Creating a New Project appeared first on Monsieur Winner.

    public Description dateInWord(TransDate _date)
    {
        Description day, month, year;

        day = int2Str(dayOfMth(_date));
        month = mthName(mthOfYr(_date));
        Year  = int2Str(Year(_date));

        return strFmt("%1th %2, %3",day,month,Year);


    }

08/06/2024 ( MM/DD/YY) will is outputted as 6th August, 2024

The post How to convert from date to string using x++ 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.

To set your custom model as default, go to

C:\Users\XYZ\Documents\Visual Studio Dynamics 365

Edit the DynamicsDevConfig file.

<DefaultModelForNewProjects>FleetManagement</DefaultModelForNewProjects>

Change FleetManagement to your custom model.

The post Default model for new projects in Visual studio D365FO appeared first on Monsieur Winner.