Troubleshoot “Cannot Read Hierarchy Folder” During PCS 7 CFC Compilation

For the reported PCS 7 V5.6 SP2 HF8 system (CFC revision K5.6.2.83), the error occurred during module-driver generation and the affected project contained CFC charts whose PH Assignment displayed --- after their plant area had been deleted. That observation narrowed the investigation but did not establish a confirmed repair. Preserve a project archive, identify the affected charts and avoid deleting orphaned charts or @-prefixed charts based only on unverified forum suggestions.

Symptoms and Applicability

The reported dialog displayed Generate module drivers (1739:260) Cannot read hierarchy folder. The Module driver log also showed: E: Could not determine insert points of block FB_In. The insert positions were not modified. Selecting Go To opened the CFC: Interconnect Blocks window but did not open a chart. The reported software was PCS 7 V5.6 + SP2 + HF8, revision K5.6.2.83, on Windows 10 Pro 21H2 in VMware Workstation 16 Pro. The project was described as not migrated.

What the Investigation Established

The project owner later narrowed the affected objects to several charts left behind after deleting the plant area to which they had belonged. In SIMATIC Manager Component View, under Charts, those objects showed --- under PH Assignment. Attempts to delete them from Component View produced Delete (1739:10) Programming error; a subsequent Save As with Reorganization (slow) attempt failed with Project <Project Name> Save As (256:159) A fatal error occurred during Save As with Reorganization (slow). The owner suspected the unassigned charts were related to the hierarchy-folder error, but the thread did not confirm that relationship or a fix.

Safe Diagnostic Checks

Make an archive or verified project backup before attempting project-structure changes; the original thread also warns to archive before experimenting.
In SIMATIC Manager Component View, inspect the affected AS chart folder and note each chart whose PH Assignment is ---.
Compare those chart names with the recently deleted plant area and with project backups or change records. Record the chart names and the exact compile log messages without deleting or moving the objects.
If a known-good archive exists, use a controlled copy or restore path approved for the project to compare the plant hierarchy and chart assignments. Do not overwrite the working project as a diagnostic shortcut.
Escalate with the project archive, PCS 7/CFC revisions, compile log and affected chart names to Siemens support or the project maintainer for a version-specific repair procedure.

Why Broad Cleanup Suggestions Are Not Established Fixes

Replies suggested deleting all charts beginning with @, running Options > Block types > Clean up, deleting empty runtime groups, compiling with Generate module drivers enabled, reorganizing the project, and updating block types from PCS 7 Basis Library or APL. These were suggestions, not a verified resolution. The original poster later said deleting the @ charts was probably not the issue and identified unassigned charts as the suspected cause. The project owner reported that reorganization failed. Do not repeat these operations on the production project without a verified, release-applicable procedure and recoverable backup.

Plant-Hierarchy Context

PCS 7 uses plant-hierarchy assignments to associate technological objects with AS chart folders and OS projects. Siemens' older Engineering Manual V6 explains that CFC/SFC objects created in Component View can lack plant assignment, while assignment changes in the hierarchy can move charts between S7 programs and may break cross-chart connections in some older versions. This documentation provides relevant context, but does not document the exact V5.6 SP2 HF8 error or an orphan-chart recovery method. Do not infer that recreating a hierarchy folder or assigning charts manually is a safe repair.

Verification

After any Siemens- or project-maintainer-approved repair, compile the same intended CFC scope with the original module-driver setting and review the Module driver log. Confirm that the hierarchy-folder message no longer appears and that the intended charts retain the expected plant-hierarchy and AS assignments. The original report contains no verified post-repair result, so it cannot establish an expected successful compile outcome.

Limitations and Operational Precautions

The exact error mapping and repair remain unresolved in the available evidence. The ticket's author suspected charts with no plant-hierarchy assignment; this is a source-reported correlation, not a proven root cause. The official hierarchy references consulted are older PCS 7 manuals and do not establish recovery steps for PCS 7 V5.6 SP2 HF8. Project reorganization, chart deletion, library-wide block-type updates and changes to hierarchy assignments can affect engineering data and must not be treated as harmless cleanup.

Engineer FAQ

What exact PCS 7 release was reported? PCS 7 V5.6 + SP2 + HF8, revision K5.6.2.83; the reported operating system was Windows 10 Pro 21H2 in VMware Workstation 16 Pro.

What did PH Assignment --- indicate in this case? The affected charts were reported as remaining in Component View after deletion of their former plant area, with no visible PH assignment.

Was this proven to cause error 1739:260? No. The author suspected a connection, but the discussion did not verify the root cause.

Did reorganization fix the project? No. The reported Save As with Reorganization (slow) attempt ended with error 256:159.

Is deleting every @-prefixed chart a supported fix here? No. That was an unverified reply suggestion, and the original poster later said those charts were probably not the issue.

Technical References

Siemens, Engineering Manual V6 – Installation of a PCS7 Project, discussion of hierarchy-folder AS/OS assignments and Component View object creation, pp. 3-35 onward: https://cache.industry.siemens.com/dl/files/317/17907317/att_108285/v1/Engineering.pdf
Siemens, Process Control System PCS 7, Tips and Tricks, A5E00080064-01, section 6.2.1 “Modifying a project in the Technological Hierarchy,” including the effects of hierarchy operations on engineering relationships: https://cache.industry.siemens.com/dl/files/410/7214410/att_50302/v1/S7Prax_e.pdf

Troubleshoot “Cannot Read Hierarchy Folder” During PCS 7 CFC Compilation