IMDTouchKnowledge BaseShop main store

Troubleshooting

Why a restored MER loses your PanelView Plus runtime users

HMI and touchscreens Published 7 min read

Short answer

Restoring an MER gives you back the screens but not the users: a runtime restore cannot carry the FactoryTalk Directory contents, so every stored login stops working while the panel keeps running. Recreate the missing users and groups in the restored project's runtime security, build a new MER, download it, and store the project as an APA or APB archive from then on.

On this page
  1. Why the screens run but the login is gone
  2. Why downloading the same MER again cannot bring it back
  3. Comparing the restored user list with the setup, Supervisor, Service and Operator logins
  4. Rebuilding the users and groups
  5. Read the macros as tag writes, not logins
  6. Store the next edit as an APA archive, not an MER
  7. When the accounts cannot be rebuilt
  8. Questions asked

Restoring an .mer runtime hands you back the screens, the tags and the graphics, and quietly drops every user and group the terminal used to have. A runtime restore cannot carry the FactoryTalk Directory contents that held those logins, so the panel keeps running while the operators' username stops working. The fix is to recreate the missing users and groups in the restored project's runtime security, build a new .mer from that project and download it; downloading the same .mer again never recreates a lost login. From then on, store the project as an .apa or .apb archive and treat the .mer as a deployment file only. Here is why the accounts vanish, how to count exactly which ones you lost, and the rebuild order that gets the login back without a second surprise.

Why the screens run but the login is gone #

A PanelView Plus keeps two different things in two different places. The runtime project is the file the terminal executes. The users and groups behind its runtime security live in the FactoryTalk Directory on the machine that built the project. When you upload the runtime and restore it for editing, you get an editable project, but the restore does not reproduce the directory contents the original was built against. The project you edit next is therefore created with the accounts that already exist in your development PC's directory, and the rebuilt runtime carries those instead of the panel's logins.

Two clarifications save time here. Selecting No at an upload prompt did not cause the loss, and there is no overlooked setting either: when you restore a runtime there is no option to restore the directory, because that function does not exist in the restore workflow. And a successful download proves only that the file transferred and ran, never that the security accounts match what the terminal had before. A password reset is also the wrong first move, because a reset cannot restore a user who no longer exists.

Do not clear runtime security or strip the login requirement to keep the line moving: until the rebuilt runtime is tested, the panel's current state is the only copy of its access control.

Why downloading the same MER again cannot bring it back #

Downloading the same .mer again transfers the project exactly as it is currently built. The restored project has no setup login in it, so the rebuilt runtime has none, and every further download copies that absence to the terminal. Converting the same file cannot regenerate account definitions that exist nowhere, not in the project and not in the development PC's directory. Reaching the panel with any fix still requires the normal mechanism, because an HMI edit only lands on the terminal through a new build and download, as explained in why an HMI edit needs a new runtime download. The download is the last step in that chain, and it faithfully delivers whatever the project contains.

Comparing the restored user list with the setup, Supervisor, Service and Operator logins #

Inputs, taken from the project as it came off this machine:

  • The Runtime Security tab of the restored project lists 3 entries: Default, Diesetter and Maintenance.
  • The machine needs 4 account names: setup, the operators' login, plus Supervisor, Service and Operator, the three names the project's macros write into their Account tags.

The rule: a FactoryTalk View ME login succeeds only when the typed name matches a user defined in the project's runtime security, so the number of working logins equals the number of required names present in that list.

The arithmetic:

  • Required names: setup, Supervisor, Service, Operator = 4.
  • Names present after the restore: Default, Diesetter, Maintenance = 3.
  • Names on both lists: 0, because setup is absent and Supervisor, Service and Operator are absent.
  • Working logins now: 4 required − 0 present = 0 of 4.
  • Accounts to recreate: 4 − 0 = 4.

The result: none of the four logins the machine needs exists in the rebuilt project, so every one of them fails regardless of password. The 3 entries that are present came from the development PC's directory; Default is the no-login account, and none of the three covers a required role.

The decision: recreate all 4 users in the project's runtime security with fresh passwords issued through your site's credential process, assign their security codes, build a new .mer and download it in a test window. The panel passes only at 4 of 4 logins working with the restricted displays staying closed; below that, the runtime is not finished.

Rebuilding the users and groups #

  1. Write down the intended operator, service and setup access levels from the working panel or the approved project records before you touch anything in security.
  2. Open the restored project's runtime security configuration and put its user list beside that record; compare names, not macro names.
  3. Recreate the missing users and groups and assign each its security codes. Handle credentials through the site's approved process, not by reusing old passwords as a shortcut.
  4. Check every login button and security-code assignment in the project so each one points at the account or level it is meant to; matching names are not connected automatically.
  5. Build a new .mer and download it during a test window, keeping the existing project and runtime files until the new one passes.
  6. On the terminal, test each role in turn: log in, open the displays that role needs, confirm restricted functions stay inaccessible, log out and move to the next role.
  7. After the last role passes, confirm the terminal is running the file you downloaded, using find the runtime file an HMI terminal actually loads, before you hand the panel back.

