Troubleshoot SIMATIC BATCH Directory Archiving When the Connection Test Passes
A passing Directory connection test in SIMATIC BATCH establishes destination checks, not successful batch archiving. Capture the actual archive error and check the selected method's authentication context before changing accounts or permissions. In the documented V9.0 SP1 workflow, Directory access uses the logged-on user's data; separate archive credentials apply to other identified methods. The reported failure needs further evidence because changing localhost to the computer name already failed.
Table of Contents
- What the Successful Test Establishes
- Documented Directory Configuration
- Check the Identity for the Selected Method
- Collect Evidence from the Actual Archive Attempt
- Verification
- Limitations and Operational Precautions
- Engineer FAQ
- Technical References
- Related Articles
- Related Tags
What the Successful Test Establishes
A completed batch begins archiving but then reports an error. The directory share is writable in the configuration test, has reported free space and already has permissions assigned. Replacing localhost with the full computer name did not resolve the problem.
The exact error image and installed BATCH version are unavailable. Record the complete error text before changing configuration; it is needed to distinguish archive creation from a destination-access failure.
Documented Directory Configuration
For SIMATIC BATCH V9.0 SP1, the operating manual's Batches > Archiving > Archiving method dialog documents this procedure:
- Select Directory.
- Enter the destination in UNC form, such as
\\ArchiveHost\BatchArchive, or browse to an existing share. - Click Test and resolve any reported connection problem.
- Close the dialog after reviewing the intended destination.
The documented test checks an entered directory, UNC form, PC accessibility and write access. It does not demonstrate successful creation of a complete batch archive. The example names above are illustrative, not actual plant addresses.
Check the Identity for the Selected Method
The V9.0 SP1 manual says Directory access uses the logged-on user's data. Its separate User credentials dialog is documented for SQL server, FTP server, PH, automatic PDF saving and automatic backup.
Consequently, entering credentials for another method is not established as the cure for a Directory failure. Confirm the actual method and installed-version authentication behavior before changing accounts. Use the required account's access and retain suitable archive protection rather than expanding permissions indiscriminately.
Collect Evidence from the Actual Archive Attempt
Use this engineering investigation after preserving the current configuration:
- Record the batch identity internally, its completed state, archive method, selected format and destination.
- Under the intended operating context, reproduce one approved archive attempt and retain the full error text.
- Record whether any new archive output is created, including whether it is complete or partial.
- Compare the failure with the successful connection-test context and timing.
- Check whether the error concerns archive data, report generation or destination access before choosing the next corrective action.
Do not delete batch records or partial evidence merely because the connection test passed.
Verification
After a demonstrated cause is corrected, archive an approved completed batch and confirm that the expected archive is available for its intended readback or reporting use. Check the configured archive format and the compatible reader separately.
Preserve the original batch data until archive acceptance is complete. A new filename or successful Test button result alone is insufficient. No successful recovery or lab test is claimed here.
Limitations and Operational Precautions
The main failure remains unresolved because the error text, exact version and archive-generation result are missing. The V9.0 SP1 workflow is a documented baseline and must be checked against the installed release.
Changing localhost to a computer name already failed in this configuration and is not a universal remedy. Protect archive confidentiality and integrity; the manufacturer explicitly discourages unrestricted Everyone access. Account or share changes need a review of both operational access and archive protection.
Engineer FAQ
Does Test prove that a completed batch can be archived?
It checks the documented destination conditions, not the entire archive operation.
Should separate SQL or FTP credentials be entered for Directory mode?
The opened V9.0 SP1 documentation identifies different authentication contexts; that remedy is not established.
Is renaming localhost a confirmed fix?
No. It was attempted without success in this configuration.
Technical References
- Siemens: SIMATIC BATCH V9.0 SP1 Operating Manual, November 2017, A5E38210537-AB — section 15.1.2.11, pages 805–809; section 15.1.11.34, page 918; security guidance on page 82. The manufacturer PDF was downloaded and read directly.