Skip to main content
1-Visitor
May 3, 2011
Question

Ilink3.3-m22 can't start - "Failed to take or refresh license".

  • May 3, 2011
  • 24 replies
  • 8793 views

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?

24 replies

1-Visitor
May 3, 2011
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...


1-Visitor
May 3, 2011



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...


1-Visitor
May 3, 2011
Further research indicates it was 10:58pm and its 2233 days..



Will PTC provide an updated dll for an unsupported product?






1-Visitor
May 3, 2011

Sorry guys, forgot to post a reminder ...



From: http://portal.ptcuser.org/p/fo/st/thread=9009


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
software.



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.




Marc
--
Marc Mettes

16-Pearl
June 15, 2017

Its happened again. On Monday the 12 June 2017 it reached the 2233 day limitation.

Any Chance PTC will create a new patch?

1-Visitor
May 3, 2011
I hope, unfortunately we without support now and I can't open call.

It's new Patch-Timeout (03052011)



1-Visitor
May 3, 2011
Yep to all questions





If you roll client clock back Intralink starts...



and as Marc M's post states
1-Visitor
May 3, 2011
Opps.. copy and paste issue..



Dates and times are...


1-Visitor
May 3, 2011
We're experiencing the same issue with 3.3

If anyone on this thread knows the fix, could they kindly post step by step instructions as to how to resolve it?

Thanks,
Stefan
1-Visitor
May 3, 2011
Given all the responses this thread has gotten, this line makes me chuckle.



Marc wrote.

Granted it is unlikely that someone will be using Intralink 3.X
in 2011



--



Lyle Beidler
MGS Inc
178 Muddy Creek Church Rd
Denver PA 17517
717-336-7528
Fax 717-336-0514
<">mailto:-> -
<">http://www.mgsincorporated.com>
1-Visitor
May 3, 2011
yeah all my 40 users are down... just a few weeks from moving to intralink
3.4...... PTC you guys need to get your finger in that compiler enter
key!!!!


I bet they are having a party right now going "yey" we get some more
windchill orders. Meanwhile all of us get to wait and loose money and time
on our projects. And its not like you can blame a single person for not
upgrading since upgrading always hurts one way or another. We would not be
having this problem if PTC did not put that expiration date on the code in
the first place. Not only once but several times now if not just twice. I
bet there is something in the ULA that says you cannot do a class action on
PTC.