Troubleshoot SIMATIC BATCH Archive Failures to a Remote Directory

A successful connection test and write access from the interactive Windows user do not establish that SIMATIC BATCH can archive a batch to the configured target. Check that the batch is complete, that the project uses the intended archive technology and UNC share, and that the Windows identity used by the Batch runtime can create and write files there. The reported error image and SIMATIC BATCH version are missing, so the specific failure cannot be diagnosed from the available details.

Applies To

This procedure addresses long-term batch archiving to a shared directory. The report says the target is remote, the directory is empty, the logged-in user can create files, and the BCC test succeeds; it does not include the actual error message, archive method configuration, server topology, or SIMATIC BATCH version. Siemens documents version-specific archive behavior, so verify each step in the installed release's online help.

How Directory Archiving Uses Windows Access

SIMATIC BATCH documentation describes the Directory method as saving batch archive files to a shared network folder. The authentication uses Windows security mechanisms rather than separate SIMATIC BATCH directory credentials. Consequently, an interactive user's ability to create files is not sufficient proof that the runtime/server process identity can write to the share. A BCC connection test checks the configured connection, but a completed archive action also requires an eligible batch and a successful write by the archiving workflow.

Check Batch Eligibility and Archive Method

Confirm the batch is completed. Siemens' SIMATIC BATCH manuals state that only completed batches can be archived.
In BatchCC, verify the configured archiving technology for the project is Directory, rather than SQL Server or FTP Server.
Check the target path exactly as configured. For a remote folder, use its network share path in UNC form, for example \\server\share\archive; do not rely on a drive letter mapped only in the logged-in desktop session.
Run the BCC connection test and record its full result. Treat success as a useful connection check, not proof that an individual batch archive completed.
Select one completed test batch and run the documented Archive command. Capture the complete error text and time if the operation fails.

Check the Actual Windows Identity and Permissions

Identify which computer hosts the SIMATIC BATCH server/runtime and which account the relevant service or process uses in this installation. Do not assume it is the currently logged-in BatchCC user.
On the remote file server, check both share permissions and NTFS permissions for the identity used by the Batch archive operation. Confirm it can create, write, close and rename files if the documented archive workflow requires those actions; avoid granting broad Everyone write access as a general fix.
Check whether the Batch server uses a domain account or local account and whether the target server can authenticate that identity. A local account on one computer may not authenticate as the same identity on another computer.
Verify that the configured UNC path resolves from the Batch server and that the share is available to that machine under the runtime security context.
Re-run the BCC test and archive a completed test batch, then inspect the target directory for the newly generated archive file and confirm the operation reports completion.

If the Connection Test Succeeds but Archiving Still Fails

A successful test narrows the issue but does not identify the cause. Compare the test and archive execution contexts and ensure the test used the exact configured path. Then check batch completion state, project archive method, the server-side Windows identity, share/NTFS rights, name conflicts, and the complete Batch/Windows event details at the failure time. These are diagnostic checks, not confirmed causes for the source case. If all match and the failure persists, preserve the message and logs and escalate using the installed version's Siemens support procedure.

Security and Data Handling

Batch archives are production records. Siemens' BATCH documentation says directory archive files are stored in a shared network folder and require Windows security protection. Grant only the required identities the needed rights, protect archive data against unauthorized access or modification, and follow site retention and backup policy. Do not make the share writable by broad groups merely because an interactive write test succeeds.

Expected Results

For a completed batch, the configured Directory archive method should produce the batch archive at the intended shared location, with the BCC operation reporting completion. Confirm the output file exists and that the archived batch can be opened or viewed using the supported BatchCC archive viewer. A successful path test alone is not the expected final result.

Verification

Use a completed, noncritical test batch where permitted. Record the configured method and UNC path, the identity used by the runtime, the full test result, and the complete archive-operation result. Verify that an archive file was created at the correct target and can be read by the authorized viewer. The source contains no successful archive result, file name or error details, so no specific recovery outcome can be claimed.

Limitations and Operational Precautions

The source's error image is absent, and the SIMATIC BATCH and PCS 7 versions are unspecified. The official documentation excerpts establish directory archiving, Windows-based access control and batch completion requirements, but the relevant Siemens PDFs could not be fully opened in this session (timeouts/HTTP 403). The exact BCC test semantics and error-specific remedy therefore remain unverified. Do not delete or overwrite existing production archives, change service identities, or grant broad share permissions without backup, security review and site change approval.

Engineer FAQ

Why can File Explorer write succeed while batch archiving fails? File Explorer may use the interactive user's identity, while the archive action can run through the Batch server/runtime context. Verify the effective identity and its share plus NTFS access.

Does a successful BCC test prove batch archiving works? No. It is a connection test, while archiving also depends on batch eligibility and the actual archive operation's security context and file handling.

Can an active or incomplete batch be archived? Siemens' documentation says only completed batches can be archived.

Should I grant Everyone full write permission? Do not use that as a general fix. Protect archive folders and grant only the identities and rights required by the approved configuration.

What is required to determine this report's exact cause? The error text/image, SIMATIC BATCH version, archive method, server/client layout, effective runtime identity and corresponding Windows/Batch logs are missing.

Technical References

Siemens, SIMATIC BATCH V9.0 Operating Manual, 05/2017, A5E38210537-AA, §§9.9.1 and 9.9.1.3, “Archiving method”; describes directory, SQL Server and FTP archive methods and archive configuration. Siemens-hosted PDF timed out during retrieval: https://cache.industry.siemens.com/dl/files/661/109748661/att_923993/v1/sb-onlinehelp_b_en-US.pdf
Siemens, Service Support and Diagnostics (V10.0), 07/2024, A5E52546790-AA, §4.2.5.4 “How to archive a batch”; indexed text states only completed batches can be archived and directory technology saves archives to a shared network folder using Windows access mechanisms. Siemens-hosted PDF returned HTTP 403: https://support.industry.siemens.com/cs/attachments/109973500/ps7slf_b_en-US.pdf
Siemens, Compendium Part F – Industrial Security (PCS 7 V9.0), Configuration Manual, 10/2020, A5E43228971-AB; archive-storage security and access-control context: https://cache.industry.siemens.com/dl/files/722/109782722/att_1036067/v1/pcs7_compendium_part_f_en-US_en-US.pdf

Troubleshoot SIMATIC BATCH Archive Failures to a Remote Directory