运行PowerShell文件迁移脚本时遭遇「文件无法访问，被其他进程占用」错误的技术求助

Troubleshooting & Fixes #

Let's break down the most likely causes and practical fixes to resolve this lock error:

1. Detect Locked Files Before Processing #

This error means another process has the file open (QlikView Desktop, a server service, even another script instance). Add a helper function to check for locks upfront:

function Test-FileLock {
    param([string]$Path)
    try {
        # Attempt to open the file with exclusive read/write access to detect locks
        $fileStream = [System.IO.File]::Open($Path, [System.IO.FileMode]::Open, [System.IO.FileAccess]::ReadWrite, [System.IO.FileShare]::None)
        if ($fileStream) { $fileStream.Close() }
        return $false
    }
    catch {
        # If we can't open it, the file is locked
        return $true
    }
}

Use this at the start of your file processing loop to skip locked files and log the issue:

$result = $files | ForEach-Object {
    Write-Host "Processing file '$($_.FullName)'"
    
    # Check for locks first
    if (Test-FileLock -Path $_.FullName) {
        $out = $_ | Select-Object @{Name='Date'; Expression={(Get-Date)}},
                                  @{Name='Source'; Expression={$_.FullName}},
                                  FileSize, Destination, Archive, Result
        $out.Result = "Error: File is locked by another process"
        $out
        continue
    }

    # Rest of your existing logic goes here...
}

2. Add Retry Logic for Transient Locks #

Network shares or busy processes often cause temporary locks. Wrap your Move-Item calls in a retry function to handle these cases:

function Move-WithRetry {
    param(
        [string]$Path,
        [string]$Destination,
        [int]$MaxRetries = 3,
        [int]$RetryDelay = 2 # Seconds between retries
    )
    $retryCount = 0
    do {
        try {
            Move-Item -Path $Path -Destination $Destination -ErrorAction Stop -Force
            return $true
        }
        catch {
            $retryCount++
            if ($retryCount -ge $MaxRetries) {
                throw $_ # Re-throw if we've exhausted retries
            }
            Write-Host "Retry $retryCount/$MaxRetries for file '$Path'..."
            Start-Sleep -Seconds $RetryDelay
        }
    } while ($retryCount -lt $MaxRetries)
}

Replace your existing Move-Item calls with this function:

# When archiving existing files
if (Test-Path -Path $existingFile -PathType Leaf) {
    $null = New-Item -Path $ArchiveData -ItemType Directory -Force
    try {
        if (Move-WithRetry -Path $existingFile -Destination $ArchiveData) {
            $out.Archive = $existingFile
            Write-Host "File '$existingFile' backed up to '$ArchiveData'"
        }
    }
    catch {
        $out.Result = "Archive Error: $($_.Exception.Message)"
        $out
        continue
    }
}

# When moving the source file
try {
    if (Move-WithRetry -Path $_.FullName -Destination $destFolder) {
        $out.Result = 'The tool has been uploaded'
        Write-Host "File '$($_.FullName)' moved to '$destFolder'"
    }
}
catch {
    $out.Result = "Move Error: $($_.Exception.Message)"
}

3. Avoid Unnecessary File Handle Leaks #

Using Get-ChildItem directly in the pipeline can sometimes leave file handles open. Instead, collect file paths as strings first, then re-fetch the file object when needed:

# Replace your initial $files collection with this
$filePaths = @(Get-ChildItem -Path $Source -File -Force -Recurse | Select-Object -ExpandProperty FullName)
if ($filePaths.Count -eq 0) { exit }

$result = $filePaths | ForEach-Object {
    $file = Get-Item -Path $_
    Write-Host "Processing file '$($file.FullName)'"
    
    # Rest of your logic uses $file instead of $_
    $out = $file | Select-Object @{Name='Date'; Expression={(Get-Date)}},
                                  @{Name='Source'; Expression={$file.FullName}},
                                  @{Name='FileSize'; Expression={$file.Length / 1GB}},
                                  Destination, Archive, Result
    # ... continue with existing checks and logic
}

4. Reset Stale SMB Connections #

Remote share connections can get stuck, causing unexpected locks. Add this at the start of your script to reset connections to the target server:

# Disconnect and re-establish SMB connections to the target server
Get-SmbConnection | Where-Object RemotePath -match '\\\\192.168.1.10' | Remove-SmbConnection -Force -ErrorAction SilentlyContinue

5. Check QlikView-Specific Locks #

Since these are .qvw files, verify:

• QlikView Desktop doesn't have the file open (close it before running the script)
• QlikView Server services (like QlikViewServer.exe or QVB.exe) aren't holding the file open (restart the service if needed)
• No scheduled QlikView tasks are running and accessing the file (wait for tasks to complete)

内容的提问来源于stack exchange，提问作者essex info