Read the macros as tag writes, not logins #

The three macros under the project's Logic and Control tab each write two tags:

Macro RemoteDisplay Account
Diesetter 100 'Supervisor'
Maintenance 200 'Service'
User 1 'Operator'

A macro writes tag values; it does not authenticate anyone and it does not create the account it names. Account = 'Supervisor' is a string written to a tag, nothing more. The same applies to RemoteDisplay: a value of 100, 200 or 1 selects a display version only where project logic actually reads the tag, so check the visibility and navigation expressions and the places the macros are invoked before deciding which number shows which version. Treat the difference between the runtime security names (Default, Diesetter, Maintenance) and the macro names (Diesetter, Maintenance, User) as an inventory mismatch to resolve, not as proof that a macro is a login or that names correspond automatically.

Store the next edit as an APA archive, not an MER #

An .mer is compiled for the terminal, portable and quick to move between machines, which is why it keeps getting treated as a backup and why this failure keeps repeating. It is not dependable project storage: restoring one can drop directory-backed data such as users and groups. The maintainable backup is the project archive, .apa, with older projects using .apb. From now on, restore to an .apa rather than a .med, edit, save the archive, then build the .mer from that archived project and send it to the panel. Before the next restore, copy the current project and runtime and restore under a new project name instead of overwriting the only working copy, and record the development software version and patch level with the archive. For any project that still has its users intact, export the user and group definitions and keep the export with the archive; it costs a moment today and saves a full rebuild after the next restore or PC migration.

When the accounts cannot be rebuilt #

If the user and group definitions cannot be reconstructed from the restored project, take them from a known-good archive or the approved security records; running the same conversion again will not regenerate them. If no archive exists at all, recovering an HMI program when the source file is lost is the next path, and the rule is the same there: recover what can be recovered, rebuild the security deliberately, and archive the result before the next edit.

Questions asked

How do I save the users and groups from a project that still has them?

In FactoryTalk View Studio, open the project Explorer, expand the project's System folder, right-click Users and Groups and choose Export. Save the exported file with the project archive. That file records the account and group definitions the project depends on, so the next restore, rebuild or move to a new development PC starts from the real list instead of a guess.

Does this also affect Windows-linked accounts?

Yes, at the directory level. If the project's accounts are Windows-linked, a restore can leave them without permissions, and vendor documentation treats missing Windows-linked account permissions after a FactoryTalk restore as its own troubleshooting case. Check that the linked accounts and the directory configuration exist on the machine you restored to before you blame the project.

What about very old PanelView Plus terminals?

Terminals from the v3 and v4 firmware era cannot restore an application from a runtime at all, so data is lost by design on upload from them and there is no rebuild path from the file itself. For those, the safe sources are the original archive or the development project. Rebuild the security in whatever editable copy you find before downloading anything to the terminal.

The restored application will not open at all, so what then?

That points at the FactoryTalk Directory, not the project. Search Windows for the FactoryTalk Directory Configuration Wizard, launch it, and enable the option to configure the FactoryTalk Local Directory, then retry the restore. A restore needs a healthy local directory on the development machine; without one it fails before your users and groups are ever involved.

Keep reading

  • How-to

    One FactoryTalk View ME Project Builds One PanelView Runtime

    One FactoryTalk View ME project creates exactly one .mer runtime, and that runtime runs on one PanelView Plus terminal. Two terminals therefore take the same .mer loaded on both, or two separate projects. For one controller and two identical 2711P terminals, build once and load twice; split into two projects only when screen size, resolution or communication targets differ.

    HMI and touchscreens

  • How-to

    Migrate a PanelView Plus 6 project from ME 5.0 to 10.00

    Yes, the application can move from FactoryTalk View ME 5.0 to 10.00, but the runtime file itself is never version-converted. Confirm the terminal is a PanelView Plus 6 700-1500 or Compact 1000, restore an editable application from the .apa archive or a restorable .mer, convert it in FactoryTalk View Studio ME 10.00, build a new .mer at the 10.00 runtime version, and download it after flashing firmware 10.00-20180411. Part 11 compliance is a separate validation job.

    HMI and touchscreens

  • How-to

    How to Recover an HMI Program When the Source File Is Lost

    If an editable backup was stored on the HMI at download time, upload it and open it as a project. If the terminal holds only the compiled runtime, no upload can recreate the source: document every screen and tag behavior from the running unit, rebuild against the controller project, and convert the runtime only where the vendor documents a path.

    HMI and touchscreens