Windows搜索索引PowerShell脚本问题求助：异常与高亮需求

Hey there, let's work through your two PowerShell script issues step by step:

First, let's tackle those random OleDbExceptions you're seeing. The fact that removing System.Search.Rank fixes things and repeated runs crash points to potential resource handling issues with the Windows Search OLE DB provider, or maybe concurrency conflicts when hitting the index too quickly. Here's how to address this:

Fix 1: Improve Resource Management #

Your current dispose calls are good, but wrapping everything in a try/finally block ensures resources get cleaned up even if an error hits mid-execution. I've also added a fallback query that skips the Rank field if the original fails:

function Search-FileInIndex ($firstname, $lastname) {
    $sql = @"
SELECT System.ItemName, System.DateCreated, System.ItemPathDisplay, System.Search.Rank 
FROM SYSTEMINDEX 
WHERE CONTAINS('"$firstname" NEAR "$lastname"') 
  AND SCOPE= 'c:\' 
  AND System.Search.Rank > 0 
ORDER BY System.ItemPathDisplay
"@
    $provider = "provider=search.collatordso;extended properties='Application=Windows'"
    
    $connector = $null
    $dataset = $null
    try {
        $connector = New-Object System.Data.OleDb.OleDbDataAdapter -ArgumentList $sql, $provider
        $dataset = New-Object System.Data.DataSet
        
        if ($connector.Fill($dataset)) {
            $dataset.Tables[0] | Format-Table -AutoSize *
        }
    }
    catch [System.Data.OleDb.OleDbException] {
        Write-Warning "OleDb Error hit: $($_.Exception.Message)"
        Write-Host "Falling back to query without System.Search.Rank..."
        
        # Fallback query without Rank
        $fallbackSql = @"
SELECT System.ItemName, System.DateCreated, System.ItemPathDisplay 
FROM SYSTEMINDEX 
WHERE CONTAINS('"$firstname" NEAR "$lastname"') 
  AND SCOPE= 'c:\' 
ORDER BY System.ItemPathDisplay
"@
        $connector = New-Object System.Data.OleDb.OleDbDataAdapter -ArgumentList $fallbackSql, $provider
        $dataset = New-Object System.Data.DataSet
        if ($connector.Fill($dataset)) {
            $dataset.Tables[0] | Format-Table -AutoSize *
        }
    }
    finally {
        # Ensure cleanup no matter what
        if ($dataset) { $dataset.Dispose() }
        if ($connector) { $connector.Dispose() }
    }
}

Search-FileInIndex john doe

Fix 2: Avoid Repeated Rapid Queries #

The "pipe ended" error often happens if you hit the index before it's finished processing the last request. Add a short delay between repeated runs:

# Example of spaced-out runs
Search-FileInIndex john doe
Start-Sleep -Milliseconds 750
Search-FileInIndex jane smith

NEAR Search Alternatives #

If NEAR is causing instability, here are some workarounds depending on your needs:

• AND with wildcards (good for filename matching):

  CONTAINS(System.ItemName, '"$firstname*" AND "$lastname*"')
  

• FREETEXT (fuzzy matching, broader results):

  FREETEXT(System.ItemName, '$firstname $lastname')
  

• LIKE with order checks (simple but less performant for large indexes):

  System.ItemName LIKE '%$firstname%$lastname%' OR System.ItemName LIKE '%$lastname%$firstname%'
  

You're right that the old API is deprecated—using the Shell COM interface is the way to go. This script uses Shell.Application to run the search and pulls highlighted fragments via extended properties:

function Search-FileWithHighlight {
    param(
        [string]$firstname,
        [string]$lastname
    )

    # Initialize Shell COM object
    $shell = New-Object -ComObject Shell.Application
    $searchRoot = $shell.Namespace("C:\")
    $searchQuery = "filename:`"$firstname`" NEAR `"$lastname`""
    
    try {
        $searchResults = $searchRoot.Search($searchQuery)
        
        foreach ($item in $searchResults.Items()) {
            # Get basic file details
            $fileName = $item.Name
            $filePath = $item.Path
            $dateCreated = $item.GetDetailsOf($item, 4) # 4 = Date Created (adjust index if needed)
            
            # Get highlighted content from search properties
            $highlightedName = $item.ExtendedProperty("System.Search.HitHighlightedDisplayName")
            $highlightedSummary = $item.ExtendedProperty("System.Search.HitHighlightedSummary")

            # Print results with highlights
            Write-Host "`n=== File Found ==="
            Write-Host "Name: $fileName"
            if ($highlightedName) {
                Write-Host "Highlighted Name: *$($highlightedName -replace '<c0>|<\/c0>', '*')*"
            }
            Write-Host "Path: $filePath"
            Write-Host "Created: $dateCreated"
            if ($highlightedSummary) {
                Write-Host "Highlighted Content: $($highlightedSummary -replace '<c0>|<\/c0>', '*')"
            }
        }
    }
    catch {
        Write-Warning "Search failed: $($_.Exception.Message)"
    }
    finally {
        # Clean up COM objects to avoid memory leaks
        if ($searchResults) { [System.Runtime.Interopservices.Marshal]::ReleaseComObject($searchResults) | Out-Null }
        if ($searchRoot) { [System.Runtime.Interopservices.Marshal]::ReleaseComObject($searchRoot) | Out-Null }
        if ($shell) { [System.Runtime.Interopservices.Marshal]::ReleaseComObject($shell) | Out-Null }
    }
}

# Run the search
Search-FileWithHighlight john doe

Notes on Highlighting: #

• The script replaces the default <c0> highlight tags with asterisks for better readability in the console.
• System.Search.HitHighlightedSummary works best for text-based files (like .txt, .docx, etc.) that Windows Search can index content for.
• If the date created index doesn't return the right value, run $searchRoot.GetDetailsOf($searchRoot.Items(), 0) to list all property indexes for your specific system.

内容的提问来源于stack exchange，提问作者Hans Blafoo