Troubleshoot the SIMATIC BATCH V9.0 “Cannot Start Printout” Error
For a SIMATIC BATCH V9.0 archived batch report that fails in preview with “internal error preparing data – Cannot start printout,” the available evidence does not establish report size as the cause or PCS 7 V9.0.3 UC04 as the fix. First identify whether preview is launched in BatchCC or a BATCH OS control and confirm the station is a supported local client. Treat the large-data explanation as unverified until the same report is compared across sizes or Siemens confirms a defect and applicable update.
Table of Contents
- Reported symptom
- Identify the preview path
- Troubleshooting sequence
- Is an additional package required?
- Expected results
- Verification
- Limitations and Operational Precautions
- Engineer FAQ
- Technical References
- Related Articles
- Related Tags
Reported symptom
The system is reported as PCS 7 V9.0 with SIMATIC BATCH V9.0. On some OS clients, previewing an archived BATCH report fails with internal error preparing data Cannot start printout. The reply attributes this possibly to large data and recommends “PCS 7 V9.0.3 UC04.” No report size, exact BATCH update level, client type, logs, or Siemens issue reference is supplied.
Identify the preview path
The SIMATIC BATCH V9.0 manual describes report printing and preview in the BATCH Control Center and through the SIMATIC BATCH OS Process Cell control. It states that Print and Print Preview are unavailable on a Web client. Identify whether the affected station is a local OS station, a configured BATCH client, or a Web client and record the interface used. The Web-client limitation is distinct from an error on a local OS client.
Troubleshooting sequence
- Record exact PCS 7 and SIMATIC BATCH versions and SP/Update levels on the affected client and relevant server.
- Identify the access path: BatchCC preview or the
SIMATIC BATCH OS Process Cellcontrol. Confirm the station is configured for the required BATCH/OS client role. - Compare preview of a small and a large archived report from the same client path, where available. Record whether the failure follows report size, report identity, or station. This is diagnostic evidence, not proof of a general data-size limit.
- Check whether the same report previews on a known-working BATCH client and whether other reports preview on the affected one.
- Capture the complete error, timestamp, report/batch reference, client/server software levels, and relevant diagnostics. Keep customer and recipe details private.
- Compare the exact installed versions with Siemens update Readmes. The phrase “PCS 7 V9.0.3 UC04” is not specific enough here to validate the package or connect it to this error; confirm its exact identity and applicability before planning an update.
Is an additional package required?
The source does not identify a missing report component or package requirement. Siemens' V9.0 manual documents print preview in supported BATCH interfaces, with a Web-client limitation. Do not install an arbitrary package based only on the message. If the design includes a Process Historian archive server, check the applicable BATCH/PH documentation for report-template and Web Service prerequisites; the ticket does not say that it does.
Expected results
A useful diagnosis should determine whether the failure is specific to a report, report size, client station, or preview interface. The source does not report a confirmed update or configuration fix. After an approved change, test the same report and a second report, and confirm the preview contents are complete.
Verification
Record the baseline result for the same archived report, client, and preview path. After an approved change, retry that report and another report; verify preview opens, page navigation works, and report content is complete. Check the installed software level and relevant diagnostics. Do not claim a PCS 7 update resolved the issue unless that result is observed on the actual system.
Limitations and Operational Precautions
No Siemens document found in this research links internal error preparing data or Cannot start printout to large report size or confirms the proposed PCS 7 V9.0.3 UC04 fix. Retain that update string as source-reported and verify its exact package identity rather than reinterpreting it. The error could require investigation of report data, client role, report-template/service configuration, or software defects, but none is established here. PCS 7 or SIMATIC BATCH updates require project backups and the matching version's update procedure.
Engineer FAQ
Is large report size a confirmed cause? No. A reply proposes it, but no report-size comparison or Siemens defect reference is provided.
Can a BATCH Web client preview reports? The SIMATIC BATCH V9.0 manual says Print and Print Preview are unavailable on a Web client.
Does the evidence prove that another package is needed? No missing component is identified. Confirm the client role and installed BATCH components before adding packages or updating software.
Technical References
- Siemens, SIMATIC BATCH V9.0 Operating Manual, 05/2017, A5E38210537-AA, §4.14 “OS controls: Print and print preview,” p. 113, and §11.4.18 “Printing, viewing and exporting a batch report,” pp. 660–663. The official PDF was downloaded and read; it documents report preview and the Web-client restriction: https://cache.industry.siemens.com/dl/files/661/109748661/att_923993/v1/sb-onlinehelp_b_en-US.pdf
- Siemens, SIMATIC BATCH V9.0 SP1 Operating Manual, 11/2017, A5E38210537-AB. This later SP1 manual applies only if the installation is confirmed at that level and does not verify the error or proposed V9.0.3 UC04 fix: https://cache.industry.siemens.com/dl/files/007/109755007/att_939521/v1/sb-onlinehelp_b_en-US.pdf
Related Articles
- Search IndustrialAutomation.net for SIMATIC BATCH report preview errors
- Search IndustrialAutomation.net for PCS 7 V9.0 updates