NSM 3.1 Agent Heartbeat

Question

Hello,
i'm testing a new install of NSM 3.1 on a new Windows 2008 R2 installation to see if we can migrate from 3.0.3 to 3.1
But as soon as i Authorize the (local) agent i get a "Warning: A heartbeat has not been received for more then 5 minutes."
i have put login on the agent en engine to debug but the only usefull info is from the agent log:
Successfully performed a heartbeat communication
Received a "ACK" HB response
Received an "Authorized" HB response, nStatus = 0.
there is noting in the engine log.
Hope you can help me,
Niels van de Haar

Answer 1

On 4/24/2013 6:26 AM, nvdhaar wrote:
>
> Hello,
>
> i'm testing a new install of NSM 3.1 on a new Windows 2008 R2
> installation to see if we can migrate from 3.0.3 to 3.1
>
> But as soon as i Authorize the (local) agent i get a "Warning: A
> heartbeat has not been received for more then 5 minutes."
>
> i have put login on the agent en engine to debug but the only usefull
> info is from the agent log:
>
> Successfully performed a heartbeat communication
> Received a "ACK" HB response
> Received an "Authorized" HB response, nStatus = 0.
>
>
> there is noting in the engine log.
>
> Hope you can help me,
>
> Niels van de Haar
>
>
Niels,
This is a cosmetic UI issue we recently discovered in NSM 3.1 (and in
Novell File Reporter 2.0.0 as well.) The Agent is actually heartbeating
just fine and will work without issue. However, when the Engine and
Agent are in timezones between UTC+1 and UTC+14, the UI incorrectly
calculates the time between heartbeats and displays this error.
A fix for this problem has already been implemented for forthcoming
releases of Storage Manager and File Reporter. Our apologies for the
confusion it creates!
- NFMS Support Team