Troubleshoot PCS 7 CFC Block-Type Update Errors During V9.1 SP1 Migration

For a project moving from PCS 7 V9.0 SP3 to V9.1 SP1, do not install APL V9.1 as an isolated library change while the project is still being engineered as V9.0 SP3. Align APL and Basic Library with the active PCS 7 baseline, or follow Siemens' ordered V9.1 SP1 project-update procedure. The logged 0xEE040000 and 0xEE0503E5 statuses do not establish a specific database repair; the project-specific block failure remains unresolved.

What the Reported Errors Establish

The source records CFC/SFC update logs including 0xEE040000 with SRV_BLOCK_UPDATE = INTEGRITY_ERROR Database inconsistent, followed by propagated 0xEE0503FF system errors. A later attempt with project-specific blocks reports 0xEE0503E5 and “Programming error.” These messages identify the failing operation and reported status; they do not, by themselves, establish the underlying database defect or a repair.

The source also mixes two contexts: a migration target of PCS 7 V9.1 SP1, and an intermediate project still at PCS 7 V9.0 SP3 while APL and Basic Library V9.1 were installed. Siemens' PCS 7 V9.1 Readme lists different library baselines for PCS 7 V9.0 SP3 and PCS 7 V9.1. Do not treat a library-only replacement as equivalent to completing a PCS 7 project migration.

Align the Library with the Active PCS 7 Version

The PCS 7 V9.1 Readme software-component table lists PCS 7 V9.0 SP3 with its specified update baseline and APL/Basic Library V9.0 SP3 updates; for PCS 7 V9.1 it lists APL and Basic Library V9.1. A PCS 7 V9.1 SP1 software-update manual likewise describes updating the project to V9.1 SP1 and installing the required PCS 7 libraries as distinct steps.

Therefore, if the engineering station is still operating a PCS 7 V9.0 SP3 project, restore or install the library versions required for that actual PCS 7 baseline using the applicable Siemens setup and readme. If the actual target is PCS 7 V9.1 SP1, follow the V9.1 SP1 software-update procedure, including required libraries and project adaptations. Confirm exact update levels in the matching PCS 7 Readme and compatibility information; do not infer the exact compatible patch range from “SP3” alone.

Supported PCS 7 V9.1 SP1 Migration Framework

Siemens publishes a specific Software Update without Utilization of New Functions procedure for PCS 7 V9.1 SP1. It applies to existing projects from PCS 7 V8.2.1 or higher; PCS 7 V9.0 SP3 is above that minimum. The manual calls for its ordered update tasks and warns that the exact sequence must be followed. Its overview includes installing additional libraries, adapting the project, checking and adapting NetPro connection data, converting CFC/SFC charts, compiling, and downloading as separate tasks.

For CFC chart conversion, the V9.1 SP1 manual describes this documented sequence for all S7 programs: open a CFC chart, move a block to initiate the conversion dialog, confirm the conversion, then perform a complete S7-program compilation and download changes as required by the documented update plan. This is the chart-format conversion procedure, not a universal cure for an SRV_BLOCK_UPDATE database-integrity error.

The manual also says projects using SFCs require updating the SFC blocks. For master-library or project-specific block-type update operations beyond the documented sequence, use the matching PCS 7/APL/Basis Library Readme and exact installed component versions. Do not substitute the forum's staged APL 8.1 → 9.0 → 9.1 recipe as a generally supported procedure; the ticket provides no reproducible evidence that it fixes this specific project.

Diagnostic Sequence for the Block-Type Failure

Stop repeated block-type update attempts and preserve a verified project archive or copy before further migration work.
Record the exact PCS 7, CFC, SFC, APL, and Basic Library versions and updates on the engineering station, plus the project's current and intended PCS 7 versions. The first post's V9.1 SP1 target and later V9.0 SP3 intermediate state must not be conflated.
Check the PCS 7 Readme and compatibility information for the precise component combination. Confirm that the currently installed libraries match the active engineering baseline, or that the correct V9.1 SP1 migration is in progress.
If the project is not yet being migrated under the V9.1 SP1 procedure, restore the matching version's library baseline through the approved installation media and Siemens instructions. If migrating, execute the V9.1 SP1 update manual's ordered tasks and use the required library versions.
Reproduce the update on a separate archived project copy and capture the complete CFC/SFC log at the first failure, identifying the block type and whether it is a standard or project-specific type. Do not repeatedly retry against the only project copy.
If a correctly aligned version set still reports 0xEE040000 or 0xEE0503E5, the cause remains unresolved by the available sources. Escalate with the project copy, complete logs, library versions and exact update sequence rather than deleting or rebuilding project database objects speculatively.

How to Interpret the Two Error Entries

0xEE040000 is the source-reported SRV_BLOCK_UPDATE integrity/database-inconsistent status. 0xEE0503FF is reported by several higher-level operations as an error being passed on. The later 0xEE0503E5 is reported as a programming error during the project-specific block update. The ticket does not establish whether these codes share one root cause. Preserve the raw log and the operation context for each occurrence.

Verification

Before accepting a migration, verify that the project is being engineered with the intended PCS 7 release and matching libraries, that the documented migration sequence completes, and that CFC/SFC charts compile without the prior update failure. Review generated compile logs and project-specific block interfaces; a dismissed dialog or successful single block update is not sufficient evidence. Any AS download must remain a separate controlled operation governed by the migration plan and plant availability requirements.

Limitations and Operational Precautions

The source does not identify the project's exact PCS 7 V9.0 SP3 update, CFC/SFC versions, APL/Basis Library update numbers, affected block types, full project database state, or complete diagnostic logs. It contains a forum workaround but no sufficiently specific verification that it resolves the reported custom-block error. The official V9.1 SP1 manual supports a version-bounded project update framework, not a diagnosis of the integrity error.

Project migration, chart conversion, compilation, and AS download are distinct stages. Preserve a recoverable source project and follow the target-version manual in order. Test the migration on a copy and schedule downloads with the site's operational approval and rollback controls.

Engineer FAQ

Can APL V9.1 be used as a library-only replacement while a project remains PCS 7 V9.0 SP3? The PCS 7 compatibility baselines distinguish those combinations. Align libraries with the active PCS 7 version or follow the full documented migration to V9.1 SP1.

Does 0xEE040000 prove that the project database is corrupt? No. It is the logged status text, but the source and opened manuals do not establish the underlying cause or database-repair procedure.

Is the forum's staged 8.1, 9.0, 9.1 library procedure Siemens-approved? No such approval was established. Do not present that reported workaround as a general migration method.

Technical References

Siemens, PCS 7 Readme V9.1 (Online), section 5 “Software components in SIMATIC PCS 7 V9.1,” component version table. https://support.industry.siemens.com/cs/attachments/109780270/pcs7-readme_en-US.pdf
Siemens, Software Update without Utilization of New Functions V9.1 SP1, sections 3.3, 4.2, 6.3–6.4 and 7.3.2, document A5E50318242-AB. https://cache.industry.siemens.com/dl/files/400/109805400/att_1089650/v1/ps7swo_b_en-US.pdf
Siemens, Software Update without Utilization of New Functions for SIMATIC PCS 7 V9.1, sections 3.3 and 6.3, document A5E50318242-AA. https://cache.industry.siemens.com/dl/files/381/109794381/att_1057443/v1/ps7swo_b_en-US.pdf

Related Tags

PCS 7 V9.1 SP1, PCS 7 V9.0 SP3, CFC, SFC, APL, Basic Library, block type update, migration

Troubleshoot PCS 7 CFC Block-Type Update Errors During V9.1 SP1 Migration