Someone accelerated the clock on my PC to year 2007. Of course I had no idea, I started PDMS and I got an error, something about time not been synchronized.
I changed the time on my PC back to the correct time, however, now I get an expired license.
[QUOTE=juno]Someone accelerated the clock on my PC to year 2007. Of course I had no idea, I started PDMS and I got an error, something about time not been synchronized.
I changed the time on my PC back to the correct time, however, now I get an expired license.
Any suggestions would greatly appreciated.
Thank you in advance,
-Juno
You may have to call Aveva and get a new license key.
I used to be able to switch back the date and everything is cool, but have run into problems like you had the last few times.
We had this problem a couple of years ago. There are files on your C drive that have a date set later than the licence file expiry date, because of the clock change. Initially we cleaned the machine's C drives of the files and the problem was resolved, some of the files were in deep and mysterious places, however some machines still refused to work so we completely rebuilt them by cloning from an existing good machine. Of course this wiped the C drives, so back-up any data you need to keep.
Dont you just hate it when someone does that. We had a few users do it as they wanted to check their holiday dates for later in the year and didnt realise the consequences of applying the new date!! Doh.
Well, nothing wrong with people changing the clock time. . . as long as they can, however AVEVA needs to fix this problem. I don’t see it as a user problem I see it as a software problem.
So I guess to prevent something like this happening it’s a good idea to restrict users from having the ability to make time changes.
Hi, I know this comes late but the solution is:
- search all the files which have a date higher than the current one (do not forget hidden and system files!)
- change their date using a touch tool
This should fix it.
Please note that this is not an AVEVA issue but it comes from FLEXMAN!
We had this problem recently, we did every thing possible including serching for files with advanced date and deltting them withot success. Finally we had to format the system and re-install all needed. This solved our problem.
I hope this will help.
Abba
I had the same problem when I was testing small utility that uses system date. I changed the system date to date where the licence was no more valid. After changing it back, PDMS stop working. So I tried to find files with date greater than the end of the licence file. All files were located in System Prefetch directory (c:\win...\Prefetch\). After deleting those files, everything was back in normal and PDMS worked fine. One of the files was cached version of CMD.EXE (c:\windows\prefetch\CMD.EXE-xxxxxx.pf), my tip is that this can cause the problem since the cmd is used to start the PDMS.
and I search all files/folders older than "today" and change them date/time to "today". I'm using Total Commander, so it was nice and easy. I tested it twice on two PCs with that problem and it work.
Problem solved within few minutes, no need to reintall.
