C135 PCS 7 (PCS7)
6C
6 Cielo Ciencia y Tecnología
·Publicada en C135 PCS 7 (PCS7)

Resolving SIMATIC BATCH Download Error Check Batch Installation on Target Computers

Resolving SIMATIC BATCH Download Error Check Batch Installation on Target Computers

The error 'Check Batch installation on target computers' during SIMATIC BATCH project download indicates a station name discrepancy in the multiproject configuration or an invalid target OS computer path. In redundant SIMATIC BATCH V7.1 / V8.x systems, verify that the Computer Name defined in the PC Station properties matches the exact uppercase Windows NetBIOS hostname of the target server. Furthermore, open the 'Configure Batch Process Cell' dialog in SIMATIC Manager, select 'OS Objects', clear any obsolete hardcoded local directory paths, and ensure the path is left blank to utilize automatic UNC resolution. Finally, recompile and download the batch process cell.

Table of Contents

Executive Summary

Deploying recipe procedural phases and unit allocation models in SIMATIC BATCH requires compiling the batch process cell from SIMATIC Manager and downloading the compiled project instances across the Terminal Bus to redundant BATCH Servers and Operator Stations. During this download sequence, engineering systems frequently abort with the error message Check Batch installation on target computers, accompanied by red warning icons next to target stations in the download dialog. While the error suggests missing software on the servers, the underlying fault almost universally stems from configuration discrepancies on the Engineering Station (ES)—specifically mismatched PC station computer names, obsolete file sharing paths, or stale redundant partner mappings. This technical guide outlines the configuration audit and network path settings required to restore clean BATCH downloads.

SIMATIC BATCH Download Architecture: Multiproject Station Resolution

The SIMATIC BATCH download engine communicates with target servers through Windows Remote Procedure Calls (RPC) and administrative file shares (C$, DEVICES, and BATCH). When an engineer initiates a download:

  1. The ES queries the local multiproject database for the Computer Name assigned to each PC Station.
  2. The ES attempts to resolve the computer name via DNS/NetBIOS and verifies that the SIMATIC BATCH runtime service (bfserverx.exe) is running on the remote node.
  3. If the hostnames do not resolve, or if the station properties point to an obsolete laptop name from a previous commissioning session, the communication handshake times out, producing the 'Check Batch installation' abort.

Root Causes for 'Check Batch Installation' Download Aborts

Four primary configuration errors cause this download failure:

  1. Host Name Mismatch: The PC Station name in SIMATIC Manager does not match the actual Windows computer name configured under Windows System Properties on the target OS server.
  2. Hardcoded Local Directory Paths: In the 'Configure Batch Process Cell > OS Objects' dialog, engineers often type local hard drive paths (e.g. D:\PCS7_OS\) which fail when queried over network shares. Leaving the target path blank forces the wizard to resolve paths automatically.
  3. Stale Redundant Partner Entries: Following a server replacement or rename, the old server entry remains registered in the BATCH process cell with a red 'X', blocking batch downloads to the healthy server pair.
  4. Windows Firewall / DCOM Blocking: If TCP port 135 or dynamic RPC ports are blocked on the target server, the BATCH installation check probe cannot establish a handshake.

Redundant Server Synchronization and OS Object Mapping

In redundant architectures (BATCH Server 1 and BATCH Server 2), both stations must be assigned identical process cell attributes. If Server 1 resolves but Server 2 has an incorrect computer name or broken network route, the BATCH compiler aborts the entire download to protect database redundancy integrity.

BATCH Download Diagnostic and Configuration Matrix

The following table compares download error states, underlying root causes, and corrective actions in SIMATIC BATCH:

Error Message / Dialog SymptomUnderlying Root CauseVerification ToolCorrective Engineering ActionCheck Batch installation on target computersPC Station computer name mismatch or invalid UNC path.Windows System Properties vs SIMATIC ManagerAlign PC Station name with uppercase Windows hostname.Red 'X' on OS Object in Batch ConfigurationStale server reference remaining after hardware rename.BATCH Process Cell dialogDelete obsolete OS object and regenerate batch objects.Target OS computer path errorHardcoded local drive path configured instead of UNC.OS Objects Properties dialogSet 'Path to target OS computer' to completely blank.Error connecting to Batch ServiceWindows firewall blocking RPC or SIMATIC service stopped.Windows Services (services.msc)Start BATCH services; open firewall ports 135, 445.Batch compilation succeeds but download disabledPlant hierarchy or OS compilation out of date.SIMATIC Manager Project TreeExecute full AS compile, OS compile, then BATCH compile.

Step-by-Step Resolution and Station Alignment Procedure

Method 1: Re-aligning PC Station Computer Names

  1. On the physical target BATCH Server, open Windows Command Prompt and type hostname. Note the exact uppercase name (e.g. BATCHSRV01).
  2. On the Engineering Station, open the project in SIMATIC Manager.
  3. Select the target BATCH Server PC Station, right-click, and select Object Properties.
  4. In the Computer name field, enter the exact hostname noted in Step 1. Ensure no trailing spaces exist.
  5. Repeat this step for the redundant partner station (e.g. BATCHSRV02).

Method 2: Blanking the Target OS Computer Path

  1. In SIMATIC Manager, select the BATCH process cell object.
  2. Right-click and choose Open Object (or open Configure Batch Process Cell).
  3. Navigate to the OS objects tab.
  4. Select each OS and BATCH server object in the list.
  5. Locate the setting Path to target OS computer and delete any text so that the field is completely BLANK.
  6. Click OK to save changes.
  7. Right-click the BATCH object, select Compile, choose Entire plant, and execute.
  8. Select Download; verify that all target servers display green checkmarks and download completes successfully.

Verification

To verify successful BATCH download and station synchronization:

  1. Download Dialog Status: Confirm that in the SIMATIC BATCH Download window, all target nodes display status 'OK' with green indicator circles.
  2. Server Operational State: On the primary and secondary BATCH servers, open the BATCH Launch Coordinator. Confirm that services transition to 'Running' (Green).
  3. Recipe Validation: Open BatchCC, create a control recipe incorporating the newly downloaded phases, and verify that the recipe validates with 0 errors.

Limitations and Operational Precautions

  • Active Batch Hazard: Never initiate a BATCH download with option 'Entire plant' while production batches are actively running; doing so interrupts recipe step timers and forces units into Hold state.
  • Redundant Pair Parity: Both redundant BATCH servers must run identical software versions, service packs, and hotfixes (e.g., both must run BATCH V7.1 SP1 HF2).
  • Administrative Privileges: The Windows user initiating the download from the ES must possess local Administrator and SIMATIC BATCH Administrators rights on all target servers.

Engineer FAQ

Why does SIMATIC BATCH recommend leaving the target OS path blank?

Leaving the path blank allows SIMATIC BATCH to resolve the target destination automatically using standardized Windows UNC shares, avoiding broken local drive letters.

Can I download SIMATIC BATCH to one server while the redundant partner is turned off?

Yes, but the download dialog will flag the offline partner as unreachable. Once powered on, execute 'Update Plant Data' on the partner to restore database synchronization.

Where are download failure details recorded on the Engineering Station?

Detailed download transaction logs are stored at C:\Program Files (x86)\Siemens\Automation\Batch\Logs\BatchDownload.log.

Technical References

Related Articles

Related Tags

  • https://industrialautomation.net/search?query=simatic-pcs7
  • https://industrialautomation.net/search?query=simatic-batch
  • https://industrialautomation.net/search?query=redundancy
  • https://industrialautomation.net/search?query=troubleshooting
6 respuestas