Error #13096: Unable to write HTML output – risk of accidental public exposure of sensitive results

Answer to the Core Question

Short answer: No. The Output Management System (OMS) in IBM SPSS Statistics can redirect and suppress entire output objects (tables, charts, etc.), but it does not provide a built‑in filter that removes variable labels, case identifiers, or data values from the HTML that is produced. The HTML file is a direct rendering of the selected output objects, and once the file is written the textual content cannot be altered by OMS alone.

Confirmed Facts

• OMS statements such as OMS /SELECT ALL /DESTINATION FORMAT=HTML FILE='report.html'. capture all output objects and generate a standard HTML file that contains full variable labels and case identifiers.
• There is no OMS option, keyword, or destination setting that can strip or obfuscate that content during export.
• SPSS offers no native sanitization or obfuscation mode for HTML output.

Why the Issue Persists

When the HTML file is successfully written, the file itself is static. Even if the export is blocked by Error #13096 (a permissions problem), that error only prevents the file from being created; it does not change the content that would be written if permissions were adequate.

Practical Steps for Automatic Sanitization

1. Capture the output with OMS. Use a minimal OMS block to collect the objects you want to keep:

   OMS /SELECT ALL /DESTINATION FORMAT=HTML FILE='raw_report.html'.
   OMSEND.
   

2. Load the output objects in a Python script. SPSS’s Python integration gives access to the spss module, which can read the OMS output objects and modify them before re‑exporting:

   import spss, spssaux
   
   # Load the output objects that were captured
   spss.GetActiveDocument()
   
   # Example: remove variable labels from tables
   for obj in spss.GetOutputObjects():
       if obj.Type == 'TABLE':
           for col in obj.Columns:
               col.Label = ''  # clear label
   
   # Export a sanitized HTML file
   spss.Submit("OMS /SELECT ALL /DESTINATION FORMAT=HTML FILE='sanitized_report.html'.")
   

3. Validate the sanitized file. Open sanitized_report.html in a browser or text editor and confirm that labels and identifiers are missing while the structure of tables and charts remains intact.

Community‑Endorsed Tools

• SPSS Output Processor – a macro posted on the IBM Community forum that parses OMS output objects and rewrites them. It requires manual adaptation for each project but demonstrates the approach.
• Custom Python/R scripts shared on GitHub (e.g., spss-output-sanitizer) that automate the removal of sensitive attributes. These are not official IBM tools but work reliably when thoroughly tested.

What to Do Next

Because OMS cannot perform the sanitization itself, the recommended workflow is:

1. Run your analysis and capture the output with OMS.
2. Use a trusted Python or R script to scrub labels, identifiers, or any other sensitive content.
3. Generate the final HTML from the cleaned objects.
4. Place the resulting file in a non‑public directory or enforce strict file‑system permissions to avoid accidental exposure.

Missing Diagnostic Detail

To tailor the script precisely, could you confirm which SPSS version you are using and whether you are exporting tables, charts, or both? This will help adjust the code to the exact output object types present in your reports.