Consistent deployment failure ASDK 1805

Question

Folks,

I’ve tried several times now but I seem to be failing at the same hurdle when trying to deploy the 1805 ASDK. At a complete guess it seems to be AD related. It occurs before the server reboots and is domain joined. Note that the DC vortual machine is running. A Rerun does NOT solve the issue.

First error is:

Invoke-EceAction : Cannot file the Windows PowerShell data file ‘WindowsPackageCab.Strings.psd1’ in directory ‘c:\windows\system32\WindowsPowerShell\v1.0\Modules\PSDesiredStateConfiguration\DSCClaassResources\WindowsPackageCab\en’ or in any parent culture directories. – 08/06/2018 03:59:20 At C:\CloudDeployment\Setup\DeploySingleNode.ps1:797 char:5

Would love to get this deployed.

Lisa x

Answer 1

Hello Lisa,

After the Server reboots, is it logging in as local\administrator or AzureStack\AzureStackAdmin?

It should be logging in as AzureStack\AzureStackAdmin.

   

Also – It seems the 1805 build of the ASDK requires a writeable drive assigned to D: for installation and also uses the D: drive for log collection after installation.

Can you verify you have a writable partition assign to D:?

If not, you can go to 'Administrative Tools / Disk Management and assign a writable partition there.

 

Let us know how it goes.

  

We apologize for any inconvenience and appreciate your time and interest in Azure Stack.

If you continue experience any issues with ASDK release, feel free to contact us.

       

 Thanks, 

---

Gary Gallanes

Answer 2

Thanks for the reply Gary. The server never reboots. I don’t think I have a writeable D:\ either (will double check). I’m just reinstalling over an existing 1804 install. There is a D:\ and E:\ drive from the previous setup. Lisa x

Answer 3

Gary,

so I checked and I have a small D:\ (346MB in size with 302MB free). Is this big enough? It is also writeable. I created a folder and a file OK.

Lisa x

Answer 4

Hello Lisa,

It appears you may need some additional space on your D: drive.  I'm looking into the specific requirements now.

Can you try extend the D: partition,  restart the AzS-DC01 VM and rerun the deployment.

If you are unable to extend you D: drive, just try restarting the AzS-DC01 VM and rerunning the deployment and see if it get past the current deployment failure.

 

Let us know how it goes.

 

We apologize for any inconvenience and appreciate your time and interest in Azure Stack.

If you continue experience any issues with ASDK release, feel free to contact us.

       

 Thanks, 

---

Gary Gallanes

Answer 5

Thanks Gary. Any idea how big the D:\ needs to be? Lisa x

Answer 6

Hello Lisa,

I haven’t received an official answer regarding how much space is required by the D: drive for ASDK 1805 deployment.  

Note: One thing to keep in mind with 1805 and above:

The ASDK now uses the D: drive for log collection and the Get-AzureStackLog script tends to collect a large amount of logs.

I’d suggest 4 gigs to make sure there is plenty of room for log collection and would think 1 Gb would be plenty for deployment.

I'll reply with the official Answer as soon as I know. 

 

Let us know how it goes.

 

We apologize for any inconvenience and appreciate your time and interest in Azure Stack.

If you continue experience any issues with ASDK release, feel free to contact us.

       

 Thanks, 

---

Gary Gallanes