FActory talk view, not valid archive

controlled

Lifetime Supporting Member
C
Join Date
Nov 2005
Location
bowmanville
Posts
419
My customer just purchased a machine with an allen Bradley pv+1000 screen. They wanted me to keep a copy of the files. I was emailed a copy of the apa file from the manufacturer. When I try to open it, I get an error stating it is not a valid archive file. I am using ver 6.00. Im not sure what version it was written in.

Does anyone know what this error means?

Ive attached a screen shot of the error
 
My best guess is that the *.APA was created in version 6.10 or version 7.0, since it contains a version code that is unknown to version 6.00.
 
If it's not protected, you could get them to send you the .mer runtime file and try that. They may have to save as a version 6.0 for you before they send it though (depends what revision the terminal firmware is at).

At least you can then 'Restore' the runtime within FactoryTalk to see what's going on...

Regards,

Rob
 
I had a same issue with apa file. I asked and they said v7. And I had v6.1.
Is it possible to save *.mer file from 7 to 6? *.mer is just for runtime and cannot be edited.
 
*.mer is just for runtime and cannot be edited
Click to expand...

As long as the option was ticked to allow edits and you are using version 5.0 or higher, then you should be able to restore the runtime file to allow full editing.

Regards,

Rob
 
Kidblue said:
As long as the option was ticked to allow edits and you are using version 5.0 or higher, then you should be able to restore the runtime file to allow full editing.

Regards,

Rob
Click to expand...

Rob,

Where is that option? And how to check if *.mer is not locked for editing. Thanks
 
As long as the option to 'Allow conversion' is selected when the runtime is created, you should be ok (see attached image).

Regards,

Rob

2013-08-23_191648.png
 
controlled said:
Thanks Ken, that's what I was thinking. I have a call into the manufacturer asking what version they used.
Click to expand...

Ken Roach said:
My best guess is that the *.APA was created in version 6.10 or version 7.0, since it contains a version code that is unknown to version 6.00.
Click to expand...

I phoned the manufacturer, and confirmed it was written with 6.10. I opened the file on another laptop that had version 6.1 and it worked perfectly.

Thanks everyone
 

Similar Topics

L
Factory Talk View SE Red Cross Error on Global Objects
Hi all, Attached below is an example of what is happening to our existing SCADA. It seems after patching some Rockwell Software that I thought...
Replies
9
Views
319
Lodd_
L
F
Is there any internal tag in the supervisory system that returns loss of Factory Talk VIEW communication?
The client has an application that when communication between the PLC and the Factory Talk VIEW supervisory fails, the object in the supervisory...
Replies
5
Views
283
Felp182
F
C
Factory Talk View SE Auto logout of User to Default
Hello all, I am looking for a way to have a user get logged out after an X amount of time because to default so that user privilages are no...
Replies
4
Views
585
Operaghost
Operaghost
E
Factory talk view studio close a view after 10min idle
Hello everybody. I was wondering if there is a way in FTVIEW Studio to close ) view after x min without interaction . My issue is the following...
Replies
2
Views
363
Cheeseface
C
D
Factory Talk View Studio Font.
Is there a way to choose the base font in ME. Text in the Arial Unicode MS which is the default font on my FTVS doesnt show up properly on a...
Replies
1
Views
673
KuulKuum
KuulKuum
Back
Top Bottom