Issue during import-module

[jurgendhooge]

Hi,

I'm not sure if this is the correct place to ask this kind of question, so I apologise in advance if it isn't.

I'm trying to debug a script that uses d365fo.tools for doing a DB refresh in LCS.
This is a Powershell script being called from a DevOps pipeline that worked fine until August 12th.

At the start of the script, it tries to confirm whether the d365fo.tools module is installed on the environment already [in this case a Tier 2 LCS F&O environment, not sure if that is relevant] and import it:

[Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12 
Install-PackageProvider nuget -force
[Environment]::SetEnvironmentVariable("ServiceDrive", "C:", "Machine")

if (Get-Module -ListAvailable -Name d365fo.tools) {
    Write-Host "Module d365fo.tools exists, importing..."
    Import-Module d365fo.tools
    Write-Host "Done"

The error in my release pipeline reads:

2022-08-18T05:02:57.1837638Z Module d365fo.tools exists, importing...
2022-08-18T05:03:10.0075003Z Import-ModuleFile : Exception calling "InvokeScript" with "4" argument(s): 
2022-08-18T05:03:10.0075691Z "The running command stopped because the preference variable 
2022-08-18T05:03:10.0076128Z "ErrorActionPreference" or common parameter is set to Stop: Cannot find drive. 
2022-08-18T05:03:10.0076550Z A drive with the name 'K' does not exist."
2022-08-18T05:03:10.0076822Z At C:\Program 
2022-08-18T05:03:10.0079201Z Files\WindowsPowerShell\Modules\d365fo.tools\0.6.71\d365fo.tools.psm1:83 char:3
2022-08-18T05:03:10.0079805Z +         . Import-ModuleFile -Path "$($script:ModuleRoot)\resourcesAft ...
2022-08-18T05:03:10.0080443Z +         ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2022-08-18T05:03:10.0080900Z     + CategoryInfo          : NotSpecified: (:) [Import-ModuleFile], MethodInv 
2022-08-18T05:03:10.0081413Z    ocationException
2022-08-18T05:03:10.0081945Z     + FullyQualifiedErrorId : ActionPreferenceStopException,Import-ModuleFile

So from what I can tell it tries to Import-Module d365fo.tools after which it lands in d365fo.tools.psm1 on line 83, but I'm not sure where the four arguments to the Import-ModuleFile command would be coming from, or where it gets this K drive from.

I noticed that in earlier, working runs of the script, it would note that it could not find a %ServiceDrive% variable and default to the C drive, even though we set it to the K drive. I've tried changing that part to the C drive instead as you can tell, but to no avail.
[Environment]::SetEnvironmentVariable("ServiceDrive", "C:", "Machine")

Any idea where it could be getting that K drive from?

Thanks in advance,
Jürgen

[FH-Inway]

Could you confirm that this is actually an LCS T2 (and not T1) environment? If yes, is this environment hosted on premise (local business data)? If not, do you know how the d365fo.tools were installed on it?

[jurgendhooge]

Hi,

Apologies for the late reply, it took a bit of asking around.

Apparently, the DevOps agent that runs the PowerShell scripts has been installed on a non-LCS VM, unrelated to the two Tier 2 environments that are the source and target of the DB refresh it's trying to execute.

We've doublechecked that the d365fo.tools module is installed on this VM and updated it to the latest version (*.73).
We also noticed in the file resourcesAfter.ps1 that the ServiceDrive is set to the C drive by default, which is a drive that exists on this non-LCS VM, so we removed our explicit setting of this value through [Environment]::SetEnvironmentVariable("ServiceDrive", "C:", "Machine") from our script, and also removed it from the system environment variables on the VM.

For now, we'll see if this helps the situation.

Thanks for your reply!