Just buy a LifeTime license and be done with the backdating aggravation.
License is identical to Xerox,, just never expires. 24 hour turn.
Nuvera, DocuTech (the few that are left), and any DocuColor
JorgeXcalak@live.com or PM
I know its an old discussion, I found this great topic, since i am trying to figure out my own freeflow problem (Freeflow server problem).
FF License is great things to think and learn how it works.
it can not to be done with change the date on the system, since FF server has a private key to initial each fetures. The license it self has a structure to be read by license manager (vendor - Feature name - software version - license - mmddyy - Hostid). since FF runs on Unix OS, so you can access license file into /opt/XRXnps/etc/license.dat
back to the topic,"How to make it read the new date" ???,
use FLEXlm by macrovision. but i have no found yet the exactly suitable for FF License. but from learning FLEXlm it self, there is BORROW menu in it. so it means we can use other license to be installed into other machine. and i have done with this........its works 100%.
Regards
Reversing Goal 1.jpg
The C16-352 code is a simple server - IOT failure to communicate. Normally resolved with the actions you have already taken (a connectivity issue), it can also be a low voltage failure in the machine , or some slot issue in the server itself.
If the interface card in the machine doesn't have power, it cannot talk to the card in the server. We used to see this in the old DocuTech 61XX
So, open the server, clean it out good with compressed air, paying particular attention to the heat sink and fan. Reseat memory and the interface card cabled to the 700.
Do the same thing on the 700, and verify that power is available to the interface card.
Cables DO fail,, wires pull out of pins, machines are moved with the servers attached.
I'm not aware that there is a license problem associated with a C16-352. I did this for a long time,, saw a lot of frustrating C15-352's I had a 252 in Boise , Idaho that would do it intermittently, lose the job. When it was rebooted it would continue to work for some indeterminate period of time. We've all had one or more of these
It turned out to be a defective cable.
Bookmarks