cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

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

Highlighted

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

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?

Tags (1)
25 REPLIES 25
Highlighted

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

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


Highlighted

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



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


Highlighted

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

Further research indicates it was 10:58pm and its 2233 days..



Will PTC provide an updated dll for an unsupported product?






Highlighted

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


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

Highlighted

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

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

Any Chance PTC will create a new patch?

Highlighted

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

I hope, unfortunately we without support now and I can't open call.

It's new Patch-Timeout (03052011)



Highlighted

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

Yep to all questions





If you roll client clock back Intralink starts...



and as Marc M's post states
Highlighted

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

Opps.. copy and paste issue..



Dates and times are...


Highlighted

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

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
Highlighted

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

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

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

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.



Highlighted

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

Yep. PACCAR is feeling this too, not for new development but for the
systems we use to build trucks that are stuck in limbo on Pro/I 3.3
until Windchill has the capability to replace the function of our tools
around that. I'd love to just be able to edit and re-compile that DLL.


Highlighted

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

gotta .dll that is working reply if you want it

Highlighted

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

ahh too quick. this DLL only works if you roll back the time to before today


Highlighted

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

I should have mentioned in my previous post that we, too, are still on
Intralink 3.x.



With that in mind, can anyone shed light on how widespread this issue is?
The subject line refers to 3.3 M22; will those of us on 3.4 have to worry
about this at some other date?



--



Lyle Beidler
MGS Inc
178 Muddy Creek Church Rd
Denver PA 17517
717-336-7528
Fax 717-336-0514
<">mailto:-> -
<">http://www.mgsincorporated.com>
Highlighted

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

I think its only intralink 3.3 M010, M020 and M022. 3.4 is probably going
to time out some other date 🙂 have you tried rolling back your clock? it
seems to work for some of our computers,, not all. We copied the
proilbase.dll file from the ones that worked and it made the others work..
We are still testing this out, have not rolled to all users.

regards

Highlighted

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

I rolled back the clock, launched Intralink, then put the clock back, per Jim's method. Seems to work OK. If you don't put the clock back to today, it will impact everything on your client machine (incl email).
Ptc's phone's are apparently very busy (they didn't even direct me to the web because it was 3.x). They actually asked if I was calling about this issue before I even explained why I was calling. Said they're working on a fix.

Stefan
Highlighted

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

Expect a notice at www.ptc.com/support fairly soon on status of a fix.



Yep, 3.4 is probably going to see this eventually, but not yet.


Highlighted

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

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


TS Bulletins


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.

Highlighted

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

This is what it says
TS Bulletins
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.


Please note my new phone number 440-240-0446

Tim McGee | CAD Adminstrator | Energy Systems
Emerson Network Power | 1510 Kansas Ave.| Lorain, Oh 44052
T 440.240.0446 | M 440.522.7261 | F 440.240.0618
www.emersonnetworkpower.com
Highlighted

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

Watch for an update shortly after 2:30 Pacific time. They are making a
go/no-go decision then.


Highlighted

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


TS Bulletins
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.
PTC has prepared a patch to correct this issue, which is available here:
Highlighted

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

Tested it and it works. I'll make no other evil remarks. I wonder if we'll
be on 3.3 in 5 years or if loosing a day from so many people is enough to
move us to 3.4.

regards,

Alfonso

Highlighted

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

I have problem with download the cure.

I see next note only - "You do not have permission to view this
directory or page using the credentials you supplied"

Send me please the new dll

TIA



Highlighted

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

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?

Cheers

Tarquin

Announcements