Resolving Multiproject Archiving Failures Involving 'Removed for Editing' Projects in PCS 7

In SIMATIC PCS 7, attempting to archive a multiproject (File > Archive) after a constituent project has been detached using 'Multiproject > Remove for editing' fails with a fatal access error stating that the directory of the removed project cannot be accessed. This occurs because the multiproject structure maintains an internal registered reference (stub pointer) to the detached project, but the physical file directory has been moved to an external location. The STEP 7 internal archiving engine (PKZip wrapper) requires all registered project paths to be locally accessible. To resolve this error, either re-insert the project into the multiproject ('Multiproject > Insert project...'), permanently remove the project reference from the multiproject if it is no longer required, or archive the constituent projects individually using Component View.

Executive Summary

Distributed multi-user engineering in SIMATIC PCS 7 allows large engineering teams to work concurrently on different plant areas. A common workflow involves an engineer detaching an S7 project or Operator Station from the centralized multiproject using the 'Remove for editing' command to work offline on a portable laptop. However, when the lead engineer subsequently attempts to create a routine baseline backup via File > Archive, SIMATIC Manager throws an error indicating that the detached project path cannot be found, aborting the archiving process. Understanding how the multiproject container manages cross-project links and adopting correct multi-user archiving protocols restores reliable backup workflows.

Architecture and Fundamental Mechanics

The multiproject architecture in SIMATIC PCS 7 coordinates separate project databases under a single logical umbrella:

The Multiproject Container Structure:
* A multiproject consists of a root descriptor file (*.s7p / *.mpr) and references to individual project folders (e.g., AS1_Proj, AS2_Proj, OS_Proj, and Master_Data_Library).
* Each project maintains its own independent relational database, while cross-project data (cross-rack S7 connections, inter-project plant hierarchy folders, global libraries) are reconciled by the multiproject manager.
The 'Remove for Editing' Mechanism:
* When an engineer executes Multiproject > Remove for editing, STEP 7 does not delete the project from the multiproject schema.
* Instead, it flags the project as 'checked out' (detached) and moves or decouples the project folder so that it can be transferred across the network to a standalone workstation.
* The multiproject descriptor retains an active pointer entry with status 'Removed for editing'.
Why Archiving Fails:
* The File > Archive command in SIMATIC Manager invokes an automated batch packaging utility.
* The archiver queries the multiproject descriptor to identify all constituent directories.
* It sequentially attempts to open every registered project folder to compress its database files, SDBs, and graphics.
* When it reaches the detached project, Windows returns error code 2 / path not found (The system cannot find the path specified).
* Because STEP 7 requires complete database integrity to guarantee that an archive can be restored without missing cross-references, the archiver immediately terminates with a fatal access violation.

Step-by-Step Implementation Procedure

Follow these procedures to resolve archiving failures and safely back up multiprojects with detached components:

Verify the Multiproject Status:
* In SIMATIC Manager, expand the top-level Multiproject icon.
* Inspect the project tree. Look for any project icon that appears with an overlay icon or is grayed out/labeled '(removed for editing)'.
* Attempting to expand this node will confirm that its physical directory is inaccessible.
Solution A: Re-insert the Project (Standard Workflow):
* If the external engineering work is complete, bring the project folder back to the engineering server (via network share or USB).
* In SIMATIC Manager, select the Multiproject folder.
* Select File > Multiproject > Insert project....
* Browse to the returned project directory, select the *.s7p file, and confirm.
* STEP 7 re-integrates the project, synchronizes cross-project connections, and clears the 'removed for editing' flag.
* Execute File > Archive; archiving completes without errors.
Solution B: Permanently Remove the Reference (If Project Abandoned or Moved Permanently):
* If the detached project was permanently migrated elsewhere or is no longer part of the multiproject:
* Right-click the missing project stub in SIMATIC Manager and select Remove from Multiproject.
* Confirm the warning dialog regarding cross-project connections.
* Once the stub reference is deleted from the multiproject descriptor, execute File > Archive.
Solution C: Temporary Workaround - Archive Projects Individually:
* If the detached project cannot be returned immediately (e.g., the remote commissioning engineer is offsite for weeks), but an immediate backup of the remaining stations is mandatory:
* Do NOT select the top-level Multiproject for archiving.
* In SIMATIC Manager, open File > Archive....
* In the Archive dialog, select the User projects radio button instead of 'Multiprojects'.
* Select the active projects individually (e.g., AS1_Proj, OS_Server_Proj, and Master_Data_Library).
* Archive each project into a separate timestamped ZIP file.
* Store the individual ZIP archives in a consolidated backup folder.

Verification

After re-inserting the project or archiving individually, verify the archive file integrity. In SIMATIC Manager, select File > Retrieve... and extract the newly created archive into a temporary test directory. Confirm that SIMATIC Manager unpacks all stations, the multiproject opens cleanly, and all plant hierarchy and CFC charts load without path errors.

Limitations and Operational Precautions

Never use third-party compression utilities (such as 7-Zip or WinRAR) to manually zip open project directories while SIMATIC Manager is running. Third-party archivers will copy locked temporary database files (*.ldf, *.log), resulting in a corrupt archive that fails during retrieval. Always use File > Archive inside SIMATIC Manager.

Engineer FAQ

What does 'Remove for editing' actually do?

'Remove for editing' decouples an individual S7 project from the multiproject and allows it to be edited independently on another machine without locking the entire multiproject.

Can I re-insert a project if the multiproject was modified while it was away?

Yes, but cross-project connections (NetPro) and Master Data Library block types must be reconciled via 'Update Block Types' and NetPro compilation upon re-insertion.

Why does SIMATIC Manager refuse to archive partial multiprojects?

A multiproject contains shared cross-references (such as S7 connections and plant hierarchy levels). Archiving a partial multiproject would create an invalid backup that cannot be safely restored.

Is there an automated backup tool for PCS 7 multiprojects?

Yes. The SIMATIC Version Trail and SIMATIC Management Console (SMMC) provide automated, centralized archiving and version tracking for complete multiprojects.