web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Microsoft Dynamics 365 | Integration, Dataverse...
Suggested Answer

D365 on Premise LocalAgent config file question

(0) ShareShare
ReportReport
Posted on by 48

Hello community.

I have just upgraded my local agent from version 2.6 to 3.0 but I could only do the upgrade using the localagent-config.json generated by my old 2.6 agent.

The new agent install complains about some values that on my old 2.6 version did not exist.

On localagent-config.json , line 128 I see this lines of code that are NOT present on my old config file :

"name": "AlmOrchestrator",
        "isEnabled": "{EnableEdgeValue}",
        "placementCriteria": "(IsOrchestratorEnabled == True)",
        "parameters": {
            "aos": {
                "authority": {
                    "value": ""
                },
                "clientId": {
                    "value": ""
                },
                "resource": {
                    "value": ""
                },
                "serviceAuthCert": {
                    "certificateSubjectName": "",
                    "manifestReferenceName": "AOSServiceAuth",
                    "findByType": "FindBySubjectName"

When I try to use this config file to deploy , I will of course get an error as this lines do not have values.

LocalAgentCLI.exe Error: 0 : Exception Newtonsoft.Json.JsonReaderException: Could not convert string to boolean: {Enable
EdgeValue}. Path 'components[2].isEnabled', line 129, position 34.
   at Newtonsoft.Json.JsonReader.ReadBooleanString(String s)
   at Newtonsoft.Json.JsonTextReader.ReadAsBoolean()

,....

....

Any idea how this lines should be populated or why are they NOT populated when I downloaded the config file from LCS from the connector setup.

Thanks in advance.

I have the same question (0)
  • Nya Profile Picture
    29,060 on at

    Hi,

    Please refer to the following article which contains a resolution.

    Newtonsoft.Json.JsonReaderException: Could not convert string to boolean | TheCodeBuzz

  • GeorgeSas Profile Picture
    48 on at

    This won't help me , this needs to run out of the box without me starting to change the CONFIGURATION and design of the localagent-config.json

  • Suggested answer
    GeorgeSas Profile Picture
    48 on at

    MS Confirmed :

    Yes, this is a known issue that will be fixed with the next release of LCS. Should be in about a week. There is a very simple workaround to this problem. In LCS go to your project settings, on-premises connectors, edit your connector, open "Enter Configuration" and save without changing anything and download the Local Agent configuration file again.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Congratulations to our 2025 Community Spotlights

Thanks to all of our 2025 Community Spotlight stars!

Leaderboard > Microsoft Dynamics 365 | Integration, Dataverse, and general topics

#1
Pallavi Phade Profile Picture

Pallavi Phade 102 Super User 2026 Season 1

#2
Abhilash Warrier Profile Picture

Abhilash Warrier 55 Super User 2026 Season 1

#3
ManoVerse Profile Picture

ManoVerse 49 Super User 2026 Season 1

Last 30 days Overall leaderboard

Product updates

Dynamics 365 release plans