Skip to main content
L
LEONIDGUREVICH1-Visitor
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

Show previous replies
D
DanielReid12-Amethyst
12-Amethyst
May 3, 2011
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.


A
amedina1-Visitor
1-Visitor
May 3, 2011
gotta .dll that is working reply if you want it

A
amedina1-Visitor
1-Visitor
May 3, 2011
ahh too quick. this DLL only works if you roll back the time to before today


L
lylebeidler1-Visitor
1-Visitor
May 3, 2011
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>
A
amedina1-Visitor
1-Visitor
May 3, 2011
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

P
ptc-1699471-Visitor
1-Visitor
May 3, 2011
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
D
DanielReid12-Amethyst
12-Amethyst
May 3, 2011
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.


P
ptc-4861921-Visitor
1-Visitor
May 3, 2011

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.

T
TimMcGee1-Visitor
1-Visitor
May 3, 2011
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
D
DanielReid12-Amethyst
12-Amethyst
May 3, 2011
Watch for an update shortly after 2:30 Pacific time. They are making a
go/no-go decision then.


Show more replies
Terms & ConditionsCookie settingsAccessibility statement