Invoke-DbaDbLogShipping error: [Backup-DbaDatabase] SQL Server cannot check if \\HOST\Share\some\url exists. You can try disabling this check with -IgnoreFileChecks #9303
WARNING: [13:25:41][Backup-DbaDatabase] SQL Server cannot check if \HOST\Share\some\url exists. You can try disabling this check with -IgnoreFileChecks
WARNING: [13:25:41][Invoke-DbaDbLogShipping] Something went wrong restoring the secondary database | Cannot bind
argument to parameter 'Path' because it is null.
Please confirm that you are running the most recent version of dbatools
2.1.5
Other details or mentions
Upon running the Invoke-DbaDbLogShipping command as described above the first time, I get the described error. If I run it a second time, I do not (the folder existence check succeeds). Seems there is latency in creating the folder that might be unaccounted for in the Invoke-DbaDbLogShipping process?
What PowerShell host was used when producing this error
Source is Microsoft SQL Server 2016 (SP3-GDR) (KB5014355) - 13.0.6419.1 (X64) May 29 2022 21:05:29 Copyright (c) Microsoft Corporation Enterprise Edition (64-bit) on Windows Server 2012 Standard 6.2 (Build 9200: ) (Hypervisor)
Destination is Microsoft SQL Server 2019 (RTM-CU24) (KB5031908) - 15.0.4345.5 (X64) Dec 4 2023 14:44:16 Copyright (C) 2019 Microsoft Corporation Developer Edition (64-bit) on Windows Server 2019 Datacenter 10.0 (Build 17763: ) (Hypervisor)
I don't see a mechanism to pass the mentioned "-IgnoreFileChecks" argument from Invoke-DbaDbLogShipping command to the erroring sub commandlet, Backup-DbaDatabase that seems to need it.
Verified issue does not already exist?
I have searched and found no existing issue
What error did you receive?
WARNING: [13:25:41][Backup-DbaDatabase] SQL Server cannot check if \HOST\Share\some\url exists. You can try disabling this check with -IgnoreFileChecks WARNING: [13:25:41][Invoke-DbaDbLogShipping] Something went wrong restoring the secondary database | Cannot bind argument to parameter 'Path' because it is null.
Steps to Reproduce
$params = @{ SourceSqlInstance = "HOST1" DestinationSqlInstance = "HOST2" Database = "SomeDB" LocalPath = "Y:\SQLBackup\SQLInstance\LogShip" SharedPath = "\HOST\Share\Test\SQLInstance\LogShip" CopyDestinationFolder = "\HOST\Share\Test\SQLInstance\LogShip" GenerateFullBackup = $true BackupJob = "zLSBackup" BackupRetention = 10080 CompressBackup = $true CopyJob = "zLSCopy" CopyRetention = 10080 RestoreJob = "zLSRestore_" RestoreRetention = 10080 Standby = $false Force = $true }
Invoke-DbaDbLogShipping @params
Please confirm that you are running the most recent version of dbatools
2.1.5
Other details or mentions
Upon running the Invoke-DbaDbLogShipping command as described above the first time, I get the described error. If I run it a second time, I do not (the folder existence check succeeds). Seems there is latency in creating the folder that might be unaccounted for in the Invoke-DbaDbLogShipping process?
What PowerShell host was used when producing this error
Windows PowerShell (powershell.exe)
PowerShell Host Version
Name Value
PSVersion 5.1.17763.4840
PSEdition Desktop
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...}
BuildVersion 10.0.17763.4840
CLRVersion 4.0.30319.42000
WSManStackVersion 3.0
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1
SQL Server Edition and Build number
Source is Microsoft SQL Server 2016 (SP3-GDR) (KB5014355) - 13.0.6419.1 (X64) May 29 2022 21:05:29 Copyright (c) Microsoft Corporation Enterprise Edition (64-bit) on Windows Server 2012 Standard 6.2 (Build 9200: ) (Hypervisor)
Destination is Microsoft SQL Server 2019 (RTM-CU24) (KB5031908) - 15.0.4345.5 (X64) Dec 4 2023 14:44:16 Copyright (C) 2019 Microsoft Corporation Developer Edition (64-bit) on Windows Server 2019 Datacenter 10.0 (Build 17763: ) (Hypervisor)
.NET Framework Version
PSChildName Version
Client 4.7.03190 Full 4.7.03190 Client 4.0.0.0