search

MicrosoftLearning / AZ-120-Planning-and-Administering-Microsoft-Azure-for-SAP-Workloads

Labs for AZ-120 Planning and administering Microsoft Azure for SAP workloads
MIT License
64 stars 86 forks source link

AZ-120_Lab01b-Azure_VM_Windows_Clustering.md - Deploy error #70

Closed TesterTesterson1004 closed 10 months ago

TesterTesterson1004 commented 1 year ago

Module/Lab: 1B

Exercise: 01

Task: 01

Step: 11

Description of issue

Multiple attempts (from fresh lab start) trying to deploy the 2 DCs for this lab are failing, apparently on extension 'PepareBDC', (sic) which I have not seen before in this course.

Repro steps:

  1. Take lab as written
  2. Received error last night in EastUS, multiple times this morning in EastUS2 & CentralUS (does not seem to be region specific)
  3. Tried workaround referenced in this steps 'note', however removing the 'PepareBDC' extension fro the BDC VM and rerunning from step 10/11 does not help. (in this case, if you attempt to redploy you have to start from the beginning, apparenlty)
  4. Have not been able to figure out anything useful whilst troubleshooting it as to why it would be failing, nor do I know how long it has been since it stopped working.

Relevant screenshots

image

image

image

image

SkillableKarl commented 1 year ago

I saw same behavior, and while the workaround given in the Step 11 didn't initially work, I believe what might be happening is that the initial long (~30 minutes deploy) occurs, and if (as I did in my first test) ...the person taking the lab has become impatient and jumped ahead to start installing the next 2 VMs, which make use of the adVNET resource from the first deploy - that is probably what causes the workaround in Step 11 to fail.

In a better world, these VM deploys would not experience the extension install failures at all and our VM deploys would 'just work' so we wouldn't have to deal with this. Until that happens, will just have to be sure student is referred to, and has read, Step 11's 'Wait for the deployment to complete before you proceed to the next task.' note.

At least, it may be good to update the text in that step 'remove the CustomScript extension' to 'remove the PepareBDC extension', since that's the one that seems to be causing every deploy to fail in this lab:

image

polichtm commented 10 months ago

this has been addressed - you can either ignore the current error (the resulting deployment is fully functional) or remediate it by following the updated instructions. rgds Marcin