IMDTouchKnowledge BaseShop main store

Troubleshooting

Fixing the older-format MER file conversion error

HMI and touchscreens Published 7 min read

Short answer

An older-format MER conversion error means the runtime was built before version 5.0 stored the development application inside the file, so no FactoryTalk View Studio release converts it. Restore the original APA archive if it exists; otherwise recover the graphics through the RSView Studio MED import from the ~MER temp directory and rebuild the rest.

On this page
  1. Why the conversion fails
  2. Decide the recovery path from the file you have
  3. Worked example: a version 4.00 MER with no APA on file
  4. Recover the graphics from a version 3.x or 4.0 runtime
  5. When the import reports a rename failure
  6. What the recovered project will not contain
  7. Questions asked

The older-format error does not mean your Studio installation is wrong; it means the runtime file itself is incomplete as source. A MER restored from a terminal whose project was built with FactoryTalk View version 4.0 or earlier does not carry the stored application information that Studio 5.0 introduced, so no release, including the newest one on your desk, can convert it into a development application.

Two paths exist. If the original APA archive survives anywhere, restore it through Application Manager and you have the full project back. If only the MER exists and it was built by version 3, 3.1, 3.2, or 4, recover the graphics through the RSView Studio MED import from the terminal's temporary ~MER directory on a Windows 2000 or XP development station, then rebuild parameters, alarm setup, datalog and macros by hand. The sections below give the decision, a worked example and both procedures.

Why the conversion fails #

Before version 5.0, a MER held only what the terminal needs to run: compiled graphics and runtime data, not the development source. Version 5.0 introduced storing the complete application information inside the runtime file, and at build time the developer chooses whether conversion runs always, never, or behind a password. A runtime built with version 3, 3.1, 3.2, or 4 predates that feature, so there is nothing in it for a newer Studio to convert. Installing the newest release changes nothing: software cannot add information the file never stored.

The APA archive is different, because it is written from the development application in the first place. A version 4 APA opens in version 5.0 without conversion, while a version 4 MER cannot become a complete project in any release. When Application Manager reports "This runtime application file was saved in an older format that does not support conversion to a development application.", that message identifies the file's generation: pre-5.0.

What each of the three files carries, and how a project moves between terminal and desk, is laid out in the MED, MER and APA project transfer guide.

Decide the recovery path from the file you have #

First confirm that the MER you retrieved is the one the terminal actually runs; finding the runtime file a terminal actually loads walks that check before you commit to a path. Then match the file in hand to a row:

File in hand Path Expected result
APA archive, any generation Restore it through Application Manager Complete development application; a version 4 archive opens in version 5.0
MER built by 5.0 or later Runtime-to-development conversion Complete when the build-time option allowed conversion or you hold the conversion password; refused when it was set to never
MER built by 3, 3.1, 3.2, or 4 RSView Studio 3.x MED import from the temporary ~MER directory Graphics and partial content; parameters, alarm setup, datalog and macros are lost
Generation unknown Identify it before testing The older-format error is itself evidence of a pre-5.0 file; do not assume the newest Studio converts it

The third row is the case where the machine supplier withholds source and the terminal is all you have. The worked example below runs it with numbers.

Worked example: a version 4.00 MER with no APA on file #

Inputs #

  • Runtime file: one MER retrieved from the terminal's storage and offered to Application Manager, the situation of a panel whose source the supplier withholds.
  • Build generation: version 4.00, established by the older-format error itself, which only pre-5.0 runtimes produce.
  • Desk seat: FactoryTalk View Studio Machine Edition 10.00, a documented current generation; substitute your own version, because it does not change the outcome.
  • Legacy station: one Windows XP PC with RSView Studio 3.x installed, the documented requirement for the recovery procedure.
  • APA archive: none on file.

The rule #

A MER converts to a development application only when two things are true: the build generation is 5.0 or later, and the conversion option chosen at build time permits conversion. Every other detail is secondary; the comparison that decides the case is the file's build generation against 5.0.

The comparison #

The desk seat never enters the comparison. A newer Studio can read older projects, but it cannot write stored application information into a file built before the feature existed. Compare the file alone: 4.00 < 5.0, so the runtime predates stored application data and the conversion path is closed in every release, including 10.00. The desk seat's own relation, 10.00 ≥ 5.0, only says this seat can create conversion-capable runtimes from now on.

Result and decision #

Conversion is refused for this file no matter what software touches it, so the Application Manager route ends here. The remaining extraction is the RSView Studio 3.x MED import, with an expected yield of the displays and whatever tag data survived, nothing else. The threshold to apply to any file you meet: below 5.0, go straight to the legacy import; 5.0 or later, return to Application Manager and let the build-time conversion option decide. Either way, keep pressing the supplier for the APA, because a partial extraction cannot reproduce what the runtime never stored.

