Skip to main content

Notifications

Announcements

No record found.

Microsoft Dynamics 365 | Integration, Dataverse...
Suggested answer

D365 on Premise LocalAgent config file question

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.

  • Suggested answer
    GeorgeSas Profile Picture
    GeorgeSas 48 on at
    RE: D365 on Premise LocalAgent config file question

    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.

  • GeorgeSas Profile Picture
    GeorgeSas 48 on at
    RE: D365 on Premise LocalAgent config file question

    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

  • Nya Profile Picture
    Nya 29,056 on at
    RE: D365 on Premise LocalAgent config file question

    Hi,

    Please refer to the following article which contains a resolution.

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

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

December Spotlight Star - Muhammad Affan

Congratulations to a top community star!

Top 10 leaders for November!

Congratulations to our November super stars!

Tips for Writing Effective Suggested Answers

Best practices for providing successful forum answers ✍️

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 291,280 Super User 2024 Season 2

#2
Martin Dráb Profile Picture

Martin Dráb 230,235 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Product updates

Dynamics 365 release plans