Thread Info
  • State Verified Answer
  • Locked Locked
  • Replies 5 replies
  • Subscribers 3 subscribers
  • Views 14027 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Clients are not updating in the enterprise console

MaxLaser

Since last week, i get the message in the Enterprise Console that our clients are not up2date. Last connection for about 120 clients was about 7:03 PM 29th March. The only client which is connected in SEC is the server itself.

Our reseller told us, that could happen when we have more clients in use that we have licensed. In the moment we have 100 licenses, and are 20 clients above. and yes, we will buy more ;).

Is this a license problem, like the reseller told us, or is it a techninally problem which can be solved otherwise?



This thread was automatically locked due to age.
Parents
  • 0

    Hello Max Laser,

    when we have more clients in use that we have licensed
    never heard of such a thing but who knows [:)]. Sounds more like something's stuck. You could check (and restart) the services, the Message Router, Agent, and Management Service. Or simply reboot the server especially if it has been running for a longer period.

    Christian 

  • 0 in reply to QC

    Hey Christian,


    we restarded the server a few times, restarded also the services before.

  • 0 in reply to MaxLaser

    Hello Max,

    then the apposite (but usually fruitless) question is: What happened or has been changed around this time? If I were to encounter something like this I'd asperse the networking group  [;)]

    Please check if there are any RMS connectivity issues. On an endpoint view the Network Communications Report. Additionally  telnet server 8192 (for server use the MRParentAddress(es) from mrinit.conf) - this should for at least one address return an IOR. You can parse the IOR here. If you get no response there's likely a firewall involved. Otherwise telnet host 8194 (using host or hostname from the parser's output. You should get a connection but no output, wait some 15 seconds and press enter and the connection should close. again, if this doesn't work it suggests that something is blocking the communication.

    Christian   

Reply
  • 0 in reply to MaxLaser

    Hello Max,

    then the apposite (but usually fruitless) question is: What happened or has been changed around this time? If I were to encounter something like this I'd asperse the networking group  [;)]

    Please check if there are any RMS connectivity issues. On an endpoint view the Network Communications Report. Additionally  telnet server 8192 (for server use the MRParentAddress(es) from mrinit.conf) - this should for at least one address return an IOR. You can parse the IOR here. If you get no response there's likely a firewall involved. Otherwise telnet host 8194 (using host or hostname from the parser's output. You should get a connection but no output, wait some 15 seconds and press enter and the connection should close. again, if this doesn't work it suggests that something is blocking the communication.

    Christian   

Children
No Data
Unfiltered HTML