Recover the graphics from a version 3.x or 4.0 runtime #

This procedure needs a Windows 2000 or Windows XP development station with RSView Studio 3.x installed, not your current desk. Copy the retrieved MER somewhere safe first and treat that copy as untouched; work on a duplicate.

  1. Run RSView ME Station from Start Menu > Programs > Rockwell Software > RSView Enterprise.
  2. Open the MER file you are recovering, but do not run the application. If an error appears while opening it, continue with the recovery attempt.
  3. Start RSView Studio and create a new application.
  4. Choose Import and select the MED file type.
  5. Locate the temporary runtime directory: ~MER.00 under C:\Documents and Settings, then your Windows user name, then Local Settings\Temp. The suffix may read ~MER.01 or higher if other runtimes were opened on that station before.
  6. Select the MED file inside that directory and complete the import prompts.
  7. When the application loads, close both RSView Studio and RSView ME Station.

This is a partial reconstruction, not a reverse conversion of the original development application. What it still owes you is the next section's list.

When the import reports a rename failure #

Some imports stop at "Failed to import project, unable to rename file". The extracted components on disk are still usable:

  1. Create a new project whose name matches the .med file in the ~MER.00 directory.
  2. In Application Explorer, right-click Displays and choose Add component into application..., then add every .gfx file from the temporary directory's Gfx folder.
  3. Copy the remaining recovered folders into C:\Documents and Settings\All Users\Documents\RSView Enterprise\ME\HMI projects, inside the new project's own folder.

What the recovered project will not contain #

Parameter files, Alarm Setup, Datalog files and Macro files cannot be recovered from these older runtimes, and under some circumstances the Tag Database does not survive either. They may appear in the reconstructed application, but they are not usable. Clean it so nothing misleading remains:

  • In the recovered project's M_Alarms folder, delete MachineAlarms.mal.
  • Open the application in RSView Studio and remove every listed Parameter, Datalog and Macro file from Application Explorer.
  • Open each recovered display and check its tag references, because the tag database may be incomplete.

Then inventory every missing parameter, alarm, datalog, macro and tag dependency before you treat this as maintainable source, and keep requesting the original APA from the machine supplier; partial extraction cannot reproduce the omitted content. If the supplier never releases anything, recovering an HMI program when the source file is lost lays out the wider rebuild options.

Once a development application exists again, protect it: creating an APA backup from a MED file gets the archive made while the recovered work is fresh. One safety rule before any of it reaches the machine: do not download a partially recovered project to the running terminal until every rebuilt alarm, parameter and datalog dependency has been proven on the bench, because a machine that runs with missing alarm setup is unprotected.

Questions asked

Application Manager asks for a conversion password on a MER restore. What do I enter?

The behaviour was chosen when the runtime was built. If the developer allowed conversion, the restore completes without any password. If conversion was prohibited, no entry works and the restore fails. If it was password-protected, the prompt appears, and without the password recorded by whoever built the project there is no recovery path; the APA archive is the only source.

Can I run the version 3.x recovery on my current PC?

No. The documented procedure needs a Windows 2000 or Windows XP development station with RSView Studio 3.x installed, and that release was built for those systems and will not install on a current 64-bit Windows desktop. Use a surviving legacy machine or a virtual machine that meets the requirement, and keep a copy of the retrieved MER off the recovery station in case the attempt damages it.

How do I avoid this dead end on the next panel?

Keep the APA archive with the machine documentation instead of relying on the terminal's MER, and record whether runtime conversion was left allowed. When building runtimes, note that FactoryTalk View Studio ME 10.00 and higher shows a popup warning whenever the target runtime is version 9.00 or earlier, so confirm the target version before saving.

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

  • Troubleshooting

    E200 HMI recovery when the supplied file is a GOT project

    The E200 is an E-series terminal programmed with E-Designer, and it accepts only a native E-Designer project file with the .MPA extension. GT Designer3 opens GOT projects and can convert E-Designer projects toward the GOT, never the reverse, so recovery means obtaining the original .MPA from the machine builder or a backup, then downloading it over the documented serial cable.

    HMI and touchscreens

  • Troubleshooting

    Fixing a PCS 7 OS download that fails with SQL errors

    The transfer fails because the target-side WinCC SQL databases, the CC_* copies, stay attached to SQL Server or sit in RECOVERY_PENDING, so WinCCOM cannot replace them. Close Runtime and all editors, reboot the target, remove the obsolete CC_* databases through the SQL administration layer rather than by deleting .mdf files, delete the stale CC_OM DSN, then run one clean download.

    HMI and touchscreens