How can I tell what versions of Calypso a Measurement Plan is compatible with?

[[Aa...]]

I have a measurement plan created on our programming machine, running Calypso 6.0.12 with Planner.  The plan opens fine on two operating machines without Planner, one running 6.0.08 and the other running 5.8.28, but another operating machine running 6.2.12 without Planner refuses to open it.  How does one troubleshoot a situation like this?  What's most baffling is that the one where the plan won't open has a newer version of Calypso than any of our other machines.

Edited April 28
Clarification

[[Ch...]]

Actually, the plan shouldn't open with 5.8!?
Can you try saving the plan under a new name on 5.8?

[[No...]]

Within the same main revision plans should always open. There wer a few cases where the next lower main revsion was also still able to open a plan saved in a newer one.

But that the higher revision won't open it is indeed strange. Can you rule out any shady activities (like meddling with version strings as is sometimes suggested) or a damaged file? What is the exact error message?

[[Aa...]]

Please sign in to view this quote.

I wasn't at the machine when attempts were made to open it, so I wouldn't have personally seen the error messages, but I was told that it just sat there like it was trying to load, but would never actually finish loading.

We've been running with our current versions for years (ever since we bought the third CMM) with no issues, so I suspect you're on the right track.  I want to investigate further, though I will likely have too much on my plate over the course of the next month.  Norbert, could you please provide me with whatever information you think I need to know how to check whether something has happened to alter the version string(s) or the file has been damaged?
 

Edited April 30
Answered Norbert's question.

[[Ro...]]

A workaround i was told about but haven't personally tested for sending programs to older rev machines, is to copy the program and delete the file called "revision". 

Its a text file and only consists of a single line of text, 6.8.08 or something like that.

The thought is that if calypso senses that it is missing it will create a new replacement file.

 

[[na...]]

Please sign in to view this quote.

A small correction

Please sign in to view this username.

-it's called version

[[Ro...]]

Please sign in to view this quote.

Did it work for you?

Im about to send a programs off to our sister plant, if it works then we will send a whole bunch more. 

[[na...]]

Please sign in to view this quote.

It's been a while, but I remember doing it this way and it worked.

I hope

Please sign in to view this username.

and others can confirm.

[[Aa...]]

Arg! It seems the problem on my end was not related to the version.  I just went in and got the error stack from the error reporting tool.

```
METHODSTACK
Unhandled exception: ERROR_ACCESS_DENIED
optimized [] in OSErrorHolder class>>initializeErrorActions
SystemError>>handleErrorFor:
NTFSFilename(Filename)>>makeDirectory
NTFSFilename(Filename)>>makePath
Zeiss.Calypso.OMInspectionManager class>>loadActualPartNamed:
Zeiss.Calypso.OMInspectionManager class>>loadObjectNamed:
Zeiss.Calypso.OMWorkshop>>addAnInspectionNamed:
Zeiss.Calypso.OMWorkshop>>addAnInspection
[] in [] in Zeiss.Calypso.OMWorkshop>>performMenuSelection:
ByteSymbol(Object)>>case:do:
[] in Zeiss.Calypso.OMWorkshop>>performMenuSelection:
BlockClosure>>ensure:
Cursor>>showWhile:
Zeiss.Calypso.OMWorkshop>>performMenuSelection:
optimized [] in Zeiss.Calypso.OMUIInterface>>menuSelectionBlock:icon:
optimized [] in ActionButtonSpec>>typeConvert:
PluggableAdaptor>>setValue:
PluggableAdaptor(ValueModel)>>value:
WinXPTriggerButtonController(TriggerButtonController)>>pressAction
TriggerButtonTracker(BasicButtonTracker)>>finishSelectionFor:
TriggerButtonTracker>>finishSelectionFor:
TriggerButtonTracker(SelectionTracker)>>redButtonReleasedEvent:
RedButtonReleasedEvent>>dispatchTo:
TriggerButtonTracker(SelectionTracker)>>handleEvent:
EventDispatcher>>dispatch:to:
EventDispatcher>>dispatchEvent:
RedButtonReleasedEvent(Event)>>dispatch
RedButtonReleasedEvent(Event)>>dispatchForWindowManager:
optimized [] in WindowManager>>safelyDispatchForWindowManager:
BlockClosure>>on:do:
WindowManager>>safelyDispatchForWindowManager:
WindowManager>>processNextEvent
optimized [] in [] in WindowManager>>newProcess
BlockClosure>>on:do:
optimized [] in WindowManager>>newProcess
BlockClosure>>on:do:
optimized [] in Process class>>forBlock:priority:
```
Does anyone know what that means?  It's all Greek to me.  Sorry, I can't give any confirmation of whether removing the file "version" works.

Edited May 21

[[Aa...]]

Drat!  The problem was file permissions.  Apparently, Calypso needs the current Windows user to have full permissions of the measurment plan directory in order to open the measurement plan, probably to create temporary files within the directory.

Edited May 21

[[Ma...]]

Please sign in to view this username.

 If you want to understand those logs, then just read a few lines from start, until you find some sort of hint.

Other lines are just stack what happened before. Here is first message "ACCESS DENIED" next few lines mention NTFS - which is filesystem used on drive ( older one is FAT32 and others ).

IT should know how to solve once they see this or their logs.

Happy day :-)