Log in

View Full Version : flexLM/'system clock setback detected' problem


incredibledible
February 23rd, 2004, 20:27
Hello all.
I am having alot of troubles with this small, but annoying problem.

First off, I have been running a Pixar graphics program that uses flexlm as its license manager, with the license.dat that is as follows:

<deleted>


Earlier today, I installed a DIVX player that had a mandatory 'thermometer/temperature' app that measures temp of your cpu or sumthing like that. I used the divx player, and decided that i dont need it, so i uninstalled the DIVX and the thermometer thing from my system. Later loking at the time on the computer, it read, something like
12:30, february, 2028, or sumthing like that.

So, i adjusted the time/date (correctly)in the box to adjust it on windows 2000.

Now, when i try to run the Pixar program, it doesnt work, and in the LRM.LOG file this is what it says:


18:01:26 (lmgrd) Logfile switching to +lmgrd.log
18:01:26 (lmgrd) -----------------------------------------------
18:01:26 (lmgrd) Please Note:
18:01:26 (lmgrd)
18:01:26 (lmgrd) This log is intended for debug purposes only.
18:01:26 (lmgrd) There are many details in licensing policies
18:01:26 (lmgrd) that are not reported in the information logged
18:01:26 (lmgrd) here, so if you use this log file for any kind
18:01:26 (lmgrd) of usage reporting you will generally produce
18:01:26 (lmgrd) incorrect results.
18:01:26 (lmgrd)
18:01:26 (lmgrd) -----------------------------------------------
18:01:26 (lmgrd)
18:01:26 (lmgrd)
<snip>
18:01:27 (pixard) System clock setback detected
18:02:27 (pixard) System clock setback detected
18:03:27 (pixard) System clock setback detected
18:04:27 (pixard) System clock setback detected
18:05:27 (pixard) System clock setback detected
18:06:27 (pixard) System clock setback detected


So I gather that because i set the clock back, the system clock, or rather the licensing software sees that the system clock setback was detected.....

Therefore, I think therein lies the problem that I am having.

I do not have any experience or knowledge with cracking and license type issues , and was wondering what the possible solution could be.

Please let me know asap, as I cannot do anything until this problem is rectified.
(and mind you, this is very annoyinng)

Any solutions would be more than greatly apperciated,

Regards,
inCreD

incredibledible
February 23rd, 2004, 22:28
please tell me what the best thing to do would be, as I am up shit creek until i can correct this problem.
I am sorry if this question is a little to "LAME" for the viewers who are just too advanced and elitist, but for those who have genuine knowledge and can offer a suggestion and arent so stuck up, that would be more than greatly appreciated.

Regards,

inCreD

Kayaker
February 24th, 2004, 02:32
Howdy,

Somebody was having a bit of fun, but don't take it personally, and it doesn't stem from an elitist attitude. That said, if your question is aboveboard, it would seem that your first line of questioning should have been to the software company using the FlexLM license. You can try reinstalling the program with the original license, but once a "System clock setback" has been detected (and assumed to be a crack attempt), registry entries or files may be left behind that won't be wiped out by reinstalling.

If your question is not aboveboard and you haven't purchased a valid license, then don't try to pretend that you have. This was likely the assumption behind the picture attachment, as people try all kinds of tricks to get free cracks here. There was no need to post the entire FlexLM license file, especially inappropriate if it's yours, so I have deleted most of it except for part of the log file.

If you still want to try to solve the problem, you can start at Square one and learn to reverse yourself, beginning with learning the Windows API's used for Time and Date accesses. If you are willing to learn you will get help here, if not then you better contact Pixar...

Kayaker

peterg70
February 24th, 2004, 08:33
Hate to state the obvious but why not set the date forward back to 2028 and continue working.

incredibledible
February 24th, 2004, 12:32
hello again
thanks for the info
this app that i am using has been cracked long ago, and in no way an i trying to get a free one.
i am only trying to restore the once smoothly functioning cracked program.

thanks kayaker for this info, and i was wondering if you could direct me to where i should go for learning resources.
ie.what are the basics i need to learn
what direction (using small programs etc.) i should take to learn this myself.

thanks again,

inCreD

incredibledible
February 24th, 2004, 12:36
of yeah, kayaker, i mean where do i start...
with windows api....
first off
where do i find out what an api is.....

and so on from SQUARE ONE...

thanks again,

inCreD

JMI
February 24th, 2004, 15:51
There are significant recources linked at the bottom of these Forums. They would be a good place to start. You could also use the search function here and try various combination of words about "timelimits" and "clock change" and such. First try your imagination and some selfhelp, and then, if that doesn't get you started, describe what you have already tried and maybe someone will/can give you some more specific guidance.

Regards,

squidge
February 24th, 2004, 19:56
Square one would be to determine the Flexlm version number and search for information, SDK's, etc on that version. I see that there is leaked source code of the flexlm library on the net to download - maybe this will help you on your quest?

SiGiNT
April 5th, 2005, 23:36
Sorry for resurecting, this old thread, I found it last night searching for a solution to this problem, (while working on a time trial my machine crashed and I had to boot into the set-ahead date), bingo! one of my apps refused to run when the date was set back, the solution can easily be found by about 5 minutes worth of searching for flexlm+clock on google, - here's what I wanted to add - the fix is incredibly simple and easy to accomplish if you don't aggravate the situation by turning the clock forward to a date your app will run - this will increase your work to fix the problem, the longer you run at the wrong date the more work it will take.

SiGiNT