We had a similar incident here. Our system people have been testing our Unix servers and systems to insure Y2K compatibility. One of the tests was to reset part of the system to year 2000 to simulate what happens next year, to actually test all software compatibility. All other software worked great except for the ANSYS license manager. The software has something that causes the manger to fail if the date has been changed, it will not let you change the date backwards. Our system people had to get in touch with our ASD to get the instructions on how to reset the license manager so ANSYS could be used again.
Don Shaffer, Mechanical Engineer Siemens Westinghouse Power Corp. Orlando, Florida
claus.preiser%sensoplan.com%SMTP%Exchange wrote:
> We just made one more combat experience with the Ansys license > manager.
> We are using following environment:
> Server: Intel based hardware, MS NT4.0 Service pack4, Ansys5.5.3 > Clients: Intel based hardware, MS NT4.0 Service pack4, Ansys5.5.3
> First everything was running well, one of the clients was busy with a > thermal transient analysis. This system crashed. After restart we > got an > error message ( see image client2.jpg) and the license manager on > the > server was down as well ( see image server.jpg).
> After reinstalling of NT and Ansys I recognized that the system > time on > the client showed year 2045 !?!?!, correcting this the problem was > solved.
> However, if a client has a system time over year 2000 or a different > time than the server , you can kill the > license manager on the server.