# Troubleshooting and Diagnostics

Troubleshooting and Diagnostics on Evotec with installation guidance, setup notes, reference details, and project documentation.

Project

PSWriteOffice

PowerShell document automation across OfficeIMO's document, spreadsheet, presentation, PDF, Project, Access, EPUB, invoicing, and conversion engines.

[View on GitHub](https://github.com/EvotecIT/OfficeIMO/tree/master/PowerShell/PSWriteOffice) [Visit Website](#) [Releases](https://github.com/EvotecIT/PSWriteOffice/releases/tag/v3.0.5) [Changelog](#) [Get package](https://www.powershellgallery.com/packages/PSWriteOffice)

Stars**722**

Forks**84**

Open issues**2**

PowerShell Gallery downloads**5165548**

Release**v3.6.2**

Language: C# Updated: 2026-11-21

Documentation

Diagnose module loading, file-format routing, rewrite safety, conversion fidelity, and platform-specific dependencies. Includes examples and cmdlet links.

Start troubleshooting by identifying the layer that failed: module loading, command binding, source-file detection, native document parsing, mutation, conversion, or final save.

## Confirm the loaded module

```powershell
Get-Module PSWriteOffice | Format-List Name,Version,Path
Get-Command -Module PSWriteOffice -Name '*OfficePdf*' | Select-Object Name,CommandType
```

Multiple installed versions can make an interactive session differ from CI. Import the intended version in a fresh process and record the module path.

## Keep the original exception and diagnostics

Use `-ErrorAction Stop` around the bounded operation and preserve the full exception. Prefer format-specific diagnostic and preflight commands over retrying the same rewrite blindly.

## Reopen generated output

After a save or conversion, load the output through the matching reader, extract a stable marker, and inspect warnings. For visual formats, a rendered review artifact can supplement structural checks but should not replace them.

## Separate unsupported behavior from corruption

A converter can reject or warn about a feature it does not map; that is different from producing a malformed destination. Retain conversion diagnostics and choose an explicit fallback policy instead of silently dropping content.

## Check optional boundaries

OCR, web transport, authentication, native rendering, and external-process adapters can have platform or deployment requirements beyond the core managed module. Confirm those dependencies in the relevant OfficeIMO package guide and test the exact deployment path.

## Prepare a useful issue

Include the PSWriteOffice version, PowerShell version/edition, operating system, command and parameters, a minimal input when shareable, the complete exception, and relevant diagnostic output. Remove secrets and personal document content before attaching files.

<!-- PowerForge markdown artifact sha256:C555B606DE2C6D0DADF12403FFD4938D2E05D3349A1562E725C0069C49CA6328 -->
