Back

Topic

[KB1273]Startup and connectivity failures after migrating a project to 17.0.0

Tags: Migration

Known issues
2 months ago
By NATA
Options
Print
Applies to:
PcVue 17.0.0
Summary:
When a project created with 15.2 or 16.3 is migrated to 17.0.0, the security configuration of the source project is not preserved: the stricter 17.0.0 defaults are applied instead. As a result, the migrated project may fail to start, lose connectivity between stations, or have protocols and security options blocked although they were operational before the upgrade. This behavior is reported as a Software Problem Report PCV-2972 and is corrected since 17.0.1. Use the latest version or apply the workaround that is described below.
Details :

On a project migrated from 15.2 or 16.3 to 17.0.0, one or more of the following are observed:

–  The project does not start, or starts with part of its services unavailable.
–  Stations no longer connect to each other (client/server, redundancy).
–  Communication protocols that were operational before the migration are blocked.
–  Security options that were enabled in the source project are refused or reset to their default value.

A project created natively in 17.0.0 is not affected.

Workaround

Apply this procedure to any project migrated from 15.2 or 16.3 to 17.0.0 that shows one of the symptoms listed above.

  1. Open the migrated project Application Explorer.
  2. Connect to a user with administration rights.
  3. Add to the current user profile the “Security Administration” right.
    1273 1
  4. Select the Security node.
  5. Run the Settings action.
  6. Allow security alterations for the areas concerned by the observed symptom.
    1373 2
  7. Save the project, then close it.
  8. Reopen the project and test the behavior again.

The procedure applies to migrated projects only. On a project created natively in 17.0.0, strict defaults are normal and must not be relaxed for this reason. This procedure restores the behavior expected after a migration; it does not apply any hardening beyond what the source project was already running with, and the alterations can be locked again at any time.

Resolution

The behavior is corrected in 17.0.1. Once that version is installed, a project migrated from 15.2 or 16.3 keeps the security configuration of its source project and the workaround is no longer required.

Related articles

Created on: 20 Jul 2026 Last update: 09 Sep 2026