MICRESS Forum

Ok. That's a bit strange. Is your license working? Have you checked Micress again?

If its not working, can you try running lmtools as an administrator (right click lmtools.exe icon and choose 'Run as Administrator') and start the server again?

OK. This looks good. Can you open your log file and see what it says? (mymicress.log file). Lets see if the server start was successful.. If yes, go ahead and try using Micress again.

No problem Sai Li. You need not copy the license file. You can keep it anywhere and then give the correct path in the field 'Path to license file'. Also give a suitable path for log file, which will be useful in future for diagnosing any errors with the license server. Right now, these fields are ma...

Hi Sai Li,
No problem.

For Micress, you need to go for the lmtools (FlexLM) first. For this, please refer to Micress manual volume 1 from page 15 onwards... Let me know if you have any hiccups..

Best Wishes,
Deepu

Great. Things are clear now. But, before I proceed further, I would strongly recommend you to delete the image from the previous post (Image containing your Institute license information). This is to avoid misuse of you institute license, as this is a public forum. Next time, you can use the feature...

Ok. Technically, its not necessary to change the environment variable as long as you are mapping the correct details in etc\hosts files. To be on the safer side, you can change it to the IP address to avoid any possibility of human error here..

Ok. Is your license server windows based or Linux? Do you have a physical access to the machine on which the license server is running?

Deepu

Ok. It looks like the IP 166.111.38.15 is the IP of the machine you are currently using (or remotely accessing), which I believe is not your Micress license server. Right? If yes, can you find out what is the IP address of the machine where your micress license server is running? That IP address is ...

Ok. One question here. Is the IP 166.111.38.15 the IP address of the license server or the IP address of the client (the machine that you are remotely accessing...)

Ok. Don't worry. Now, we can go back to your micress simulation. Instead of typing 'verbose', can you just press the Enter key after the error comes?. Or else, type something and press enter. Through one of these steps, we can make micress to spit out some messages on the screen (diagnostic messages...