Troubleshoot PCS 7 DriverUpdate.cpp 3 After Opening a V8.2 Project in V9.0 SP1

The message Internal error! DriverUpdate.cpp 3 does not, by itself, establish a root cause. For a project last compiled in PCS 7 V8.2 and opened in V9.0 SP1, preserve the source project, verify that the documented PCS 7 software-update procedure was completed, and check that required Basis/APL and other project libraries are installed at compatible versions before recompiling. The available evidence does not support a specific one-step fix.

What is known

The project was last compiled in PCS 7 V8.2 and opened in PCS 7 V9.0 SP1, where compilation reportedly returned Internal error! DriverUpdate.cpp 3. Replies suggested checking library blocks and installed add-ons, then using the PCS 7 software-update method. The source's screenshot is unavailable; the exact error cause cannot be identified.

Use the documented software-update path

Siemens provides separate PCS 7 V9.0 SP1 procedures for updates with and without utilization of new functions. Select the path according to project goals and source prerequisites. The official update manual says compatible library blocks must be used and recommends checking library compatibility; it also requires the software update to be completed before additional configuration changes.

Check libraries and engineering dependencies

Inventory the PCS 7 Basis Library, APL and any other vendor or project libraries installed on the old Engineering Station. Compare each block version/author against the target software and the migration manual. An older project may depend on blocks or libraries that are absent on the new station; a generic “update all blocks” action is not supported by the evidence.

Troubleshooting sequence

Preserve and verify an archive of the original V8.2 project; work on a copy.
Record exact V8.2/V9.0 SP1 update levels, CFC version and installed libraries/add-ons.
Capture the complete compile log and exact error context.
Apply the PCS 7 V9.0 SP1 software-update procedure appropriate to the project, including required library checks/updates.
Recompile and investigate any remaining errors using the full log and version-specific Siemens support information.

Verification

Confirm that the documented project update completes, relevant AS/OS objects compile without unresolved differences, and the resulting project passes project-specific runtime tests in a suitable environment. A compile success is not proof of correct operation.

Limitations and Operational Precautions

No Siemens reference found during this review mapped DriverUpdate.cpp 3 to a specific root cause or repair. The source omits the error screenshot, block list, add-ons and V8.2 update level. Do not delete blocks, replace libraries or download to a production AS based only on the abbreviated error string.

Engineer FAQ

Does DriverUpdate.cpp 3 prove the Basis Library is missing? No. That was a diagnostic suggestion in the replies, not a confirmed cause.

Can the old project simply be compiled in the newer version? Siemens documents a software-update process, including library checks; merely opening and compiling is not shown as an adequate migration.

Technical References

Software Update with Utilization of New Functions, PCS 7 V9.0 SP1, official service manual, 10/2017, A5E40924473-AB; sections 3.2–3.3 and 8.5 “Updating the blocks.” Opened and read.
Siemens PCS 7 documentation — find the corresponding “Software Update Without Utilization of New Functions” manual and any component readmes for the actual project.