Starting Ilink returns with note "Failed to take or refresh license".
Pro/Ework and can open models from workspace.
What's the problem, anybody know the solution?
In Reply to Ian Cure:
We've just had the same problem.
Last occurred March 22, 2005 10:50pm. Would seem that patched
proilbase.dll that was supplied to resolve the problem has reached a
time limit.. by my calcs its 2000 days ago...
Sorry guys, forgot to post a reminder ...
If you compare a text dump of the old affected library, you will
find embedded time stamps, which correspond to these dates:
Windows: Tue Mar 22 17:59:00 2005
Unix: Wed Mar 23 12:05:31 2005
The patch replaces these dates with new dates farther into the
future, but does not remove the expiration date:
Windows: Tue May 3 03:28:41 2011
Unix: Tue May 3 04:02:16 2011
If you set your clock past May 3rd, 2011, you'll see the same
problem again. I guess the license is perpetual, but not the
Granted it is unlikely that someone will be using Intralink 3.X
in 2011. But, if you are transitioning away from Intralink 3.3
and will need to maintain it for historical purposes, you better
upgrade to an unaffacted build code. You've got six years to
get it done.
You only need to ensure that it works until 2027, that's the last
year the FlexLM is capable of supporting, since it uses 7 bit
year values which start from 1900.
Its happened again. On Monday the 12 June 2017 it reached the 2233 day limitation.
Any Chance PTC will create a new patch?
I just saw an alert on the ptc.com/support but since we don't currently carry maintenance I can't read it. Can anyone let me know what it says?
Thanks for the information.....
Intralink 3.3 Refresh License Issue from May 3rd 2011
PTC has identified a software issue affecting all Pro/INTRALINK 3.3 installations, starting May 3rd 2011.
Specifically, this time-based issue prevents Pro/INTRALINK clients from obtaining a license from the license server, returning the error: "Failed to take or refresh license". The issue does not impact Pro/INTRALINK release 3.4.
Necessary resources within PTC have been engaged to work on this issue, and an update will be posted shortly in this bulletin.
The problem is back again on 12th June.
Yes, we still use Intralink after all these years. Intralink and ProE do what I need to so we didnt upgrade because we had permanent licenses anyway. The data migration from Intralink to Windchill sucked so much we never got it complete and working.
What are my options for getting Intralink running again? Changing the client date back and forth does work but is a pain to do.
Any chance of a new DLL to reset the date problem another 6 years?