License server communication error

[pankaj]

Hi all
Recently we upgraded our OS to Solaris9 from Solaris8. Since then we
are unable to check out the license of some of the features like
Silicon Ensemble or SignalScan. The error we are getting is
ERROR(LM -15) License sever communication error, try longer time out.
I did increased the timeout interval as recommended but it had no
effect on the error. Any solution to this problem

Thanks in advance
Pankaj

 

[David Cuthbert]

pankaj wrote:

Hi all
Recently we upgraded our OS to Solaris9 from Solaris8. Since then we
are unable to check out the license of some of the features like
Silicon Ensemble or SignalScan. The error we are getting is
ERROR(LM -15) License sever communication error, try longer time out.
I did increased the timeout interval as recommended but it had no
effect on the error. Any solution to this problem

Upgraded on the license server or the client?

The one bit that comes to mind in the latter case is:
1. You had your license server listed in /etc/hosts, and
2. It was erased/reset during the OS upgrade.

Make sure, of course, that the license server really is running and not
crashing or refusing to start. (You did just upgrade the OS and not the
hardware, right?)

When all else fails, running truss on the executable can be informative
(though it takes some patience to wade through the sheer amount of data
it provides).

Unfortunately, FlexLM is not known for producing the most informative
error messages.

Dave

 

[pankaj]

Hi
Thanks Dave for your answer.
We upgraded the OS on the client. The license server is fine as we are
able to check out the licenses for other features.
I will try using truss.
Any more advice.
Thanks again
Panakj
David Cuthbert wrote:

pankaj wrote:
Hi all
Recently we upgraded our OS to Solaris9 from Solaris8. Since then
we
are unable to check out the license of some of the features like
Silicon Ensemble or SignalScan. The error we are getting is
ERROR(LM -15) License sever communication error, try longer time
out.
I did increased the timeout interval as recommended but it had no
effect on the error. Any solution to this problem


Upgraded on the license server or the client?

The one bit that comes to mind in the latter case is:
1. You had your license server listed in /etc/hosts, and
2. It was erased/reset during the OS upgrade.

Make sure, of course, that the license server really is running and
not
crashing or refusing to start. (You did just upgrade the OS and not
the
hardware, right?)

When all else fails, running truss on the executable can be
informative
(though it takes some patience to wade through the sheer amount of
data
it provides).

Unfortunately, FlexLM is not known for producing the most informative

error messages.

Dave