ADO build fails ramdomly with 10.0.8 build VM: "Error preparing build environment: IISReset . Access denied"

(0) Share

Report

Posted on by nmaenpaa

101,172 Moderator

We recently deployed a 10.0.8 / PU32 build VM in Azure. For some reason about half of our nightly builds fail in step "Prepare for build". The error message is:

"Error preparing build environment: IISReset . Access denied, you must be an administrator of the remote computer to use this command. Either have your account added to the administrator local group of the remote computer or to the domain administrator global group."

Has anyone else faced this, and any ideas how to fix it? It's a freshly deployed system, and we didn't make any changes in it. And it also works about 50% of the time without issues.

I have the same question (0)

All responses (4)

Answers (2)

Sort by

André Arnaud de Cal... 306,230 Super User 2026 Season 1 on at

Like
a
(0)

Report
Copy link

Link copied!

Hi Nikolaos,

I noticed you also had created a Yammer post on the Dynamics feedback. Did you also create an incident for Microsoft Support?

Was this reply helpful? Yes No
Verified answer

Sergei Minozhenko 23,097 on at

Like
a
(0)

Report
Copy link

Link copied!

Hi Nikolaos,

Did you check how the IIS stop is done in the script? Could it be that error is incorrect and it can't be stopped because of timeout or certain activity? Is it 24 hours running VM?

Was this reply helpful? Yes No
Verified answer

Joris dG 17,782 on at

Like
a
(0)

Report
Copy link

Link copied!

I agree with Sergei, it's likely that the service is in a weird state and windows doesn't allow you to change the state.

Was this reply helpful? Yes No
nmaenpaa 101,172 Moderator on at

Like
a
(1)

Report
Copy link

Link copied!

Thanks Sergei & Joris, it indeed seems to have been related to wrong/unexpected status of IIS. Our VM is started before the build, and we have had 15 min lead time between the VM start and build start, and never had any issues. But seems that with 10.0.8 VM it was not enough. Now we increased the time to 20 min and it seems that the problem is gone.

Was this reply helpful? Yes No