Finance | Project Operations, Human Resources, ...

Failed to deploy D365FO OnPrem environment

(2) Share

Report

Posted on by ISDev

253

hello,

i am in the steps of deploying a d365fo on prem environment, i completed all MS steps. everything is fine, but the status is stuck on "Deploying", i checked the event viewer, the following warning is showing:

Failed to get images with error: FABRIC_E_SERVICE_OFFLINE. Query failed 22 times sequentialy, next function for querying images will be scheduled in 3600 seconds. NOTE, this warning may be benign and can be ignored if the cluster is not using container based apps. Setting "DisableContainers" to true in the Hosting section of their cluster manifest will mute this error.

anyone can tell me how to resolve it?

Categories:

Dynamics 365 Finance

All responses (9)

Answers (0)

ISDev 253 on at

Like (0)

Report

Failed to deploy D365FO OnPrem environment

Hi Komi,

i have disabled Encrypt data access, then re-run the Test. its still showing same error.

Moreover, i checked eventViewer and found the following errors

Automatic registration failed at join phase.
Exit code: Unknown HResult Error code: 0x801c001d
Server error:
Tenant type: undefined
Registration type: undefined
Debug Output:
joinMode: Join
drsInstance: undefined
registrationType: undefined
tenantType: undefined
tenantId: undefined
configLocation: undefined
errorPhase: discover
adalCorrelationId: d18ed055-0b43-4ed3-9560-cd7c4e8f621d
adalLog:
undefined
adalResponseCode: 0x0
Komi Siabi 12,835 Most Valuable Professional on at

Like (0)

Report

Failed to deploy D365FO OnPrem environment

Could you check the property of the file share and disable the option Encrypt data access, then re-run the Test.
Suggested answer

Komi Siabi 12,835 Most Valuable Professional on at

Like (0)

Report
Failed to deploy D365FO OnPrem environment

Great, a different error, great.. There is progress :).

Unable to get file endpoint, the network name cannot be found, this means Local agent is not able to resolve the file path where to save the topology file.

Few things to check :

Ensure the LocalAgent account does have permissions on it the fileShare Path. You can test by running .\Test-FileShares.ps1 -ConfigurationFilePath .\ConfigTemplate.xml, On the file share machine

Let's be sure that fileshareLocation value in the localagent-config.json is same as FileShare path in ConfigTemplate.xml
ISDev 253 on at

Like (0)

Report

Failed to deploy D365FO OnPrem environment

, Hi Komi,

the message agent is validated, and have restarted all my VM's, deleted previous deployement, cleared the localagent and re-installed it, and now started new deployment.

regarding the \\filesserver\agent\assets\topology.xml,, i was not able to find anything named topology.xml. maybe i didnt find the correct path, but in sql server the progress is showing.

Hopefully, it doesnt get stuck on this step as usual. step name is processArtifacts.

now after checking the eventviewer, i got the below error:
Komi Siabi 12,835 Most Valuable Professional on at

Like (0)

Report
Failed to deploy D365FO OnPrem environment

Let's double check that Local agent working and LCS is able to connect to your On-prem.

Validate the On-Prem connector on LCS by sending message.

Confirm that you have a good internet connectivity.

If this works fine, then you would want to check the file server to see if the topology got downloaded. here is the path. \\filesserver\agent\assets\topology.xml

If no topology exists, then the deployment has not kick-started, please restart all your VMs, delete and reconfigure the environment from LCS.
ISDev 253 on at

Like (0)

Report
Failed to deploy D365FO OnPrem environment

hi @Komi Siabi

regarding first point, my primary orch is orch3, and im getting the below warnings:

Failed to get images with error: FABRIC_E_SERVICE_OFFLINE. Query failed 76 times sequentialy, next function for querying images will be scheduled in 11700 seconds. NOTE, this warning may be benign and can be ignored if the cluster is not using container based apps. Setting "DisableContainers" to true in the Hosting section of their cluster manifest will mute this error.

GetImages returned ErrorCode=FABRIC_E_SERVICE_OFFLINE

GetImages(): Failed communication with docker with error=FABRIC_E_SERVICE_OFFLINE

ContainersApiOperation::FinishInvokeContainerApi: InvokeContainerApiOperation failed with error=FABRIC_E_SERVICE_OFFLINE.

aebbbbbd-3f66-4b42-be3f-0634ba2de2b5 not found in CUID list (33d3fd3c-d98b-47c3-aa09-f2dc6000edbd)

31c1ae5b-0abe-4401-8823-5c22ef5029ff not found in CUID list (9604150a-fee3-40ae-8997-ee1a67938cba)

c0173912-c4f7-47a5-a69f-fd9a6972d7d3 not found in CUID list (d5f2278a-e81e-439e-a710-583e4534f2fa)

10.78.10.3:19001-10.78.10.10:19001 target 18702edc3c0-666f827d7e230507aae701d155833f1c-a3c3dcf276837964afa693acaa629bde: invalid frame: frameLength=0x0x1030317,spMask=0x24,fhFlags=0x24,fhCRC=0x54,mhLength=0x41379,fbCRC=0x0x4652691F

31c1ae5b-0abe-4401-8823-5c22ef5029ff not found in CUID list (9604150a-fee3-40ae-8997-ee1a67938cba)

regarding point 2, the error from the AX-LocalAgent view and lastly share the details error instead for General is:

The description for Event ID 65002 from source Microsoft-Dynamics-AX-LocalAgent cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

HRIS-ORCH01
Unable to update the status for queue message 8d30abd1-e502-4a9a-b5b1-c3df9b2580f9
Microsoft.Dynamics.AX.LifecycleManager.Proxy.LcsServerException: Exception of type 'Microsoft.Dynamics.AX.LifecycleManager.Proxy.LcsServerException' was thrown.
at Lcs.DeploymentAgent.Proxy.DeploymentAgentClient.<UpdateDeploymentStatus>d__8.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Dynamics.Operations.Local.BridgeService.BridgeServiceOperations.<PublishLCSTopologyInstanceUpdate>d__3.MoveNext()
0
ErrorPrettify
C:\__w\1\s\Source\LocalAgentEvents\LocalAgentEventSource.cs
79

The publisher has been disabled and its resource is not available. This usually occurs when the publisher is in the process of being uninstalled or upgraded
Komi Siabi 12,835 Most Valuable Professional on at

Like (0)

Report

Failed to deploy D365FO OnPrem environment

Please, double check to be sure you are getting the log from the primary Orch.

In addition, get the error from the AX-LocalAgent view and lastly share the details error instead for General.

Lastly, you are likely to have two succeeding errors, if that's the case, share both.
ISDev 253 on at

Like (0)

Report

Failed to deploy D365FO OnPrem environment

hi@Komi Siabi,

here is the status of my service fabric, its all healthy.

the warning is from Orch1 VM

and find below error in event viewer logs:
Komi Siabi 12,835 Most Valuable Professional on at

Like (0)

Report

Failed to deploy D365FO OnPrem environment

Hello,

Please, can you tell us what VM gave you this warning ? In fact, this does not really mean anything to us.

Can you share with us the status of your service fabric explorer? How many applications do we have? You should collect logs from the primary Orchestrator and share with us.