Troubleshoot “Could Not Find AdvLib81” During a PCS 7 Library Migration

Troubleshoot “Could Not Find AdvLib81” During a PCS 7 Library Migration

For a PCS 7 migration, first confirm the exact project version and use the library set and update procedure documented for that stage. The Siemens PCS 7 V9.1 SP1 project-update procedure applies to projects at V8.2.1 or later; older projects should first be brought to V8.2.1 using the corresponding manuals. The reported 8.1 → 9.0 → 9.1 library sequence succeeded in one case, but Siemens documentation reviewed here does not establish it as a universal fix for “Could not find AdvLib81.”

Table of Contents

What the Error Means—and Does Not Mean

The reported CFC compilation message is “Could not find AdvLib81.” The source first identifies a PCS 7 V8.0 project using APL 7.1 and then describes installing APL 8.1 before compiling. A reply suggests installing the matching library before compiling; a later post reports a staged project conversion through APL/Basic Library 8.1, 9.0 and 9.1, ending with a successful build.

That is a source-reported result for one project, not proof that this library sequence is supported for every PCS 7 migration. The ticket does not specify the exact V8.0 service pack/update, CFC version, all library levels, or the complete error context.

Check the Supported Starting Point

The Siemens PCS 7 V9.1 SP1 software-update manual defines its procedure for projects originating in PCS 7 V8.2.1 or higher. Its general information says projects older than V8.2.1 should first be updated to PCS 7 V8.2.1 using the corresponding manuals. A project identified only as V8.0 is below that documented starting point; do not begin by applying the V9.1 SP1 project-update sequence directly.

The V9.1 Readme component table also distinguishes the APL and Basic Library versions for PCS 7 V9.0 SP3 from those for PCS 7 V9.1. An APL library version is not a substitute for the PCS 7 engineering-system version. Confirm the exact installed versions and use the libraries specified for each stage.

Version-Bounded Troubleshooting Procedure

  1. Make a recoverable archive or working copy of the project before further library or chart updates. Record the exact PCS 7, CFC, SFC, APL and Basic Library versions and updates, plus the full CFC compile log.
  2. Confirm whether the project is PCS 7 V8.0, V8.0 SP2, or another level. “V8.0” and the later reply's “8.02” are not precise enough to select the upgrade manual.
  3. If the project is older than PCS 7 V8.2.1, follow Siemens' applicable earlier-version update manuals to reach the documented V8.2.1 starting point. The V9.1 SP1 update manual states that this intermediate preparation is needed for older projects.
  4. For each stage, install the library versions required by that PCS 7 release and update the project using that stage's official software-update instructions. The V9.1 SP1 manual separates library installation, project adaptation, CFC/SFC chart conversion, compilation and downloading; do not collapse those into one library swap.
  5. If “Could not find AdvLib81” occurs during a version-appropriate compile, capture which project/library is open, the affected chart or block, exact library registration/version, and complete error log. Check the installed library and project references against the matching release documentation.
  6. If the message remains after the correct library set and documented migration stage are confirmed, stop repeating updates on the only project copy and escalate with the archived project and version inventory. The cited manufacturer manuals do not map this exact message to a definitive repair.

How to Treat the Reported Staged Workaround

The author reports success after unarchiving an 8.0 SP2 project, adding APL/Basic Library 8.1, using SIMATIC Manager > Options > Charts > Update block types, compiling with Generate Module Driver enabled, removing the 8.1 libraries, repeating at 9.0, and then updating with 9.1 libraries. This is useful as a report of what happened in that project. The available Siemens update manual does not validate this exact staged recipe for the reported starting version or block set, so it should not be copied as a general procedure.

Verification

Verify each migration stage against the exact Siemens Readme/manual and retain the project copy and logs. Confirm CFC/SFC conversion, compilation, and any required module-driver generation separately. Then check that the project's block/library versions match the intended target release. A successful CFC compile alone does not show that the full PCS 7 system migration or any later AS download is complete.

Limitations and Operational Precautions

The source's initial V8.0 description and later “8.02” resolution differ in specificity. It omits exact service packs, updates, CFC version, library update levels, block names, full compiler output, and proof that the staged recipe applies beyond that project. The exact cause of “Could not find AdvLib81” remains unverified. No database repair or universal workaround is established.

Library and project updates can alter offline engineering data. Preserve an archive and test each documented stage on a copy. Compilation, project migration, and AS download are separate operations; perform downloads only under the site's approved migration, availability, and rollback plan.

Engineer FAQ

Can PCS 7 V8.0 use the PCS 7 V9.1 SP1 update procedure directly? The V9.1 SP1 manual defines its starting projects as V8.2.1 or later and recommends older projects first be updated to V8.2.1 using the matching documentation.

Does “Could not find AdvLib81” prove APL V8.1 is missing? It is the message reported during compilation, but the source and manufacturer references do not identify its exact cause. Verify the installed library, project version, and full diagnostic context.

Is the 8.1 → 9.0 → 9.1 library sequence a universal Siemens procedure? No. It is a project-specific forum-reported resolution; the cited manual does not establish it as a universal migration path.

Technical References

  • Siemens, Software Update without Utilization of New Functions V9.1 SP1, document A5E50318242-AB, sections 3.3 and 4.2; project starting-version scope and ordered update procedure. https://cache.industry.siemens.com/dl/files/400/109805400/att_1089650/v1/ps7swo_b_en-US.pdf
  • Siemens, PCS 7 Readme V9.1 (Online), section 5, software-component version table for PCS 7 V9.0 SP3 and PCS 7 V9.1. https://support.industry.siemens.com/cs/attachments/109780270/pcs7-readme_en-US.pdf
  • Siemens, Software Update without Utilization of New Functions for SIMATIC PCS 7 V9.1, document A5E50318242-AA, sections 3.3 and 6.3–6.4 on library requirements and installation. https://cache.industry.siemens.com/dl/files/381/109794381/att_1057443/v1/ps7swo_b_en-US.pdf

Related Articles

Related Tags

PCS 7 V8.0, PCS 7 V9.1 SP1, APL, Basic Library, CFC compile, AdvLib81, project migration

20 respuestas