Timeout on step execution during manual package application

(0) Share

Report

Posted on by Andrew Wallis

I'm trying to apply an update package to a Dynamics 365 Finance and Operations Development environment hosted locally (i.e. not connected to LCS). It has failed on step 20 (update AOS service) because the timeout value of 75 min has been exceeded.

I appreciate that I could simply download the latest VM instead but I'm trying to understand the process of manually applying packages.

How do I edit the timeout value of the step? Do I need to input any new commands before attempting to edit the runbook?

I have the same question (0)

All responses (5)

Answers (1)

Suggested answer

Joris dG 17,775 on at

Like (0)

Report

Since you're hosting this locally, have you turned off the snapshot feature for your VM? With that feature turned on, updating gigabytes worth of files is going to be the worst experience ever.

Was this reply helpful? Yes No
Andrew Wallis 85 on at

Like (0)

Report

Hi Joris

The snapshot feature is turned off so I don't think that was the cause of my problems.

I did come across another couple of potential issues. Firstly the VM had inadequate disk space which certainly can't have helped. Secondly I may not have been using the correct package. I was using the same package Microsoft had created for me to update a cloud hosted development machine that I also have. I don't know whether that package is also suitable for a locally hosted machine so I'm now trying to download the Service Update - Version 10.0.6 with Platform update 30 package from the shared asset library.

I couldn't rollback the failed update so I've restored a fresh copy of the 10.0 VM to try again.

What is the correct process when encountering a timeout during the execution of the runbook if you need to extend the timeout parameter?

Was this reply helpful? Yes No
Suggested answer

arkaitzv on at

Like (0)

Report

Hi Andrew,

you can search and modify the TimeoutValue setting in the runbook that you generate and set it up to another value that works better for your.

I did test this in my environment:

And it worked just as expected:

Could you give it a try and let me know if it works for your?

Was this reply helpful? Yes No
Andrew Wallis 85 on at

Like (0)

Report

Thanks for this.

I've managed to get past the failure now (I think the absence of disk space was the culprit).

With regards to changing the timeout value, I can understand how you would do that after generating the runbook and before importing it and executing it, but if you have already started executing the runbook and then need to edit a value in the runbook, how would you do that? Do you have to export it in the state it is in and then reimport it?

Was this reply helpful? Yes No
Verified answer

arkaitzv on at

Like (0)

Report

The first approach should always be what you actually did: investigate why the VM was having such a lack of performance which was making it to timeout in this step. So, normally, when you fix that, your deployment will complete in timely fashion as well.

However, if the issue persists, or you are not able to troubleshoot the performance of your VM, you can change the value in the runbookfolder, then Import it again and rerun the failed step:

Hope this helps

Was this reply helpful? Yes No